Kevin, on TextRenderInfo sub-objects:
Kevin Day wrote > I wonder if that functionality would make getCharacterSpacing and > getWordSpacing unnecessary? I think the API should offer both. Depending on the use case at hand, either concept might be the most natural one, the most easy to integrate one. Additionally unit tests using both concepts next to each other and comparing the results might keep the code quality up. ;) On LocationTextExtractionStrategy and superscript: > this at least results in the same behavior as before we added Rise into > the baselines. I'm not sure that that is a good objective to pursue. As long as the resulting text does not somehow allow to recognize its superscript parts, this remains somewhat unsatisfying. Maybe it really is time for the LocationRichTextExtractionStrategy... ;) Regards, Michael -- View this message in context: http://itext-general.2136553.n4.nabble.com/PdfContentStreamProcessor-not-handling-TJ-operator-correctly-maybe-tp4656117p4656287.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
