bocoup
diff --git a/‎css2/aural.src‎
Lines changed: 5 additions & 5 deletions b/‎css2/aural.src‎
Lines changed: 5 additions & 5 deletions
diff --git a/‎css2/cascade.src‎
Lines changed: 5 additions & 5 deletions b/‎css2/cascade.src‎
Lines changed: 5 additions & 5 deletions
diff --git a/‎css2/changes.src‎
Lines changed: 2 additions & 7 deletions b/‎css2/changes.src‎
Lines changed: 2 additions & 7 deletions
diff --git a/‎css2/colors.src‎
Lines changed: 2 additions & 2 deletions b/‎css2/colors.src‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎css2/conform.src‎
Lines changed: 9 additions & 8 deletions b/‎css2/conform.src‎
Lines changed: 9 additions & 8 deletions
diff --git a/‎css2/fonts.src‎
Lines changed: 14 additions & 14 deletions b/‎css2/fonts.src‎
Lines changed: 14 additions & 14 deletions
diff --git a/‎css2/generate.src‎
Lines changed: 3 additions & 3 deletions b/‎css2/generate.src‎
Lines changed: 3 additions & 3 deletions
diff --git a/‎css2/lists.src‎
Lines changed: 4 additions & 4 deletions b/‎css2/lists.src‎
Lines changed: 4 additions & 4 deletions
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html lang="en">
-<!-- $Id: aural.src,v 1.13 1997-12-30 14:37:38 ijacobs Exp $ -->
+<!-- $Id: aural.src,v 1.14 1998-01-14 17:44:33 ijacobs Exp $ -->
 <HEAD>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <TITLE>Aural style sheets</TITLE>
@@ -57,7 +57,7 @@ to me (perhaps through the 5 speaker home theater set-up)</i>
 
 <p>Hence, aural or mixed aural/visual presentation is likely to increase
 in importance over the next few years. Realizing that the aural
-rendering is essentially independent of the visual rendering:
+rendering is essentially independent of the visual rendering:</p>
 
 <ul>
 
@@ -82,7 +82,7 @@ class="propinst-volume">'volume'</span></H3>
 <p>Percentage values are calculated relative to the inherited value,
 and are then clipped to the range 0 to 100.
 
-<P>There is a fixed mapping between keyword values and volumes:
+<P>There is a fixed mapping between keyword values and volumes:</p>
 
 <UL>
 <li>'silent' = no sound at all, the element is spoken silently
@@ -105,7 +105,7 @@ range.
 100 to be set by the listener. No one setting is universally
 applicable; suitable values depend on the equipment in use (speakers,
 headphones), the environment (in car, home theater, library) and
-personal preferences. Some examples:
+personal preferences. Some examples:</p>
 
 <ul>
 <li>A browser for in-car use has a setting for when there is lots
@@ -373,7 +373,7 @@ Examples:
 do so. If spatial-azimuth is specified and the output device cannot
 produce sounds <em>behind</em> the listening position, values in the
 rearwards hemisphere should be converted into forwards hemisphere
-values.  One method is as follows:
+values.  One method is as follows:</p>
 
 <ul>
     <li>if 90deg &lt; x &lt;= 180deg then x := 180deg - x
 
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html lang="en">
-<!-- $Id: cascade.src,v 1.28 1998-01-12 12:18:51 ijacobs Exp $ -->
+<!-- $Id: cascade.src,v 1.29 1998-01-14 17:44:43 ijacobs Exp $ -->
 <HEAD>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <TITLE>Assigning property values, Cascading, and Inheritance</TITLE>
@@ -28,7 +28,7 @@ necessary.
 
 <P>User agents must first assign a <span class="index-def"
 title="specified value">specified value</span> to a property 
-based on the following mechanisms (in order of precedence):
+based on the following mechanisms (in order of precedence):</p>
 
 <ol>
 <li>If the <a href="#cascade">cascade</a> results in a value,
@@ -176,7 +176,7 @@ same property.
 <H2><a name="cascade">The cascade</a></h2>
 
 <P>Style sheets may have three different origins: author, user, and
