Re: punycode vs. No such anchor

[Katsumi Yamaoka <yamaoka@xxxxxxx>]

In [emacs-w3m : No.11721] Aota-san wrote:
> jidanni@xxxxxxxxxxx writes:

>> When browsing
>> http://www.taipower.com.tw/cgi-bin/powerlimitread.pl?kind=d105a
>> one clicks
>> http://www.taipower.com.tw/cgi-bin/powerlimitread.pl?kind=d105a#01月16日
>> Only to get "No such anchor: 0xn--116-v08f53c"
>>
>> Obviously punycode confusion...
>>
>> OK, their anchors don't work in Firefox... but at least no punycode messages.

> I don't get the point.. You mean you want to get
> "No such anchor: 01月16日" instead?

I get the same behavior with Jidanni.  "0xn--116-v08f53c" is the
encoded version of "01月16日" that `w3m-url-transfer-encode-string'
generates.  This is not the essence of the problem, though.

The real cause is that the page in question provides a name
anchor as <a name="#01月16日">, not <a name="01月16日">.  If
there are many of such an illegally encoded html in the world,
we can add a workaround to emacs-w3m.  But I don't think it's
worth doing in the CVS repository.