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

Hi John,

> Even if defined with font-weight and font-style defaulting to "all",
> that means you're going to ignore bold and italic faces and use the
> normal face in all situations. That's not really a good way of defining
> what 'serif' means.

We're doing this at the moment without ignoring bold and italic, as 
described in my other email on the topic.

@font-face {
     font-family: serif;
     font-weight: all;
     font-style: all;
     src: local("Times New Roman")
}

will result in Times New Roman being used with the appropriate weight 
and style in Prince at the moment.

> Using your original font-family list, let's say you wanted to override
> the Arabic glyphs used in Times New Roman with Scheherazade instead.
> 
> @font-face {
>   font-family: Scheherazade;
>   src: url(ScheherazadeRegAAT.ttf) format("truetype-aat"), url(ScheherazadeRegOT.ttf) format("opentype");
> }
> 
> body: { font-family: Scheherazade, Times New Roman, OpenSymbol, ...; }

I find that a very compelling example. Perhaps what I'm looking for is 
an explicit way of creating a union font, eg.

@font-face {
     font-family: MyFont;
     src: union(font(local("Times New Roman"), url("times.ttf")),
             font(local("Symbol")))
}

apologies for the awful syntax, the idea is that MyFont would use Times 
New Roman and then Symbol for glyph fallback, where Times New Roman 
would either be the system font with that name or a a file if no system 
font with that name existed.

I'm not very enthusiastic about the proposed method of doing this with 
multiple @font-face rules, as it doesn't seem to make it clear what is 
going on. I can't say my example above is particularly attractive, but 
perhaps it hints at what I'm aiming for?

Cheers,

Michael

-- 
Print XML with Prince!
http://www.princexml.com

Received on Thursday, 22 January 2009 06:12:42 UTC