Ah - now I see what you have in mind - I like the idea of providing character-by-character TextRenderInfo sub-objects... Another approach that might be even more flexible would be to provide the effective TextRenderInfo sub-object given a start and stop character.
I wonder if that functionality would make getCharacterSpacing and getWordSpacing unnecessary? Also, I have just committed changes that make the Rise be part of the baseline, ascentline, etc... The LocationTextExtractionStrategy has been adjusted to take the rise into account. It would still be better if LocaitonTextExtractionStrategy used the actual positioning of the superscript text to determine whether it should be part of the same text line or not, but this at least results in the same behavior as before we added Rise into the baselines. -- View this message in context: http://itext-general.2136553.n4.nabble.com/PdfContentStreamProcessor-not-handling-TJ-operator-correctly-maybe-tp4656117p4656274.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
