https://bugs.documentfoundation.org/show_bug.cgi?id=164604
--- Comment #45 from HeartLetter <[email protected]> --- A note about substituting DejaVu Serif with Noto Sans: some other characters like "Downwards harpoon with barb rightwards", ↾ U+21BE, appear as 'tofu' in ODT as Noto promises not to happen. Substituting Liberation Serif with FreeSerif fixes this issue in ODT, and in the PDF it appears correctly. It is true what V Stuart said right above: <pre>"Using the font substitution tables may help but I would not trust it as it is too imprecise--you still will not know what font gets selected for Unicode that has no coverage in either the PS/CS source or the replacement font from the table. And while you may control the result in the LO app frame on display, when printing or exporting to PDF/EPUB, it is a whole different rendering path--the font substitution tables can't be trusted and won't match what is rendered to display."</pre> FreeSerif stands as the better substitution font for both DejaVu Serif and Liberation Serif. About what V Stuart said there: "This is a os/DE system controlled font fallback issue", I have no idea why that is the case. The Operating System and the Desktop Environment have no business messing with specialized software decisions. I have been trying in distributions based off Arch Linux and Ubuntu, albeit only in GNOME, not KDE or MATE, with the same result. Now about what he said right after that: "No, instead what you *still must do* is clear your Direct Formatting and structure your notation using the fonts directly as needed to supplement PS/CS to have any chance of reliable reproduction when printed or exported" ― I have no idea how this would solve the issue if the issue is caused by OS/DE behavior. All of the occurrences of misappearence of characters are devoid of Direct Formatting, and all the configurations of fonts are included in Paragraph Styles and Character Styles, which are used abundantly in the document. Adding Direct Formatting after configuring Font Substitution with {DejaVu ,Liberation }Serif -> FreeSerif does NOT make the issue to happen anyway. TODO: It still could be that the ODT possessing some Direct Formatting, or some amount of it, is actually by some mechanism causing the issue indirectly in those non-Direct Formatted lines. Test that when generous time is available. -- You are receiving this mail because: You are the assignee for the bug.
