Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] rev 31326: /trunk/docbook/ /trunk/docboo

From: Jaap Keuter <jaap.keuter@xxxxxxxxx>
Date: Mon, 21 Dec 2009 07:57:48 +0100
Hi Bill,

Yes, FOP 0.95 tries to do a better job, but if you look at the details:

http://xmlgraphics.apache.org/fop/0.95/graphics.html#png
-------8<-------
PNG

PNG images are supported through an Image I/O codec. Transparency is supported but not guaranteed to work with every output format.
-------8<-------

And that means:

-------8<-------
Image I/O

The image loading framework in XML Graphics Commons provides a wrapper to load images through the JDK's Image I/O API (JSR 015). Image I/O allows to dynamically add additional image codecs. An example of such an add-on library are the JAI Image I/O Tools available from Sun.
-------8<-------

So you still need JAI or jimi to do the actual work. Without it, no graphics in your PDF's

Thanks,
Jaap

Bill Meier wrote:
jake@xxxxxxxxxxxxx wrote:
 Update readme information, ...


Re: the changes to remove the "for fop 0.20.5 only" notes

such as:

-JIMI (for PDF generation with fop 0.20.5 only)
+JIMI (for PDF generation)


My understanding is that 0.95 doesn't require JIMI & etc.
Is there something special about the Wireshark docbook stuff that does require JIMI when using FOP 0.95 (or am I missing something) ??


From: the FOP 0.95 release notes: http://xmlgraphics.apache.org/fop/0.95/releaseNotes_0.95.html

"...
The image libraries Jimi and JAI are no longer needed (and used) for image loading. Instead we rely completely on the Image I/O API that has been introduced with Java 1.4. If you still need support for bitmap image formats that do not work out-of-the-box, we recommend adding JAI Image I/O Tools (an Image I/O compatible image codec package) to the classpath. ...."

Bill