Closed Bug 581633 Opened 15 years ago Closed 14 years ago

Italic text uses different font on some websites

Categories

(Camino Graveyard :: Page Layout, defect)

1.9.2 Branch
PowerPC
macOS
defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: wakky_sack, Unassigned)

References

()

Details

(Whiteboard: [CLOSEME - 10/24])

Attachments

(2 files)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en; rv:1.9.2.8pre) Gecko/20100722 Camino/2.1a1pre (like Firefox/3.6.8pre) Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en; rv:1.9.2.8pre) Gecko/20100722 Camino/2.1a1pre (like Firefox/3.6.8pre) With Camino 2.1a1pre, instead of staying in the same font family as plain text, italicized text uses a different font. But I don't see it on every website; so far, I've seen it consistently on Wikipedia, where a semi-cursive font gets used, and forums.dpreview.com, where it appears to be Times New Roman italic (or some other similar serif font). The italicized text appears smaller than the plain text as well. It's a little jarring, and more importantly, the size difference makes it more difficult to read. I do not see this when I go to the same pages with Safari or Camino 2.0.3. Reproducible: Always Steps to Reproduce: 1. Go to Wikipedia. 2. Find any page with italic text. 3. Actual Results: I see italic text in a different font. It looks a little odd next to the usual sans serif plain text. Expected Results: It should have used the same sans serif plain text, only italicized.
Did you specify a different font for sans-serif in the Camino preferences, e.g. one that lacks an italics face ? Wikipedia uses your default settings (for the default Camino settings, that would be Helvetica).
(In reply to comment #1) I have never changed the font settings for any version of Camino I have ever used.
Is this still an issue with the latest nightly: http://caminobrowser.org/contribute/#nightly ?
Whiteboard: [CLOSEME - 10/24]
Closing as INCOMPLETE, since we never got an answer to comment 3.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
(In reply to comment #3) Sorry, I've been extremely busy lately. Yes, the bug persists as of the latest nightly build.
<:sigh:> Have you tried clearing all font caches ? (re-)Starting your Mac in Safe Mode will do this: 1. Shut down the computer. 2. Press the power button. 3. Immediately after you hear the startup tone, press and hold the Shift key. 4. Release the Shift key when you see the gray Apple and progress indicator. During startup in Mac OS X v10.4.x or later, you will see "Safe Boot" on the login window, even if normally you log in automatically. While in Safe Mode, check if the issue still happens. To leave Safe Mode, restart the computer normally, without holding any keys during startup. or (on 10.4) you can simply remove the font caches folder, then log out and log in: /Library/com.apple.ats (that is the top level Library folder, not the user level one)
(temporarily reopening this pending answers to comment 6)
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: INCOMPLETE → ---
(In reply to comment #6) > Have you tried clearing all font caches ? I tried clearing the font cache, and it does no good.
Did you try in safe mode ? (restarting your Mac while holding the Shift key as noted in comment 6) - this will (temporarily) disable all user installed fonts. Alternatively, can you try a different user account on your Mac (assuming you installed third party fonts in ~/Library/Fonts). Another thing you may want to try is check / validate your fonts with Font book - Open Font book (Applications/Font Book) and from the File menu: Validate. --- I suspect you may have a third party font that runs afool of the Gecko font code.
(In reply to comment #9) > I suspect you may have a third party font that runs afool of the Gecko font > code. I'll check it out. Has the code changed since 2.0.x? Because I don't have this problem with the stable release.
(In reply to comment #10) > I'll check it out. Has the code changed since 2.0.x? Because I don't have > this problem with the stable release. Yes, the Gecko font code has seen significant changes since 2.0.x (and the ability to "fake" italics for fonts that don't have italics even broke once, a long time ago, iirc). Also, can you take a screenshot of what you're seeing and attach it here? It sounds from your description that an entirely different font is being used for italic text, but a screenshot of the problem would let us at least see what you're seeing. Also, do you have the same problem if you view the pages with Firefox 3.6.x?
Here's what I see (hope the image host is okay): http://img199.imagevenue.com/img.php?image=72907_ishot_1_122_256lo.jpg I see this with both the Camino nightly build, and Firefox 3.6.x. I validated my fonts, and found a bad font. I deleted it, rebooted, and checked again, and the problem persisted. However, rebooting in Safe Mode alleviated the problem. So I guess there's another font that validates just fine, but still clashes with the Gecko font code? BTW, I scrolled through my entire Font Book, and that font isn't in it.
For future reference, you can attach screenshots directly to the bug using the "Add attachment" link just above the first comment. :) > I validated my fonts, and found a bad font. Out of curiosity, do you recall what font it was? > I deleted it, rebooted, and > checked again, and the problem persisted. However, rebooting in Safe Mode > alleviated the problem. Rebooting in Safe Mode will clear the font caches; simply disabling or even deleting the font won't. > So I guess there's another font that validates just > fine, but still clashes with the Gecko font code? BTW, I scrolled through my > entire Font Book, and that font isn't in it. I'm confused; you still see the problem in "normal-boot" sessions even after you've deleted the problem font and then rebooted in Safe Mode once?
(In reply to comment #13) > For future reference, you can attach screenshots directly to the bug using the > "Add attachment" link just above the first comment. :) Whoops, didn't notice that, thanks. :) > Out of curiosity, do you recall what font it was? I don't, but it had some weird name, with some underscores in it. Like "somethingsomething-sys___.ttf" and I think it was identified as a Microsoft font. > I'm confused; you still see the problem in "normal-boot" sessions even after > you've deleted the problem font and then rebooted in Safe Mode once? Actually, I booted in Safe Mode before deleting the bad font. After finding the bad font, I deleted it, then cleared the font cache manually as per the instructions in Comment 6, and rebooted normally. Do I need to boot into Safe Mode again?
(In reply to comment #14) > > I'm confused; you still see the problem in "normal-boot" sessions even after > > you've deleted the problem font and then rebooted in Safe Mode once? > > Actually, I booted in Safe Mode before deleting the bad font. After finding > the bad font, I deleted it, then cleared the font cache manually as per the > instructions in Comment 6, and rebooted normally. Do I need to boot into Safe > Mode again? No; we just want to know if you're at all able to reproduce the problem after having booted in Safe Mode the one time. If the theory Smokey's working on is correct, the answer to this question is "I can no longer reproduce this problem at all, whether booted in Safe Mode or normal mode."
(In reply to comment #15) > No; we just want to know if you're at all able to reproduce the problem after > having booted in Safe Mode the one time. If the theory Smokey's working on is > correct, the answer to this question is "I can no longer reproduce this problem > at all, whether booted in Safe Mode or normal mode." Okay, here's how it went: 1) Deleted font cache manually and rebooted normally - problem persisted 2) Booted into Safe Mode - problem disappeared 3) Rebooted normally - problem returned 4) Validated fonts - found and deleted bad font 5) Deleted font cache manually and rebooted normally - problem persisted So the only time I can't reproduce the problem is when I boot into Safe Mode.
Booting in Safe mode disables all third-party, user installed fonts (fonts that are not installed by the OS). For a list of pre-installed fonts, see this Wikipedia article: http://en.wikipedia.org/wiki/List_of_typefaces_included_with_Mac_OS_X). Apparently (based on your screenshot), you have a cursive type font installed that trips the Gecko font code.
Worse yet, that's Cochin, a default font on most Macs.
wakky_sack, can you also have Font Book check for duplicate fonts? I'm not sure about the Font Book UI on 10.4, but on 10.5 any fonts that have duplicates have a dot to the right of their names, and there's a "Resolve Duplicates" item in the Edit menu that will apparently do a best-guess automatic disabling of the duplicate fonts (or you can manually disable one font out of each pair). My working theory now is that you've got a duplicate of whatever Wikipedia is using for the italic face there (Helvetica Oblique if you've not changed Camino's font settings), and the OS is known to choose random fonts sometimes when duplicate fonts are involved! However, just to cover some other bases, can you also load this testcase https://bug396002.bugzilla.mozilla.org/attachment.cgi?id=280694 and verify that the appearance matches https://bug396002.bugzilla.mozilla.org/attachment.cgi?id=282656
Version: unspecified → 1.9.2 Branch
(In reply to comment #19) I didn't see any duplicate fonts, but I resolved them anyway. Loading the test case, the appearance isn't 100% the same - there are slight differences in size, spacing, the slant of the oblique characters, and the exact shade of red - but for the most part it's the same.
Did resolving duplicates fix the issue, or are you still seeing random font(s) for italics?
Attached file test case
Hmm, that test case posted in comment 19 has one problem - it explicitly specifies Helvetica. Attached is the same test case but doesn't specify that font (it matches what Wikipedia does). Does this display correctly (approx. the same as the screenshot linked in comment 19)?
(In reply to comment #22) > Does this display correctly (approx. the same as the screenshot linked in > comment 19)? That one displays correctly. Smokey, I'm still seeing Cochin for italics. (Thanks for identifying the font, Raymie!)
ResovingWFM per comment from reporter, issue was duplicate font.
Status: REOPENED → RESOLVED
Closed: 15 years ago14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: