[Indic] Characters in textfield and menu controls are cut off

NEW
Assigned to

Status

()

defect
15 years ago
10 years ago

People

(Reporter: craig.cummings, Assigned: smontagu)

Tracking

({intl})

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [oracle-nls])

Reporter

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040219
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040219

Indic characters (for Hindi, Gujurati, and Gurumukhi) in textfield and menu 
controls is cut off at bottom. The bottom third of the characters is cut off. 



Reproducible: Always
Steps to Reproduce:
1. Create a file with the following HTML: 

<html dir="rtl"> 
<body> 
<form> 
<input type="text"> 
</form> 
</body> 
</html> 

2. Open the HTML file in Mozilla
3. Select any Indic input method (e.g., Hindi), 
4. Type some Indic characters into the text input control.



Actual Results:  
Indic character input into the text input control or displayed by the menu
control have the bottom third of the character cut off.

Expected Results:  
The entire Indic glyphs should have been displayed rather than cut off.

Here is a Hindi HTML snippet that will reproduce the Indic menu control 
problem. 

<html> 
<body> 
<form> 
<select> 
  <option>&#2361;&#2367;&#2344;&#2381;&#2342;&#2368; 
  <option>&#2350;&#2352;&#2366;&#2336;&#2368; 
  <option>&#2344;&#2375;&#2346;&#2366;&#2354;&#2368; 
  <option>&#2360;&#2306;&#2352;&#2325;&#2371;&#2340;&#2307; 
</select> 
</form> 
</body> 
</html> 

This can be reproduced by simply running this HTML (you should set the browser
encoding to UTF-8). That is, input like the text input control is not required.

Comment 1

15 years ago
I can't reproduce the bug on Win2k with the test case given (i.e in <option>,
but I can reproduce it in <input> field. There seems to be a problem with the
font metric measurement (because the font - Mangal - uses a different baseline
convention than that used for Latin fonts ?) Some more data points:

1. MS IE6 is even worse (about the half of Hindic letters are cut off.) :-)
2. Tamil doesn't have this problem.

Btw, what is 'rtl' for? Indic scripts are all LTR. 
When your comment include non-ASCII characters, please, make sure to set View |
Character Encoding to UTF-8. It'd have been better if you just had attached the
test case instead of including it in your bug report.
Status: UNCONFIRMED → NEW
Component: Internationalization → Layout: CTL
Ever confirmed: true
Keywords: intl
Summary: [INDIC] CHARACTERS IN TEXTFIELD AND MENU CONTROLS ARE CUT OFF → [INDIC] CHARACTERS IN TEXTFIELD AND MENU CONTROLS ARE CUT OFF
Reporter

Comment 2

15 years ago
(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a)
Gecko/20040219
> Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a)
Gecko/20040219
> 
> Indic characters (for Hindi, Gujurati, and Gurumukhi) in textfield and menu 
> controls is cut off at bottom. The bottom third of the characters is cut off. 
> 
> 
> 
> Reproducible: Always
> Steps to Reproduce:
> 1. Create a file with the following HTML: 
> 
> <html dir="rtl"> 
> <body> 
> <form> 
> <input type="text"> 
> </form> 
> </body> 
> </html> 
> 
> 2. Open the HTML file in Mozilla
> 3. Select any Indic input method (e.g., Hindi), 
> 4. Type some Indic characters into the text input control.
> 
> 
> 
> Actual Results:  
> Indic character input into the text input control or displayed by the menu
> control have the bottom third of the character cut off.
> 
> Expected Results:  
> The entire Indic glyphs should have been displayed rather than cut off.
> 
> Here is a Hindi HTML snippet that will reproduce the Indic menu control 
> problem. 
> 
> <html> 
> <body> 
> <form> 
> <select> 
>   <option>&#2361;&#2367;&#2344;&#2381;&#2342;&#2368; 
>   <option>&#2350;&#2352;&#2366;&#2336;&#2368; 
>   <option>&#2344;&#2375;&#2346;&#2366;&#2354;&#2368; 
>   <option>&#2360;&#2306;&#2352;&#2325;&#2371;&#2340;&#2307; 
> </select> 
> </form> 
> </body> 
> </html> 
> 
> This can be reproduced by simply running this HTML (you should set the browser
> encoding to UTF-8). That is, input like the text input control is not required.

(In reply to comment #1)
> I can't reproduce the bug on Win2k with the test case given (i.e in <option>,
> but I can reproduce it in <input> field. There seems to be a problem with the
> font metric measurement (because the font - Mangal - uses a different baseline
> convention than that used for Latin fonts ?) Some more data points:
> 
> 1. MS IE6 is even worse (about the half of Hindic letters are cut off.) :-)
> 2. Tamil doesn't have this problem.
> 
> Btw, what is 'rtl' for? Indic scripts are all LTR. 
> When your comment include non-ASCII characters, please, make sure to set View |
> Character Encoding to UTF-8. It'd have been better if you just had attached the
> test case instead of including it in your bug report.
> 

