Font name combobox shows wrong font for fields when paragraph directionality set to RTL. Steps to reproduce: 1) Open Writer and insert some field (like page number). 2) Make sure that the paragraph directionality set to RTL. 3) As you can see, the font that used to display the field is not the same font as displayed in the font combobox. If you'll switch to LTR, you'll see that the field displayed with the right font, but switching back to RTL reverts that. Extra steps: 4) Select the field and try to change the font name. 5) As you can see, the font combobox shows the new font name, while the field itself still displayed with another font. 6) If you change the directionality of the field to LTR, you'll see the font change, but if you switch back to RTL you won't. Workaround: Open Character dialog (Format->Character...) and set 'CTL Font'. It's a bug, since even if a field should be treated as CTL text when directionality = RTL, the font combobox should expose the CTL font as well. Affected Versions: Reproducible with OOo 3.3 and with all LO versions since then, including master ( 4.2.0.0.alpha0+ Build ID: d6b4644da2c74500aa5ddfe69c36fc1f987bce0d TinderBox: Win-x86@6-debug, Branch:master, Time: 2013-08-31_22:06:59).
There's a easier way to explain the problem - on fields in RTL paragraphs, the font box show the LTR font instead of the RTL font. The fields' font change according to the paragraph directionality.
Created attachment 115814 [details] Faulty font name display
Comment on attachment 115814 [details] Faulty font name display This may be a related issue. In LO 4.3.7 the 'Free 3 of 9' barcode font appears correctly in the font selection list. In LO 4.4.3 the same font appears with the name 'New' as the attached screen-shot shows. This is within a standard Western LTR paragraph I hope that this helps. Best wishes John
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Works for me at: Version: 5.4.2.2.0+ Build ID: 1:5.4.2-3~bpo9+1 CPU threads: 8; OS: Linux 4.9; UI render: default; VCL: gtk2; Locale: en-US (en_US.utf8); Calc: group OS: Debian 64bit Stretch (Debian 9.2, with some backported packages)
With LO 5.3.12 on Lubuntu 17.04, I am: * not seeing bug described in item 3 of the instructions * seeing the problem in item 6 * Am seeing the problem described in item 5 - but am also seeing it in LTR So reopening for now, but I think this should be unpacked into multiple bugs, the last of which not even
(In reply to Eyal Rozenberg from comment #6) > With LO 5.3.12 on Lubuntu 17.04, I am: > > * not seeing bug described in item 3 of the instructions > * seeing the problem in item 6 > * Am seeing the problem described in item 5 - but am also seeing it in LTR > > So reopening for now, but I think this should be unpacked into multiple > bugs, the last of which not even It seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
So in master in a RTL paragraph with RTL text, it will show Liberation Serif when the cursor is after the field character, though the field is not rendered in that font, so this is a problem. While if the only thing in the RTL paragraph was the field, then it will show Liberation Serif when the cursor is before or after it, though the field is rendered with the CTL font. Version: 6.0.0.0.alpha1+ Build ID: 6070dec9ca9a15587a2aece81f9ae1ab5ac0f8c4 CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group
Bug still manifests with: Version: 6.1.1.2 Build ID: 5d19a1bfa650b796764388cd8b33a5af1f5baa1b CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; Locale: en-GB (en_GB.UTF-8); Calc: group threaded
Dear Maxim Monastirsky, 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
Re Comment 3. Bug no longer found in :- Version: 6.2.6.2 Build ID: 20(Build:2) (openSUSE repositories) Thanks John