Hi Vincent,
You are right, I was totally confused. I use an unstable version of Debian,
so I thought apt-get install will pick up FOP 0.95 from the unstable (trunk)
version of FOP. Now I understand that trunk is for source files only. I do
use FOP 0.95. All this long discussion aims at:
1) Getting rid of the font warnings in a proper way :-)
2) Ability to compile a PDF that shows Zapfdingbats symbols, and not #
instead.
Thank you (and others) for your help and patience!
Best regards,
Nancy
Vincent Hennebert-2 wrote:
Hi Nancy,
There seems to be a lot of confusion around here :-) And my own earlier
confusion about which version of FOP is affected by the change of the
default value for font-family didn’t help :-|
So please reset your memory, and let’s start again from the beginning.
Which version of FOP are you currently using? You can get it by running
‘fop -v’ on the command line (the first line of output).
Don’t use any FOP configuration file, don’t use any XSLT stylesheet
customization, just the plain default. What problem do you run into, if
any? Please reduce your source XML file to the strict minimum that still
shows the issue, and send us the XSL-FO file resulting from the XSLT
transformation. Then we can have a look at it and figure out what’s
wrong.
Thanks,
Vincent
nancy_b wrote:
Hi Andreas,
Thanks for your response! So if I install FOP 0.95 from trunk, will it
still
issue the warnings?
I don't understand what you mean by :
... is specified as the first font (depending on which
character/codepoint
you want to
render. In my XML file, I just specify the code of the Zapfdingbats
symbol
(in the above example, the phone symbol).
Thanks in advance!
Nancy
Andreas Delmelle-2 wrote:
On 04 Jun 2009, at 10:15, nancy_b wrote:
Hi Nancy
Thanks for your explanations. I think my version of FOP 0.95 does
insert
Symbol and Zapfdingbats into the font-family parameter - along with
sans-serif. Apparently, my repository points to the trunk. Look:
fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format;
font-family=serif,Symbol,ZapfDingbats font-size=12pt text-
align=start
line-height=normal font-selection-strategy=character-by-character
line-height-shift-adjustment=disregard-shifts language=en
...
So, I don't see the reason why the # symbol appears in the PDF doc.
It seems
that FOP finds the Zapfdingbats font...
FOP 0.95 does not yet implement automatic selection of the correct
font. In the above sample, 0.95 or earlier will always use only the
'serif' font (the first specified in the list). FOP Trunk should be
able to deal with that, as it considers all the specified fonts.
You have to make sure that either Symbol or ZapfDingbats is specified
as the first font (depending on which character/codepoint you want to
render).
HTH!
Andreas
-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
--
View this message in context:
http://www.nabble.com/FOP-0.95-fails-to-compile-large-PDF-files---java-heap-space-tp23816647p23869093.html
Sent from the FOP - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
