One of the complaints I hear from people whom I suggest LibreOffice is, that when they open in LO an existing document written on another platform, the fonts look funny. I mainly get this complaint for people who open a document written on Windows and opened on Linux, with Hebrew, but I'm sure other people get this with other language and platform combinations. LibreOffice has a font substitution mechanism already; and it seems to apply "recessively", i.e. only perform a substitution if the font is actually missing. I therefore propose that LO include a default substitution table for some or all of the fonts used in Microsoft Office in different languages, (1) where LO bundles fonts that can serve as such substitutes. With my more specific motivating example being Hebrew, I suggest the following substitutions: David -> David CLM Arial -> Arial Unicode MS Times New Roman -> Liberation Serif Frank Ruehl -> Frank Ruehl CLM these are often used in MS Office on Windows for Hebrew text (see bug 113538). I'm sure others could be added for Mac OS. Similar substitutions would be relevant for other languages as well, I believe. Be reminded that the user can turn off substitution entirely with a few clicks or edit the table to his/her hearts' content.
we have this feature, see... officecfg/registry/data/org/openoffice/VCL.xcu if we search there for "liberationserif" there is an entry like this... <node oor:name="liberationserif" oor:op="replace"> <prop oor:name="SubstFonts"> <value>thorndaleamt;thorndale;timesnewroman;nimbusromanno9l;times;timesroman;newyork;timmons;lucidaserif;lucidabright;roman;nimbusromanno9;bookman;itcbookman;garamond;garamondmt;palatino</value> </prop> <prop oor:name="SubstFontsMS"> <value>Times New Roman</value> </prop> <prop oor:name="SubstFontsPS"> <value>Times</value> </prop> <prop oor:name="SubstFontsHTML"> <value>serif</value> </prop> <prop oor:name="FontWeight"> <value>Normal</value> </prop> <prop oor:name="FontWidth"> <value>Normal</value> </prop> <prop oor:name="FontType"> <value>Default,Standard,Normal,Serif</value> </prop> </node> In this example the SubstFontsMS entry is the fallback font name that we set in the MSOffice file format to tell MSOffice what font to use in place of Liberation Serif if it is not available, Times New Roman in this case. In the other direction, for timesnewroman <node oor:name="timesnewroman" oor:op="replace"> <prop oor:name="SubstFonts"> <value>thorndaleamt;thorndale;liberationserif;... </prop> ... </node> when not available LibreOffice will try the options listed under SubstFonts in order (though when fontconfig is available on a platform fontconfig is consulted instead) What we *don't* have in here is entries for two of the font pairs you mention, David/David CLM and Frank Ruehl/Frank Ruehl CLM. So, assuming the feature is working correctly, I think the best thing to try first is to add entries for those two missing font pairs to VCL.xcu
(In reply to Caolán McNamara from comment #1) > we have this feature, see... I did acknowledge that. But like you said, LO currently only has substitutions for fonts it uses by default. > So, assuming the feature is working correctly. It is > I think the best thing to try first is to add entries for those two missing font pairs to VCL.xcu I've used the substitutions dialog to add the specific substitutions for Hebrew, and they work fine. Please add them by default (and perhaps also substitutions for MS-Word defaults in other languages).
Dear Eyal Rozenberg, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Nothing has changed for LO 6.3 - or 6.4 AFAICT.
Why am I getting this automated close-threat twice? Fonts are still not added to version: Version: 6.3.2.2 Build ID: 1:6.3.2-1 CPU threads: 4; OS: Linux 5.2; UI render: default; VCL: gtk3; Locale: he-IL (en_IL); UI-Language: en-US as far as I can tell.
Dear Eyal Rozenberg, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I don't know that this has changed, as of 7.2
Liberation Serif is not substituted for Times New Roman. David CLM is not substituted for David Frank Ruehl CLM is not substituted for Frank Ruehl ... with: Version: 7.2.0.1 / LibreOffice Community Build ID: 32efc3b7f3a71cfa6a7fa3f6c208333df48656cc CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-US (en_IL); UI: en-US
There is a bug for this and David and Frank, for which this one was confirmed, may be added there, explaining the replacement and font licences. *** This bug has been marked as a duplicate of bug 64509 ***
Timur, stop closing people's bugs - especially NEW ones - in non-trivial cases without discussing it with them first. To the point: I will bring this up on bug 64509. If the discussion there results in consensus about adding the substitutions here, then we could possibly close this bug as a dupe. For now, the bugs are related.
This should not be difficult, since it's just adding some table entries. As for the discussion on bug 64509 - it did not progress to an adoption of the suggestions here.