Closed
Bug 180914
Opened 22 years ago
Closed 17 years ago
Mozilla doesn't render Latin-1 and Latin Extended A/B chars using specified font
Categories
(Core Graveyard :: GFX: Mac, defect, P2)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
Future
People
(Reporter: nikd, Assigned: jshin1987)
References
Details
(Keywords: intl, testcase)
Attachments
(3 files)
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2b) Gecko/20021031 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2b) Gecko/20021031 When defining a stylesheet with the font stheiti (or stkeiti, stfangsong, stsong, other), Mozilla doesn't use this to render all content on a page. Specifically, Mozilla ignores the stylesheet definition for all Latin Extended A and B glyphs (Pinyin uses these), even though these are defined for the said fonts. This is not a TEC problem (bug 111728), according to Henri Sivonen, so we're filing this as a new bug. It is irrelevant what encoding is used (GB 18030, UTF-16, UTF-8). Reproducible: Always Steps to Reproduce: 1. Load testcase 2. Load screen dumps 3. Compare Actual Results: Mozilla is uselss rendering Pinyin Expected Results: Mozilla should render Pinyin flawlessly
Reporter | ||
Comment 3•22 years ago
|
||
This is how a Mac OS X app renders this. This is how it should be.
![]() |
||
Comment 5•22 years ago
|
||
There's a component for this. ;)
Assignee: asa → font
Component: Browser-General → Layout: Fonts and Text
QA Contact: asa → ian
Updated•22 years ago
|
Summary: Mozilla doesn't render using specified font → Mozilla doesn't render Latin Extended A/B chars using specified font
Updated•22 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reporter | ||
Comment 6•22 years ago
|
||
Note that ביםףתאטלעשֱֹֽ׃�ְָּׂ� are in Latin-1, a pretty common encoding.
Summary: Mozilla doesn't render Latin Extended A/B chars using specified font → Mozilla doesn't render Latin-1 and Latin Extended A/B chars using specified font
Reporter | ||
Comment 7•22 years ago
|
||
Btw, those Latin-1 chars caused Universal Auto-Detect to bring on Traditional Chinese.
Reporter | ||
Comment 8•22 years ago
|
||
Similar weird rendering at http://www.i18nguy.com/unicode-example.html Look at René Magritte, Céline Dion, Søren Kierkegård, François Truffaut, Rudi Völler for a starter with extremely common Latin-1 glyphs. The more "unusual" Latin glyphs (Extended A, Extended B, Latin Additional) look like they always have in Mozilla, although the fonts defined in the style sheet have the relevant glyphs. Some Greek and Cyrillic samples also look ****, while the Asian and Semitic samples render perfectly (minus Latinized Vietnamese, which uses Latin Ext. A and B heavily).
Updated•22 years ago
|
Priority: -- → P2
Target Milestone: --- → Future
Comment 13•20 years ago
|
||
Can someone check the status of this bug with latest 1.8 build? last checkin from bug 120401 should change something...
Assignee | ||
Comment 14•20 years ago
|
||
The patch for bug 120401 didn't fix this bug. Hmm... I need to run mozilla under gdb and see what's really going on... Taking this for now.
Assignee: core.layout.fonts-and-text → jshin
Component: Layout: Fonts and Text → GFX: Mac
Assignee | ||
Comment 15•20 years ago
|
||
What I think is happening is: 1. QuickDraw routine doesn't recognize that a Chinese font covers Latin-1 and extended Latin for Pinyin because they're not a part of Mac Simplified Chinese. 2. ATSUI fallback is invoked. However, ATSUI doesn't respect the current selected font and just picks a font that happens to cover Latin-1 and extended Latin We have to figure out a way to let ATSUI APIs know the current font and use it. Alternatively, we have to find a way to use ATSUI from the beginning without perf. hit.
Are bug 208037, bug 219426, bug 223823, bug 148361, or bug 158560 duplicates of this one or just similar-sounding? (This seems to be the only one with a developer postulating the underlying issue)
*** Bug 288094 has been marked as a duplicate of this bug. ***
Comment 18•17 years ago
|
||
WORKSFORME in current trunk
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•