|
Subject: Re: [xsl] codepoints-to-string for new line From: Liam R E Quin <liam@xxxxxx> Date: Sat, 07 Sep 2013 20:12:54 -0400 |
On Sun, 2013-09-08 at 01:04 +0200, Heiko Niemann wrote:
> b) Are there just no (top-rated) samples around because
> codepoints-to-string() belongs to an extended set of functions that people
> (like me) rarely/never use?
It's part of XSLT 2 [1], which doesn't have as widespread use as XSLT 1.
Using <xsl:value-of select="codepoints-to-string('10')" /> will indeed
give you a newline in cases where using an XML editor on your stylesheet
would turn into a literal newline which might then be reformatted
as a space by buggy ill-behaved software you shouldn't use :-) :-)
The right way for an editor to show indenting of XML documents is
visually, not by changing the text of the document.
Probably I'd have a global variable,
<xsl:variable name="newline" select="codepoints-to-string('10')" />
and document in a comment why you are using it.
Then you can use concat("abc", $newline, "cde") to get something much
more readable.
Liam
[1] http://www.w3.org/TR/xpath-functions/#func-codepoints-to-string
--
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml
| Current Thread |
|---|
|
| <- Previous | Index | Next -> |
|---|---|---|
| Re: [xsl] codepoints-to-string for , G. Ken Holman | Thread | Re: [xsl] codepoints-to-string for , Stefan Krause |
| Re: [xsl] codepoints-to-string for , G. Ken Holman | Date | Re: [xsl] codepoints-to-string for , Stefan Krause |
| Month |