[css-values-4] Export or change all the unexported and unreferenced definitions.

tabatkins · tabatkins · commit 7c2d642d5c31 · 2018-05-14T15:44:18.000-07:00
diff --git a/css-values-4/Overview.bs b/css-values-4/Overview.bs
@@ -492,7 +492,7 @@ Resource Locators: the <<url>> type</h3>
 
 	The <dfn>url()</dfn> <a>functional notation</a>,
 	denoted by <<url>>,
-	represents a <dfn>URL</dfn>,
+	represents a <l spec=url>[=/URL=]</l>,
 	which is a pointer to a resource.
 	The typical syntax of a <<url>> is:
 
@@ -1149,8 +1149,8 @@ Absolute lengths: the ''cm'', ''mm'', ''Q'', ''in'', ''pt'', ''pc'', ''px'' unit
 	and anchored to some physical measurement.
 	They are mainly useful when the output environment is known.
 	The absolute units consist of
-	the <dfn>physical units</dfn> (''in'', ''cm'', ''mm'', ''pt'', ''pc'', ''Q'')
-	and the <dfn>visual angle unit</dfn> (''px''):
+	the <dfn export lt="physical unit">physical units</dfn> (''in'', ''cm'', ''mm'', ''pt'', ''pc'', ''Q'')
+	and the <dfn export lt="pixel unit | visual angle unit">visual angle/pixel unit</dfn> (''px''):
 
 	<table class="data" export>
 	<thead>
@@ -1176,7 +1176,7 @@ Absolute lengths: the ''cm'', ''mm'', ''Q'', ''in'', ''pt'', ''pc'', ''px'' unit
 		<tr><th><dfn id="pt">pt</dfn>
 		    <td>points
 		    <td>1pt = 1/72th of 1in
-		<tr><th><dfn id="px" lt="px|pixel unit">px</dfn>
+		<tr><th><dfn id="px" lt="px">px</dfn>
 		    <td>pixels
 		    <td>1px = 1/96th of 1in
 	</table>
@@ -1196,33 +1196,33 @@ Absolute lengths: the ''cm'', ''mm'', ''Q'', ''in'', ''pt'', ''pc'', ''px'' unit
 	All of the absolute length units are <a>compatible</a>,
 	and ''px'' is their <a>canonical unit</a>.
 
-	For a CSS device, these dimensions are <dfn lt="anchor unit">anchored</dfn> either
+	For a CSS device, these dimensions are <dfn export lt="anchor unit">anchored</dfn> either
 
 	<ol type=i>
 		<li>by relating the <a>physical units</a> to their physical measurements, or
-		<li>by relating the <a value>pixel unit</a> to the <a>reference pixel</a>.
+		<li>by relating the <a>pixel unit</a> to the <a>reference pixel</a>.
 	</ol>
 
 	For print media at typical viewing distances,
-	the anchor unit should be one of the standard physical units (inches, centimeters, etc).
+	the [=anchor unit=] should be one of the [=physical units=] (inches, centimeters, etc).
 	For screen media (including high-resolution devices),
 	low-resolution devices,
 	and devices with unusual viewing distances),
-	it is recommended instead that the anchor unit be the pixel unit.
-	For such devices it is recommended that the pixel unit
+	it is recommended instead that the [=anchor unit=] be the [=pixel unit=].
+	For such devices it is recommended that the [=pixel unit=]
 	refer to the whole number of device pixels that best approximates the reference pixel.
 
-	Note: If the anchor unit is the pixel unit,
-	the physical units might not match their physical measurements.
-	Alternatively if the anchor unit is a physical unit,
-	the pixel unit might not map to a whole number of device pixels.
+	Note: If the [=anchor unit=] is the [=pixel unit=],
+	the [=physical units=] might not match their physical measurements.
+	Alternatively if the [=anchor unit=] is a [=physical unit=],
+	the [=pixel unit=] might not map to a whole number of device pixels.
 
-	Note: This definition of the pixel unit and the physical units
+	Note: This definition of the [=pixel unit=] and the [=physical units=]
 	differs from previous versions of CSS.
-	In particular, in previous versions of CSS the pixel unit and the physical units
+	In particular, in previous versions of CSS the [=pixel unit=] and the [=physical units=]
 	were not related by a fixed ratio:
-	the physical units were always tied to their physical measurements
-	while the pixel unit would vary to most closely match the reference pixel.
+	the [=physical units=] were always tied to their physical measurements
+	while the [=pixel unit=] would vary to most closely match the reference pixel.
 	(This change was made because too much existing content relies on the assumption of 96dpi,
 	and breaking that assumption broke the content.)
 
@@ -1984,7 +1984,7 @@ Serialization</h4>
 	Issue: This section is still <a href="https://lists.w3.org/Archives/Member/w3c-css-wg/2016AprJun/0239.html">under discussion</a>.
 
 	<div algorithm="serialize a calc() value">
-		To <dfn>serialize a ''calc()'' value</dfn>
+		To <dfn export>serialize a ''calc()'' value</dfn>
 
 		1. [=Simplify the expression=] inside of it.
 
@@ -2004,7 +2004,7 @@ Serialization</h4>
 	</div>
 
 	<div algorithm="serialize a min()/max() value">
-		To <dfn lt="serialize a min() value|serialize a max() value">serialize a ''min()'' or ''max()'' value</dfn>:
+		To <dfn export lt="serialize a min() value|serialize a max() value">serialize a ''min()'' or ''max()'' value</dfn>:
 
 		1. For each comma-separated expression inside of it,
 			[=simplify the expression=].
@@ -2021,7 +2021,7 @@ Serialization</h4>
 	</div>
 
 	<div algorithm="simplify an expression">
-		To <dfn lt="simplify an expression | simplify the expression" for="math function">simplify an expression</dfn>:
+		To <dfn export lt="simplify an expression | simplify the expression" for="math function">simplify an expression</dfn>:
 
 		1. Replace any ''calc()'' values with parentheses containing their contents.
 		2. Resolve all multiplications and divisions.
@@ -2038,7 +2038,7 @@ Serialization</h4>
 	</div>
 
 	<div algorithm="serialize a summation">
-		To <dfn lt="serialize a summation|serialize the summation" for="math function">serialize a summation</dfn>:
+		To <dfn export lt="serialize a summation|serialize the summation" for="math function">serialize a summation</dfn>:
 
 		1. Sort the terms in the following order:
 
