This is an interoperability issue. OOo writer seems to store and read text alignment not according to spec. The fo:text-align tag gets the value 'end' for text that has a visual alignment right and a text progression (style:writing-mode) of right-to-left. If you look at the spec; http://www.w3.org/TR/xsl/#text-align then 'end' is specified as; «Specifies that the content is to be aligned on the end-edge in the inline-progression-direction.» This means that for LTR paragraphs end equals right and for RTL paragraphs end equals the visual alignment of left. Yet OOo seems to equate 'end' with 'right' unconditionally. Test documents and related materials can be found in the koffice bugtracker; http://bugs.kde.org/207915 This is a critical issue preventing adoption of LibreOffice at some labs at my former university. The original OOo bug is here: http://openoffice.org/bugzilla/show_bug.cgi?id=105270 Now that LibreOffice is becoming well-known one of the labs contacted me to see if this issue is resolved. Please, people are trying to flee MSO to LibreOffice but this issue is preventing users of RTL languages from adopting the software as it's biggest selling point (interoperability) is broken.
It seems that od started to implement this in CWS textalignment01.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Yes, still valid, and a very critical interoperability issue. Switching to NEW, and increasing the Importance as the whole premise of LibreOffice is interoperability and standards compliance. What is the point of having yet another proprietary office suite?
i agree that this is a problem. as fixing this requires quite a bit of effort, ideally we'd want to use the significant work that has already been done by od in OOo CWS textalignment01. unfortunately that work is not integrated at ApacheOO yet, and is AFAIK only available under LGPLv3 license; we'd really like to be able to license the whole of LO under MPL/LGPLv3+, so it would need integrating and re-licensing at ApacheOO first, then we could merge it from there.
Hallo zusammen, entschuldigt bitte, dass ich in deutsch schreibe, aber ich kann leider kein englisch. Ich arbeite seit den MS-Dos Anfaengen mit StarOffice, nun LibreOffice. In meiner LibreOffice-Version 3.6.1.2 (Build ID: e29a214) unter Windows 7Pro passiert folgendes: Die Datei (Writer) umfasst ca. 200 KB, ca. 150 Seiten, viele Abbildungen (Verknuepft) und die Verzeichnisse Inhalt, Literatur, Index. Immer wenn ich die Datei speicher, stuerzt LibreOffice ab. Nach der automatischen Wiederherstellung ist haeufig der letzte Stand nicht wiederhergestellt. Es ich sehr aergerlich, mit einem solchen Fehler zu leben. Habe schon ein Globaldokument erzeugt, in der Hoffnung auf Besserung. Leider ohne Erfolg! Leider kann ich noch nicht auf die Version 4 umsteigen, da ich den Dudenkorrektor eingebunden habe. Gibt es eventuell eine Loesung? Lieben Gruß aus dem sonnigen Emden/ Deutschland Werner Bruns
(In reply to comment #5) > entschuldigt bitte, dass ich in deutsch schreibe, aber ich kann leider kein > englisch. Dein Problem ist etwas komplett anderes als das Thema dieses Bugs hier, bitte keine Bugs kapern und speziell keine Felder umsetzen. Erstelle stattdessen einen neuen Bug oder besser bitte jemanden aus der deutschsprachigen Gemeinschaft einen neuen Bug auf Englisch zu erstellen. Siehe http://de.libreoffice.org/hilfe-kontakt/mailing-listen/ Mailingliste users@de.libreoffice.org [Commenter hijacked this bug to write about something completely unrelated]
(This is an automated message.) LibreOffice development currently prioritizes bugs with the so called MAB (most annoying bugs) -- as this bug has not run through that process (including writing a short rationale for this bug being a candidate and other who are watching the tracker bug silently approving that rationale etc.) its priority is set to high. Note this is effectively no change in the urgency assigned to this bug, as we are currently not making a difference between high and highest and severity is untouched. You can find out more about MABs and how the process works by contacting libreoffice qa on irc: http://webchat.freenode.net/?channels=libreoffice-qa The QA wiki page also gives you hints on how to get in contact with the team (if IRC fails you, your next best choice is the mailing list): https://wiki.documentfoundation.org/QA
Restricted my LibreOffice hacking area
** 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 (4.4.2 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
Still a big issue with 4.4.2.2 Arch Linux build-1.
Related OOo link rotted when OOo bugtracker was moved. Here is the link on archive.org: https://web.archive.org/web/20110301055910/http://openoffice.org/bugzilla/show_bug.cgi?id=105270
Users confirm that the issue is not resolved in the latest LibreOffice release, 4.4 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
Still an issue in 5.2.2.2.0 (Arch Linux x86-64).
** 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 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
Any plan to fix this in ODF 1.3?
Isn't the bug here really just the fact that LO fails to distinguish between Start/End and Left/Right? These are missing from the UI as well. I'm pretty sure there's a separate bug about that. At the very least it should be related, if not an outright dupe. I'll also say that while this bug is reasonably easy to ignore by casual RTL users, in some scenarios - e.g. involving automatic processing of documents in which directions are changed, or file format is converted - this can be super-problematic.
Dear Dotan Cohen, 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
(In reply to Eyal Rozenberg from comment #17) > Isn't the bug here really just the fact that LO fails to distinguish between > Start/End and Left/Right? So, yes, but no. There is now a separate bug about properly supporting Start and End in addition to Left and Right: bug 131192. But this really needs to be fixed! Our output files for RTL languagues are broken now already for 14 years :-O
Does this occur with all other modules too, or is it Writer-specific?