[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: punycode vs. No such anchor
- From: Hideyuki SHIRAI ($BGr0f=(9T(B) <shirai@xxxxxxxxxxx>
- Date: Fri, 13 Jan 2012 09:16:41 +0900 (JST)
- X-ml-name: emacs-w3m
- X-mail-count: 11723
- References: <877h0xd40z.fsf@xxxxxxxxxxx> <87boq96sop.fsf@xxxxxxxxx> <b4mk44wcw0s.fsf@xxxxxxx>
(BFrom: Katsumi Yamaoka <yamaoka@xxxxxxx> $B$5$s[)$/(B
(BSubject: [emacs-w3m:11722] Re: punycode vs. No such anchor
(BDate: Fri, 13 Jan 2012 08:59:31 +0900
(B> 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?
(B> I get the same behavior with Jidanni. "0xn--116-v08f53c" is the
(B> encoded version of "01$B7n(B16$BF|(B" that `w3m-url-transfer-encode-string'
(B> generates. This is not the essence of the problem, though.
(B> The real cause is that the page in question provides a name
(B> anchor as <a name="#01$B7n(B16$BF|(B">, not <a name="01$B7n(B16$BF|(B">. If
(B> there are many of such an illegally encoded html in the world,
(B> we can add a workaround to emacs-w3m. But I don't think it's
(B> worth doing in the CVS repository.
$B:rF|!"5$$K$J$C$F;n$7$F$?$i!"$J$s$H(B MS-IE $B$O(B # $B$D$$$F$$$F$bHt$Y$A$c(B
$B$$$^$7$?!*(BFirefox, Google chrome, opera $B$OEvA3(B NG$B!#(B