Re: Issue with Mozilla/Firefox & named anchor with Japanese/Korean character

Henri Sivonen wrote:
> In article <[email protected]>,
>  "kgs" <[email protected]> wrote:
> 
> 
>>I currently see a problem with named anchor that has Korean/Japanese
>>character. The hyperlink doesn't work . But it works fine if the

If you set 'netword.standard-url.encode-utf8' to true in about:config It 
should work fine.

> 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.)

It's now the standard (being an RFC in the standard track). See
http://www.faqs.org/rfcs/rfc3987.html  You can either %-encode URL or 
just use raw UTF-8 (with only URL-unsafe characters %-encoded)

The server at http://docs.hp.com/ko/allproducts.html understands 
%-encoded UTF-8 (IRI) but does not understand %-encoded EUC-KR (the 
document encoding).