Closed
Bug 240841
Opened 21 years ago
Closed 18 years ago
Wrong display of special East-Asian characters
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: phiw2, Assigned: jshin1987)
References
()
Details
(Keywords: intl, testcase)
Attachments
(1 file)
840 bytes,
application/xhtml+xml
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7b) Gecko/20040316 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7b) Gecko/20040316 Special East-Asian characters coded using html entities in the range #93** display wrongly [numerics in circle, numerics between ()......]. This happens independently of the encoding of the page. Sample page: http://dev.l-c-n.com/Gecko/specialChar.php This happens both in Mozilla1.7b and Firefox nightly builds. Every other browser on Mac OS X (tested: Opera7.5pr4, Safari 1.2.1, IE5.23) and IE5.x on OS9 (japanese localisation) can display the characters correctly. Reproducible: Always Steps to Reproduce: 1.code an html doc with one of the characters mentioned 2.view page (see sample url) 3. Actual Results: The browser displays the wrong characters. see the screenshot included in the sample page. Expected Results: The browser should display the correct charaters [numerics in circle, numerics between (), numerics followed by a . (period), alpha-numerics between ()].
![]() |
||
Comment 1•21 years ago
|
||
Odd... I get the right rendering with a current Linux trunk build. Is this Mac-only?
Confirmed using Camino/2004041608. Whether encoded as decimal 9312, hex 2460 or embedded directly as a real Unicode character, the Circled Digit One character displays as an exclamation point on OS X. Reassigning to Layout: Fonts and Text.
Assignee: general → nobody
Severity: normal → major
Status: UNCONFIRMED → NEW
Component: Browser-General → Layout: Fonts and Text
Ever confirmed: true
Keywords: intl
QA Contact: general → core.layout.fonts-and-text
It does appear to work properly using Mozilla-Win/1.6, so this is probably Mac only.
Assignee | ||
Comment 4•21 years ago
|
||
This is certainly Mac only. Let me take it for the now (I may have a Mac soon...)
Assignee: nobody → jshin
Comment 5•21 years ago
|
||
dup of Bug 155551?
Assignee | ||
Comment 6•21 years ago
|
||
Philippe, can you switch fonts to Osaka (if what you use is Hirango(sp?)) and see if the problem goes away?
This isn't just about Japanese fonts. As shown by this testcase, some fonts do display the circled numbers correctly (TITUS Cyberbit Basic, Code2000, Arial Unicode MS and Osaka), but Lucida Grande fails (though it does contain these characters). (Note also the poor spacing of the characters using TITUS Cyberbit Basic. This is also evident in bug 174506. See bug 208037 for another Mozilla/TITUS Cyberbit Basic problem.)
![]() |
Reporter | |
Comment 8•21 years ago
|
||
(In reply to comment #6) > Philippe, can you switch fonts to Osaka (if what you use is Hirango(sp?)) and > see if the problem goes away? > I've update my test file (http://dev.l-c-n.com/Gecko/specialChar.php), linking two more test, one using Osaka[1] (works OK), one using Hiragino [2] (doesn't work). The original test file doesn't mention any font-family, except for 'sans-serif', and -for me- falls back on 'Optima', my default font in Gecko browsers. [1] http://dev.l-c-n.com/Gecko/specialChar_Osaka.php [2] http://dev.l-c-n.com/Gecko/specialChar_Hiragino.php
Assignee | ||
Comment 9•21 years ago
|
||
It seems that this bug is closely related with (if not a dupe of) bug 120401. Judging from my brief experiment, Mozilla has little trouble with 'dfont' (data fork font) but has trouble with otf (open type font) and ttf (Windows truetype font : I'm using the terminology used by MacOS font info.). As noted in bug 120401, Mozilla is ignorant of the true character coverage of those two types of fonts. Circled/parenthesized letters/numbers are not covered by JIS X 0201 and JIS X 0208 so that they can't be represented in Shift_JIS and EUC-JP. Therefore, Mozilla's character coverage evaluation based on the mapping between 'legacy character sets' and languages (Japanese -> Shift_JIS?) fails to recognize that 'Hiragino' has glyphs for circled/parenthesized letters/numbers. This explanation has some missing links (for instance, it can't explain why circled/parenthesized letters are rendered with '!', '#', etc)
Assignee | ||
Comment 10•21 years ago
|
||
At least, this bug depends on bug 120401. We'll see whether this bug is fixed completely by an upcoming patch for that bug.
Depends on: 120401
Assignee | ||
Comment 11•21 years ago
|
||
*** Bug 155551 has been marked as a duplicate of this bug. ***
Comment 12•21 years ago
|
||
This is fixed with the *last* patch for bug 120401 (this was a result of the quickdraw converter).
Comment 13•20 years ago
|
||
...it is not fixed anymore, becaue we restord the quickdraw converter (see last comments in bug 120401)... but it will be fixed in bug 254585.
![]() |
Reporter | |
Comment 14•18 years ago
|
||
Since the landing of Cairo (Bug 328116) and the use of ATSUI this now works correctly.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•