-user agent.
+user agent.</p>
 
 <ul>
 <li><strong>Author</strong>. The author specifies style sheets
@@ -228,7 +228,7 @@ the same precedence rules apply.
 <H3><a name="cascading-order">Cascading order</a></H3>
 
 <P>To find the value for an element/property combination, user agents
-must apply the following algorithm:
+must apply the following algorithm:</p>
 
 <OL>
     <LI>
@@ -298,7 +298,7 @@ class="propinst-background">'background'</span>) to be important
 is equivalent to declaring all of its sub-properties important.
 
 <H3>Cascading order in HTML</H3>
-In HTML, a selector's specificity is calculated as follows:
+<P>In HTML, a selector's specificity is calculated as follows:</p>
 
 <ul>
 <li>(a) count the number of "id" attributes in the selector
 
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html lang="en">
-<!-- $Id: changes.src,v 1.10 1998-01-12 12:19:00 ijacobs Exp $ -->
+<!-- $Id: changes.src,v 1.11 1998-01-14 17:44:49 ijacobs Exp $ -->
 <HEAD>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <TITLE>Appendix B: Changes from CSS1</TITLE>
@@ -20,7 +20,7 @@ descriptions of CSS1 functionality, and changes to CSS1.
 
 <H2>New functionality</H2>
 
-<P>In addition to the functionality of CSS1, CSS2 supports:
+<P>In addition to the functionality of CSS1, CSS2 supports:</p>
 
 <UL>
 
@@ -69,8 +69,6 @@ semantics.
 
 <H2>Changes</H2>
 
-<P>In CSS2
-
 <UL>
 
 <LI>In CSS2 <A HREF="syndata.html#color-units">color values</A> are clipped
@@ -87,9 +85,6 @@ specification reflects this.
 <LI>Initial value of 'display' is 'inline', not 'block' as in CSS1.
 </UL>
 
-
-
-
 </BODY>
 </HTML>
 
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html lang="en">
-<!-- $Id: colors.src,v 1.23 1998-01-12 12:19:09 ijacobs Exp $ -->
+<!-- $Id: colors.src,v 1.24 1998-01-14 17:44:56 ijacobs Exp $ -->
 <HEAD>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <TITLE>Colors and backgrounds</TITLE>
@@ -196,7 +196,7 @@ positions are allowed.
 <P> One can also use keyword values to indicate the position of the
 background image. Keywords cannot be combined with percentage values,
 or length values.  The possible combinations of keywords and their
-interpretations are as follows:
+interpretations are as follows:</p>
 
   <UL>
     <LI>
 
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html lang="en">
-<!-- $Id: conform.src,v 1.37 1998-01-13 14:09:11 ijacobs Exp $ -->
+<!-- $Id: conform.src,v 1.38 1998-01-14 17:45:07 ijacobs Exp $ -->
 <HEAD>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <TITLE>Conformance: requirements and recommendations</TITLE>
@@ -46,8 +46,8 @@ inheritance</a>.</P>
 <dd>The <span class="index-def" title="valid style sheet">validity</span>
 of a style sheet depends on the level of CSS used for the style sheet.
 
-<P>All style sheets of level N-1 are valid level N style sheets. Thus,
-all CSS1 style sheets are valid CSS2 style sheets.
+<P>All valid level N-1 style sheets are valid level N style sheets. In
+particular, all valid CSS1 style sheets are valid CSS2 style sheets.
 
 <P>A valid CSS2 style sheet must respect the <a
 href="grammar.html">grammar of CSS2</a> and the <a
@@ -143,7 +143,7 @@ For example, the following HTML document:
 
 <P>results in the following tree:</P>
 
-<IMG src="images/doctree.gif" alt="Sample document tree">
+<P><IMG src="images/doctree.gif" alt="Sample document tree"></p>
 
 <P>According to the definition of HTML, HEAD elements will be inferred
 during parsing and become part of the document tree even if the HEAD
@@ -162,7 +162,7 @@ or otherwise use a document and its associated style sheets.</dd>
 <dt><dfn><strong><a name="user-agent">User agent</a></strong></dfn>
 <dd>A <span class="index-def" title="user agent|UA">user
 agent</span> is any program that interprets a document written in
