Description: In this example, I created a document with a few Arabic-script characters (U+08A2, U+08A3 & U+08A4), which were quite recently added to Unicode for various Arabic-script African languages such as Fulfulde. The font I had used in the rest of the document was DejaVu Sans, so I used that font setting even for these characters. In reality, these glyphs are not found in DejaVu Sans but had to be substituted from another font, in my case Scheherazade (from fonts-sil-scheherazade, available through packages.sil.org). After rotating the letters by 90 degrees, everything looked fine on the screen but when I created a PDF, everything was displaced about one inch upwards and one inch to the left. See the attached screenshot, where everything looks fine, and the PDF where all the letters are displaced. If I change the font setting for this text to Scheherazade, everything looks fine even in a generated PDF. So apparently LibreOffice gets confused by the different font metrics of the two fonts, the one selected by the user and the one used as the real source for the glyphs. This bug was first reported on Launchpad for LO 5.4.6.2 on Ubuntu 17.10 at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1774244 . After my initial report, I have upgraded to LO 6.0.3.2 and can still reproduce the problem. Another user on Launchpad confirmed the bug on LO 6.0.3.2 and 6.1.0.3 on Ubuntu 18.04, as well. Steps to Reproduce: 1. In a new Writer document, type Arabic characters that are not present in the default font (in my example "ࢢࢣࢤ"). 2. Select the text and rotate it by 90 degrees through the Font properties dialog. 3. Generate a PDF. Actual Results: In the generated PDF, the text is displaced one inch to the left and one inch upwards. In Writer everything looks fine. Expected Results: The generated PDF should look the same as the document view in Writer. Reproducible: Always User Profile Reset: No Additional Info: Version: 6.0.3.2 Build ID: 1:6.0.3-0ubuntu1 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); Calc: group
Created attachment 144267 [details] PDF with displaced Arabic text
Created attachment 144268 [details] Screenshot of Writer document view
Created attachment 144269 [details] ODT document used to create the screenshot and the PDF
Repro. Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: 033a68c49fe2b8aa397832d92d400eb0259ea809 CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; Locale: fi-FI (fi_FI.UTF-8); Calc: threaded Built on September 5th 2018 Arch Linux 64-bit LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
Dear vaaydayaasra, 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
Still reproducible on: Version: 6.3.2.2 Build ID: libreoffice-6.3.2.2-snap1 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded
Dear vaaydayaasra, 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
This particular problem seems to have been resolved on LO 7.3.0.3 on Windows 10. Rotating these and other Arabic-script characters does not work as expected (sometimes the text won't rotate at all or if it does, the letters are in reversed order) but these seem to be separate issues. Version: 7.3.0.3 (x64) / LibreOffice Community Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL
Sorry, I take back my word. It's still the same issue in RTL paragraphs on LO 7.3.0.3. Writing my previous comment, I had only tested LTR paragraphs, which had other issues. RTL paragraphs still displace the text one inch to the left and up.
FWIW, this seems to be related to font fallback. If the selected font supports Arabic, the text is exported correctly.
*** Bug 124713 has been marked as a duplicate of this bug. ***
Bug 124713 has an example not involving Arabic text at all. It seems to depend entirely on the fact that a fallback font is used or not.
Still repro on: Version: 7.6.6.3 (X86_64) / LibreOffice Community Build ID: 60(Build:3) CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: fi-FI Ubuntu package version: 4:7.6.6-0ubuntu0.23.10.1 Calc: threaded