Note: There are a few cases of duplicates in user autocompletion which are being worked on.

In quoting under Plain Text option, Japanese period is placed too high



MailNews Core
18 years ago
9 years ago


(Reporter: Katsuhiko Momoi, Assigned: Erik van der Poel)


Windows NT

Firefox Tracking Flags

(Not tracked)




(3 attachments)



18 years ago
** Observed with 11/9/99 Win32 build (1999110911) **

The Japanese period is input via the period key on the US keyboard
when the JPN IME is on.
Here's the problem.

1. Choose a mail msg which already has a Japanese period in
   the text body. For example, the 2nd msg in the Smoketest file.
2. Select this msg and engage "Reply" button under Plain Text mail
   send option.
3. Note the positioning of the JPN period in the quoted text body.
   It is placed as high as the top of the other characters.
4.Note that in the subject header, the period is placed correctly slightly
  above the base line.
5. Interestingly, when you insert the cursor into the text body and
   input the JPN period, it is placed at the high position as well.

So somehow, the JPN period is positioned incorrectly in the
quoted Plain text mail composer.

Interestingly, if you start a new Plain Text compose window and
input the Japanese period, it is placed correctly at the base line.

See an illustration of this problem (via 2 contrasting images) at the
above URL.


18 years ago
QA Contact: lchiang → momoi

Comment 1

18 years ago
Created attachment 2751 [details]
HTML file with 2 contrasting images

Comment 2

18 years ago
Created attachment 2752 [details]
An image of the JPN period quoted too high

Comment 3

18 years ago
The 1st HTML failed to upload the accompanying images.
So, I'm uplaoding images directly.

1st image -- the JPN period is placed too high in the quoted
             Plain Text mail.
2nd image -- the JPn period apperas at the normal base line position
             when a new Plain Text mail composer is used.

Comment 4

18 years ago
Created attachment 2753 [details]
the JPN period apperas at the normal base line position in new Plain Text composer window


18 years ago
Assignee: ducarroz → buster
should a Ender widget display matter. Reassign to Ender folk

Comment 6

18 years ago
this maybe a dup of 17503

Comment 7

18 years ago
Bug 17503 refers to centering of normal text material in certain widgets.
This bug applies only when a body text is quoted as part of Reply
operation and under Plain Text mail send option only. There is something
else going on within quoted text.
For normal new mail compose, this problem does not exist.


18 years ago
Assignee: buster → ftang
Target Milestone: M13

Comment 8

18 years ago
asking ftang to take a quick look and see if he can narrow down the issue. Frank
-- please reassign to me after you review and comment -- thanks


18 years ago
Assignee: ftang → erik

Comment 9

18 years ago
erik- I think this is a GFX problem w/ a particular font face size combination.
I take a look at it in Momoi's cube. I cannot find out what Japanese font it
used to render the text.

Comment 10

18 years ago
I saw the same kind of problem before. In that case, vertical font was used
(Japanese period in vertical font is placed at upper right instead of lower left
of the normal horizontal font).


18 years ago
Target Milestone: M13 → M15

Comment 11

18 years ago
Is it easy to confirm Naoki's theory?
Will the font pref work might fix this, if we default to a non-vertical
font for Japanese?  But why would only the period be from picked from the
vertical font and not the other Japanese characters?

Comment 12

18 years ago
It's not really a theory, it's just a info that I saw the same problem in the
same code base before. That time, it happened in everywhere.
It may be checked by trying other characters which have different glyphs in
vertical (such as Japanese comma, parenthesis).

Comment 13

18 years ago
Yes, please try comma and other chars that look different in vertical fonts.
I disabled vertical fonts by ignoring all font names that start with '@' in the
global font enumerator (which is used when the algorithm reaches the end of the
font-family list without finding a match).

Comment 14

18 years ago
Moving all of my M15s to M16. Please add comments if you disagree.
Target Milestone: M15 → M16

Comment 15

18 years ago
Does this problem still occur? Leaving target at M16.

Comment 16

18 years ago
I don't think this happens any more under Windows. 
I looked at similar test cases to the original ones
which prompted me to file this bug. The additional condition
was to 1) Leave Unicode font setting at defaults on a new profile.

On quoted data under Japanese plain text mail, periods and
commas are displaying normally. 
I'm going to mark this "Worksforme" for Windows. There is
another bug filed for Linux and that is still a problem
without specific font settings.
Last Resolved: 18 years ago
Resolution: --- → WORKSFORME

Comment 17

18 years ago
Verified as Worksforme.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.