Closed Bug 26852 Opened 25 years ago Closed 25 years ago

Japanese period is placed too high in the subject field.

Categories

(MailNews Core :: Composition, defect, P3)

Other
Linux
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 26182

People

(Reporter: ji, Assigned: rhp)

References

Details

(Keywords: platform-parity)

For linux builds, starting from 2000020408 build, the Japanese period is placed too high in the subject field. And in the plain text mode, on the mail compose window it appears too high in the mail body as well. This might be a dup of bug 18436. Since bug 18436 has this problem in the reply mail, so I'm filing this in case it's a new problem.
Is that only for a period? Could you also try Japanese comma, parenthesis?
Japanese comma is placed too high as well. But Japanese ( , {, and [ are okay.
Reassign to erik, looks similar to bug 18436.
Assignee: nhotta → erik
Status: NEW → ASSIGNED
Target Milestone: M16
changing QA contact
QA Contact: lchiang → ji
I believe it's picking up the Daewoo font, which has high period and comma. It ought to pick up a Japanese font, of course. We need LANG attribute support for this (bug 26237). The Subject field may also need to be changed, to pass the language down to the font engine. Marking dependency on bug 26237, and reassigning this bug to Naoki, who may know who owns the Subject field.
Assignee: erik → nhotta
Status: ASSIGNED → NEW
Depends on: 26237
ji, the subject in thread pane or else?
The subject in the message view pane. Period in the thread pane is in the right place.
Reassign to rhp, cc to mscott. The bug is depending 26237 - implement LANG attribute handling in layout. For mail compose problem, please test again since 18436 is now FIXED. If not fixed, open a separate bug.
Assignee: nhotta → rhp
Keywords: pp
Target Milestone: M16
I could be wrong, but I think I already have a bug to track this issue. - rhp *** This bug has been marked as a duplicate of 26182 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Verified as such.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.