Abel,
thanks for these, I'll investigate and see how I go.
In this case the data is coming out of a FileMaker database, so I've
just got to hope that they improve the situation in the future.
They're using the Xalan C++ implementation so anything like EXSLT or
XSLT2 seems to be a way off unfortunately. Because I'm using the
built in XSLT processor, I'm stuck with their choice until I program
my own processing functions, and that's not likely to happen in the
near future.
Thanks to all who helped out.
Cheers,
Nick
On 21/06/2007, at 12:56 AM, Abel Braaksma wrote:
Nicholas Orr wrote:
Yes, I agree. The source I have no control over, other than to
submit error reports and hope for the best. It's coming out of an
app where I don't control the output.
But having investigated this I came to the same conclusion, and
I'll submit some reports about it and see what happens.
Nicholas, if you draw a blank on your error reports, i.e., if you
*have* to remove the whitespace yourself, consider the following
three options:
1. The FAQ entry: http://www.dpawson.co.uk/xsl/sect2/
N8321.html#d11899e830
2. One of the two solutions below, which is rather straightforward,
the second admittedly being a bit obfuscated while trying to
minimize the code
3. XSLT 2 (convince your bosses to upgrade): replace($text, '\s*([^
\s]+)\s*', '$1')
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--