office-gobmx/sw/qa
Miklos Vajna 0f165b7f2f tdf#161708 sw content controls: handle font color when exporting to PDF form
Export the bugdoc to PDF, the orange "date" lost its font color.

This went wrong in commit 82d90529dc (sw
content controls, rich text: add initial PDF export, 2022-09-12), we
export the content control as a PDF form widget by default since then.
Various properties like checkbox status and dropdown items were handled
already, but not text color.

Fix the problem by mapping the SwFont color to the widget descriptor
color, this fixes the color of the already filled in content of the
widget.

Note that given this is a property of the form widget, the color is
correctly applied also to strings filled in via PDF readers, interacting
with the form.

Change-Id: Id3e8611e415c0d571afe1cd14561c97b8a910ce9
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/169317
Tested-by: Jenkins
Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
2024-06-21 10:23:33 +02:00
..
api loplugin:ostr in sw/qa/api 2024-05-21 15:39:35 +02:00
complex/indeterminateState
core tdf#161708 sw content controls: handle font color when exporting to PDF form 2024-06-21 10:23:33 +02:00
extras rtf: Don't export changes author/date when in privacy mode 2024-06-20 09:22:30 +02:00
filter loplugin:ostr in various 2024-06-18 13:16:23 +02:00
inc loplugin:ostr in sw/qa 2024-06-13 19:56:40 +02:00
python
uibase loplugin:ostr in sw/qa 2024-06-13 19:56:40 +02:00
uitest tdf#145972 sw image dialog: fix bad rel width w/ pt units and kept aspect ratio 2024-05-24 13:58:07 +02:00
unit loplugin:ostr in sw/qa 2024-06-13 19:56:40 +02:00
unoapi
writerfilter CppunitTest_sw_writerfilter_ooxml: turn on set_non_application_font_use 2024-06-20 19:40:47 +02:00
README

You can find different types of Writer tests here, the following directories
are available:

- core:
  - filters-test: loads different file types (see SwFiltersTest::testCVEs() for
    the list of supported filter types), and only makes sure Writer does not
    crash. To add new tests, you just need to drop in the test files to the
    relevant directory, no code change is necessary.
  - uwriter: this test has access to private Writer symbols, add new tests here
    if you need that.
- extras:
  - see its own README -- executes import and export filters and asserts the
    UNO model to verify the resulting document is the expected one.
  - also, any new C++ test that links to libsw (but does not need access to
    private Writer symbols) should go in this directory, whether using the UNO
    API or the internal one.
- complex: JUnit-based tests using the UNO API
- unoapi: JUnit-based test trying to get/set every UNO property, etc.