Hello, I have .rtf files which contains RTL text with brackets and colons. They were created using TextEdit, and now I want to save them as .odt, but they are imported incorrectly. -In the original file, each word has colons and two spaces between them (space, colon, space), but when imported it becomes (colon, space, space). -Brackets do not follow RTL direction, they become LTR instead. -Brackets between RTL characters has also messed up formatting and rendering issues. I'll now attach .pdf, .rtf, and .odt versions, also the font itself. Note: I am using OS X, so CoreText imports the RTL text correctly, but not the colon and the brackets (or LibreOffice). I have no idea how it will look on Linux or Windows. Also the .odt file I am attaching is not touched after importing, just embedded the font. Writing direction of all text needs to be changed to RTL to get the formatting like in .PDF file.
Created attachment 83388 [details] ODT file with incorrect formatting
Created attachment 83389 [details] Original .RTF file
Created attachment 83390 [details] .PDF file with correct formatting
Created attachment 83391 [details] Old Turkic font file
Please see line 3 for brackets.
Further testing: Saved the .rtf file as .odt in TextEdit, then opened it with LibreOffice, the same formatting errors. Opened the same file in TextEdit, no formatting errors.
Created attachment 85070 [details] screenshot The original RTF looks quite ugly on Version: 4.1.0.4 and Version: 4.2.0.0.alpha0+ Build ID: c41920416c22bfccf7fdeeefcd69baf6eadedaa3 Import all text as black squares, with a white circle in it and a 1 in that white circle. Doesn't look correctly I guess :)? Kind regards, Joren
@Joren, Since .rtf files do not allow font embedding, you'll have to install the attached font file. But it does not matter, the issue is, there should be one space before and after the colon, in this case colon is imported right next to the word; please see the attached .pdf file.
(In reply to comment #8) > @Joren, > > Since .rtf files do not allow font embedding, you'll have to install the > attached font file. Oh I'm sorry. Didn't read/saw that part :) > But it does not matter, the issue is, there should be > one space before and after the colon, in this case colon is imported right > next to the word; please see the attached .pdf file. With the font installed, I can reproduce this behavior using Mac OSX 10.8.4 with LibreOffice Version: 4.2.0.0.alpha0+ Build ID: c41920416c22bfccf7fdeeefcd69baf6eadedaa3 Kind regards Joren :)
@Joren, Thank you very much for confirming. :)
** 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-04-18
Installed font, rtf still messed up. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: 80ec99db4325a439a8a3f1d420d0a80f8bf9c439 TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-06-16_00:00:20 Locale: fi-FI (fi_FI)
** 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
Confirmed with LibreOffice 5.4.1.
(In reply to Emir Sarı (away) from comment #0) > -In the original file, each word has colons and two spaces between them > (space, colon, space), but when imported it becomes (colon, space, space). works for me on linux. > -Brackets do not follow RTL direction, they become LTR instead. > > -Brackets between RTL characters has also messed up formatting and rendering > issues. works for me on linux. The only problem i see now is that it incorrectly imports the font table (bug 1130840). Steve, Alex, Telesto: Can you guys test if this is fine on Mac?
(In reply to Yousuf Philips (jay) from comment #15) > The only problem i see now is that it incorrectly imports the font table > (bug 1130840). This is actually bug 113084.
So, I added Orkun font to my OSX Font book manager, but the font doesn't show up in the list of fonts recognized by LO, which means that the RTF remains a series of illegible squares... Version: 6.0.0.0.alpha0+ Build ID: 643e9001bff137b6e5a8784d9e1f25a51e0d1644 CPU threads: 4; OS: Mac OS X 10.13; UI render: default; Locale: fr-FR (fr_FR.UTF-8); Calc: group
Oh FFS, after a repeated restart of LO master, I can now see the font in LO and it appears to even display the RTF file correctly...but I am not an expert by any means as to how it is supposed to look. Enclosing screenshot for comparison.
Created attachment 136954 [details] Screenshot from own LO master build 20171013
So with confirmation that its fine on Mac, we can close this.