steps: 1. open impress with an RTL locale enabled 2. right click on the title slide placeholder textboxes and select paragraph 3. in alignment tab, notice that text direction is set to LTR rather than RTL 4. add a new slide and notice that the text direction of the content textbox is also LTR 5. switch to 'Titl, Content' layout 6. notice that bullet point is on the left side when it should be on the right This is a regression as it worked fine in 5.2.7. Version: 6.0.0.0.beta1 Build ID: 97471ab4eb4db4c487195658631696bb3238656c CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2; Locale: ar-SA (en_US.UTF-8); Calc: group threaded
Regression introduced by: author Khaled Hosny <khaledhosny@eglug.org> 2016-08-26 15:19:26 +0200 committer Khaled Hosny <khaledhosny@eglug.org> 2016-08-30 17:22:41 +0000 commit cf425acfd4a5ff7c660523601964d45cbad74b53 (patch) tree 80c4ff111dd350d0b5d2be9aa4eeb2b73c1f46ec parent 3e289cf10b36f423ae6626296d739291850aa53b (diff) tdf#56403: Text is right aligned in RTL locales Draw/Impress is setting writing mode to RTL (which in turn sets text alignment to right) if the current locale is RTL one. This does not make sense at all since it means document prepared on a LTR locale and contains LTR text will appear right aligned on RTL locales. It would have slightly more sense if SetDefaultWritingMode() actually just set a default (for e.g. new documents), but that is not the case here as it affects all documents. This was introduced in 2c32696a04bc195c8ce61a0df6dcafb8c0c49fe0 with a branch merge and no further explanation. Bisected with: bibisect-linux-64-5.3 Adding Cc: to Khaled Hosny
Well the old behavior was certainly buggy, what needs to be done now is this: > It would have slightly more sense if SetDefaultWritingMode() actually > just set a default (for e.g. new documents), but that is not the case > here as it affects all documents. No idea how to do that, though. Personally I like how text direction works in Google Docs; if you start writing in Arabic then the paragraph direction and alignment are set to RTL and right, respectively, and vice versa. This makes it locale-independent and sensitive to the actual content being written (i.e. just because I use an Arabic locale does not mean every single document I wright is RTL, and the reverse is also true).
Hi, Maybe code removed in 2c32696a04bc195c8ce61a0df6dcafb8c0c49fe0 can be moved to SdDrawDocument::NewOrLoadCompleted in drawdoc.cxx, so that only new document is affected. It might be an easyhack.
(In reply to Mark Hung from comment #3) > Hi, > > Maybe code removed in 2c32696a04bc195c8ce61a0df6dcafb8c0c49fe0 > can be moved to SdDrawDocument::NewOrLoadCompleted in drawdoc.cxx, so that > only new document is affected. It might be an easyhack. Ignore me in comment #3 - it can't differ load from new despite its name.
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 Yousuf Philips (jay) (retired), 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
Dear Yousuf Philips (jay) (retired), 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://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
Dear Yousuf Philips (jay) (retired), 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