On 6/09/2010 18:09, elyesl wrote: > Now I don’t understand why would any tool (developer) associate ASCII > characters with different glyphs.
You should learn more about PDF instead of making assumptions. > 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 No, as Leonard rightly pointed out from the start: OCR is your only option. > (since all the PDF readers still can). This allegation in contradiction with what you said earlier: "But when parsing using iText, only strange characters appear. Same behavior/result when copying the text to the clipboard and pasting to notepad." PDF Readers CAN'T INTERPRET the characters correctly!!! Pdf Reader can map a character to the code to draw a glyph that is present in the font program embedded in the PDF. But if they see "moveTo x, y, curveTo x, y, lineTo x,y,...", they can't tell you if this syntax represents an a, b, c, or any other character. > We must be missing something but we figure out a workaround for now. The information you have received was very detailed. We're very sorry that our efforts trying to explain the problem weren't well received. ------------------------------------------------------------------------------ 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/
