Hi All,
Could someone give me a hand regarding my understanding of whitespace.
Whitespace is significant in any element that can contain text, as I
understand it.
so
parasdfsdfsdfdspara
is better than
para
sadsdsd/para
Does this apply also with subelements?
-Original Message-
From: Samuel Wright [mailto:[EMAIL PROTECTED]
Sent: Monday, June 04, 2007 6:11 AM
To: docbook-apps@lists.oasis-open.org
Subject: [docbook-apps] whitespace - confirmation please
Hi All,
Could someone give me a hand regarding my understanding of whitespace.
El Lunes, 4 de Junio de 2007 13:10, Samuel Wright escribió:
Hi All,
Could someone give me a hand regarding my understanding of whitespace.
Whitespace is significant in any element that can contain text, as I
understand it.
That depend on the xml:space value assigned to that element on the
Hi all,
Before I assume there's no fix to this, I thought I'd ping the group one
more time to make sure this question actually made it to the list.
thanks if you have any thoughts!
cheri
-Original Message-
From: Dennison, Cheri [mailto:[EMAIL PROTECTED]
Sent: Friday, May 25, 2007 11:52
I guess that has to be a fop bug, but I would think others would have
noticed it. Perhaps you could avoid the situation by replacing the
spaces with nbsps:
l:template name=page.citation text=#x00A0;(p.#x00A0;%p)/
No line break, no problem? :-)
David
-Original Message-
From:
I haven't seen this behavior before with xrefs, Cheri. Have you looked
at the fo output produced by Saxon to see if the page references look
ok? Do you see any difference in the fo output between the page
references that look ok and that ones that do not?
If the FO output is ok, then maybe the
The FO that Saxon produces looks the same between good and bad examples,
and I can't determine a consistent algorithm explaining when FOP 0.20.5
produces bad vs. good. FOP also seems to have some other weird little
bugs randomly affecting the text that comes immediately after the page
citation.
