66 < meta content ="text/html;charset=utf-8 " http-equiv =Content-Type >
77 < title > CSS Fonts Module Level 3</ title >
88
9- < link href ="https://www.w3.org/TR/2018/CR-css-fonts-3-20180129/ "
10- rel =canonical >
9+ < link href ="https://dev.w3.org/csswg/css-fonts-3/ " rel =canonical >
1110 < meta content ="width=device-width " name =viewport >
1211 < link href ="http://purl.org/dc/terms/ " rel =schema.dcterms >
1312 < link href ="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright "
1413 rel =dcterms.rights >
1514 < meta content ="CSS Fonts Module Level 3 " name =dcterms.title >
1615 < meta content =text name =dcterms.type >
17- < meta content =2018-01-29 name =dcterms.date >
16+ < meta content =2018-02-14 name =dcterms.date >
1817 < meta content ="John Daggett " name =dcterms.creator >
1918 < meta content ="Myles C. Maxfield " name =dcterms.creator >
2019 < meta content =W3C name =dcterms.publisher >
21- < meta content ="https://www .w3.org/TR/2018/CR- css-fonts-3-20180129 / "
20+ < meta content ="https://dev .w3.org/csswg/ css-fonts-3/ "
2221 name =dcterms.identifier > <!--
2322 FIXME when publishing: copy the current default.css and link to
2423 "default.css" rather than "../default.css"
111110 # fonts ul .indexlist ul , # fonts ul .indexlist dl { font-size : inherit; }
112111
113112 </ style >
114- < link href ="https://www.w3.org/StyleSheets/TR/W3C-CR .css " rel =stylesheet
113+ < link href ="https://www.w3.org/StyleSheets/TR/W3C-ED .css " rel =stylesheet
115114 type ="text/css ">
116115 < script defer =defer
117116 src ="https://test.csswg.org/harness/annotate.js#CSS3-FONTS_DEV "
125124
126125 < h1 > CSS Fonts Module Level 3</ h1 >
127126
128- < h2 class ="no-num no-toc "> W3C Candidate Recommendation 29 January 2018</ h2 >
127+ < h2 class ="no-num no-toc "> Editor's Draft 14 February 2018</ h2 >
129128
130129 < dl id =authors >
131130 < dt > This version:
132131
133132 < dd > < a
134133 href ="https://drafts.csswg.org/css-fonts/ "> https://drafts.csswg.org/css-fonts/</ a >
135- <!-- <dd><a href="https://www.w3.org/TR/2018/CR -css-fonts-3-20180129 /">https://www.w3.org/TR/2018/CR -css-fonts-3-20180129 /</a> -->
134+ <!-- <dd><a href="https://www.w3.org/TR/2018/ED -css-fonts-3-20180214 /">https://www.w3.org/TR/2018/ED -css-fonts-3-20180214 /</a> -->
136135
137136 < dt > Latest version:
138137
@@ -222,32 +221,24 @@ <h2 class="no-num no-toc" id=abstract>Abstract</h2>
222221 < h2 class ="no-num no-toc " id =status > Status of this document</ h2 >
223222 <!--begin-status-->
224223
225- < p > < em > This section describes the status of this document at the time of
226- its publication. Other documents may supersede this document. A list of
227- current W3C publications and the latest revision of this technical report
228- can be found in the < a href ="http://www.w3.org/TR/ "> W3C technical reports
229- index at http://www.w3.org/TR/.</ a > </ em >
224+ < p > This is a public copy of the editors' draft. It is provided for
225+ discussion only and may change at any moment. Its publication here does
226+ not imply endorsement of its contents by W3C. Don't cite this document
227+ other than as work in progress.
230228
231- < p > Publication as a Candidate Recommendation does not imply endorsement by
232- the W3C Membership. This is a draft document and may be updated, replaced
233- or obsoleted by other documents at any time. It is inappropriate to cite
234- this document as other than work in progress.
235-
236- < p > This document was produced by the < a
237- href ="http://www.w3.org/Style/CSS/members "> CSS Working Group</ a > as a < a
238- href ="http://www.w3.org/Consortium/Process/tr#RecsCR "> Candidate
239- Recommendation.</ a >
240-
241- < p > A Candidate Recommendation is a document that has been widely reviewed
242- and is ready for implementation. W3C encourages everybody to implement
243- this specification and return comments to the (< a
229+ < p > The (< a
244230 href ="http://lists.w3.org/Archives/Public/www-style/ "> archived</ a > ) public
245231 mailing list < a
246- href ="mailto:www-style@w3.org?Subject=%5Bcss-fonts-3%5D%20PUT%20SUBJECT%20HERE "> www-style@w3.org</ a >
247- (see < a href ="http://www.w3.org/Mail/Request "> instructions</ a > ). When
248- sending e-mail, please put the text “css-fonts-3” in the subject,
249- preferably like this: “[<!----> css-fonts-3<!----> ] < em > …summary of
250- comment…</ em > ”
232+ href ="mailto:www-style@w3.org?Subject=%5Bcss-fonts-3%5D%20PUT%20SUBJECT%20HERE ">
233+ www-style@w3.org</ a > (see < a
234+ href ="http://www.w3.org/Mail/Request "> instructions</ a > ) is preferred for
235+ discussion of this specification. When sending e-mail, please put the text
236+ “css-fonts-3” in the subject, preferably like this:
237+ “[<!----> css-fonts-3<!----> ] < em > …summary of comment…</ em > ”
238+
239+ < p > This document was produced by the < a
240+ href ="http://www.w3.org/Style/CSS/members "> CSS Working Group</ a > (part of
241+ the < a href ="http://www.w3.org/Style/ "> Style Activity</ a > ).
251242
252243 < p > This document was produced by a group operating under the < a
253244 href ="http://www.w3.org/Consortium/Patent-Policy-20040205/ "> 5 February
@@ -260,11 +251,7 @@ <h2 class="no-num no-toc" id=status>Status of this document</h2>
260251 href ="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential "> Essential
261252 Claim(s)</ a > must disclose the information in accordance with < a
262253 href ="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure "> section
263- 6 of the W3C Patent Policy</ a > .
264-
265- < p > This document is governed by the < a
266- href ="http://www.w3.org/2015/Process-20150901/ "
267- id ="w3c_process_revision "> 1 September 2015 W3C Process Document</ a > .</ p >
254+ 6 of the W3C Patent Policy</ a > .</ p >
268255 <!--end-status-->
269256
270257 < p > See the section < a href ="#cr-exit-criteria "> CR Exit Criteria</ a > for
@@ -898,7 +885,7 @@ <h5 class="no-num no-toc"> <span class=index-def id=sans-serif0
898885
899886 < p > Glyphs in sans-serif fonts, as the term is used in CSS, are generally
900887 low contrast (vertical and horizontal stems have the close to the same
901- thickness) and have stroke endings that are plain -- without any flaring,
888+ thickness) and have stroke endings that are plain — without any flaring,
902889 cross stroke, or other ornamentation. Sans-serif fonts are typically
903890 proportionately-spaced. They often have little variation between thick and
904891 thin strokes, compared to fonts from the ‘< a href ="#serif "> < code
@@ -4661,6 +4648,7 @@ <h3 id=font-variant-numeric-prop><span class=secno>6.7. </span>Numerical
46614648 As such, it's not suitable for use as a paragraph-level style.
46624649 </ div >
46634650 <!-- prop: font-variant-alternates -->
4651+ <!-- moved to Fonts 4 -->
46644652
46654653 < h3 id =font-variant-alternates-prop > < span class =secno > 6.8.
46664654 </ span > Alternates and swashes: the < a
@@ -5023,7 +5011,7 @@ <h4 id=basic-syntax><span class=secno>6.9.1. </span>Basic syntax</h4>
50235011 < a href ="#feature_type "> < i title ="feature_type "> feature type</ i > </ a > . The
50245012 same identifier used with a different < a href ="#feature_type "> < i
50255013 title ="feature_type "> feature type</ i > </ a > is treated as a separate and
5026- distinct value. If the same identifier is defined mulitple times for a
5014+ distinct value. If the same identifier is defined multiple times for a
50275015 given < a href ="#feature_type "> < i title ="feature_type "> feature type</ i > </ a >
50285016 and font family, the last defined value is used. Values associated with a
50295017 given identifier are limited to integer values 0 or greater.
@@ -6165,7 +6153,7 @@ <h2 class=no-num id=platform-props-to-css>Appendix A: Mapping platform font
61656153 < p > Specifically, font family name data is handled differently across
61666154 platforms. For TrueType and OpenType fonts these names are contained in
61676155 the ‘< code class =property > name</ code > ’ table, in name records with
6168- name ID 1. Mulitple names can be stored for different locales, but
6156+ name ID 1. Multiple names can be stored for different locales, but
61696157 Microsoft recommends fonts always include at least a US English version of
61706158 the name. On Windows, Microsoft made the decision for backwards
61716159 compatibility to limit this family name to a maximum of four faces; for
0 commit comments