Hello Kevin,
Thank you for the reply.
Currently the event model is read-only, and it does do a good job telling us
some text and image information. However, when it comes to modifying the
existing document content, we have to write it back. That's a lacking feature
for the event model.
For example, quite often, some documents use fonts which are too thin and not
so pleased for our eyes to read, we can apply a outlined text rendering mode to
each text, making a thin black outline surrounding the text. As a result, the
text will look "bolder" by the effect of the outline.
Up to now, the page stamper can not achieve this. That's why I am looking for
solution to change the content.
WMJ.
>________________________________
> From: Kevin Day <[email protected]>
>Subject: Re: [iText-questions] Save PDF as plain text
>
>WMJ -
>
>Your comment about "requiring lots of classes" makes me think that maybe you
>are trying to interact with the low level PdfContentStreamProcessor, instead
>of registering a RenderListener? I'm wondering if you might be trying to
>use the wrong level of the architecture.
>
>There is a hierarchy of event handlers, starting at the lowest level
>(handling each individual content stream command). These, in turn, fire
>drastically consolidated events on a registered RenderListener (right now,
>there are events for drawing text and drawing images. Support for drawing
>paths is in the works). The events received by the listener are much, much
>more consolidated than if you were trying to look at every event in the PDF
>content stream.
>
>No doubt, it is still event based, but you are looking at a listener
>interface with a small number of callback methods on it. It generally
>requires only one class implementing the listener interface to get what you
>want. Wrapping a DOM generator around the RenderListener interface is a
>trivial activity, which is why we have been a bit puzzled by the comments
>about how hard the current implementation is to work with...
>
>- K
>
>--
>View this message in context:
>http://itext-general.2136553.n4.nabble.com/Save-PDF-as-plain-text-tp4041246p4086380.html
>Sent from the iText - General mailing list archive at Nabble.com.
>
>------------------------------------------------------------------------------
>All the data continuously generated in your IT infrastructure
>contains a definitive record of customers, application performance,
>security threats, fraudulent activity, and more. Splunk takes this
>data and makes sense of it. IT sense. And common sense.
>http://p.sf.net/sfu/splunk-novd2d
>_______________________________________________
>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
>
>
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
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
