Hi,
For questions related to FOP usage, please ask in fop-user list.
FOP cannot concatenate PDFs, but you can do that in a post-process.
see [1] for existing post-processors.
Pascal
[1] http://xmlgraphics.apache.org/fop/resources.html#products-pdf
Message d'origine
Hi Michael,
It turned out that the bug I was facing was caused by an incorrect handling
of streams (input and output streams).
The initial version of the code was:
oTransformer.transform(
new FileInputStream( oPreXSLFOFileName ),
Hi,
What you need here are integer values for keep-together and keep-with-*.
Unfortunately, FOP doesn't implement this yet.
As a workaround, you can approximatively evaluate the text length and choose to
keep or not...
Pascal
Message d'origine
De: Lewis, Eric
Hi
It turns out that a combination of checking the text length and keeping
title and body together does the trick.
I remember that Jeremias said that integer values for keep-together etc.
were kind of supported (not officially, though).
Anyway, thanks for the help!
Best regards,
Eric
__
On Thursday 20 September 2007 15:52, Pascal Sancho wrote:
> Hi,
> What you need here are integer values for keep-together and
> keep-with-*. Unfortunately, FOP doesn't implement this yet.
>
> As a workaround, you can approximatively evaluate the text length and
> choose to keep or not...
>
> Pascal
Hi Manuel
Yes, that's how I solved the problem in the end.
But my XSL-FO looked different, since it didn't contain explicit blocks for the
title (just some inline formatting).
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: Manuel Mall [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag,
Is it possible to disable the PJL command lines of the PCL-Renderer ?
We have updated from 0.20.5 to 0.94 the old PCL-renderer didn't generate
PJL-Commands, so we wraped all pages in a PJL-Job ... so we could support all
printerfunctions like booklet-printing, duplex-printing and so on ... with
On Sep 19, 2007, at 22:58, [EMAIL PROTECTED] wrote:
Hi
Actually more of an XSLT-related question, and as such a bit off-
topic for the list... Please try to keep in mind that this list is
specifically meant for questions WRT using FOP. For XSLT-related
issues, there are better lists than th
I am having the same error in several of my fo reports. I've tried some of
these suggestions, but they didn't help my issue either.
On 9/17/07, Andreas L Delmelle <[EMAIL PROTECTED]> wrote:
>
> On Sep 17, 2007, at 21:28, Andreas L Delmelle wrote:
>
> Sorry, realized that I expressed myself badly,
On Sep 17, 2007, at 22:06, Andreas L Delmelle wrote:
... If you subsequently use FO properties like linefeed- and white-
space-treatment, that may lead to strange cases, that are
semantically 100% correct.
BUT, even if FOP would not choke on it, chances are that the
'correct' treatment woul
On Sep 20, 2007, at 19:51, Lance Goforth wrote:
Hi
I am having the same error in several of my fo reports. I've tried
some of these suggestions, but they didn't help my issue either.
Can you provide a sample of a FO causing the error on your end, so
that we can have a closer look?
TIA
I haven't had much time to do any debugging, so for now I'm staying with the
older version. But this fo with the new version is the one that gets the
error.
On 9/20/07, Andreas L Delmelle <[EMAIL PROTECTED]> wrote:
>
> On Sep 20, 2007, at 19:51, Lance Goforth wrote:
>
> Hi
>
> > I am having the s
On Sep 20, 2007, at 20:47, Lance Goforth wrote:
I haven't had much time to do any debugging, so for now I'm staying
with the older version. But this fo with the new version is the
one that gets the error.
The error I get for this FO is unrelated to the one in the OP. In
your case, the fi
I recognize that error, I have seen it and fixed it before. However I
wasn't getting that error, just the array index error. Finding and fixing
that cell does prevent the error from occurring though. Thanks.
On 9/20/07, Andreas L Delmelle <[EMAIL PROTECTED]> wrote:
>
> On Sep 20, 2007, at 20:47
Andreas,
Thanks for your input. Yes, I took the fo generated on the server for which I
was getting those warnings and analyzed and found no issues or missing tags
indicated in the warnings. Also, I generated the PDF from my dev environment
succesfully without any issues. Also was able to create t
15 matches
Mail list logo