Hi
The pdf produced is mangled with badly positioned glyphs. The source uses Unicode script Kannada (0xc80-0xcFF). I am attaching the word source, font, pdf, and pdf produced using eval ver of Win2PDF pdf printer.
Also would it be possible to have an o/p option for PDF, PDF/1A ?
I understand the o/p is already PDF/1A, and am able to search for text.
Regards
Floater
Invalid rendering of Unicode script (Kannada)
Moderators: TrackerSupp-Daniel, Tracker Support, Vasyl-Tracker Dev Team, Chris - Tracker Supp, Sean - Tracker, Tracker Supp-Stefan
-
- User
- Posts: 2
- Joined: Fri Aug 24, 2012 8:33 am
Invalid rendering of Unicode script (Kannada)
You do not have the required permissions to view the files attached to this post.
-
- Site Admin
- Posts: 17949
- Joined: Mon Jan 12, 2009 8:07 am
- Location: London
Re: Invalid rendering of Unicode script (Kannada)
Hello Floater,
I just tested your sample and could produce a correct result using our PDF XChange Standard printing drivers, and had the same issue using the Lite driver - so I've created a ticket in our system:
#1621: Lite 5.0.264 Issues with placing of Unicode (Kannada) characters
That will allow us to investigate and fix this problem.
We will post back here in this topic as soon as the problem is resolved.
Best,
Stefan
I just tested your sample and could produce a correct result using our PDF XChange Standard printing drivers, and had the same issue using the Lite driver - so I've created a ticket in our system:
#1621: Lite 5.0.264 Issues with placing of Unicode (Kannada) characters
That will allow us to investigate and fix this problem.
We will post back here in this topic as soon as the problem is resolved.
Best,
Stefan
-
- Site Admin
- Posts: 17949
- Joined: Mon Jan 12, 2009 8:07 am
- Location: London
Re: Invalid rendering of Unicode script (Kannada)
Hello Floater,
Ticket 1621 was resolved, and the fix should be available in build 268 of our drivers we released last Friday:
https://www.pdf-xchange.com/product/downloads
Best,
Stefan
Ticket 1621 was resolved, and the fix should be available in build 268 of our drivers we released last Friday:
https://www.pdf-xchange.com/product/downloads
Best,
Stefan