Leonard Rosenthol <lrosenth <at> adobe.com> writes: > > Another great example of poor PDF generation :(. Wasting all those bytes > for ASCII values.
As far as I remember this method was pioneerd by Adobe InDesign, the first full unicode Windows version, I do not remember the number. Actually it makes a lot of sense, because InDesign just copied info from Windows structures that had it in Unicode. Trying to convert it into plain PDF string is another set of problems. Plain PDF strings are not ASCII, they are PDFDocEncoding, that is another can of worms nobody wanted to open. And by the way there was a niche software that expected these keys to be in Unicode, otherwise it crashed :) -- Ivan ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions iText(R) is a registered trademark of 1T3XT BVBA. Many questions posted to this list can (and will) be answered with a reference to the iText book: http://www.itextpdf.com/book/ Please check the keywords list before you ask for examples: http://itextpdf.com/themes/keywords.php
