Created attachment 50155 [details] A file displaying the problem. The Unicode character U+202E Right-to-Left Override (RLO) should force all text following it to be displayed right-to-left, overriding the normal direction of the script. Instead, in Writer, Calc, Impress, and Draw, U+202E has no effect on the direction of text and, depending on the font, may display as a box instead of an invisible control character. Steps to Reproduce: 1) Open any LibreOffice program. 2) Enter the character U+202E (Unicode direct input varies by OS, but Ctrl+Shift+u,202e,return works on most Linux distros). 3) Type in any left-to-right script. 3a) Note that this bug does not appear if a right-to-left script has previously been typed on the same line. Actual behavior: Input appears as normal. U+202E may display as a box. Expected behavior: Characters should be displayed from right to left. Documented in: LibreOffice 3.3.2 (1:3.3.2-1ubuntu5 from the Ubuntu repository, x64) LibreOffice 3.3.3 (Fedora) OpenOffice 3.3 (Windows 7 SP1 x64, 32-bit program)
While switching the paragraph direction to RTL without using an RTL script also enables Right-to-Left Override, the font (by either method) is changed to the default CTL font.
I see the effect with "LibreOffice 3.4.2 - WIN7 Home Premium (64bit) German UI [OOO340m1 (Build:203)]" , also Master and OOo 3.4., but my knowledge is too poor for any conclusion
@Urmas: Please leave some information concerning your observations, OS, LibO version, reasons why you confirm that it's a bug, ...
Please, verify if in last version of LibreOffice still reproducible
Setting to INVALID, since no further feedback has been provided for over a year.
The issue is that RLO has no effect unless there are some RTL characters anywhere in the paragraph. There is no justification for this behavior.
I don't see a confirmation in the comments. Urmas if you've confirmed please set the bug to NEW - else moving this to UNCONFIRMED for independent confirmation. Thanks all.
That still happens in 4.4 master, at least on Windows.
** 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
Bug is still present on my system: Debian Linux Version: 5.2.1.2 Build ID: 1:5.2.1-2
** 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.4.1 or 5.3.6 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-20170929
This works for me, and from bug description I suspect it was the same underlying issue as bug 107204, so marking as duplicate. *** This bug has been marked as a duplicate of bug 107204 ***