Jungshik Shin Reporter
	Description • 21 years ago

Bugzilla does better than Mozilla-mail in recognzing URIs with non-ASCII
characters (see bug 228543 comment #3 and attachment 137453 [details]), but it fails to
anchor the whole URI if the 'path' part has non-ASCII characters. Well, they're
not supposed to be there, but people use them as following:

http://株式会社アスキー.jp/ の 「株」
http://だいぎん.jp/ の 「だ」
http://トッパンフォームズ.jp/ の 「ム」
http://昭栄.jp/ の 「栄」

	Jungshik Shin Reporter
	Comment 1 • 21 years ago

Ooops. Sorry this bug is invalid unless the following URI (without space)
recognition fails as well.  I didn't realize that there are 'space' characters
following  '/' in all four cases. 

http://株式会社アスキー.jp/の株

	Jungshik Shin Reporter
	Comment 2 • 21 years ago

Even without space following '/', the path part is not recognized as a part of
the URI so that this bug is valid.

	Roland Mainz
	Comment 3 • 21 years ago

jshin:
BTW: What about filing a bug to make the default charset for
bugzilla.mozilla.org UTF-8 ?

	Jungshik Shin Reporter
	Comment 4 • 21 years ago

It's already filed by Markus Kuhn a long long time ago :-) See bug 135762.

	Roland Mainz
	Comment 5 • 21 years ago

Jungshik Shin wrote:
> It's already filed by Markus Kuhn a long long time ago :-) See bug 135762.

Cool... let's PUSH for that change... :)

	Dave Miller [:justdave]
	Comment 6 • 21 years ago

turning it on is a one-line change in the current version of Bugzilla (see bug
126266).  It won't happen on bugzilla.mozilla.org until someone comes up with a
feasible means of migrating the existing data (which is in different charsets in
different bugs (and sometimes even in different comments in the same bug).  See
bug 126266 comment 123.

	Jungshik Shin Reporter
	Comment 7 • 21 years ago

This is certainly off-topic here, but ....
Markus Kuhn, I and others already came up with a reasonable (in our opinion)
migration path (bug 126266 comment #112, bug 135762 comment #7), but the trouble
is that we haven't reached a consensus on that. The consequence is that as time
goes by, we accumulate more and more 'legacy' data that is hard to deal with
when we finally decide to migrate (unless somebody conjures up the character
encoding detector that is guaranteed to work  for even a very short chunk of
text like several bytes. Markus and my migration path don't call for such a
magic, but not everyone is satisfied with it). Hopefully, this will change with
bug 126266 fixed (as the first step toward the migration in a sense).

	Roland Mainz
	Comment 8 • 21 years ago

Can't we simply add a small hack in bugzilla which allows per-bugreport charset
ids and marks all NEW bug reports as UTF-8 ?

	Dave Miller [:justdave]
	Comment 9 • 21 years ago

and then you have non-utf8 non-ascii data showing up in buglists....

which I suppose is already toasted now if you get more than one in the same
list, so I guess that wouldn't be such a bad thing...

	Dave Miller [:justdave]
	Comment 10 • 20 years ago

Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist.  This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it.  If you
are dealing with this bug, please assign it to yourself.

	Teemu Mannermaa (:wicked)
	Comment 11 • 16 years ago

Link in comment #1 is now recognised correctly so I'd say this got fixed by the dependent bugs.