office-gobmx/sw/qa
Miklos Vajna d06de2e049 Related: tdf#162072 DOCX import: handle font family for characters
Open the bugdoc, the first paragraph is meant to be sans and the second
paragraph is meant to be serif, but both of them are serif.

The bugdoc uses the fonts 'IBM Plex Sans' and 'IBM Plex Serif', which is
not something we bundle, so the font fallback is expected, but the
fallback should have a matching font family (roman vs swiss).

Fix the problem by implementing support for <w:family w:val="..."> in
the DOCX import, which was just ignored previously.

Now the DOCX import result in on par with the ODT import result.

Change-Id: I321b9fc6f63126ca5ad61af57af8a5bc7456d5b4
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/170772
Tested-by: Jenkins
Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
2024-07-19 22:38:42 +02:00
..
api
complex/indeterminateState
core tdf#150621 Changed Korean word counting to use words 2024-07-17 15:45:41 +02:00
extras CppunitTest_sw_uiwriter3: avoid font fallback in testTdf133967 2024-07-19 14:37:57 +02:00
filter tdf#71749 Unit test for sw: WW8: don't loop on tables in footnotes 2024-07-18 01:11:12 +02:00
inc
python
uibase
uitest SW: random ID for new content controls 2024-07-19 21:26:28 +02:00
unit
unoapi
writerfilter Related: tdf#162072 DOCX import: handle font family for characters 2024-07-19 22:38:42 +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.