Hello there,
Forgive me my dullness but is this something that is "fixed" with XSLT 2 ? I
came across the same issue recently and I still haven't found a good solution.
This is frustrating :(
- Sylvain
Selon Colin Paul Adams <colin(_at_)colina(_dot_)demon(_dot_)co(_dot_)uk>:
This is a problem, as a URI must be a subset of pure ASCII.
You can get round this by %-encoding the characters as their UTF-8 byte
hex values, but doing this within an XSLT 1.0 program is difficult.
No doubt Dimitre can come up with an FXSL solution.
--
Colin Adams
Preston Lancashire
--~------------------------------------------------------------------
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>
--~--
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
--~------------------------------------------------------------------
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>
--~--