You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by Stefan Haberl <st...@hvb.sozvers.at> on 2007/06/04 14:55:58 UTC

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: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org