mkl wrote > > > If rise is used in a document for superscript and subscript, exposing it > might make recognizing that really easy. If a document uses it for other > stuff, interpreting rise like that may be misleading. Oh well... >
One last comment on the above: In the early days of my parser work, I tried to use the characteristics of the underlying draw operations to attempt to "intuit" what the content was trying to do (i.e. gaps between words, superscript, etc...). I have come to a point where I am 100% convinced that this approach will just not work. Algorithms need to be able to determine the characteristic of the render operation based purely on layout information. So while Rise may indicate supescript, any algorithm that is really trying to figure this stuff out should rely only on the fact that the text is positioned such that it *looks* like superscript. -- View this message in context: http://itext-general.2136553.n4.nabble.com/PdfContentStreamProcessor-not-handling-TJ-operator-correctly-maybe-tp4656117p4656245.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