> I can't reproduce the bug on Win2k with the test case given (i.e in <option>,
> but I can reproduce it in <input> field.

Sorry, yes, the option does, in fact, appear to be fine.

> 1. MS IE6 is even worse (about the half of Hindic letters are cut off.) :-)

My MS IE6 shows Hindi glyphs fine -- not cut off. Not sure the difference in our
test environment or why you see Hindi problems in IE <input>. Regardless, does
Mozilla want to be as bad as the competition or better?

> Btw, what is 'rtl' for? Indic scripts are all LTR. 

My apologies, I had the RTL version stuck in my clipboard from previous BiDi
Mozzy bugs that I was filing.

> It'd have been better if you just had attached the
> test case instead of including it in your bug report.

Thank you, will do so in future reports.

Comment 3

15 years ago
(In reply to comment #2)

> > 1. MS IE6 is even worse (about the half of Hindic letters are cut off.) :-)
 
> My MS IE6 shows Hindi glyphs fine -- not cut off. Not sure the difference in our
> test environment or why you see Hindi problems in IE <input>. 

Did you turn on complex script support on your Win2k (NT 5.0 is Win2k, right?)?
It seems like you did. Do you have any other Devanagari fonts other than Mangal
that comes with Win2k? I have RagHindi (from http://www.bbchindi.com) and
Code2000, but MS IE6 was configured to use Mangal for Devanagari. As I vaguely
recall, Indic scripts have  different 'baseline' conventions ('hanging'
baseline?) than those used for Western script so that I was wondering if Indic
fonts have font metrics the way we didn't expect them to be. 

> Regardless, does Mozilla want to be as bad as the competition or better?

  Hmm, is it a question? The answer is (needless to say), that we want to be
better. It was just a data point to help me and others understand the issue here.

P.S. Please, minimize the amount of quotation in your comment. I don't see any
point of including the whole text of comment #0 in your comment #2, which made
it a hard to read this bug unnecessarily.
Summary: [INDIC] CHARACTERS IN TEXTFIELD AND MENU CONTROLS ARE CUT OFF → [Indic] Characters in textfield and menu controls are cut off
Reporter

Comment 4

15 years ago
>that comes with Win2k?Did you turn on complex script support on your Win2k (NT
>5.0 is Win2k, right?)? It seems like you did.

Yes, complex script support on my W2K is on. That is, the Indic box is checked
in Regional Options in regarding to the configuration of reading/writing
ability. Or is there a different setting that you speak of?

> I have RagHindi (from http://www.bbchindi.com) and
>Code2000, but MS IE6 was configured to use Mangal for Devanagari.

Thanks for the link. Don't have this font. I do have a different Devanagari
fonts. I tried both direct input as well as setting the initial text value on
<input>. Setting Mozzy prefs for my test Devanagari font (from Monotype), the
browser showed Hindi glyphs in the text input field without them being cut-off
(in both cases). Cool. An interesting side effect of this test was that <option>
now displayed extra space below the typical baseline. Certainly a less severe,
rather cosmetic side effect.

> As I vaguely
>recall, Indic scripts have  different 'baseline' conventions ('hanging'
>baseline?) than those used for Western script so that I was wondering if Indic
>fonts have font metrics the way we didn't expect them to be. 

Might be, the certainly have vowel glyphs, for example, that stack below the
line. Seems strange how Mangal has a different baseline than my test font or
RagHindi. I'm checking with our font experts for their opinion as to the
differences.

>Hmm, is it a question? The answer is (needless to say), that we want to be
>better. It was just a data point to help me and others understand the issue >here.

Call me paranoid, but I have seen bugs closed for these very reasons (not
necessarily by the Mozzy folks). I don't want that to happen here. Thanks for
reassuring me that such would be unlikely to occur (at least for Mozilla).

> P.S. Please, minimize the amount of quotation in your comment. I don't see any
> point of including the whole text of comment #0 in your comment #2, which made
> it a hard to read this bug unnecessarily.

Yes, sorry, the browser didn't reset the text for this when I clicked between
different 'reply' links. Will be more careful next time.
Reporter

Updated

15 years ago
Whiteboard: [oracle-nls]

Updated

11 years ago
Component: Layout: CTL → Layout: Text
QA Contact: amyy → layout.fonts-and-text
Duplicate of this bug: 484126
You need to log in before you can comment on or make changes to this bug.