1.1 --- a/css-fonts/Fonts.html Fri May 31 14:54:16 2013 +0900
1.2 +++ b/css-fonts/Fonts.html Fri May 31 15:40:35 2013 +0900
1.3 @@ -1847,8 +1847,10 @@
1.4 stylesheet. Values for the <a href="#propdef-font-variant"
1.5 title="font-variant!!property">‘<code
1.6 class=property>font-variant</code>’</a> property may also be included
1.7 - but only those supported in CSS 2.1, none of the font-variant values added
1.8 - in this specification can be used in the <span class=property>‘<a
1.9 + but only those supported in CSS 2.1, none of the <a
1.10 + href="#propdef-font-variant" title="font-variant!!property">‘<code
1.11 + class=property>font-variant</code>’</a> values added in this
1.12 + specification can be used in the <span class=property>‘<a
1.13 href="#propdef-font"><code class=property>font</code></a>’</span>
1.14 shorthand:
1.15
1.16 @@ -3420,24 +3422,25 @@
1.17 provide glyphs for a wide range of ligatures, contextual and stylistic
1.18 alternates, tabular and old-style figures, small capitals, automatic
1.19 fractions, swashes, and alternates specific to a given language. To allow
1.20 - authors control over these font capabilities, the font-variant property
1.21 - has been expanded for CSS3, it now functions as a shorthand for a set of
1.22 - properties that provide control over stylistic font features.
1.23 + authors control over these font capabilities, the ‘<code
1.24 + class=property>font-variant</code>’ property has been expanded for CSS3.
1.25 + It now functions as a shorthand for a set of properties that provide
1.26 + control over stylistic font features.
1.27
1.28 <h3 id=glyph-selection-positioning><span class=secno>6.1 </span>Glyph
1.29 selection and positioning</h3>
1.30
1.31 <p>Simple fonts used for displaying Latin text use a very basic processing
1.32 - model, fonts contain a <a href="#character-map"><em>character map</em></a>
1.33 - which maps a given character to a glyph for that character. Glyphs for
1.34 - subsequent characters are simply placed next in line along a run of text.
1.35 - Font formats such as OpenType and AAT (Apple Advanced Typography) use a
1.36 - richer processing model, the glyph for a given character can be chosen and
1.37 - positioned not just based on a single character, but also based on
1.38 - surrounding characters along with the language, script, and features
1.39 - enabled for the text. Font features may be required for specific scripts,
1.40 - or recommended as enabled by default or they may be stylistic features
1.41 - meant to be used under author control.
1.42 + model. Fonts contain a <a href="#character-map"><em>character map</em></a>
1.43 + which maps each character to a glyph for that character. Glyphs for
1.44 + subsequent characters are simply placed one after the other along a run of
1.45 + text. Modern font formats such as OpenType and AAT (Apple Advanced
1.46 + Typography) use a richer processing model. The glyph for a given character
1.47 + can be chosen and positioned not just based on the codepoint of the
1.48 + character itself, but also on adjacent characters as well as the language,
1.49 + script, and features enabled for the text. Font features may be required
1.50 + for specific scripts, or recommended as enabled by default or they might
1.51 + be stylistic features meant to be used under author control.
1.52
1.53 <p>For a good visual overview of these features, see the <a
1.54 href="#OPENTYPE-FONT-GUIDE"
1.55 @@ -3446,40 +3449,43 @@
1.56 href="#WINDOWS-GLYPH-PROC"
1.57 rel=biblioentry>[WINDOWS-GLYPH-PROC]<!--{{WINDOWS-GLYPH-PROC}}--></a>.
1.58
1.59 - <p>Stylistic font features can be classified into two broad categories,
1.60 + <p>Stylistic font features can be classified into two broad categories:
1.61 ones that affect the harmonization of glyph shapes with the surrounding
1.62 - context, such as kerning and ligature features, and those such as the
1.63 + context, such as kerning and ligature features, and ones such as the
1.64 small-caps, subscript/superscript and alternate features that affect shape
1.65 selection.
1.66
1.67 - <p>The subproperties of font-variant listed below are used to control these
1.68 - stylistic font features; they do not control features that are required
1.69 - for displaying certain scripts, such as the OpenType features used when
1.70 - displaying Arabic or Indic language text. They affect glyph selection and
1.71 - positioning, they do not affect font selection as described in the font
1.72 - matching section (except in cases required for compatibility with CSS
1.73 - 2.1).
1.74 + <p>The subproperties of <a href="#propdef-font-variant"
1.75 + title="font-variant!!property">‘<code
1.76 + class=property>font-variant</code>’</a> listed below are used to control
1.77 + these stylistic font features. They do not control features that are
1.78 + required for displaying certain scripts, such as the OpenType features
1.79 + used when displaying Arabic or Indic language text. They affect glyph
1.80 + selection and positioning, but do not affect font selection as described
1.81 + in the font matching section (except in cases required for compatibility
1.82 + with CSS 2.1).
1.83
1.84 <p>To assure consistent behavior across user agents, the equivalent
1.85 - OpenType property settings are listed for individual properties and must
1.86 - be considered normative. When using other font formats these should be
1.87 - used as a guideline to map CSS font feature property values to specific
1.88 - font features.
1.89 + OpenType property settings are listed for individual properties and are
1.90 + normative. When using other font formats these should be used as a
1.91 + guideline to map CSS font feature property values to specific font
1.92 + features.
1.93
1.94 <h3 id=language-specific-support><span class=secno>6.2
1.95 </span>Language-specific display</h3>
1.96
1.97 <p>OpenType also supports language-specific glyph selection and
1.98 positioning, so that text can be displayed correctly in cases where the
1.99 - language dictates a specific display behavior. Languages often share a
1.100 - common script but the shape of certain letters may vary across those
1.101 - languages, such as the variations in certain Cyrillic letters used in
1.102 - Russian and Bulgarian text. In Latin text, it's common to render "fi" with
1.103 - an explicit fi-ligature that lacks a dot on the "i". However, in languages
1.104 - such as Turkish which uses both a dotted-i and a dotless-i, it's important
1.105 - to not use this ligature or use a specialized version that contains a dot
1.106 - over the "i". The example below shows language-specific variations based
1.107 - on stylistic traditions found in Spanish, Italian and French orthography:
1.108 + language dictates a specific display behavior. Many languages share a
1.109 + common script, but the shape of certain letters can vary across those
1.110 + languages. For example, certain Cyrillic letters have different shapes in
1.111 + Russian text than in Bulgarian. In Latin text, it's common to render "fi"
1.112 + with an explicit fi-ligature that lacks a dot on the "i". However, in
1.113 + languages such as Turkish which uses both a dotted-i and a dotless-i, it's
1.114 + important to not use this ligature or use a specialized version that
1.115 + contains a dot over the "i". The example below shows language-specific
1.116 + variations based on stylistic traditions found in Spanish, Italian and
1.117 + French orthography:
1.118
1.119 <div class=featex><img alt="language specific forms, spanish"
1.120 src=locl-1.png></div>
1.121 @@ -3490,7 +3496,7 @@
1.122 <div class=featex><img alt="language specific forms, french"
1.123 src=locl-3.png></div>
1.124
1.125 - <p>If the content language of the element is known, according to the rules
1.126 + <p>If the content language of the element is known according to the rules
1.127 of the <a
1.128 href="http://www.w3.org/TR/CSS21/conform.html#doclanguage">document
1.129 language</a>, user agents are required to infer the OpenType language
1.130 @@ -4639,7 +4645,10 @@
1.131 union of these rules. This allows a set of named-values to be defined for
1.132 a given font family globally for a site and specific additions made
1.133 per-page. If the same <feature-value-name> is defined mulitple times
1.134 - for a given font-variant value, the last defined value is used.
1.135 + for a given <a href="#propdef-font-variant"
1.136 + title="font-variant!!property">‘<code
1.137 + class=property>font-variant</code>’</a> value, the last defined value is
1.138 + used.
1.139
1.140 <pre>
1.141 site.css:
1.142 @@ -4681,8 +4690,12 @@
1.143 Each property value that is font specific is clearly marked as such.
1.144 Feature value names follow the rules of CSS user identifiers and are
1.145 case-sensitive. They are unique only for a given set of font families and
1.146 - font-variant property value; the same identifier used with a different
1.147 - font-variant property value is treated as a separate and distinct value.
1.148 + <a href="#propdef-font-variant" title="font-variant!!property">‘<code
1.149 + class=property>font-variant</code>’</a> property value; the same
1.150 + identifier used with a different <a href="#propdef-font-variant"
1.151 + title="font-variant!!property">‘<code
1.152 + class=property>font-variant</code>’</a> property value is treated as a
1.153 + separate and distinct value.
1.154
1.155 <p>Using a commonly named value allows authors to use a single style rule
1.156 to cover a set of fonts for which the underlying selector is different for
1.157 @@ -4703,9 +4716,11 @@
1.158 font-variant: annotation(circled);
1.159 }</pre>
1.160
1.161 - <p>Most font specific font-variant property values take a single value
1.162 - (e.g. swash). The character-variant property value allows two values and
1.163 - styleset allows an unlimited number. If a larger number of values are
1.164 + <p>Most font specific <a href="#propdef-font-variant"
1.165 + title="font-variant!!property">‘<code
1.166 + class=property>font-variant</code>’</a> property values take a single
1.167 + value (e.g. swash). The character-variant property value allows two values
1.168 + and styleset allows an unlimited number. If a larger number of values are
1.169 assigned to a given name, a syntax error occurs and the entire
1.170 <font-feature-values-declaration> is ignored.
1.171
1.172 @@ -5065,20 +5080,26 @@
1.173 <td>see individual properties
1.174 </table>
1.175
1.176 - <p>The ‘<code class=property>font-variant</code>’ property is a
1.177 - shorthand for all font-variant subproperties. The value <dfn
1.178 - id=font-variant-normal-value title="normal!!font-variant">‘<code
1.179 - class=property>normal</code>’</dfn> resets all subproperties of
1.180 - font-variant to their inital value. The <dfn id=font-variant-none-value
1.181 - title="none!!font-variant">‘<code class=property>none</code>’</dfn>
1.182 - value sets ‘<a href="#propdef-font-variant-ligatures"><code
1.183 + <p>The <a href="#propdef-font-variant"
1.184 + title="font-variant!!property">‘<code
1.185 + class=property>font-variant</code>’</a> property is a shorthand for all
1.186 + font-variant subproperties. The value <dfn id=font-variant-normal-value
1.187 + title="normal!!font-variant">‘<code
1.188 + class=property>normal</code>’</dfn> resets all subproperties of <a
1.189 + href="#propdef-font-variant" title="font-variant!!property">‘<code
1.190 + class=property>font-variant</code>’</a> to their inital value. The <dfn
1.191 + id=font-variant-none-value title="none!!font-variant">‘<code
1.192 + class=property>none</code>’</dfn> value sets ‘<a
1.193 + href="#propdef-font-variant-ligatures"><code
1.194 class=property>font-variant-ligatures</code></a>’ to ‘<code
1.195 class=property>none</code>’ and resets all other font feature properties
1.196 to their initial value. Like other shorthands, using <a
1.197 href="#propdef-font-variant" title="font-variant!!property">‘<code
1.198 - class=property>font-variant</code>’</a> resets unspecified font-variant
1.199 - subproperties to their initial values. It does not reset the values of
1.200 - either ‘<a href="#propdef-font-language-override"><code
1.201 + class=property>font-variant</code>’</a> resets unspecified <a
1.202 + href="#propdef-font-variant" title="font-variant!!property">‘<code
1.203 + class=property>font-variant</code>’</a> subproperties to their initial
1.204 + values. It does not reset the values of either ‘<a
1.205 + href="#propdef-font-language-override"><code
1.206 class=property>font-language-override</code></a>’ or <a
1.207 href="#propdef-font-feature-settings"
1.208 title="font-feature-settings!!property">‘<code
1.209 @@ -5438,9 +5459,11 @@
1.210
1.211 <li>Font features implied by the value of the <a
1.212 href="#propdef-font-variant" title="font-variant!!property">‘<code
1.213 - class=property>font-variant</code>’</a> property, the related
1.214 - font-variant subproperties and any other CSS property that may use
1.215 - OpenType features (e.g. the ‘<a href="#propdef-font-kerning"><code
1.216 + class=property>font-variant</code>’</a> property, the related <a
1.217 + href="#propdef-font-variant" title="font-variant!!property">‘<code
1.218 + class=property>font-variant</code>’</a> subproperties and any other CSS
1.219 + property that may use OpenType features (e.g. the ‘<a
1.220 + href="#propdef-font-kerning"><code
1.221 class=property>font-kerning</code></a>’ property).
1.222
1.223 <li>Font features implied by the value of <a
1.224 @@ -5755,9 +5778,11 @@
1.225 of character variant usage for displaying text on Byzantine seals. Ken
1.226 Lunde and Eric Muller provided valuable feedback on CJK OpenType features
1.227 and Unicode variation selectors. The idea for supporting font features by
1.228 - using font-variant subproperties originated with Håkon Wium Lie, Adam
1.229 - Twardoch and Tal Leming. Elika Etemad supplied some of the initial design
1.230 - ideas for the <a
1.231 + using <a href="#propdef-font-variant"
1.232 + title="font-variant!!property">‘<code
1.233 + class=property>font-variant</code>’</a> subproperties originated with
1.234 + Håkon Wium Lie, Adam Twardoch and Tal Leming. Elika Etemad supplied some
1.235 + of the initial design ideas for the <a
1.236 href="#at-font-feature-values-rule"><code>@font-feature-values</code></a>
1.237 rule. Thanks also to House Industries for allowing the use of Ed Interlock
1.238 in the discretionary ligatures example.
