Michael- The reason we don't expose the graphics state is because that would break abstraction between the logical levels of the API. The goal of the text render listener was to provide a neutral mechanism for describing a text draw operation. If the information being provided isn't sufficient, then that's something that absolutely needs to be addressed. Exposing the full graphics state seems like overkill in this regard, though (and it would encourage breaking the encapsulation).
Note that the values returned by calls to text render info are always in the same coordinate system - if you start messing with the graphics state directly, it opens up a world of hurt for the coordinate transformations, etc... If I'm understanding the issue, there are cases where it is necessary to use the word and character spacing to properly lay text out on screen. I am in the process of exposing those two values (scaled to user coordinates) in TextRenderInfo - should have that checked in shortly. I am quite interested in learning how these values are being used, and what changes to LocationTextExtractionStrategy might need to be made to account for these values. Please post back with your thoughts on that. Also, please let me know what other parameters from the graphics state are of interest in TextRenderInfo and I'll add getters for them (returning user space coordinates, of course). Thanks, -- View this message in context: http://itext-general.2136553.n4.nabble.com/PdfContentStreamProcessor-not-handling-TJ-operator-correctly-maybe-tp4656117p4656224.html Sent from the iText - General mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ iText-questions mailing list [email protected] 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
