Hi,
I'm working with FOP embedded in a CMS for generating PDFs. The version of
FOP is v0_20_5. The problem is the following one:
If I use a basic link and the external-destination is linked to a pdf, all /
(slashes) turn into \ (backslashes). Most readers correct this failure, but
not adobe
Hi Stephan,
Stephan Thesing wrote:
Hello,
snip/
My idea is now along the following lines:
- Remember for each element during parsing the change bars it is
influenced by.
- After layout, go over all areas produced by those influenced elements
and add the areas for the change bars
On 04.09.2009 10:55, JPee wrote:
I'm working with FOP embedded in a CMS and using verdana (referenced as
verdanattf.tff) and georgia (referenced as georgia.ttf), also with bold and
italic fonts of it.
When I generate a PDF and copy a word, everything i get is
and not the correct
On 04.09.2009 10:49, JPee wrote:
If I use a basic link and the external-destination is linked to a pdf, all /
(slashes) turn into \ (backslashes).
As a wild guess: if you generate the PDF with the backslashes on
Windows, try on a UNIX/LINUX system and check whether the problem
goes away.
Other
On 03 Sep 2009, at 22:07, Stephan Thesing wrote:
Hi Stephan,
snip /
Seems reasonable, although... validateChildNode() is more meant to
take care of very specific cases, mentioned in the definition of the
content model. Now I'm thinking: a change-bar-* is a neutral item
that
is basically
