This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Special Characters in URLs
- To: "'xsl-list at lists dot mulberrytech dot com'" <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] Special Characters in URLs
- From: Eriksson Magnus <Magnus dot eriksson at softronic dot se>
- Date: Tue, 19 Jun 2001 18:00:43 +0200
- Reply-To: xsl-list at lists dot mulberrytech dot com
Thanks for the help, Chris.
Yes, the URIs are interpreted by the Web Server/Web browser but I need them
to be generated correctly by the XSLT processor -- to comply with the
HTTP-standard (e.g. no white space in URLs). Is there a way to achieve this?
Regards,
Magnus Eriksson
-----Original Message-----
From: Christopher R. Maden [mailto:crism@maden.org]
Sent: den 19 juni 2001 13:37
To: xsl-list@lists.mulberrytech.com
Subject: RE: [xsl] Special Characters in URLs
At 04:12 19-06-2001, Eriksson Magnus wrote:
>I'm sorry, I don't really understand. I have encoding set to iso-8859-1 for
>the xsl:stylesheet and the xsl:output elements, why would it replace it
with
>the UTF-8 values? How should go about doing this, with characters not valid
>for the URL replaced with their HTTP/URL replacement (e.g. " " replaced
with
>"+", "+" with "%2B" etc)?
The content of the document should be encoded in ISO 8859-1, yes. But a
URI is interpreted by a URI resolver such as a Web server, not an XML
parser, so the rules for encoding are different. The rules for URI
encoding are described in RFC 2718 (§2.2.5) and in the W3C
internationalization guidelines (er... somewhere).
IE 5, at least, interprets this correctly, as does (IIRC) Mozilla 5 and
Netscape 6, and Opera 4.
-Chris
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list