[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: punycode vs. No such anchor
- From: Katsumi Yamaoka <yamaoka@xxxxxxx>
- Date: Fri, 13 Jan 2012 08:59:31 +0900
- X-ml-name: emacs-w3m
- X-mail-count: 11722
- References: <877h0xd40z.fsf@xxxxxxxxxxx> <87boq96sop.fsf@xxxxxxxxx>
In [emacs-w3m : No.11721] Aota-san wrote:
(B> jidanni@xxxxxxxxxxx writes:
(B>> When browsing
(B>> one clicks
(B>> Only to get "No such anchor: 0xn--116-v08f53c"
(B>> Obviously punycode confusion...
(B>> OK, their anchors don't work in Firefox... but at least no punycode messages.
(B> I don't get the point.. You mean you want to get
(B> "No such anchor: 01$B7n(B16$BF|(B" instead?
(BI get the same behavior with Jidanni. "0xn--116-v08f53c" is the
(Bencoded version of "01$B7n(B16$BF|(B" that `w3m-url-transfer-encode-string'
(Bgenerates. This is not the essence of the problem, though.
(BThe real cause is that the page in question provides a name
(Banchor as <a name="#01$B7n(B16$BF|(B">, not <a name="01$B7n(B16$BF|(B">. If
(Bthere are many of such an illegally encoded html in the world,
(Bwe can add a workaround to emacs-w3m. But I don't think it's
(Bworth doing in the CVS repository.