Hi, Tuesday, April 24, 2007, 9:54:28 AM, you wrote: > Firefox does it correctly, TB doesn't interpret the high-ASCII > characters correctly, if I understand RFC3986 correctly:
I am a bit confused as to that RFC because the HTML 3.2, 4.0 and 4.01 specifications specifically do not allow non-ASCII characters in URI attribute values. See http://www.w3.org/TR/html4/appendix/notes.html#h-B.2.1 [quote] Although URIs do not contain non-ASCII values (see [URI], section 2.1) authors sometimes specify them in attribute values expecting URIs (i.e., defined with %URI; in the DTD). For instance, the following href value is illegal: <A href="http://foo.org/Håkon";>...</A> We recommend that user agents adopt the following convention for handling non-ASCII characters in such cases: 1. Represent each character in UTF-8 (see [RFC2279]) as one or more bytes. 2. Escape these bytes with the URI escaping mechanism (i.e., by converting each byte to %HH, where HH is the hexadecimal notation of the byte value). [/quote] -- Robert ________________________________________________________ Current beta is 3.99.03 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
