Mercurial > drafts / changeset

     1.1 --- a/css-fonts/Fonts.html	Tue May 28 17:37:06 2013 -0700
     1.2 +++ b/css-fonts/Fonts.html	Wed May 29 09:58:56 2013 +0900
     1.3 @@ -112,7 +112,7 @@
     1.4  
     1.5     <h1>CSS Fonts Module Level 3</h1>
     1.6  
     1.7 -   <h2 class="no-num no-toc" id=editors-draft-24-may-2013>Editor's Draft 24
     1.8 +   <h2 class="no-num no-toc" id=editors-draft-29-may-2013>Editor's Draft 29
     1.9      May 2013</h2>
    1.10  
    1.11     <dl id=authors>
    1.12 @@ -120,7 +120,7 @@
    1.13  
    1.14      <dd><a
    1.15       href="http://dev.w3.org/csswg/css-fonts/">http://dev.w3.org/csswg/css-fonts/</a>
    1.16 -     <!-- <dd><a href="http://www.w3.org/TR/2013/ED-css3-fonts-20130524/">http://www.w3.org/TR/2013/ED-css3-fonts-20130524/</a> -->
    1.17 +     <!-- <dd><a href="http://www.w3.org/TR/2013/ED-css3-fonts-20130529/">http://www.w3.org/TR/2013/ED-css3-fonts-20130529/</a> -->
    1.18       
    1.19  
    1.20      <dt>Latest version:
    1.21 @@ -713,7 +713,8 @@
    1.22      alternative for improved robustness.
    1.23    </dl>
    1.24  
    1.25 -  <p>Font family names must either be given quoted as <a
    1.26 +  <p>Font family names other than generic families must either be given
    1.27 +   quoted as <a
    1.28     href="//www.w3.org/TR/CSS21/syndata.html#strings">strings,</a> or unquoted
    1.29     as a sequence of one or more <a
    1.30     href="//www.w3.org/TR/CSS21/syndata.html#value-def-identifier">identifiers.</a>
    1.31 @@ -1488,8 +1489,8 @@
    1.32  
    1.33    <p class=note><em><strong>Note 1.</strong> To preserve readability, an UA
    1.34     applying these guidelines should nevertheless avoid creating font-size
    1.35 -   resulting in less than 9 device pixels per EM unit on a computer display
    1.36 -   .</em>
    1.37 +   resulting in less than 9 device pixels per EM unit on a computer
    1.38 +   display.</em>
    1.39  
    1.40    <p class=note><em><strong>Note 2.</strong> In CSS1, the suggested scaling
    1.41     factor between adjacent indexes was 1.5 which user experience proved to be
    1.42 @@ -2218,13 +2219,14 @@
    1.43  
    1.44    <p>This descriptor specifies the resource containing font data. It is
    1.45     required for the <code>@font-face</code> rule to be valid. Its value is a
    1.46 -   prioritized, comma-separated list of external references or locally
    1.47 -   installed font face names. When a font is needed the user agent iterates
    1.48 -   over the set of references listed, using the first one it can successfully
    1.49 -   activate. Fonts containing invalid data or local font faces that are not
    1.50 -   found are ignored and the user agent loads the next font in the list.
    1.51 -
    1.52 -  <p>As with other URLs in CSS, the URL may be partial, in which case it is
    1.53 +   prioritized, comma-separated list of external references or
    1.54 +   locally-installed font face names. When a font is needed the user agent
    1.55 +   iterates over the set of references listed, using the first one it can
    1.56 +   successfully activate. Fonts containing invalid data or local font faces
    1.57 +   that are not found are ignored and the user agent loads the next font in
    1.58 +   the list.
    1.59 +
    1.60 +  <p>As with other URLs in CSS, the URL may be relative, in which case it is
    1.61     resolved relative to the location of the style sheet containing the <span
    1.62     class=index-inst id=font-face0
    1.63     title="@font-face"><code>@font-face</code></span> rule. In the case of SVG
    1.64 @@ -2324,8 +2326,8 @@
    1.65     font and download it if it's not, <code>local()</code> can be used. The
    1.66     locally-installed <dfn
    1.67     id=font-face-name-value><var>&lt;font-face-name&gt;</var></dfn> argument
    1.68 -   is a format-specific string that uniquely identifies a single font face
    1.69 -   within a larger family. The syntax for a <a
    1.70 +   to <code>local()</code> is a format-specific string that uniquely
    1.71 +   identifies a single font face within a larger family. The syntax for a <a
    1.72     href="#font-face-name-value"><var>&lt;font-face-name&gt;</var></a> is a
    1.73     unique font face name enclosed by "local(" and ")". The name can
    1.74     optionally be enclosed in quotes. If unquoted, the unquoted font family
    1.75 @@ -2528,8 +2530,8 @@
    1.76     style implied by the underlying font data. This allows authors to combine
    1.77     faces in flexible combinations, even in situations where the original font
    1.78     data was arranged differently. User agents that implement synthetic
    1.79 -   bolding and obliqueing must only apply synthetic styling in cases where
    1.80 -   the font descriptors imply this is needed, rather than based on the style
    1.81 +   bolding and obliquing must only apply synthetic styling in cases where the
    1.82 +   font descriptors imply this is needed, rather than based on the style
    1.83     attributes implied by the font data.
    1.84  
    1.85    <h3 id=unicode-range-desc><span class=secno>4.5 </span>Character range: the
    1.86 @@ -2598,7 +2600,7 @@
    1.87     digit (e.g. "U+0???" = "U+0000-0FFF"). Wildcard ranges that extend beyond
    1.88     the range of valid Unicode codepoints are invalid. Because of this, the
    1.89     maximum number of trailing ‘<code class=css>?</code>’ wildcard
    1.90 -   characters is four, even though the <a
    1.91 +   characters is five, even though the <a
    1.92     href="http://www.w3.org/TR/CSS21/syndata.html#tokenization"><code
    1.93     title="UNICODE-RANGE token">UNICODE-RANGE</code></a> token accepts six.
    1.94  
    1.95 @@ -2611,7 +2613,7 @@
    1.96     the list of ranges into a list that is different but represents the same
    1.97     set of codepoints.
    1.98  
    1.99 -  <p>The associated font may not contain glyphs for the entire set of
   1.100 +  <p>The associated font might not contain glyphs for the entire set of
   1.101     codepoints defined by the ‘<a href="#descdef-unicode-range"><code
   1.102     class=property>unicode-range</code></a>’ descriptor. When the font is
   1.103     used the effective <a href="#character-map"><em>character map</em></a> is
   1.104 @@ -2878,7 +2880,7 @@
   1.105     guidelines</h3>
   1.106  
   1.107    <p>The <code>@font-face</code> rule is designed to allow lazy loading of
   1.108 -   fonts, fonts are only downloaded when needed for use within a document. A
   1.109 +   font resources that are only downloaded when used within a document. A
   1.110     stylesheet can include <code>@font-face</code> rules for a library of
   1.111     fonts of which only a select set are used; user agents must only download
   1.112     those fonts that are referred to within the style rules applicable to a
   1.113 @@ -3021,15 +3023,15 @@
   1.114     normalization.
   1.115  
   1.116    <p class=note> For authors this means that font family names are matched
   1.117 -   case insensitively, whether or not those names exist in a platform font or
   1.118 -   in the <code>@font-face</code> rules contained in a stylesheet. Authors
   1.119 -   should take care to ensure that names use a character sequence consistent
   1.120 -   with the actual font family name, particularly when using combining
   1.121 -   characters such as diacritical marks. For example, a family name that
   1.122 -   contains an uppercase A (U+0041) followed by a combining ring (U+030A)
   1.123 -   will <strong>not</strong> match a name that looks identical but which uses
   1.124 -   the precomposed lowercase a-ring character (U+00E5) instead of the
   1.125 -   combining sequence.
   1.126 +   case insensitively, whether those names exist in a platform font or in the
   1.127 +   <code>@font-face</code> rules contained in a stylesheet. Authors should
   1.128 +   take care to ensure that names use a character sequence consistent with
   1.129 +   the actual font family name, particularly when using combining characters
   1.130 +   such as diacritical marks. For example, a family name that contains an
   1.131 +   uppercase A (U+0041) followed by a combining ring (U+030A) will
   1.132 +   <strong>not</strong> match a name that looks identical but which uses the
   1.133 +   precomposed lowercase a-ring character (U+00E5) instead of the combining
   1.134 +   sequence.
   1.135  
   1.136    <h3 id=font-style-matching><span class=secno>5.2 </span>Matching font
   1.137     styles</h3>
   1.138 @@ -3489,7 +3491,7 @@
   1.139     User agents must also support fonts that only support kerning via data
   1.140     contained in a ‘<code class=property>kern</code>’ font table, as
   1.141     detailed in the OpenType specification. Authors may prefer to disable
   1.142 -   kerning in situations where performance is more important that precise
   1.143 +   kerning in situations where performance is more important than precise
   1.144     appearance. If the ‘<code class=property>letter-spacing</code>’
   1.145     property is defined, kerning adjustments are considered part of the
   1.146     default spacing, letter spacing adjustments are made after kerning has
   1.147 @@ -5049,6 +5051,13 @@
   1.148  font-feature-settings: dlig;           /* invalid, tag must be a string */
   1.149  </pre>
   1.150  
   1.151 +  <p>When values greater than the range supported by the font are specified,
   1.152 +   the behavior is explicitly undefined. For boolean features, in general
   1.153 +   these will enable the feature. For non-boolean features, out of range
   1.154 +   values will in general be equivalent to a 0 value. However, in both cases
   1.155 +   the exact behavior will depend upon the way the font is designed
   1.156 +   (specifically, which type of lookup is used to define the feature).
   1.157 +
   1.158    <p>Authors should generally use ‘<a href="#propdef-font-variant"><code
   1.159     class=property>font-variant</code></a>’ and its related subproperties
   1.160     whenever possible and only use this property for special cases where its