Yes, that's a newer version (though of course it doesn't tell us what the changes are). > Location /Library/Fonts/Baskerville.ttc > Looks like they may have updated it? here's what's in the Info panel on Lion: OK, so Firefox definitely knows it exists - it's in our list of installed fonts. > Yes, also listed in the font list in Preferences -> Content in Firefox. (In reply to Alex Limi (:limi) - Firefox UX Team from comment #5) Looks like they may have updated it? here's what's in the Info panel on Lion: > Collection file at /Library/Fonts/Baskerville.ttc. > Preview/Show Font Info option) that they're installed as a TrueType > 6 faces (regular and italic of three different weights), and (using the > On my Mac (running 10.6), Font Book shows me that the Baskerville family has Yes, also listed in the font list in Preferences -> Content in Firefox. > (Content tab), and check whether it appears there. > Then look in the font list in Firefox prefs Yup, Baskerville is definitely there (and also standard in OS X, but smart to double check). Could you check in Font Book and verify that > So the question is why FF isn't using Baskerville on your machine, if the > existence of a family named Baskerville. > be expected behavior if, for some reason, the browser doesn't recognize the > font-family: Baskerville, Times, "Times New Roman", serif ), so this would > I notice that your font-family properties have Times as a fallback (e.g. Yup, that's exactly it, thanks for the fontspotting help. The difference is fairly subtle for the Regular > Offhand, it looks to me like much (all?) of the text is appearing in Times (In reply to Jonathan Kew (:jfkthame) from comment #3) You're right, Firefox actually does the right thing here in that particular case. > Looks to me like the other browsers are failing to apply the lowercase I didn't study all your CSS, but I did notice > However, I suspect in this case Firefox may be right, and the other browsers > This would be a separate issue from the failure to use Baskerville. Small-caps style doesn't seem to be working either. > (In reply to Alex Limi (:limi) - Firefox UX Team from comment #0) (In reply to Jonathan Kew (:jfkthame) from comment #4) I'm curious whether the Lion version is significantly different. The six faces are all marked as being version 6.1d5e1. On my Mac (running 10.6), Font Book shows me that the Baskerville family has 6 faces (regular and italic of three different weights), and (using the Preview/Show Font Info option) that they're installed as a TrueType Collection file at /Library/Fonts/Baskerville.ttc. Could you check in Font Book and verify that there's a Baskerville family? Then look in the font list in Firefox prefs (Content tab), and check whether it appears there. So the question is why FF isn't using Baskerville on your machine, if the other browsers can find it. font-family: Baskerville, Times, "Times New Roman", serif ), so this would be expected behavior if, for some reason, the browser doesn't recognize the existence of a family named Baskerville. I notice that your font-family properties have Times as a fallback (e.g. The difference is fairly subtle for the Regular face, but much more obvious in Italic. Offhand, it looks to me like much (all?) of the text is appearing in Times rather than Baskerville. I designed the layout in Firefox 3.6/4 on 10.6, and it looked correct at the time. I'm pretty sure this used to work (or still works) on OS X 10.5/10.6, but seems broken in 10.7. Looking at the font, it renders slightly differently, especially noticable in the "p" in "proposed", which makes me think it's using the wrong font variant. Small-caps style doesn't seem to be working either.Ĥ. The additional spacing here also seems to indicate that the wrong font and/or weight/spacing is being used.ģ. Should be a "fancy" italics version of the ampersand, but seems to either have the wrong typeface or doing a manual italicized version instead of picking the dedicated font variant.Ģ. Annotations from the image (Firefox is top left, Safari top right, Chrome bottom left):ġ. When loading in various browsers, notice how Firefox isn't rendering the fonts correctly. I'm pretty sure that these things used to work when I use Firefox on earlier versions of OS X, but I don't have one here to test with, so any help here would be appreciated. Image with annotations that describe differences
0 Comments
Leave a Reply. |