Laurent Yaish wrote:
Why would you store data with line breaks in an XML element attribute that
way in the first place?
Sounds like instead of havin <tag attribute="values with line breaks" />
you
should reformat your data to be more flexible such as something like:
<tag>
<attr_tag>value1</attr_tag>
<attr_tag>value2</attr_tag>
<attr_tag>value3</attr_tag>
</tag>
Depends, maybe that isn't semantically correct for their data (it isn't
for ours either.)
For example, take something like an email body. It has multiple lines
so line breaks should be formatted as linebreaks in the output, but each
line shouldn't really be treated as a separate element since they occur
in the same chunk of content.
(We do our own breaking by substituting <fo:block/> elements into the
appropriate places before running through FOP, although it sounds like
this attribute to make linebreaks significant may be cleaner.)
Daniel
--
Daniel Noll
Nuix Pty Ltd
Suite 79, 89 Jones St, Ultimo NSW 2007, Australia Ph: +61 2 9280 0699
Web: http://nuix.com/ Fax: +61 2 9212 6902
This message is intended only for the named recipient. If you are not
the intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
message or attachment is strictly prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
