ok, this goes a long way to clearing up my confusion ... On Mon, 12 May 2003, Jeremias Maerki wrote:
> Ok, let's go over this. I'm looking at the code: i'll probably break down one of these days and do the same ... > GIF, JPEG, BMP, EPS and SVG are supported without any additional > library: welllllll ... semantically, i'd say that SVG *does* require the additional batik stuff, but that's being pedantic. > - GIF is supported through JDK classes. > - JPEG is implemented directly because it can be more or less embeded > 1:1 in a PDF. so far, so good. > - BMP is directly implemented. ahhh ... the online docs claim that BMP is supported through JIMI or JAI, not via native support. good, that clears up *that* point. > - EPS is similar to JPEG. EPS images get embedded 1:1 in the PDF. > Acrobat Reader cannot display them (blank output) but looking at the > PDF in GhostView or printing it on a PostScript printer shows the EPS > content. ahhh again. i was viewing the final PDF through "xpdf" on linux. perhaps that's why i saw nothing in the way of EPS output. i'll test that shortly, and see if xpdf has the same limitation. > - SVG is supported through Batik and FOP's own code. yup, been there, done that, got my SVG output. > TIFF is a special case. TIFF images with JPEG or CCITT content will be > rendered to PDF as with plain JPEGs: simple embedding without > decompressing. Other TIFF subformats will be handled by JAI. TIFFs don't > seem to be handled with JIMI installed (technical: since it is derived > from JAIImage). So it seems like TIFF is totally unsupported if JAI is > not present. i think that's definitely worth noting on the graphics page, since TIFF is curerntly listed as supported by *either* JAI or JIMI. > PNG images are supported through either JAI or JIMI whichever is present. yup, that's what i saw. > As J�rg already said, FOP falls back to SVG mode if it cannot > identify an image. Since an unsupported image format is not SVG an error > like above occurs. That's the reason for the first message. The second > message tells something about ImageReaders. For each image format > supported by FOP an ImageReader must exist. It's responsible to identify > a particular image format and to extract some header information such as > resolution and image size. Basically FOP tries through all ImageReaders > until it finds a format it recognizes. The last to try is always SVG. So > even if JAI or JIMI support additional format, if there's no > corresponding ImageReader, the format is not supported. just to make sure i understand this part, FOP is not responsible for processing the image in its entirety, just for perhaps recognizing the image type and invoking the correct library, right? after all, by saying that FOP supports an image format through JIMI or JAI, i'm assuming that all FOP has to do is call the appropriate routine for processing that image. that means that all that has to be done for FOP is to add the additional ImageReaders. is this even remotely close to accurate? > > 3) EPS doesn't render, although the table does state that this > > native support is still limited for PDF output. > > See above. EPS doesn't show in Acrobat Reader. i'll check to see if this is why nothing shows up in xpdf. thanks. slowly but surely, i'm filling out my little cheat sheet. rday --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
