Stephen Haberman wrote:
Processing xml as text is kinda dangerous, especially when you are trying to
fiddle with tags, I believe a better and more safe way is to handle \n\n stuff
one stage earlier - during fo generation, that's pretty simple in xslt to
tokenize string into blocks by any delimiter, trivial recursive template can
2) Run this result through a text manipulation program to replace all of
the \n\n with </fo:block><fo:block> to simulate a paragraph break.
3) Run this result through FOP.
I'm thinking this will work once I get some scripts setup for it, but
I'm just wondering if there is a better, within-FO/FOP way?
Search in the archive - that's faq, you can use either <block/> or unicode
line separator (
Also, a subset of this problem is that I was wanting to have a little
bit of control over breaking from the XML file, e.g. force a line break.
This is a long line that I want broken<br/>here.
Wrong way, disable-output-escaping implies serialization of a result tree
hence doesn't work otherwise, e.g. in mozilla, cocoon and fop. This facility
is for generating text (e.g. SQL), but not markup.
Multiconn Technologies, Israel