It is certainly difficult and we are certainly not expert in PDF specs details but it is a bit simple to say that the code is wrong and the PDFs are fine. The same code, chain of tools, worked fine with 99% of other fine PDFs.
Now I don’t understand why would any tool (developer) associate ASCII characters with different glyphs. Whatever the reason, we thought that it would be possible to use an API to interpret the mixed character/glyph mapping and continue to use the same code (since all the PDF readers still can). We must be missing something but we figure out a workaround for now. Thanks again for you help. -- View this message in context: http://itext-general.2136553.n4.nabble.com/Strange-ASCII-character-replacement-pattern-Character-Mapping-Table-tp2526561p2528606.html Sent from the iText - General mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://www.itextpdf.com/book/ Check the site with examples before you ask questions: http://www.1t3xt.info/examples/ You can also search the keywords list: http://1t3xt.info/tutorials/keywords/
