Georg Datterl a écrit :
Hello Pascal,
What you need is the property initial-page-number (=auto-odd or =auto-even) set on your fo:page-sequence.
That should help you.
Yes, that seems to make the page-sequence-masters unnecessary. Thanks a lot.
But I would still have to start a new
pedro a écrit :
Hi all
my problem is the same problem of all developer ,preview PDF.
Now i'm use Adobe or Foxit but sometimes i have problem with speed,Adobe
Update Dialog
I try the PreviewDialog but it's a frame and i want a modal dialog.
I try to use PreviewPanel but i'm not
Vincent Hennebert a écrit :
FOP definitely paints borders over backgrounds; what you’re seeing is
a rendering defect of your PDF viewer, partly due to the relatively big
size of pixels on monitors. The printed document should look ok.
I have a table related question about that :
Is that
to a single font file by its name,
and fop
would generate the font metric at execution time.
Well I could copy the font in a temp dir and still use auto-detect,
but I'd like to avoid this copy.
Thanks,
Laurent Morel
FOP does exactly what
you tell it to do. There's a 1pt border between lines 2 3 when I run
your snippet.
On 29.07.2008 16:02:21 Laurent Morel wrote:
Hello,
I have a strange behaviour for table rendering, which I can't explain.
See example below.
Basically, if number-columns-spanned 1
Some kind of reply to this (old) message :
http://markmail.org/message/iyyco7ffxs6qj2i7
I confirm this problem also in 0.95beta
The AWT display order is not reversed here :
pages 1,2,3...N are displayed in that order :
N, 1, 2, 3 ... N-1
This bug only appears if my document has a
Hello,
I have a strange behaviour for table rendering, which I can't explain.
See example below.
Basically, if number-columns-spanned 1, the border-bottom property
is applied only to first (original) cell. The next cells only have half the
border thickness (example line 2).
This is not the case
