Hi,
I've a problem using basic-links.
When i give a fo:basic-link for some word, it
leaves two spaces before and after the string.
Egs.
1. APPLE p.10
2. BAT
p.10
3.
CAT p.12
Does anybody know why this empty space is created
before and after the word with
Hi,
I've a problem using basic-links.
When i give a fo:basic-link for some word, it
leaves two spaces before and after the string.
Egs.
1. APPLE p.10
2. BAT
p.10
3.
CAT p.12
Does anybody know why this empty space is created
before and after the word with
Hi,
We r generating PDF files using fo. We want to provide some security
features to the PDF like non-printable, non-editable etc., when opened thru
Adobe acrobat. Can somebody help in achieving this? Can this be done thru
FOP itself or do we need to use Adobe's API? If somebody could help
You should try http://forum.planetpdf.com
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 10, 2002 11:22 AM
Subject: RE: basic-link
Hi,
We r generating PDF files using fo. We want to provide some security
features to the
[EMAIL PROTECTED] wrote:
We r generating PDF files using fo. We want to provide some security
features to the PDF like non-printable, non-editable etc., when opened thru
Adobe acrobat. Can somebody help in achieving this? Can this be done thru
FOP itself or do we need to use Adobe's API? If
Hi, I', trying to do a toc using a table. The xsl code is
Hi all.
I transform a xml file and add FO vocabulary, generating a PDF with fop
afterwards. Now that I got it work using xalan and fop from the command
line I embedded both into a JSP and a bean following the example code
from docs/examples/embedding.
The problem: When I generate the PDF with th
Ralf Steppacher wrote:
I transform a xml file and add FO vocabulary, generating a PDF with fop
afterwards. Now that I got it work using xalan and fop from the command
line I embedded both into a JSP and a bean following the example code
from docs/examples/embedding.
The problem: When I generate
The problem: When I generate the PDF with the JSP my fo:basic-links
don't make it into the PDF. If I dump the FO DOM tree to a file and
use fop from the commandline the links are present in the PDF.
Are you, by any chance, using disable-output-escaping somewhere?
Yes, but somewhere else in the st
Ralf Steppacher wrote:
Are you, by any chance, using disable-output-escaping somewhere?
Yes, but somewhere else in the stylesheet producing the fo document.
It doesn't matter where. Do not use d-o-e if you expect your style
sheet to work with short-circuit XSLT processor applications.
XSLT doesn't
>>> Are you, by any chance, using disable-output-escaping somewhere?
>>
>> Yes, [..].
>
> XSLT doesn't del with tags, it uses a tree of nodes for input and
> output.[..]
>
>> Behaviour does not change if I comment out the two lines (that do
>> not work with embedded fop either).
>
> If you delete t
Ralf Steppacher wrote:
OK, I got rid of all the d-o-e.
But the basic-links still are not present in the pdf generated by the
embedded FOP but are if the .fo document is dumped to a file and then
rendered using FOP from commandline.
Can you post a trimmed down version of your source XML
and the st
Can you post a trimmed down version of your source XML
and the style sheet which demonstrates the problem?
I attached the XML source and the FO file as it is dumped for debugging
purpose from my code. The stylesheet is still a bit lengthy (main style
sheet is allInOne2FO_short). The link should b
Ralf Steppacher wrote:
^^^
Well, mystery solved. Indenting the result should and usually
does not alter the semantics of the document, but there is no
guarantee, the spec explicitely warns that whitespace for
intendation could result in a differe
First of all: Thank you very much for your help!
>>
>>
>>
>
> This is the real problem. You probably noticed that the link area is
> not the whole page number, in particular with multiple digit page
> numbers.
Yes, that is right. I will follow your advise and use the headline text
as link area
Ralf Steppacher wrote:
> If this comes directly from your original style sheet, you should
> better use matching precise templates instead of piping everything
> into a match-all and then use a choose in it.
Is this just a matter of style or do exact templates perform better?
A matter of robustn
16 matches
Mail list logo
