User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1 Ok, my name is François Gagné and when I submit a new bug, in the result page "Bug xxx Submitted" in the Reporter Field it's written: Fran?ois Gagn? It appear fine in other bugzilla pages. It's probably related to the page encoding. Reproducible: Always Steps to Reproduce:

What bugzilla version do you use? If it is cvs head or 2.21.1, did you enable UTF8?

This bug was spot on bugzilla.mozilla.org Also interesting to note, my name François Gagné was replace by François Gagné in my first post, the ç is the UTF8 for ç and é is the UTF8 for é

I'm willing to test this bug on a more recent bugzilla installation if you give me a URL.

The encoding is forced to UTF-8 on the enter_bug page on bugzilla.mozilla.org. Your "real name" field on your account is encoded in Windows-1252. The create account page is also forced to UTF-8, so you must have and older account or you've changed it recently. The show_bug page doesn't set an encoding because we have a lot of legacy data in a variety of character sets, so it relies on your browser's autodetect, which gets very confused when there's both UTF-8 and Windows-1252 on the same page. I just changed the coding on your real name to UTF-8. That should hopefully clear it up. This is a mozilla.org-specific problem. Upstream Bugzilla forces UTF-8 on everything these days.

Hmm, Firefox Auto-detect this page as windows-1252 and so it don't display my name correctly. Why not but a meta tag in this page to put the charset to UTF8. (Because pretty much every on this page should have been entered as UTF8 anyway?)

sry Dave, I just re-read your comment and my suggestion is void.

me again, sry for spamming, Firefox auto-detect works _fine_ on UTF8 only page.

(In reply to comment #5) > Hmm, Firefox Auto-detect this page as windows-1252 and so it don't display my > name correctly. Yeah, that's because comment 0 and comment 2 have mixed character sets in them so it confuses everything.

> Yeah, that's because comment 0 and comment 2 have mixed character sets in them > so it confuses everything. I don't get why everything shouldn't be in UTF8, I understand that the page encoding isn't force to UTF8 (for legacy reason) but why not force the entry of new data to UTF8? (put something like 'acceptcharset="utf-8" accept-charset="utf-8"') in the form tag)

(In reply to comment #9) > I don't get why everything shouldn't be in UTF8, I understand that the page > encoding isn't force to UTF8 (for legacy reason) but why not force the entry > of new data to UTF8? (put something like 'acceptcharset="utf-8" > accept-charset="utf-8"') in the form tag) That's bug 304149.