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

[css3-fonts] Typos and comments

From: Lobotom Dysmon <lobotom.da.dismon@free.fr>
Date: Thu, 28 Oct 2010 01:25:54 +0200
Message-ID: <4CC8B502.50804@free.fr>
To: www-style@w3.org
  Below are a few typos/editorial things I noted,
typos can still be found on latest version of the ED, dated 10 August 2010.

In 3.1 Font family: the font-family property:
In first paragraph:
"This allows for differences in available fonts across across platforms..."
Which makes one "across" too many.

In Chapter 4.3 Font reference: the src descriptor:
Example X says:
"...regardless whether a particular system locale parameter is set to 
Finnish or not"
I believe a more correct, and intended phrasing, would be "regardless 
_of_ whether".

Now about comments I feel may help improving the text:
About Chapter 4 Font Resources:
Since an _@font-face_ rule serves to build _font_families_ by mean of 
designating a resource (usually containing several style _faces_) so 
that a certain _face_ of this resource can be used when its 
_font-family_ descriptor's name is given in the _font-family_ property 
(and if I phrased it right one should already get my point about the 
ease to make this matter confusing) I think that outlining clearly the 
"face effects" and the "family effects" of @font-face is a clarity must-do.
Regarding this, my suggestion is an addition/edit to Chapter 4.1's first 
paragraph, from:
"Multiple @font-face rules can be used to construct font families with a 
variety of faces."
to
"Multiple @font-face rules with a unique [common?] font-family 
descriptor value can be used to construct font families with a variety 
of faces."
or
"Multiple @font-face rules with a unique font-family descriptor value 
can be used to construct a font family with a variety of faces."
which I believe would tie the loose ends of @font-face rule's purpose 
from the get-go.

Finally, in Chatper 5 Font matching algorithm:
In my opinion steps 1 and 2 could use a little rephrasing, even though 
I'm not sure what would be fit. Specifically, step on says user agent 
starts with the first family name, without saying what it starts doing 
with it, and step 2 puts family names and generic family names rather in 
one piece, and @font-face rules in the middle of it.

Trying to feedback my experience as a reader for any benefit it may bring.
Lobotom Dysmon
Received on Wednesday, 27 October 2010 23:26:37 GMT

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