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

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

From: John Daggett <jdaggett@mozilla.com>
Date: Wed, 21 Jan 2009 00:03:39 -0800 (PST)
To: www-style <www-style@w3.org>
Message-ID: <24827398.6254521232525019669.JavaMail.root@cm-mail01.mozilla.org>


Zack Weinberg <zweinberg@mozilla.com> wrote:

> * The phrase "Ranges that do not follow the syntax above" is
>   confusing; suggest "Ranges that do not fit any of the above
>   three forms".
> 
> * The term "ranges that have no meaning" is defined only by a
>   nonexhaustive example -- if you mean "interval ranges where
>   the second number is less than the first" please say so.
> 
> * You do not say what happens if some of the ranges in a list
>   overlap each other.
> 
> * You do not say what happens if ranges specify code points greater
>   than U+10FFFF.

Edits for these pushed.

> > * Define which names are allowed with local().
> 
> This still does not give *syntax* for what goes inside the parentheses,
> we need a specification in terms of CSS tokens.  I suggest
> 
>   <font-face-name> : "local(" [ ID | STRING ] ")"

There are two issues here.  The first is whether or not to *require*
quotes (since it's a string) and the second is the meaning of the value,
what within font data it should match.

For the first issue related mainly to syntax, CSS has never enforced
family names to be strict strings, quotes are not required.  So it seems
natural to want to do the same with names within local().  Same for
format(), as previously noted here:

http://lists.w3.org/Archives/Public/www-style/2008Jun/0199.html

In your suggestion, what does 'ID' imply exactly, a CSS identifier?

As for the second issue, what the name within local() means, it will
vary with format but I think we need to define this clearly for TrueType/OpenType 
fonts to assure cross-platform consistency.  Using the full
name name from the TrueType/OpenType name table indicates a specific
piece of font data to match against but even that has problems; some
fonts include localized names for these and I think we probably need to
explicitly include or exclude these to avoid the problem of name
matching being localization-dependent.

John Daggett
Mozilla Japan
Received on Wednesday, 21 January 2009 08:04:22 GMT

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