From 3fd51d527c5f525706f5d40d14603bb593e915a7 Mon Sep 17 00:00:00 2001 From: "Edward Z. Yang" Date: Fri, 31 Oct 2008 12:55:07 -0400 Subject: [PATCH] Add a nod to the RFC's recommendation that UTF-8 be used in URIs. Mentioned in http://unspecified.wordpress.com/2008/06/29/do-browsers-encode-urls-correctly/ Signed-off-by: Edward Z. Yang --- docs/enduser-utf8.html | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/enduser-utf8.html b/docs/enduser-utf8.html index 00dcdca9..9ff9da4c 100644 --- a/docs/enduser-utf8.html +++ b/docs/enduser-utf8.html @@ -589,8 +589,10 @@ looks something like: %C3%86. There is no official way of determining the character encoding of such a request, since the percent encoding operates on a byte level, so it is usually assumed that it is the same as the encoding the page containing the form was submitted -in. You'll run into very few problems if you only use characters in -the character encoding you chose.

+in. (RFC 3986 +recommends that textual identifiers be translated to UTF-8; however, browser +compliance is spotty.) You'll run into very few problems +if you only use characters in the character encoding you chose.

However, once you start adding characters outside of your encoding (and this is a lot more common than you may think: take curly