Bug 11054 – REGRESSION: Traditional Chinese encoding in login authentication

• Status: RESOLVED
• Resolution: FIXED
• Component: Page Loading

[Leevl]

This simplified Chinese site interprets/encodes one traditional Chinese character of my username unproperly during the login authentication. This character displays correctly in the input field of the login page, but turns scratched on the pop-up  with a warning of "username A??BC doesn't exist".

This bug does not exist in built-in Safari(419.3) and firefox(1.5-2.0b)

[Alexey Proskuryakov]

Could you please tell which character causes this problem?

[Leevl]

(In reply to comment #1)
> Could you please tell which character causes this problem?
> 

¹P£¨pen£©

[Alexey Proskuryakov]

Confirmed, we now encode this character, as if it weren't present in the encoding.

Another (probably related) issue with this page: although it specifies its charset as gb2312 and is rendered correctly by default, it is rendered as garbage in TOT if the charset is set to GB 2312 manually via Text Encoding menu.

[Alexey Proskuryakov]

Created attachment 10915 [details]
proposed fix

This patch fixes both issues; also, we now correctly handle the euro symbol (something that stock Safari doesn't do).

For more information, see: <http://en.wikipedia.org/wiki/GB2312>. I do not know why ICU has such a behavior with GB_2312-80.

[Darin Adler]

Comment on attachment 10915 [details]
proposed fix

I would have done it slightly differently (for example, I don't normally use !strcmp for string equality; I like strcmp == 0 because it has an "==" in it), but this looks good.

r=me

[Alexey Proskuryakov]

Committed revision 16807.

(In reply to comment #5)
> I like strcmp == 0 because it has an "==" in it),

Heh, so do I - but somehow I thought that WebKit style was !strcmp :). Corrected.

[Alexey Proskuryakov]

Reporter, could you please verify that this issue is fixed in the latest nightly build from <http://nightly.webkit.org>?