Subject: Re: [xsl] tokenizing and counting with xsl:analyze-string From: "Martin Honnen martin.honnen@xxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Date: Sat, 17 Oct 2020 17:15:02 -0000 |
On Sat, Oct 17, 2020 at 4:27 PM Mukul Gandhi gandhi.mukul@xxxxxxxxx <mailto:gandhi.mukul@xxxxxxxxx> <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx <mailto:xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>> wrote:
With above mentioned XSLT stylesheet, the thing that worked is, not explicitly declaring the type forB xsl:variable name="temp_result".
I find this strange.
With context to my example, ifB xsl:variable name="temp_result" without an explicit type declaration on the variable, presents the result of this variable as string (and string-length(translate(... working fine on such a variable),
Without having any "as" attribute your variable is a document fragment node containing the content constructed by the sequence constructor; of course if you use functions like "translate" expecting a string value the string value of the document fragment (which is the concatenation of the string value(s) of all child nodes) is being used.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] tokenizing and counting w, Mukul Gandhi gandhi. | Thread | Re: [xsl] tokenizing and counting w, Mukul Gandhi gandhi. |
Re: [xsl] tokenizing and counting w, Mukul Gandhi gandhi. | Date | Re: [xsl] tokenizing and counting w, Mukul Gandhi gandhi. |
Month |