Description: I'm using Persian language and when trying to export my `odt` file into `PDF` it goes successful but some characters goes wrong way. Steps to Reproduce: 1.making an `odt` file using Persian language 2.exporting to PDF 3.opening PDF file Actual Results: wrong characters for some text not all of them but it happens for every text I export to PDF Expected Results: It should have done it without any problem just like Microsoft Office 2010 above. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36
Created attachment 137379 [details] it is in Persian and some characters are wrong but in odt file all are OK.
Could you please also upload the ODT file, and a screenshot of the PDF where some of the incorrect characters are circled for reference? Change back status to UNCONFIRMED after providing the files.
Created attachment 137478 [details] OTD and Screenshot of PDF file
(In reply to Nima Dolatabadi from comment #3) > Created attachment 137478 [details] > OTD and Screenshot of PDF file I just made the files you needed as a compressed file in .zip format. regards
I downloaded B Nazanin font, and what I noticed is that it looks different (thicker) than the font in the PDF in the attachment. Could it be some kind of font subtsitution issue?
Confirmed in master and 5.4 daily and is a regression as doesnt happen in 5.3.7. Version: 6.0.0.0.alpha1+ Build ID: 4058d85963e371be657f531d8f30e31381a9ccab CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group Version: 5.4.4.0.0+ Build ID: 76c54edc8ee972c63da8ed1f5d6ab75ea552da46 CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:libreoffice-5-4, Time: 2017-11-04_11:30:43 Locale: en-US (en_US.UTF-8); Calc: group
Created attachment 137563 [details] pdfs of 5.3, 5.4, and master
Created attachment 137564 [details] 5.3 vs 5.4
(In reply to Yousuf Philips (jay) from comment #8) > Created attachment 137564 [details] > 5.3 vs 5.4 now what is the solution to this problem? do I need to downgrade my LibreOffice? if "yes", then How to do it? best regards
(In reply to Aron Budea from comment #5) > I downloaded B Nazanin font, and what I noticed is that it looks different > (thicker) than the font in the PDF in the attachment. Could it be some kind > of font subtsitution issue? the answer is "no". because I have the right font to use. although I used all kinds of BNazanin font and they did not help. the other guy called Yusuf just found that the problem does not exist in lower versions. regards
(In reply to Nima Dolatabadi from comment #9) > now what is the solution to this problem? do I need to downgrade my > LibreOffice? if "yes", then How to do it? > best regards Presently you can downgrade to 5.3 from the download page[1] of the website if you require an immediate fix until the situation is investigated more and resolved. [1] http://www.libreoffice.org/download/
Regression introduced by 9eb4b14ffa57cd7bbdf0fc43096f5f1e65c8e388 which is the same as in bug 113428 *** This bug has been marked as a duplicate of bug 113428 ***
After upgrading to 5.4.3.2, the problem still exist and did not solved. My problem still occures, And why the topic was changed to "resolved" though the problem still exist?
It was marked as duplicate of another bug report, bug 113428. Please monitor that one for details. Additionally, if an issue is set to RESOLVED FIXED or VERIFIED FIXED (as you can see in the other ticket), it means the bug is fixed in the development version. However, important bug fixes are backported into current release versions, and are released with the next update once backporting is done. The Whiteboard field has "target:X.Y.Z" entries to show which version will contain the commit, in this case the fix will be part of the 5.4.4 update. *** This bug has been marked as a duplicate of bug 113428 ***