Re: Issue with Mozilla/Firefox & named anchor with Japanese/Korean character
Christian Biesinger <[email protected]>
| Newsgroups | gmane.comp.mozilla.internationalization |
|---|---|
| Organization | Another Netscape Collabra Server User |
| Message-ID | <[email protected]> |
Jean-Marc Desperrier wrote: > Henri Sivonen wrote: >> Nowadays the stance seems to be that non-ASCII in URIs should be >> (percent-encoded) UTF-8. (Note that there is no way for the URI to >> declare its encoding.) > > I'm not sure Mozilla implements that anywhere. It does. This is now the default. > URL inside HTML content are assumed to be in the encoding of the HTML > content. This is not true anymore... they will be sent as encoded UTF-8 to the server. > Outside, they are usually considered as in the system local encoding. Only for special types of URLs, iirc. (http, https, file, ftp) (http://lxr.mozilla.org/seamonkey/source/docshell/base/nsDefaultURIFixup.cpp#234)