Item5928: solve encoding bug

\x{6211}\x{4eec}\x{77e5}\x{9053}\x{5728}firefox\x{91cc}\x{9762}\x{5b57}\x{4f53}url\x{8f6c}\x{7801}\x{548c}\x{4e0d}\x{8f6c}\x{7801}\x{662f}\x{6ca1}\x{6709}\x{4ec0}\x{4e48}\x{533a}\x{522b}\x{7684}\x{ff0c}\x{4f46}\x{662f}\x{5728}ie6\x{4e0b}\x{5fc5}\x{987b}\x{8981}url\x{8f6c}\x{7801}\x{ff0c}\x{5426}\x{5219}ie6\x{5c31}\x{4f1a}\x{6210}\x{4e3a}\x{4e71}\x{7801}\x{ff0c}(ie7\x{6b63}\x{5e38})\x{4e8e}\x{662f}\x{ff1a}
1\x{ff0c}\x{4fee}\x{6539}TWiki/Render.pm\x{6587}\x{4ef6}\x{ff1a}
\x{627e}\x{5230}\x{51fd}\x{6570}\x{ff1a}

sub makeAnchorName {

\x{5728}\x{51fd}\x{6570}\x{672b}\x{5c3e}\x{4fee}\x{6539}\x{8fd4}\x{56de}\x{503c}\x{4e3a}\x{ff1a}

return urlEncode($anchorName);

\x{63a5}\x{7740}\x{5728}\x{8be5}\x{51fd}\x{6570}\x{540e}\x{9762}\x{52a0}\x{4e0a}\x{51fd}\x{6570}urlEncode\x{ff1a}

sub urlEncode {
my $text = shift;
$text =~ s/([^0-9a-zA-Z-_.:~!*'\/%])/'%'.sprintf('%02x',ord($1))/ge;
return $text;
}

2\x{ff0c}\x{4fee}\x{6539}TWiki.pm\x{6587}\x{4ef6}\x{ff1a}
\x{627e}\x{5230}\x{51fd}\x{6570}\x{ff1a}

sub _make_params {

\x{4fee}\x{6539}\x{ff1a}

$anchor .= '#' . shift( @args );

\x{4e3a}

$anchor .= '#' . urlEncode(shift( @args ));

\x{5373}\x{53ef}\x{3002}

\x{8be6}\x{60c5}\x{89c1}\x{ff1a}http://my.huhoo.net/archives/2008/08/twiki422bug.html

-- TWiki:Main/CfcnAngel - 15 Aug 2008

The topic above is not readable at all.

And how can it be confimed when we cannot even read it?

Is this bug report in Chinese or what? This bug tracker does not use utf8 and the text above looks like it was copies from UTF8 text in non-english.

-- TWiki:Main.KennethLavrsen - 15 Aug 2008

I'm 99% sure that this is indeed in Chinese, because the provided backlink points to a copy which can be translated (cf. here). And we can always read the code, no?

If I understand correctly, the problem is that while URLs are encoded, arguments currently are not which may cause problems for certain (localised) setups--at least with IE6...

-- TWiki:Main.MarkusUeberall - 15 Aug 2008

Seems you already solved this Markus.

Thus, I'm closing this bug.

-- OlivierRaginel - 17 Dec 2008