I would think the default should be to continue (warning in
LOG/stdout) create an empty (blank/transparent) container the size and
placement of the image.
It would be nifty if it could be a flag in the config or CLI args
giving the user the choiice to fail on missing images.
Clay
I concur with
I would think the default should be to continue (warning in
LOG/stdout) create an empty (blank/transparent) container the size and
placement of the image.
It would be nifty if it could be a flag in the config or CLI args
giving the user the choiice to fail on missing images.
Clay
On 2/16/08, A
Yes... If you build it, it will be tested... ;-) I guess I was just
trying to identify the minimum PDF viewers FOP strives to support.
As for 'cleanup', you mentioned the PS & PDF code'll be messier but it
doesn't matter much... If it doesn't matter much (e.g., it's still
valid) then I guess we're
Hi all
Reason for this question is I'm trying out a test-suite that was
shared by Kumar Puppala (see a recent thread on fop-users).
The image formats are the same (PNG), and they are never present.
Mostly, when the images are not available, I simply see an error in
the log, but the proces
Should be fixed now together with a few other details I found while
diving in even deeper. In the end I decided to rip out the old glyph
list which seems to have been modified manually to hack in support for
special characters like NBSP. This should be cleaner now.
There's a little detail concerni
