Description: When i open a pdf file that contains Persian text, the word characters are reverse. for example the "Word" shows "droW". کلمه shows هملک in all LibreOffice programs. this problem there is in many PDF programs, but the "Foxit" programs or "Wondershare PDFElement" program there is not. Please you fix it too. Thanks. Actual Results: When i open a pdf file that contains Persian text, the word characters are reverse. Expected Results: Show words of Persian text true. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Hi Saad, Would you be so kind to provide an .odt persian file sample and its PDF transfer? Thank you very much.
Created attachment 140109 [details] Contains .odt and .pdf files
Thank you Saad. I didn't reproduce with LO 6.0.1.1 (x64) Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6 Threads CPU : 2; OS : Windows 6.1; UI Render : par défaut; Locale : fr-FR (fr_FR); Calc: CL Lets see if somebody else find it.
This seems to have begun at the below commit. Adding Cc: to Thorsten Behrens ; Could you possibly take a look at this one? Thanks 4939051176402d6a7d6c1d5d67397799e6b15b2c is the first bad commit commit 4939051176402d6a7d6c1d5d67397799e6b15b2c Author: Matthew Francis <mjay.francis@gmail.com> Date: Fri Sep 18 10:48:28 2015 +0800 source-hash-ff140bb6b8b109f14c270ff059f0b8d71dab5d6c commit ff140bb6b8b109f14c270ff059f0b8d71dab5d6c Author: Thorsten Behrens <tbehrens@suse.com> AuthorDate: Thu Mar 21 00:37:28 2013 +0100 Commit: Thorsten Behrens <tbehrens@suse.com> CommitDate: Thu Mar 21 00:54:16 2013 +0100 Remove StringMirror UNO service. This was a kludge from back in the day when pdfimport was an extension and could not link against office libs. While at it, fix mirror method to handle unicode surrogates correctly. Change-Id: I3582a7870efdfea50446d3604a185025b1d5a196
Created attachment 140196 [details] pdf import printscreen
It looks the same bug as bug 104597 ( bibisect commit is the same ). Closing as RESOLVED DUPLICATED *** This bug has been marked as a duplicate of bug 104597 ***