W3C home > Mailing lists > Public > www-style@w3.org > January 2009

Re: [css3-fonts] new editor's draft

From: Michael Day <mikeday@yeslogic.com>
Date: Thu, 22 Jan 2009 18:03:35 +1100
Message-ID: <49781A47.10004@yeslogic.com>
To: John Daggett <jdaggett@mozilla.com>
CC: www-style <www-style@w3.org>

Hi John,

> So what happens with the rule below?
> @font-face {
>   font-family: serif;
>   font-weight: all;
>   font-style: all;
>   src: local("Times New Roman Bold Italic");
> }

This doesn't match anything, as there are no fonts installed on the 
system called "Times New Roman Bold Italic".

Prince cannot map non-italic text to an italic local font. (You could do 
it by specifying a URL source instead pointing to an italic font file, 
but why would you? :)

> This is *exactly* what the unicode-range feature allows you to do,
> it allows a set of fonts to be unioned together.  

Right, but in this case we don't know the coverage in advance, and we 
want to avoid using the Symbol font unless there really is no glyph 
found in the Times font, ie. we want a union that tries each font in 
turn until it finds something.



Print XML with Prince!
Received on Thursday, 22 January 2009 07:04:18 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:23 UTC