Chris,
I'm not sure how to read this. Are you endorsing string-replace as the way
to go to get cmyk into the pdf or was that meant to be tongue-in-cheek?
I was about to switch over to using rgb-icc since we have two colour
profiles in play. If you're suggesting that string-replace is
Ok if Vincent agrees this is a bug I can make the issue and supply the test
fo. The patch is his and I don't think I should claim it.
Glenn Adams-2 wrote
First, someone needs to open a bug and submit a patch against the bug.
--
View this message in context:
I am happy to report (rather belatedly I'm afraid) that the patch has done
the trick.
The test fo supplied no longer presents the problem and we see none in our
book. It's hard to know from the book itself whether the lack of problems is
happy coincidence or not, but the test is quite clear.
Is
in the pdf for replacement. (Legacy
code).
If I can't find a local explanation, I'm headed for a serious re-write of
color handling. Should have been done long ago, I concede. Still not a
good time, um, er, corporately.
Thanks
rsargent wrote
I'm not finding certain strings related to colour
We've hit this a couple of times now and I have a small fo showing the
problem.
In production we are using fop-1.0, but I've generated this on both
1.0 and 1.1rc1 (with a small patch from Vincent related to
http://apache-fop.1065347.n5.nabble.com/page-number-is-stuttering-tt36312.html
Show the stack trace.
Quoting Wilhelm wilhelm.me...@fh-kl.de:
Hi,
using fop-1.0 oder fop-1.1rc1 I get NullPointerExceptions if I enable
hyphenation (language=de).
Any hints?
--
Wilhelm
-
To unsubscribe, e-mail:
