Peter B. West wrote:
public final static int JUSTIFY = 54;
This indicates a missing break in the JUSTIFY case...
bingo, right! I'm humilated. :-/
J.Pietschmann
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
J.Pietschmann wrote:
May be creating -outfo param for fop.bat/sh is better?
Certainly, but this is real work. Even better would be
fop -xml foo.xml -xsl foo.xsl -fo foo.fo
but this requires even more work (because the FO file is
no longer automatically an input)/
Yeah, lets leave that
Oleg Tkachenko wrote:
Yeah, lets leave that command line stuff alone. btw, what about moving
it to CLI in the trunk? I've been thinking about it, it seems to me CLI
doesn't support such optional options like our -fo, but the rest looks
okay.
Certainly an idea. However, I'd like to have the
J.Pietschmann wrote:
Yeah, lets leave that command line stuff alone. btw, what about moving
it to CLI in the trunk? I've been thinking about it, it seems to me
CLI doesn't support such optional options like our -fo, but the rest
looks okay.
Certainly an idea. However, I'd like to have the
J.Pietschmann wrote:
Hi,
I more or less fixed the leader generation causing all sorts of
problems and specifically #15936.
Some issues:
- The state machine detecting line breaks is brittle. It will probably
cause problems if leaders are mixed with graphics on the same line
I'm again tempted
J.Pietschmann wrote:
3. Distribute any slack space left equally on the resizable spaces
(subject to round off, should use a Bresenham-like algo for
perfection :-)
Can anybody come up with an algorithm to distribute slack space
over several leaders which can deal with
