This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Implementing " and ' in literals
- To: "'xsl-list at mulberrytech dot com'" <xsl-list at mulberrytech dot com>
- Subject: RE: Implementing " and ' in literals
- From: Kay Michael <Michael dot Kay at icl dot com>
- Date: Tue, 25 Apr 2000 10:00:12 +0100
- Reply-To: xsl-list at mulberrytech dot com
> Actually using C style backslash escaping would be rejected by other
> parsers, I believe. So that's probably a better long term
> solution (and it's prettier too!).
The string '\n' is perfectly legal in XPath 1.0 and means backslash followed
by letter 'n'. In fact there are no reserved characters in XPath 1.0 strings
and there is therefore no way of introducing an escape convention
retrospectively, which is why I suggested using a different delimiter.
In fact I think the best approach would be to use the only extension
capability allowed by the XPath syntax, which is an extension function. You
could allow the user to write:
x:escape('He said, \qI won\at!\q')
and interpret \q as double-quote and \a as single-quote.
Mike Kay
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list