On Sun, 11 May 2003, J.Pietschmann wrote:
> Robert P. J. Day wrote:
> > just to test JIMI, i figured i'd rebuild fop.jar without JAI support
> > just to see what JIMI could do. so i removed the jai* files from
> > {fop}/lib, did a build, noticed that the "prepare-jai" step did
> > *not* echo that JAI support was being built in, rebuilt my PDF
> > file and ... JAI was called to process the PNG files. huh?
>
> Probaly nothing was compiled, and the JAR wasn't rebuild.
> Changing build time dependencies doesn't cause a rebuild
> all by istelf. Try a "build clean".
>
> Again, a short look into build.xml would have probably
> saved you some embarassment.
oh, i'm *long* past the point of personal embarrassment here.
although i'm willing to admit that some of my difficulties were
my fault, i think i've also established that there are some definite
deficiencies in the docs for graphics support. where to start?
(first, since i made it clear that i was working with the CVS
tree, to clean that tree requires "build.sh clean", not
"build clean" as you wrote above. a picky detail, but the sort
of thing that has been costing me time and forced me to dig
around when i didn't have to.)
next, and as i've already mentioned, there is *nothing* i can see
in the docs that suggest that, if you build in JAI support, JIMI
support is simply dropped. *that* really deserves a prominent
place in the docs.
next, regarding a build, there's *nothing* that suggests you need
to do a "build.sh clean" to actually get a new "fop.jar". early on,
as part of my tests, i explicitly deleted {fop}/build/fop.jar,
and watched the output from "build.sh" carefully to confirm that,
yes, the support i wanted was being built in. afterwards, i
verified that a new "fop.jar" had been created under {fop}/build.
was i really supposed to suspect that the messages being printed
by the build process didn't actually correspond to the new fop.jar
file? this is pretty thoroughly non-intuitive for anyone used to
the "make" system.
> > but again, according to the online docs, SVG support is handled by
> > batik, which i definitely have on my CLASSPATH.
>
> PCX files are not SVG, and can't be handled by Batik, therefore
> the errors.
> Take a closer look at the output.
and once i did a clean, and built with only JIMI support, here's
the output (or at least an excerpt of it):
[INFO] Failed to load JAI, using Jimi instead <-- looks good ...
....
[ERROR] Could not load external SVG: Content is not allowed in prolog.
[ERROR] Error while creating area : No ImageReader for this type of image
(file:xclock.pcx)
[INFO] [30]
[ERROR] Could not load external SVG: Content is not allowed in prolog.
[ERROR] Error while creating area : No ImageReader for this type of image
(file:xclock.pict)
[INFO] [31]
[INFO] [32]
[ERROR] Could not load external SVG: Content is not allowed in prolog.
[ERROR] Error while creating area : No ImageReader for this type of image
(file:xclock.pnm)
[INFO] [33]
[ERROR] Could not load external SVG: Content is not allowed in prolog.
[ERROR] Error while creating area : No ImageReader for this type of image
(file:xclock.psd)
[INFO] [34]
[ERROR] Could not load external SVG: Content is not allowed in prolog.
[ERROR] Error while creating area : No ImageReader for this type of image
(file:xclock.ras)
[INFO] [35]
[ERROR] Could not load external SVG: Content is not allowed in prolog.
[ERROR] Error while creating area : No ImageReader for this type of image
(file:xclock.tga)
[INFO] [36]
[ERROR] Error while creating area : Error while loading image file:xclock.tiff
: class java.lang.Exception - Image error
[INFO] [37]
[ERROR] Could not load external SVG: Content is not allowed in prolog.
[ERROR] Error while creating area : No ImageReader for this type of image
(file:xclock.xbm)
[INFO] [38]
[ERROR] Could not load external SVG: Content is not allowed in prolog.
[ERROR] Error while creating area : No ImageReader for this type of image
(file:xclock.xpm)
and you can see that a number of formats that are documented as being
supported through JIMI failed to be rendered.
i'm using, as my guide, http://xml.apache.org/fop/graphics.html, so if
something in that table suggests it's supported by JIMI, i figure i have a
right to be confused if it doesn't work.
while i appreciate your assistance thus far, i could really do without
the smug, condescending tone about how i'm embarrassing myself.
i'm trying *really* hard to point out deficiencies in the docs so that
others after me don't have to go throught what i went through. and your
attitude i can really live without.
rday
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
