Re: Ref-IDs in custom FOP 0.93 extension
Hi, I had a look at the rendered PS files and it seems like the PS FOP renderer is producing easily processable output. I'll go ahead and try to use the EPSTranscoder of FOP to render the SVG DOM containing the barcode into EPS and then enrich the original PS file. I'll let you know of the results. Just a follow up for anybody interested: This worked nicely. I ended up writing a FOPBarcodePostscriptOutputStream which I can pass to FOP (or use individually in a separate post-processing step). The Outputstream enriches the original stream with the barcode, which I build as an SVG DOM Tree and render to PS with Batik. This works straight forward as expected using the Batik Transcoder API, except that I had to add a ImageTranscoder.KEY_PIXEL_UNIT_TO_MILLIMETER Transcoding Hint manually, as FOP seems to use 72dpi internally whereas Batik (1.6) uses 96dpi. Thanks again Jeremias for pointing me towards the right direction, Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Ref-IDs in custom FOP 0.93 extension
Hi Jeremias, PageViewport page = (PageViewport) context.getProperty(PAGE_VIEWPORT); int pageCount = page.getPageSequence().getPageCount(); already tried this, but as you say, the page count is not the final one but only includes the pages added so far to the PageSequence. The PageNumberCitationLayoutManager can insert an UnresolvedPageNumber area tree object into the area tree. UnresolvedPageNumber implements Resolvable. Maybe something could be done with this interface but I'm not sure without going deeper. I'll look into it but thinking about it I rather like your second approach... Let me just say that I'm usually post-processing the print files if I have to add packaging marks (like OMR etc.). That would certainly be easier to implement and provides options for parallelizing document production as FOP is usually the most CPU-eating part of the chain. I had a look at the rendered PS files and it seems like the PS FOP renderer is producing easily processable output. I'll go ahead and try to use the EPSTranscoder of FOP to render the SVG DOM containing the barcode into EPS and then enrich the original PS file. I'll let you know of the results. BTW, what's that barcode you're implementing? The barcode applied to the output is read by the BOEWE 154/2-91SB mass printing facility, so that the printed output ends up in the correct envelope for postal shipment. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
