Closed
Bug 258750
Opened 20 years ago
Closed 20 years ago
Poor rendering of japanese text with utf-8 encoding when no font-family is specified
Categories
(Camino Graveyard :: Preferences, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 175651
People
(Reporter: phiw2, Assigned: sfraser_bugs)
References
()
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a4) Gecko/20040909 Camino/0.8+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a4) Gecko/20040909 Camino/0.8+ see : http://dev.l-c-n.com/Gecko/Camino_japanese_utf-8.php When an (xhtml) page is served as utf-8, Camino cannot render the Japanese text correctly, unless a (Japanese) font-family is specified in the stylesheet. The test page shows 3 blocks of text; the first one renders incorrectly (no font-family specified, except 'sans-serif'), the second and third one have a font-family specified and render correctly. OS X 10.3.5, but happened on previous Panter releases This happens even if I set all font-preferences (unicode) to Hiragino. Reproducible: Always Steps to Reproduce: 1.see description 2. 3. Actual Results: Incorrect rendering of Japanese text; the kanjis are decent, the kanas... pooh. Expected Results: Render Japanese text decently, even if no font-family is specified.
Comment 1•20 years ago
|
||
looks exactly the same to me in firefox. dont' think it's camino specific. that said, the no-font-family looks the same, just a bit lighter. am i missing something?
Assignee: pinkerton → nobody
Status: UNCONFIRMED → NEW
Component: Page Layout → Layout: Fonts and Text
Ever confirmed: true
Product: Camino → Browser
QA Contact: core.layout.fonts-and-text
Version: unspecified → Trunk
![]() |
Reporter | |
Comment 2•20 years ago
|
||
Top part shos the poor rendering, bottom part show rendering with Osaka font specified.
![]() |
Reporter | |
Comment 3•20 years ago
|
||
(In reply to comment #1) > looks exactly the same to me in firefox. dont' think it's camino specific. that > said, the no-font-family looks the same, just a bit lighter. Firefox, and Mozilla render everything correctly, but Camino does not.
Comment 4•20 years ago
|
||
i see what you mean now (in the screenshot), but i don't see that kind of discrepancy on a stock us system. looks fine to me, only lighter.
![]() |
Reporter | |
Comment 5•20 years ago
|
||
Oops, wait a minute. I logged as another user (which never used Camino), creating a new profile for Camino... Then the japanese text renders correctly indeed. It never occured to me that something might be corrupted in my Camino profile, although there is nothing fancy or special in there. I only use Camino for testing pages under development. Sorry for the spam.
Comment 6•20 years ago
|
||
would be helpful to know what pref in your profile caused this difference.
![]() |
Reporter | |
Comment 7•20 years ago
|
||
(In reply to comment #6) > would be helpful to know what pref in your profile caused this difference. I don't think it's the profile. When I first tested the file under a different user (see #5), I hadn't set any preferences for Camino. I now just tested : 1/ test-user one is running OS X in English - setting the preferences for fonts in Camino, for Japanese, it reports missing fonts (Hiragino... ?, they all there and work fine in other browsers or apps.). I select the font to Hiragino font-family, Kaku Gothic W3 (not yet going into the advanced tab). As soon as I close the pref's window, my test-file displays incorrectly. 2/ test user two is running OS X in Japanese. Exactly the same problem; trying with Osaka font gives same result. Clicking the advance button: the pull down menu reports missing fonts, although I just set them (I think there are few bugs noted about this). (under both users, I compared the test file in Firefox (stock 0.9.3) and Safari, both always render it correctly). Hope this narrow down a bit the problem.
![]() |
||
Comment 8•20 years ago
|
||
Sounds like a Mac fonts bug, not a layout one....
Assignee: nobody → sfraser
Component: Layout: Fonts and Text → GFX: Mac
QA Contact: core.layout.fonts-and-text
![]() |
Reporter | |
Comment 9•20 years ago
|
||
The problem is specific to Camino. As said before: no problems whith other browsers (Gecko or others), and no problems with any other application my system when using Japanese fonts (daily working with Japanese texts). The various Hiragino fonts appears particularly sensitive to this. Other Gecko browsers have some problems with these fonts as well (bug 240841 and many others), but Camino appears more sensitive - it doesn't even recognize those fonts as preferences (I'll attach a screeenshot). Note - as a developper I can easily solve that main problem by specifying a font-family in the stylesheet.
![]() |
Reporter | |
Comment 10•20 years ago
|
||
Preferences > Appearance > Fonts > Japanese With a brand new profile.
The behavior in comment 7 is definitely bug 175651 (see bug 175651 comment 17; when Camino's font prefs show "missing" for Asian fonts, the correct font is used. When the user corrects the "missing" fonts, Gecko/Gfx:Mac doesn't know which font to use.) As far as I can tell, comment 7 sums up this bug, so it's a dupe. There are other serious i18n bugs/holes in Gfx:Mac, but this doesn't look like one of them. *** This bug has been marked as a duplicate of 175651 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
philippe, do you happen to still have that testcase sitting around? If so, could you attach it here?
Oops, moving this back to Camino since it was a Camino bug; sorry for the extra bugspam.
Component: GFX: Mac → Preferences
Product: Core → Camino
Version: Trunk → unspecified
You need to log in
before you can comment on or make changes to this bug.
Description
•