[css3-syntax] Minor editorial tweaks, removed some FIXUP bits leftover from the template, added some issues.

Tue, 28 Aug 2012 16:24:01 -0700

author
Tab Atkins Jr. <jackalmage@gmail.com>
date
Tue, 28 Aug 2012 16:24:01 -0700
changeset 6598
d299d23a9704
parent 6597
61181d2760f2
child 6599
618c38b7e982

[css3-syntax] Minor editorial tweaks, removed some FIXUP bits leftover from the template, added some issues.

css3-sizing/Overview.src.html file | annotate | diff | comparison | revisions
css3-syntax/Overview.html file | annotate | diff | comparison | revisions
css3-syntax/Overview.src.html file | annotate | diff | comparison | revisions
     1.1 --- a/css3-sizing/Overview.src.html	Tue Aug 28 16:17:05 2012 -0700
     1.2 +++ b/css3-sizing/Overview.src.html	Tue Aug 28 16:24:01 2012 -0700
     1.3 @@ -129,7 +129,7 @@
     1.4  			The space into which a box is laid out,
     1.5  			typically either a measurement of its <i>containing block</i>
     1.6  			or an infinite size.
     1.7 -			An <i>available size</i> can also be either a
     1.8 +			An <i>available size</i> can alternatively be either a
     1.9  			<dfn>min-content constraint</dfn> or
    1.10  			a <dfn>max-content constraint</dfn>.
    1.11  
     2.1 --- a/css3-syntax/Overview.html	Tue Aug 28 16:17:05 2012 -0700
     2.2 +++ b/css3-syntax/Overview.html	Tue Aug 28 16:24:01 2012 -0700
     2.3 @@ -36,7 +36,7 @@
     2.4  
     2.5     <h1>CSS Syntax Module Level 3</h1>
     2.6  
     2.7 -   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 24 August 2012</h2>
     2.8 +   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 28 August 2012</h2>
     2.9  
    2.10     <dl>
    2.11      <dt>This version:
    2.12 @@ -342,18 +342,6 @@
    2.13  
    2.14       <li><a href="#conformance-classes"><span class=secno>4.2. </span>
    2.15        Conformance classes</a>
    2.16 -
    2.17 -     <li><a href="#partial"><span class=secno>4.3. </span> Partial
    2.18 -      implementations</a>
    2.19 -
    2.20 -     <li><a href="#experimental"><span class=secno>4.4. </span> Experimental
    2.21 -      implementations</a>
    2.22 -
    2.23 -     <li><a href="#testing"><span class=secno>4.5. </span> Non-experimental
    2.24 -      implementations</a>
    2.25 -
    2.26 -     <li><a href="#cr-exit-criteria"><span class=secno>4.6. </span> CR exit
    2.27 -      criteria</a>
    2.28      </ul>
    2.29  
    2.30     <li class=no-num><a href="#acknowledgments"> Acknowledgments</a>
    2.31 @@ -2090,8 +2078,7 @@
    2.32      comment, cdo, cdc, colon, semicolon, at-keyword, ], ), and }.
    2.33      <p class=note> This means that the following tokens emitted by the
    2.34       tokenizer stage will <strong>not</strong> appear in the stylesheet
    2.35 -     object: function, bad-string, bad-url, [, (, {. <span class=issue>I need
    2.36 -     to make sure this is true.</span>
    2.37 +     object: function, bad-string, bad-url, [, (, {.
    2.38  
    2.39     <dt>function
    2.40  
    2.41 @@ -2811,25 +2798,26 @@
    2.42  
    2.43    <p> <em>This section is non-normative.</em>
    2.44  
    2.45 -  <p> Here are the changes that I know that I've made to the Core Grammar of
    2.46 -   2.1. If there are changes not present here, please let me know as they may
    2.47 -   be unintentional.
    2.48 -
    2.49 -  <p> Note that the point of this spec is to match reality; changes from
    2.50 -   CSS2.1‘<code class=css>s Core Grammar are nearly always because the Core
    2.51 -   Grammar specified something that doesn</code>’t match actual browser
    2.52 -   behavior, or left something unspecified. If some detail doesn't match
    2.53 -   browsers, please let me know as it's almost certainly unintentional.
    2.54 +  <p class=issue> Here are the changes that I know that I've made to the Core
    2.55 +   Grammar of 2.1. If there are changes not present here, please let me know
    2.56 +   as they may be unintentional.
    2.57 +
    2.58 +  <p class=issue> Note that the point of this spec is to match reality;
    2.59 +   changes from CSS2.1&apos;s Core Grammar are nearly always because the Core
    2.60 +   Grammar specified something that doesn't match actual browser behavior, or
    2.61 +   left something unspecified. If some detail doesn't match browsers, please
    2.62 +   let me know as it's almost certainly unintentional.
    2.63  
    2.64    <ol>
    2.65     <li> No whitespace or comments are allowed between the DELIM(!) and
    2.66      IDENT(important) tokens when processing an !important directive at the
    2.67      end of a style rule.
    2.68 -
    2.69 -   <li> The handling of some miscellanous ‘<code
    2.70 -    class=property>special</code>’ tokens (like an unmatched } token)
    2.71 -    showing up in various places in the grammar has been specified with some
    2.72 -    reasonable behavior shown by at least one browser. Previously,
    2.73 +    <p class=issue> Exactly how to treat ‘<code
    2.74 +     class=css>!important</code>’ is still under discussion in the WG.
    2.75 +
    2.76 +   <li> The handling of some miscellanous "special" tokens (like an unmatched
    2.77 +    } token) showing up in various places in the grammar has been specified
    2.78 +    with some reasonable behavior shown by at least one browser. Previously,
    2.79      stylesheets with those tokens in those places just didn't match the
    2.80      stylesheet grammar at all, so their handling was totally undefined.
    2.81  
    2.82 @@ -2907,8 +2895,8 @@
    2.83    <h3 id=conformance-classes><span class=secno>4.2. </span> Conformance
    2.84     classes</h3>
    2.85  
    2.86 -  <p>Conformance to <var class=replaceme>CSS TEMPLATE Module</var> is defined
    2.87 -   for three conformance classes:
    2.88 +  <p>Conformance to CSS Syntax Module Level 3 is defined for three
    2.89 +   conformance classes:
    2.90  
    2.91    <dl>
    2.92     <dt><dfn id=style-sheet title="style sheet!!as conformance class">style
    2.93 @@ -2929,132 +2917,20 @@
    2.94      that writes a style sheet.
    2.95    </dl>
    2.96  
    2.97 -  <p>A style sheet is conformant to <var class=replaceme>CSS TEMPLATE
    2.98 -   Module</var> if all of its statements that use syntax defined in this
    2.99 -   module are valid according to the generic CSS grammar and the individual
   2.100 -   grammars of each feature defined in this module.
   2.101 -
   2.102 -  <p>A renderer is conformant to <var class=replaceme>CSS TEMPLATE
   2.103 -   Module</var> if, in addition to interpreting the style sheet as defined by
   2.104 -   the appropriate specifications, it supports all the features defined by
   2.105 -   <var class=replaceme>CSS TEMPLATE Module</var> by parsing them correctly
   2.106 -   and rendering the document accordingly. However, the inability of a UA to
   2.107 -   correctly render a document due to limitations of the device does not make
   2.108 -   the UA non-conformant. (For example, a UA is not required to render color
   2.109 -   on a monochrome monitor.)
   2.110 -
   2.111 -  <p>An authoring tool is conformant to <var class=replaceme>CSS TEMPLATE
   2.112 -   Module</var> if it writes style sheets that are syntactically correct
   2.113 -   according to the generic CSS grammar and the individual grammars of each
   2.114 -   feature in this module, and meet all other conformance requirements of
   2.115 -   style sheets as described in this module.
   2.116 -
   2.117 -  <h3 id=partial><span class=secno>4.3. </span> Partial implementations</h3>
   2.118 -
   2.119 -  <p>So that authors can exploit the forward-compatible parsing rules to
   2.120 -   assign fallback values, CSS renderers <strong>must</strong> treat as
   2.121 -   invalid (and <a
   2.122 -   href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore as
   2.123 -   appropriate</a>) any at-rules, properties, property values, keywords, and
   2.124 -   other syntactic constructs for which they have no usable level of support.
   2.125 -   In particular, user agents <strong>must not</strong> selectively ignore
   2.126 -   unsupported component values and honor supported values in a single
   2.127 -   multi-value property declaration: if any value is considered invalid (as
   2.128 -   unsupported values must be), CSS requires that the entire declaration be
   2.129 -   ignored.
   2.130 -
   2.131 -  <h3 id=experimental><span class=secno>4.4. </span> Experimental
   2.132 -   implementations</h3>
   2.133 -
   2.134 -  <p>To avoid clashes with future CSS features, the CSS2.1 specification
   2.135 -   reserves a <a
   2.136 -   href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
   2.137 -   syntax</a> for proprietary and experimental extensions to CSS.
   2.138 -
   2.139 -  <p>Prior to a specification reaching the Candidate Recommendation stage in
   2.140 -   the W3C process, all implementations of a CSS feature are considered
   2.141 -   experimental. The CSS Working Group recommends that implementations use a
   2.142 -   vendor-prefixed syntax for such features, including those in W3C Working
   2.143 -   Drafts. This avoids incompatibilities with future changes in the draft.
   2.144 -
   2.145 -  <h3 id=testing><span class=secno>4.5. </span> Non-experimental
   2.146 -   implementations</h3>
   2.147 -
   2.148 -  <p>Once a specification reaches the Candidate Recommendation stage,
   2.149 -   non-experimental implementations are possible, and implementors should
   2.150 -   release an unprefixed implementation of any CR-level feature they can
   2.151 -   demonstrate to be correctly implemented according to spec.
   2.152 -
   2.153 -  <p>To establish and maintain the interoperability of CSS across
   2.154 -   implementations, the CSS Working Group requests that non-experimental CSS
   2.155 -   renderers submit an implementation report (and, if necessary, the
   2.156 -   testcases used for that implementation report) to the W3C before releasing
   2.157 -   an unprefixed implementation of any CSS features. Testcases submitted to
   2.158 -   W3C are subject to review and correction by the CSS Working Group.
   2.159 -
   2.160 -  <p>Further information on submitting testcases and implementation reports
   2.161 -   can be found from on the CSS Working Group's website at <a
   2.162 -   href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>.
   2.163 -   Questions should be directed to the <a
   2.164 -   href="http://lists.w3.org/Archives/Public/public-css-testsuite">public-css-testsuite@w3.org</a>
   2.165 -   mailing list.
   2.166 -
   2.167 -  <h3 id=cr-exit-criteria><span class=secno>4.6. </span> CR exit criteria</h3>
   2.168 -
   2.169 -  <p class=issue>[Change or remove the following CR exit criteria if the spec
   2.170 -   is not a module, but, e.g., a Note or a profile. This text was <a
   2.171 -   href="http://www.w3.org/Style/CSS/Tracker/actions/44"> decided on
   2.172 -   2008-06-04.</a>]
   2.173 -
   2.174 -  <p> For this specification to be advanced to Proposed Recommendation, there
   2.175 -   must be at least two independent, interoperable implementations of each
   2.176 -   feature. Each feature may be implemented by a different set of products,
   2.177 -   there is no requirement that all features be implemented by a single
   2.178 -   product. For the purposes of this criterion, we define the following
   2.179 -   terms:
   2.180 -
   2.181 -  <dl>
   2.182 -   <dt>independent
   2.183 -
   2.184 -   <dd>each implementation must be developed by a different party and cannot
   2.185 -    share, reuse, or derive from code used by another qualifying
   2.186 -    implementation. Sections of code that have no bearing on the
   2.187 -    implementation of this specification are exempt from this requirement.
   2.188 -
   2.189 -   <dt>interoperable
   2.190 -
   2.191 -   <dd>passing the respective test case(s) in the official CSS test suite,
   2.192 -    or, if the implementation is not a Web browser, an equivalent test. Every
   2.193 -    relevant test in the test suite should have an equivalent test created if
   2.194 -    such a user agent (UA) is to be used to claim interoperability. In
   2.195 -    addition if such a UA is to be used to claim interoperability, then there
   2.196 -    must one or more additional UAs which can also pass those equivalent
   2.197 -    tests in the same way for the purpose of interoperability. The equivalent
   2.198 -    tests must be made publicly available for the purposes of peer review.
   2.199 -
   2.200 -   <dt>implementation
   2.201 -
   2.202 -   <dd>a user agent which:
   2.203 -    <ol class=inline>
   2.204 -     <li>implements the specification.
   2.205 -
   2.206 -     <li>is available to the general public. The implementation may be a
   2.207 -      shipping product or other publicly available version (i.e., beta
   2.208 -      version, preview release, or “nightly build”). Non-shipping product
   2.209 -      releases must have implemented the feature(s) for a period of at least
   2.210 -      one month in order to demonstrate stability.
   2.211 -
   2.212 -     <li>is not experimental (i.e., a version specifically designed to pass
   2.213 -      the test suite and is not intended for normal usage going forward).
   2.214 -    </ol>
   2.215 -  </dl>
   2.216 -
   2.217 -  <p>The specification will remain Candidate Recommendation for at least six
   2.218 -   months.
   2.219 +  <p>A style sheet is conformant to CSS Syntax Module Level 3 if it is
   2.220 +   syntactically valid according to this module.
   2.221 +
   2.222 +  <p>A renderer is conformant to CSS Syntax Module Level 3 if it parses a
   2.223 +   stylesheet according to this module.
   2.224 +
   2.225 +  <p>An authoring tool is conformant to CSS Syntax Module Level 3 if it
   2.226 +   writes style sheets that are syntactically valid according to this module.
   2.227 +   
   2.228  
   2.229    <h2 class=no-num id=acknowledgments> Acknowledgments</h2>
   2.230  
   2.231 -  <p><var class=replaceme>[acknowledgments]</var>
   2.232 +  <p> Thanks for feedback and contributions from David Baron, 呂康豪
   2.233 +   (Kang-Hao Lu), and Simon Sapin.
   2.234  
   2.235    <h2 class=no-num id=references> References</h2>
   2.236  
     3.1 --- a/css3-syntax/Overview.src.html	Tue Aug 28 16:17:05 2012 -0700
     3.2 +++ b/css3-syntax/Overview.src.html	Tue Aug 28 16:24:01 2012 -0700
     3.3 @@ -2094,7 +2094,6 @@
     3.4  				[,
     3.5  				(,
     3.6  				{.
     3.7 -				<span class='issue'>I need to make sure this is true.</span>
     3.8  
     3.9  		<dt>function
    3.10  		<dd>
    3.11 @@ -2813,15 +2812,15 @@
    3.12  	<p>
    3.13  		<em>This section is non-normative.</em>
    3.14  
    3.15 -	<p>
    3.16 +	<p class='issue'>
    3.17  		Here are the changes that I know that I've made to the Core Grammar of 2.1.
    3.18  		If there are changes not present here, 
    3.19  		please let me know
    3.20  		as they may be unintentional.
    3.21  
    3.22 -	<p>
    3.23 +	<p class='issue'>
    3.24  		Note that the point of this spec is to match reality;
    3.25 -		changes from CSS2.1's Core Grammar are nearly always because the Core Grammar specified something that doesn't match actual browser behavior,
    3.26 +		changes from CSS2.1&apos;s Core Grammar are nearly always because the Core Grammar specified something that doesn't match actual browser behavior,
    3.27  		or left something unspecified.
    3.28  		If some detail doesn't match browsers,
    3.29  		please let me know
    3.30 @@ -2832,8 +2831,11 @@
    3.31  			No whitespace or comments are allowed between the DELIM(!) and IDENT(important) tokens 
    3.32  			when processing an !important directive at the end of a style rule.
    3.33  
    3.34 +			<p class='issue'>
    3.35 +				Exactly how to treat ''!important'' is still under discussion in the WG.
    3.36 +
    3.37  		<li>
    3.38 -			The handling of some miscellanous 'special' tokens
    3.39 +			The handling of some miscellanous "special" tokens
    3.40  			(like an unmatched } token)
    3.41  			showing up in various places in the grammar
    3.42  			has been specified with some reasonable behavior shown by at least one browser.
    3.43 @@ -2922,8 +2924,8 @@
    3.44  <h3 id="conformance-classes">
    3.45  Conformance classes</h3>
    3.46  
    3.47 -	<p>Conformance to <var class="replaceme">CSS TEMPLATE Module</var>
    3.48 -	is defined for three conformance classes:
    3.49 +	<p>Conformance to CSS Syntax Module Level 3 is defined for three conformance classes:
    3.50 +
    3.51  	<dl>
    3.52  		<dt><dfn title="style sheet!!as conformance class">style sheet</dfn>
    3.53  			<dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
    3.54 @@ -2937,136 +2939,24 @@
    3.55  			that writes a style sheet.
    3.56  	</dl>
    3.57  	
    3.58 -	<p>A style sheet is conformant to <var class="replaceme">CSS TEMPLATE Module</var>
    3.59 -	if all of its statements that use syntax defined in this module are valid
    3.60 -	according to the generic CSS grammar and the individual grammars of each
    3.61 -	feature defined in this module.
    3.62 +	<p>A style sheet is conformant to CSS Syntax Module Level 3
    3.63 +	if it is syntactically valid according to this module.
    3.64  	
    3.65 -	<p>A renderer is conformant to <var class="replaceme">CSS TEMPLATE Module</var>
    3.66 -	if, in addition to interpreting the style sheet as defined by the
    3.67 -	appropriate specifications, it supports all the features defined
    3.68 -	by <var class="replaceme">CSS TEMPLATE Module</var> by parsing them correctly
    3.69 -	and rendering the document accordingly. However, the inability of a
    3.70 -	UA to correctly render a document due to limitations of the device
    3.71 -	does not make the UA non-conformant. (For example, a UA is not
    3.72 -	required to render color on a monochrome monitor.)
    3.73 +	<p>A renderer is conformant to CSS Syntax Module Level 3
    3.74 +	if it parses a stylesheet according to this module.
    3.75  	
    3.76 -	<p>An authoring tool is conformant to <var class="replaceme">CSS TEMPLATE Module</var>
    3.77 -	if it writes style sheets that are syntactically correct according to the
    3.78 -	generic CSS grammar and the individual grammars of each feature in
    3.79 -	this module, and meet all other conformance requirements of style sheets
    3.80 -	as described in this module.
    3.81 -
    3.82 -<h3 id="partial">
    3.83 -Partial implementations</h3>
    3.84 -
    3.85 -	<p>So that authors can exploit the forward-compatible parsing rules to
    3.86 -	assign fallback values, CSS renderers <strong>must</strong>
    3.87 -	treat as invalid (and <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore
    3.88 -	as appropriate</a>) any at-rules, properties, property values, keywords,
    3.89 -	and other syntactic constructs for which they have no usable level of
    3.90 -	support. In particular, user agents <strong>must not</strong> selectively
    3.91 -	ignore unsupported component values and honor supported values in a single
    3.92 -	multi-value property declaration: if any value is considered invalid
    3.93 -	(as unsupported values must be), CSS requires that the entire declaration
    3.94 -	be ignored.</p>
    3.95 -	
    3.96 -<h3 id="experimental">
    3.97 -Experimental implementations</h3>
    3.98 -
    3.99 -	<p>To avoid clashes with future CSS features, the CSS2.1 specification
   3.100 -	reserves a <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
   3.101 -	syntax</a> for proprietary and experimental extensions to CSS.
   3.102 -	
   3.103 -	<p>Prior to a specification reaching the Candidate Recommendation stage
   3.104 -	in the W3C process, all implementations of a CSS feature are considered
   3.105 -	experimental. The CSS Working Group recommends that implementations
   3.106 -	use a vendor-prefixed syntax for such features, including those in
   3.107 -	W3C Working Drafts. This avoids incompatibilities with future changes
   3.108 -	in the draft.
   3.109 -	</p>
   3.110 - 
   3.111 -<h3 id="testing">
   3.112 -Non-experimental implementations</h3>
   3.113 -
   3.114 -	<p>Once a specification reaches the Candidate Recommendation stage,
   3.115 -	non-experimental implementations are possible, and implementors should
   3.116 -	release an unprefixed implementation of any CR-level feature they
   3.117 -	can demonstrate to be correctly implemented according to spec.
   3.118 -	
   3.119 -	<p>To establish and maintain the interoperability of CSS across
   3.120 -	implementations, the CSS Working Group requests that non-experimental
   3.121 -	CSS renderers submit an implementation report (and, if necessary, the
   3.122 -	testcases used for that implementation report) to the W3C before
   3.123 -	releasing an unprefixed implementation of any CSS features. Testcases
   3.124 -	submitted to W3C are subject to review and correction by the CSS
   3.125 -	Working Group.
   3.126 -	
   3.127 -	<p>Further information on submitting testcases and implementation reports
   3.128 -	can be found from on the CSS Working Group's website at
   3.129 -	<a href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>.
   3.130 -	Questions should be directed to the
   3.131 -	<a href="http://lists.w3.org/Archives/Public/public-css-testsuite">public-css-testsuite@w3.org</a>
   3.132 -	mailing list.
   3.133 -
   3.134 -<h3 id="cr-exit-criteria">
   3.135 -CR exit criteria</h3>
   3.136 -
   3.137 -	<p class=issue>[Change or remove the following CR exit criteria if
   3.138 -	the spec is not a module, but, e.g., a Note or a profile. This text was <a
   3.139 -	href="http://www.w3.org/Style/CSS/Tracker/actions/44"> decided on 2008-06-04.</a>]</p>
   3.140 -
   3.141 -	<p>
   3.142 -	For this specification to be advanced to Proposed Recommendation,
   3.143 -	there must be at least two independent, interoperable implementations
   3.144 -	of each feature. Each feature may be implemented by a different set of
   3.145 -	products, there is no requirement that all features be implemented by
   3.146 -	a single product. For the purposes of this criterion, we define the
   3.147 -	following terms:
   3.148 -	
   3.149 -	<dl>
   3.150 -		<dt>independent <dd>each implementation must be developed by a
   3.151 -		different party and cannot share, reuse, or derive from code
   3.152 -		used by another qualifying implementation. Sections of code that
   3.153 -		have no bearing on the implementation of this specification are
   3.154 -		exempt from this requirement.
   3.155 -	
   3.156 -		<dt>interoperable <dd>passing the respective test case(s) in the
   3.157 -		official CSS test suite, or, if the implementation is not a Web
   3.158 -		browser, an equivalent test. Every relevant test in the test
   3.159 -		suite should have an equivalent test created if such a user
   3.160 -		agent (UA) is to be used to claim interoperability. In addition
   3.161 -		if such a UA is to be used to claim interoperability, then there
   3.162 -		must one or more additional UAs which can also pass those
   3.163 -		equivalent tests in the same way for the purpose of
   3.164 -		interoperability. The equivalent tests must be made publicly
   3.165 -		available for the purposes of peer review.
   3.166 -	
   3.167 -		<dt>implementation <dd>a user agent which:
   3.168 -	
   3.169 -		<ol class=inline>
   3.170 -			<li>implements the specification.
   3.171 -	
   3.172 -			<li>is available to the general public. The implementation may
   3.173 -			be a shipping product or other publicly available version
   3.174 -			(i.e., beta version, preview release, or “nightly build”). 
   3.175 -			Non-shipping product releases must have implemented the
   3.176 -			feature(s) for a period of at least one month in order to
   3.177 -			demonstrate stability.
   3.178 -	
   3.179 -			<li>is not experimental (i.e., a version specifically designed
   3.180 -			to pass the test suite and is not intended for normal usage
   3.181 -			going forward).
   3.182 -		</ol>
   3.183 -	</dl>
   3.184 -	
   3.185 -	<p>The specification will remain Candidate Recommendation for at least
   3.186 -	six months.
   3.187 +	<p>An authoring tool is conformant to CSS Syntax Module Level 3
   3.188 +	if it writes style sheets that are syntactically valid according to this module.
   3.189  
   3.190  <h2 class=no-num id="acknowledgments">
   3.191  Acknowledgments</h2>
   3.192  
   3.193 -	<p><var class="replaceme">[acknowledgments]</var></p>
   3.194 +	<p>
   3.195 +		Thanks for feedback and contributions from
   3.196 +		David Baron,
   3.197 +		呂康豪 (Kang-Hao Lu),
   3.198 +		and Simon Sapin.
   3.199 +
   3.200  
   3.201  <h2 class=no-num id="references">
   3.202  References</h2>

mercurial