xmlgraphics-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremias Maerki <...@jeremias-maerki.ch>
Subject Re: Using PNGEncoder and PNGDecoder
Date Fri, 19 Sep 2008 14:35:32 GMT
On 19.09.2008 15:38:21 Jean-François El Fouly wrote:
> Jeremias Maerki a écrit :
> > Right, that's the downside of Image I/O. But then, the XML-based approach
> > to metadata is also very powerful.
> >
> >   
> I'm not sure I understand. Am I missing something ?
> The images I (pre) process will be used by FOP somewhere downstream. 
> And, as far as I understand, FOP uses the PHYS metadata for its layout. 

Indirectly, yes.

> That's why I have been through considerable effort to give these 
> metadata sensible values.

Ok, makes sense.

Here's an example that uses Image I/O to produce a PNG including
resolution information:
Maybe that helps to understand how Image I/O does this.

Another alternative: If you only need the resolution right, you can just
as well use Common's ImageWriter which is great for just quickly save an
image with control over the most important features:

> > Another option that would give you a lot of control but possibly with a
> > simpler API is Apache Sanselan (incubating).
> > http://incubator.apache.org/sanselan
> >
> >   
> Interesting, did'nt know of this project.
> But the project I work on uses and embeds FOP and its dependencies, so I 
> guess it makes sense to use xmlgraphics-commons whenever possible.

Sure, whatever you think works best for you. Just listing alternatives.

Jeremias Maerki

Apache XML Graphics Project URL: http://xmlgraphics.apache.org/
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org

View raw message