Created attachment 61942 [details] Word document demonstrating import issues Problem description: When RTL text mixed with numbers rotated by 90 or 270 degrees it is not displayed correctly. Steps to reproduce: 1. Import MS Word document with table containing hebrew text mixed with numbers rotated 90 or 270 degrees. Or 2. Try to create such text in LO writer (inside or outside table) using Format/Character/Position/Rotation & scaling Current behavior: Various problems: rotated hebrew text is displayed as boxes or as wrong characters, sometimes only text is rotated, but numbers are not. Expected behavior: Display rotated text correctly. Platform (if different from the browser): Tried on windows & linux. On windows with LO 3.5.3, 3.5.4 RC1 and daily build (version 3.6.0alpha0+ (Build ID: 8b1d29b) Browser: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120513 Firefox/14.0a2
Confirmed with LOdev 3.6 (master - 18-May-2012 02h44 x86@6-fast; Build ID: 8b1d29b), LibO 3.4.5 and LibO 3.3.4 under Windows Vista 64 / Windows XP.
Additional (not related) problem I discovered: see Bug 50207
Created attachment 102854 [details] PDF from MS Word 2007 I add a pdf exported from MS Word 2007 as a reference representation. In LibreOffice 4.2.5 and 4.3.0 on Debian x86_64 and Windows 7 bottom box is invisible.
** 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.1 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-07-18
Reproducible with LibreOffice 4.4.5 and 5.0.0 on Debian Jessie.
** 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 happens in: 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) Also, export to PDF does not faithfully reproduce the mess being seen. I am attaching both screenshot and PDF export.
Created attachment 137433 [details] What is being displayed by Writer All text is at least enclosed in the boxes.
Created attachment 137434 [details] File as exported to PDF Vertical text is now outside of the two vertical boxes at top right.
I don’t see anything RTL specific here, replacing the Hebrew text with English one shows the same issue.
It's (In reply to Khaled Hosny from comment #10) > I don’t see anything RTL specific here, replacing the Hebrew text with > English one shows the same issue. Those are two sentences; the second is basically valid, the first isn't. If I replace טארק with trak, the Latin letters appear in the wrong order also: I see kart, not trak, just like in Hebrew we see טארק while in fact what's typed in is קראט (the letters follow QWERTY on the keyboard, sort of). So, this is an RTL issue, but it's not Hebrew-specific. And actually it's multiple issues: 1. Letter ordering reversed 2. Typing enter can make you go up rather than down a line w.r.t. how the letters are facing (i.e. you type Enter, type some text, and you've typed the _previous_ line's content. A weird experience). 3. Mis-rendering: Typing or deleting some of the text occasionaly keeps a part of the previously-rendered text still painted while it no longer exists, supposedly. 4. The red triangle. You see it, right? I'm not imagining things... where does that come from?
(In reply to Eyal Rozenberg from comment #11) > It's (In reply to Khaled Hosny from comment #10) > > I don’t see anything RTL specific here, replacing the Hebrew text with > > English one shows the same issue. > > Those are two sentences; the second is basically valid, the first isn't. If > I replace טארק with trak, the Latin letters appear in the wrong order also: > I see kart, not trak, just like in Hebrew we see טארק while in fact what's > typed in is קראט (the letters follow QWERTY on the keyboard, sort of). > > So, this is an RTL issue, but it's not Hebrew-specific. And actually it's > multiple issues: > > 1. Letter ordering reversed > 2. Typing enter can make you go up rather than down a line w.r.t. how the > letters are facing (i.e. you type Enter, type some text, and you've typed > the _previous_ line's content. A weird experience). > 3. Mis-rendering: Typing or deleting some of the text occasionaly keeps a > part of the previously-rendered text still painted while it no longer > exists, supposedly. > 4. The red triangle. You see it, right? I'm not imagining things... where > does that come from? Then each of these issues should be reported as a separate bug, right now there are several issues in this report that might be completely unrelated.
** 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
Dear Pavel R, 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 Pavel R, 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