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

Re: new CSS3 Fonts edits

From: John Daggett <jdaggett@mozilla.com>
Date: Tue, 19 May 2009 01:17:56 -0700 (PDT)
To: Zack Weinberg <zweinberg@mozilla.com>
Cc: W3C Emailing list for WWW Style <www-style@w3.org>
Message-ID: <15260564.90071242721076937.JavaMail.root@cm-mail01.mozilla.org>

These are all reasonable, except I'm not sure why there needs to be a comma after "Ranges can overlap", that sentence seems to work either way.  Possibly my engrish is getting rusty. ;)

Edits pushed.


----- Original Message -----
From: "Zack Weinberg" <zweinberg@mozilla.com>
To: "John Daggett" <jdaggett@mozilla.com>, "W3C Emailing list for WWW Style" <www-style@w3.org>
Sent: Tuesday, May 19, 2009 2:16:26 AM GMT +09:00 Japan
Subject: Re: new CSS3 Fonts edits

John Daggett <jdaggett@mozilla.com> wrote:

> - unicode-range now defined for U+0-10FFFF

This sentence

# Ranges containing values greater than 10FFFF are also omitted.

would be more future-proof if it read

# Ranges are clipped to the domain of Unicode code points
# (currently 0 - 10FFFF inclusive); a range entirely 
# outside the domain is ignored.

It is not clear how to interpret "[a] range specified with '?' that
lacks an initial digit".  I suggest:

# Interval ranges consisting of a single codepoint are valid.
# Ranges specified with ‘?’ that lack an initial digit (e.g. "U+???")
# are also valid, and are treated as if there was a single 0 before
# the question marks (thus, "U+???" = "U+0???" = "U+0000-0FFF").
# "U+??????" is not a syntax error, even though "U+0??????" would be.

Also, I would recommend some editorial tweaks on that paragraph:

 - move the sentence beginning "Ranges that do not fit any of the
   above three forms..." to the beginning of the paragraph
 - add a comma after "Ranges can overlap"
 - change the comma before "they have no effect" to a semicolon

Received on Tuesday, 19 May 2009 08:18:37 UTC

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