-the document language and applies associated style sheets by according
+the document language and applies associated style sheets according
 to the terms of this specification. A user agent may display a
 document, read it aloud, cause it to be printed, convert it
 to another format, etc.</dd>
@@ -184,7 +184,8 @@ claiming conformance to this specification:</P>
 supports.
 <li>For each source document, it must retrieve all 
 associated style sheets that are appropriate for the supported media
-types.
+types. If a user agent cannot retrieve a specified style sheet,
+it should make a best effort to display the document.
 <li>It must parse the style sheets according to this specification.
 In particular, it must recognize all at-rules, blocks, declarations,
 and selectors (see the <a href="grammar.html">grammar of CSS2</a>).
@@ -205,7 +206,7 @@ assign a value for every supported property according to
 the rules of <a href="cascade.html">cascading and inheritance</a>.
 </ol>
 
-<P>Not every user agent must observe every point, however:
+<P>Not every user agent must observe every point, however:</p>
 
 <ul>
 <li>A user agent that <em>inputs</em> style sheets must
@@ -227,7 +228,7 @@ not imply non-conformance. </P>
 
 <p>This specification also recommends that a user agent offer the following
 functionality to the user (these do not refer to any specific
-user interface):
+user interface):</p>
 
 <UL>
  <LI>Allow the user to specify user style sheets
 
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html lang="en">
-<!-- $Id: fonts.src,v 1.33 1998-01-08 20:54:04 ijacobs Exp $ -->
+<!-- $Id: fonts.src,v 1.34 1998-01-14 17:45:37 ijacobs Exp $ -->
 <HEAD>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <TITLE>Fonts</TITLE>
@@ -33,7 +33,7 @@ representations, all observing same basic motif according to design,
 size, appearance, and other attributes associated with the entire set.
 
 <P>A visual user agent must address the following issues before actually
-	rendering a character:
+	rendering a character:</p>
 
 <ul>
 <li>Has the author specified a font for this character?
@@ -353,7 +353,7 @@ sometimes <EM>Medium</EM>.
 <P> The association of other weights within a family to the numerical
 weight values is intended only to preserve the ordering of darkness
 within that family. However, the following heuristics tell how the
-assignment is done in typical cases:
+assignment is done in typical cases:</p>
 
 <UL>
     <LI>
@@ -411,7 +411,7 @@ weight values, the matching of 'bolder' is to the next darker face
 available on the client within the family and the matching of
 'lighter' is to the next lighter face within the family.  To be
 precise, the meaning of the relative keywords 'bolder' and 'lighter'
-is as follows:
+is as follows:</p>
 
 <UL>
     <LI>
@@ -703,7 +703,7 @@ available fonts, etc. The details of the <a href="#algorithm">font
 matching algorithm</a> are provided below.
 
 <P>There are four possible font selection actions:
-matching, intelligent matching, synthesis, and download.
+matching, intelligent matching, synthesis, and download.</p>
 
 <UL>
 
@@ -788,7 +788,7 @@ vary from just the name of the font up to a list of glyph
 representation widths. This data is a subset of the glyph
 representation metrics contained in the font.
 
-<P>Font descriptors may be classified into three types:
+<P>Font descriptors may be classified into three types:</p>
 
 <ol>
 <li>those that provide the link between the CSS usage of the font and
@@ -950,7 +950,7 @@ same reason).
 <p>This is the descriptor for the weight of a face relative to others
 in the same font family. It takes the same values as the <span
 class="propinst-font-weight">'font-weight'</span> property with three
-exceptions:
+exceptions:</p>
 
 <ol><li>relative keywords (bolder, lighter) are not permitted
 <li>a comma separated list of values is permitted
@@ -1403,7 +1403,7 @@ or alternative stylesheet languages. Fonts retrieved by one medium and
 stored in a proxy cache could be re-used by another medium, saving
 download time and network bandwidth.
 
-<p>A non-exhaustive list examples of such media includes:
+<p>A non-exhaustive list examples of such media includes:</p>
 
 <ul>
 <li>2-D vector formats
