Subject:Repress conversion of
to actual line feed Author:Solomon Fried Date:21 Mar 2002 11:50 AM
to actual line feed Solomon Fried sfried sofried@yahoo.com
Is there a way to tell the editor not to convert escaped CR/LF sequences &.#.10;&.#.13; into actual cr/lf when I hit the "Indent XML Tags" toolbar button.
I have XSLT that contains staments like (I have placed periods between the characters in the escape strings so that it does not get translated when I post the message)
If I use the indent function, the escaped values are changed to actual line feeds and my xslt functions that use the $__crlf var, no longer work.
Subject:Re: Repress conversion of Author:(Deleted User) Date:21 Mar 2002 12:35 PM
At 12.01 21/03/2002 -0500, you wrote:
>From: "Solomon Fried"
>
>Is there a way to tell the editor not to convert escaped CR/LF sequences
>&.#.10;&.#.13; into actual cr/lf when I hit the "Indent XML Tags" toolbar
>button.
>I have XSLT that contains staments like
> (I have placed
> periods between the characters in the escape strings so that it does not
> get translated when I post the message)
>
>If I use the indent function, the escaped values are changed to actual
>line feeds and my xslt functions that use the $__crlf var, no longer work.
Hi Solomon,
unfortunately we cannot do much about it, as the entities are inside an
attribute value, and the XML parser is unable to report them to us.
However, you can achieve the same functionality (and be able to indent the
XSL file) if you use
(remove the extra dots and replace curly bracket with angle brackets).
Indentation will preserve the character entities, although they will be
replaced by their hexadecimal equivalent &.#.xD; and &.#.xA;