W3C home > Mailing lists > Public > www-style@w3.org > September 2010

Re: [css3-fonts] @font-face matching and font-style descriptor

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 14 Sep 2010 09:46:44 -0700
Message-ID: <AANLkTinYjaq9z5itSCZTej+JGLTe2jSKL2pFUJ9ioAhy@mail.gmail.com>
To: Brad Kemper <brad.kemper@gmail.com>
Cc: Thomas Phinney <tphinney@cal.berkeley.edu>, John Hudson <tiro@tiro.com>, Sergey Malkin <sergeym@microsoft.com>, John Daggett <jdaggett@mozilla.com>, Sylvain Galineau <sylvaing@microsoft.com>, www-style@w3.org, www-font <www-font@w3.org>
On Tue, Sep 14, 2010 at 7:57 AM, Brad Kemper <brad.kemper@gmail.com> wrote:
>
> On Sep 14, 2010, at 4:00 AM, Thomas Phinney wrote:
>
>> I should clarify that I am not seeking a change in the default behavior, but if the existing behaviors are to persist, it would be a Very Good Thing if there were some mechanism to suppress or turn off all faux italics and faux bold.
>
> How about this:
>
> @font-face {
>  font-family: MyFont;
>  src: local(Arial);
> }
>
> @font-face {
>  font-family: MyFont;
>  src: local(Arial);
>  font-style:italic
> }
>
> @font-face {
>  font-family: MyFont;
>  src: local(Arial);
>  font-weight:bold;
> }

This is, indeed, the correct and already-working way to say "don't
synthesize my bold - I know exactly what I want for it".

Unless you want it to fallback to another font, for the
bold/italics/whatever, in which case you can just specify that font as
the italic face of your font-family.  (The only way this can go wrong
is if you have multiple font fallback stacks that all start with the
same font but then fallback to different fonts.  That's... definitely
an edge case.)

~TJ
Received on Tuesday, 14 September 2010 16:47:43 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:31 GMT