16878 - [dogfood] non-ascii chars display incorrectly in the Subject field

Status: VERIFIED DUPLICATE of bug 16886

(MailNews Core :: Internationalization, defect, P1)

Description

[marina]

In the today's build compose window comes only in Plain text format. When
attempting to enter non-ascii chars into the Subject filed you're stuck there,
caption of the window though reflects your typing. Us-ascii are OK.
**** observerd with 1999-10-20-M11 Win build *****

Comment 1

[nhottanscp]

I used the same build, some Latin1 characters (alt+0223) cannot input others
(alt+0225) can type but got a wrong glyph.
This is reproducabe in other text field (e.g. search field in
home.netscape.com).
Reassigining to ftang since this is a generic key input problem.

Comment 2

[Frank Tang]

Naoki, could you find out what widget we are using there ? are we using
nsGfxTextControl ?

Comment 3

[nhottanscp]

Attachment: simple test for text widget

Comment 4

[nhottanscp]

It looks like the text is processed fine but drawing has the problem.
That can be tested by the html I attached.
Also in the mail, when I type alt+0225 in the subject then send, it sends á
correctly. Only the display is incorrect.

Comment 5

[marina]

After looking at this problem again i can add that when non-ascii are inputed
into the body they display fine but they disappear upon send.

Comment 6

[nhottanscp]

Reassign to ftang, changed the summary.

Comment 7

[Frank Tang]

The problem is not input but display . Somehow we display wrong for the font we
used in URL bar or Subject filed. You can easily reproduce in Composer after you
change the format to "PREFORMAT".

Reassign this to erik and change the summary from "[dogfood] Unable to view
input non-ascii chars correctly in the Subject field" to "[dogfood] non-ascii
chars display incorrectly in the Subject field"

Comment 8

[Frank Tang]

*** Bug 16997 has been marked as a duplicate of this bug. ***

Comment 9

[Frank Tang]

*** Bug 17022 has been marked as a duplicate of this bug. ***

Comment 10

[Frank Tang]

erik: please treat this as high priority. Look at those bug mark as dup of this
bug. It is everywhere ....

Comment 11

[kipp]

*** This bug has been marked as a duplicate of 16886 ***

Comment 12

[marina]

verified as such