Salam,
I wonder if your issue is related to this old Ubuntu poppler bug:
<https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/151608>
[Evince Document Viewer 2.20.0 fails to read Arabic PDFs]
no, it's not related to this, because :
1- Evince, GIMP on Linux, pdf x-change viewer and acrobat reader on Linux
are viewing my exported PDF correctly both on WinXP and Ubuntu-10.10
2- Both on WinXP and Ubuntu-10.10, LibO-Draw-3.3 + PDFImport extension have
exactly the same problem handling the last chars of the Unicode block
"Arabic Presentation Forms-B"
You might also want to look through:
<https://launchpad.net/+search?field.text=openoffice+%2Bpdf+%2Barabic>
It's talking about problems when exporting to PDF, but mine is when
repoening Exported pdf with (LibO or OoO)-Draw-3.3+PDFImport Extension1.0.4
I have already filed an issue on LibO/BugZilla and on OoO-Extensions.
Should i repost my problem on the Dev-MailingList...?
Thank you for your time and your efforts.
Regards,
Amine.
--
Amine Arrahmane Achargui
Effectiveness (“Do the right things”)
Efficiency (“Do the things right”)
Great to see that great projects choose to use great projects to become even
greater
--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***
Context
- Re: [libreoffice-users] Which Unicode Standard LibreOffice uses...? (continued)
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.