Created attachment 186413 [details] Miriam CLM font When a document with localized font is transferred across LO with different UI language, fonts are not selected correctly. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9c7d3ce813c761b116232bc291e2737c59d383da CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Prerequisite: Install font "Miriam CLM" with localized names (attached, see also screenshot) Steps to reproduce: 1. Open LO Writer with English UI 2. Observe "Miriam CLM" font is present 3. Create and save document which uses "Miriam CLM" font (attached as English_UI_test.odt) 4. Close LO Writer 5. Open LO Writer with Hebrew UI, using flag --language=he 6. Observe the "מרים" font is present - same font with Hebrew name (see screenshot) 7. Load the document English_UI_test.odt 8. Observe that the font used in the document is displayed in UI as slanted "Miriam CLM", as if it were not found, and not with its Hebrew hame.
Created attachment 186414 [details] English UI - font name in English Screenshot of English UI with font name in English
Created attachment 186415 [details] Miriam font info, showing localized names
Created attachment 186416 [details] document which uses "Miriam CLM" font
Created attachment 186417 [details] Font listed with localized Hebrew name
Created attachment 186418 [details] Doument font is listed by English name and marked slanted, as if not present
This bug is a follow-up of recently fixed https://bugs.documentfoundation.org/show_bug.cgi?id=151722
Confirmed as described with: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 61b41646c5a93ca24f2c9f143cdb0da2c9258989 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: he-IL Calc: threaded Caolán, CCing you in following your work on bug 151722, in case you're interested.
Dear Maxim Iorsh, 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