How difficult can あ be

Character set issues can sometimes be troublesome. Here’s a simple URL.
It contains "あ" which is the Japanese letter corresponding to our "A".

http://bisqwit.iki.fi/jutut/aa/あ.txt

If you see a square or a question mark instead of a curvy symbol, you don’t have a Japanese font installed. That’s alright, because it does not matter in this test.

Copypaste this URL to IRC and ask people to tell what they see when they click it or copypaste to their browser.

The fact is that what they get depends on their IRC client, its encoding, their operating system and its configured language, and of the browser they use and its settings.

Note: If they see a ?.txt before even clicking the URL, the test bears no meaning.

Results

Here is a list of results so far (manually updated):
%E3%81%82.txt UTF-8 (normal url-encoding) - OK
%e3%81%82.txt UTF-8 (with lowercase url-encoding) - OK
%82%A0.txt Normal SHIFT-JIS encoding, technically OK
%A4%A2.txt Normal EUC-JP encoding, technically OK
%1B$B$%22%1B(B.txt Normal ISO-2022-JP encoding, technically OK
%1B$B$%1B(B.txt Broken ISO-2022-JP encoding (1 byte missing)
$B$(B.txt Broken raw ISO-2022-JP encoding (1 byte missing)
$B$%22(B.txt Broken ISO-2022-JP encoding (ESCs missing)
$B$"(B.txt Raw ISO-2022-JP encoding, technically OK
$".txt Broken ISO-2022-JP encoding (JIS shift codes missing)
B.txt Broken ISO-2022-JP encoding
%C3%A3%C2%81%C2%82.txt UTF-8 representation encoded in UTF-8, broken
%C3%A3%C2%81%E1%80%9A.txt ??? broken
%C2%A4%C2%A2.txt SHIFT-JIS representation encoded in UTF-8, broken
%c3%a3AB.txt First byte of UTF-8 representation encoded in UTF-8, urlencoded in lowercase, ???, broken
?.txt ?, broken

Author

Written by Joel Yliluoma