@@ -1614,8 +1614,7 @@ heights, as a means of comparison between font families. The terms
 large-eye, small-eye are also used to indicate the height of lowercase
 glyph representations relative to the height of uppercase.
 
-<br>
-<img src="./images/x-height.gif" alt="Illustration of x-height">
+<P><img src="./images/x-height.gif" alt="Illustration of x-height"></p>
 
 <p>This descriptor is not useful for fonts that do not contain any glyph
 representations from these scripts. Since the heights of lowercase and
@@ -1624,8 +1623,9 @@ different fonts, it may be useful to set both the lowercase and
 uppercase heights to the same value for unicameral scripts such as
 Hebrew, where for mixed Latin and Hebrew text the Hebrew characters
 are typically set at a height midway between the capital and lowercase
-heights of the Latin font.<br>
-<img src="./images/heb-height-54.gif" alt="Height of Hebrew characters">
+heights of the Latin font.
+
+<P><img src="./images/heb-height-54.gif" alt="Height of Hebrew characters"></p>
 
 <p>For Type 1 fonts, this value may be obtained from the
 <tt>Bluevalues</tt> entry in the Private dictionary.
@@ -1792,7 +1792,7 @@ results of this matching process are as consistent as possible across
 UAs (assuming that the same library of font faces and font
 descriptions is presented to each of them). This algorithm may be
 optimized, provided that an implementation behaves as if the algorithm
-had been followed exactly.
+had been followed exactly.</p>
 
 <OL>
 
@@ -1918,7 +1918,7 @@ the CSS2 properties for each character.
 </em>
 </div>
 
-<P>The per-descriptor matching rules from (2) above are as follows:
+<P>The per-descriptor matching rules from (2) above are as follows:</p>
 
 
 <OL>
 
@@ -21,11 +21,11 @@ seventh chapter title. For audio or braille in particular, user agents
 should be able to insert these strings.
 
 <p>The inserted content can consist of fixed strings (e.g., "Figure"),
-fixed images (such as an icon: <img src="images/caution.gif"
+fixed images (such as an icon: <img id="caution-img" src="images/caution.gif"
 alt="caution icon">), or counters that automatically
 increment. Combinations are also possible ("Chapter 7").
 
-<P>The following sections describe the mechanisms CSS2 offers
+<P>Below we describe the mechanisms CSS2 offers
 for specifying generated content.
 
 <h2><a name="before-after-content">The</a> <span class="index-def"
@@ -83,7 +83,7 @@ BODY:after {
 property is a sequence of strings, URIs, and counters. The various
 parts are laid out as inline boxes inside the element.</p>
 
-<P>The values have the following meanings:
+<P>The values have the following meanings:</p>
 
 <ul>
 <li><span class="index-def" title="&lt;string&gt;, definition of"><a
 
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html lang="en">
-<!-- $Id: lists.src,v 1.15 1998-01-08 20:16:23 ijacobs Exp $ -->
+<!-- $Id: lists.src,v 1.16 1998-01-14 17:46:34 ijacobs Exp $ -->
 <HEAD>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <TITLE>Lists</TITLE>
@@ -61,7 +61,7 @@ marker will appear next to list items:
 
 <P>The list might be formatted as follows:</P>
 
-<img src="./images/list-none.gif" alt="A list with no markers.">
+<P><img src="./images/list-none.gif" alt="A list with no markers."></p>
 
 <P>The illustration shows the relationship between the current left
 margin and the margins and padding of the list element (UL) and the
@@ -79,7 +79,7 @@ LI { display: list-item; list-style: square }
 placement of the square does not affect the block formatting of the
 list item content:</P>
 
-<img src="./images/list-square.gif" alt="A list with square markers.">
+<p><img src="./images/list-square.gif" alt="A list with square markers."></p>
 </div>
 
 <div class="note"><P>
@@ -222,7 +222,7 @@ For example:
 
 <P> The above example may be formatted as:</P>
 
-<img src="./images/list-inout.gif" alt="Difference between inside and outside list style position">
+<P><img src="./images/list-inout.gif" alt="Difference between inside and outside list style position"></p>
 </div>
 
 <P>In right-to-left text, the markers would have been on the right