W3C home > Mailing lists > Public > www-font@w3.org > July to September 2009

Re: Problems with style-linked EOTs

From: Aryeh Gregor <Simetrical+w3c@gmail.com>
Date: Wed, 22 Jul 2009 13:23:29 -0400
Message-ID: <7c2a12e20907221023n6e807e30t68fbb00d26189348@mail.gmail.com>
To: Laurence Penney <lorp@lorp.org>
Cc: John Daggett <jdaggett@mozilla.com>, www-font <www-font@w3.org>
On Wed, Jul 22, 2009 at 10:55 AM, Laurence Penney<lorp@lorp.org> wrote:
> Could you elaborate on the problems IE has with bold and italic styles?

My understanding is that, effectively, if a @font-face is being used,
font-style/font-weight/etc. are simply ignored by IE.  More
specifically, there's no way to tell it which fonts to substitute for
bold/italic/etc., so it can't respect those directives.  You could
still get bold/italics, it's just a minor pain.  You'd have to change
the font-family along with every font-style/font-weight change, like

body { font-family: myfont; }
b { font-weight: bold; font-family: myfont-bold; }

Moreover, it makes almost no difference at all for header fonts, since
you're unlikely to have some parts of the header italicized or bolded
but not other parts.  Header fonts are the biggest use-case for
@font-face anyway, as far as I understand, so I don't think this
deficiency of IE is a deal-breaker at all.  If you do want to use a
custom font and have bold and italics work right, it's somewhat
hackish but should still work okay in most cases.

I haven't tested this, though, and could be way off the mark.
Received on Wednesday, 22 July 2009 17:24:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 11 June 2011 00:14:03 GMT