[css3-fonts] how italics are synthesized is now officially undefined :(

Author: John Daggett

css-fonts/Fonts.html

@@ -112,15 +112,15 @@
 
    <h1>CSS Fonts Module Level 3</h1>
 
-   <h2 class="no-num no-toc" id=editors-draft-6-june-2013>Editor's Draft 6
+   <h2 class="no-num no-toc" id=editors-draft-7-june-2013>Editor's Draft 7
     June 2013</h2>
 
    <dl id=authors>
     <dt>This version:
 
     <dd><a
      href="http://dev.w3.org/csswg/css-fonts/">http://dev.w3.org/csswg/css-fonts/</a>
-     <!-- <dd><a href="http://www.w3.org/TR/2013/ED-css3-fonts-20130606/">http://www.w3.org/TR/2013/ED-css3-fonts-20130606/</a> -->
+     <!-- <dd><a href="http://www.w3.org/TR/2013/ED-css3-fonts-20130607/">http://www.w3.org/TR/2013/ED-css3-fonts-20130607/</a> -->
 
 
     <dt>Latest version:
@@ -574,11 +574,12 @@ <h2 id=typography-background><span class=secno>2 </span>Typography
    defines the mapping of characters to glyphs for that font. If a document
    contains characters not supported by the <a href="#character-map"><em
    title="character map">character maps</em></a> of the fonts contained in a
-   font family list, a user agent may use a system font fallback procedure to
-   locate an appropriate font that does. If no appropriate font can be found,
-   some form of "missing glyph" character will be rendered by the user agent.
-   System fallback can occur when the specified list of font families does
-   not include a font that supports a given character.
+   font family list, a user agent may use a <a
+   href="#system-font-fallback"><em>system font fallback</em></a> procedure
+   to locate an appropriate font that does. If no appropriate font can be
+   found, some form of "missing glyph" character will be rendered by the user
+   agent. System fallback can occur when the specified list of font families
+   does not include a font that supports a given character.
 
   <p>Although the <a href="#character-map"><em>character map</em></a> of a
    font maps a given character to a glyph for that character, modern font
@@ -1330,25 +1331,21 @@ <h3 id=font-style-prop><span class=secno>3.4 </span>Font style: the <a
   </dl>
 
   <p>If no italic or oblique face is available, oblique faces can be
-   synthesized by rendering non-obliqued faces with a right sloping
-   transformation applied. When synthesizing these faces, the transformation
-   should apply to all glyphs in the same way and not vary based on codepoint
-   or due to horizontal or vertical line orientation.
-
-  <p class=issue>It has been <a
-   href="http://lists.w3.org/Archives/Public/www-style/2013May/0272.html">proposed</a>
-   that for vertical text runs, synthetic italics should not mimic normal
-   italic glyphs but instead mimic the customs of Japanese obliquing
-   (斜体、shatai), where the obliquing is applied across the text run
-   regardless of glyph orientation.
+   synthesized by rendering non-obliqued faces with an artificial obliquing
+   operation. The use of these artificially obliqued faces can be disabled
+   using the ‘<a href="#propdef-font-synthesis"><code
+   class=property>font-synthesis</code></a>’ property. The details of the
+   obliquing operation are not explicitly defined.</p>
+  <!-- resolution on the "undefined" nature of synthetics: http://www.w3.org/2013/06/06-css-minutes.html#item03 -->
 
   <p>Many scripts lack the tradition of mixing a cursive form within text
    rendered with a normal face. Chinese, Japanese and Korean fonts almost
    always lack italic or oblique faces. Fonts that support a mixture of
    scripts will sometimes omit specific scripts such as Arabic from the set
    of glyphs supported in the italic face. User agents should be careful
    about making <a href="#character-map"><em>character map</em></a>
-   assumptions across faces.</p>
+   assumptions across faces when implementing support for <a
+   href="#system-font-fallback"><em>system font fallback</em></a>.</p>
   <!-- prop: font-size -->
 
   <h3 id=font-size-prop><span class=secno>3.5 </span>Font size: the <a
@@ -2214,7 +2211,8 @@ <h3 id=font-face-rule><span class=secno>4.1 </span>The <dfn
    other applications or to documents that don't directly link to the same
    font. User agent implementers might consider it convenient to use
    downloaded fonts when rendering characters in other documents for which no
-   other available font exists as part of the system font fallback procedure.
+   other available font exists as part of the <a
+   href="#system-font-fallback"><em>system font fallback</em></a> procedure.
    However, this would cause a security leak since the contents of one page
    would be able to affect other pages, something an attacker could use as an
    attack vector. These restrictions do not affect caching behavior, fonts
@@ -3265,9 +3263,10 @@ <h3 id=font-style-matching><span class=secno>5.2 </span>Matching font
      is downloaded.</p>
 
    <li>If there are no more font families to be evaluated and no matching
-    face has been found, then the user agent performs a <em>system font
-    fallback</em> procedure to find the best match for the character to be
-    rendered. The result of this procedure may vary across user agents.
+    face has been found, then the user agent performs a <dfn
+    id=system-font-fallback>system font fallback</dfn> procedure to find the
+    best match for the character to be rendered. The result of this procedure
+    may vary across user agents.
 
    <li>If a particular character cannot be displayed using any font, the user
     agent should indicate by some means that a character is not being
@@ -3285,9 +3284,9 @@ <h3 id=cluster-matching><span class=secno>5.3 </span>Cluster matching</h3>
    matching algorithm for clusters is more specialized than the general case
    of matching a single character by itself. For sequences containing
    variation selectors, which indicate the precise glyph to be used for a
-   given character, user agents always attempt system font fallback to find
-   the appropriate glyph before using the default glyph of the base
-   character.
+   given character, user agents always attempt <a
+   href="#system-font-fallback"><em>system font fallback</em></a> to find the
+   appropriate glyph before using the default glyph of the base character.
 
   <p>A font is considered to <em>support</em> a given character if (1) the
    character is contained in the font's <a
@@ -3365,11 +3364,12 @@ <h3 id=char-handling-issues><span class=secno>5.4 </span>Character handling
   <p>If a given character is a Private-Use Area Unicode codepoint and none of
    the fonts in the fontlist contain a glyph for that codepoint, user agents
    must display some form of missing glyph symbol for that character rather
-   than attempting system font fallback for that codepoint. When matching the
-   replacement character U+FFFD, user agents may skip the font matching
-   process and immediately display some form of missing glyph symbol, they
-   are not required to display the glyph from the font that would be selected
-   by the font matching process.
+   than attempting <a href="#system-font-fallback"><em>system font
+   fallback</em></a> for that codepoint. When matching the replacement
+   character U+FFFD, user agents may skip the font matching process and
+   immediately display some form of missing glyph symbol, they are not
+   required to display the glyph from the font that would be selected by the
+   font matching process.
 
   <p>In general, the fonts for a given family will all have the same or
    similar <a href="#character-map"><em title="character map">character
@@ -6662,6 +6662,9 @@ <h2 class=no-num id=index>Index</h2>
 
    <li>swash, <a href="#swash" title=swash><strong>6.8</strong></a>
 
+   <li>system font fallback, <a href="#system-font-fallback" title="system
+    font fallback"><strong>5.2</strong></a>
+
    <li>tabular-nums, <a href="#tabular-nums"
     title=tabular-nums><strong>6.7</strong></a>