bocoup
diff --git a/‎css2/colors.src‎
Lines changed: 58 additions & 25 deletions b/‎css2/colors.src‎
Lines changed: 58 additions & 25 deletions
diff --git a/‎css2/fonts.src‎
Lines changed: 42 additions & 25 deletions b/‎css2/fonts.src‎
Lines changed: 42 additions & 25 deletions
@@ -1,23 +1,30 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html lang="en">
-<!-- $Id: colors.src,v 2.27 2002-08-02 17:37:18 bbos Exp $ -->
+<!-- $Id: colors.src,v 2.28 2002-11-17 19:28:26 bbos Exp $ -->
 <HEAD>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <TITLE>Colors and backgrounds</TITLE>
+<!-- Changed by: Tantek Celik, 2002-11-16 -->
+<style type="text/css">
+.current,.proposed { background:#feb }
+ins.proposed { background:#bfb }
+del.proposed { background:#fbb }
+body>del,body>ins {display:block}
+</style>
 </HEAD>
 <BODY>
 <H1>Colors and Backgrounds</H1>
 
-<P>CSS properties allow authors to specify the foreground color and
+<p>CSS properties allow authors to specify the foreground color and
 background of an element. Backgrounds may be colors or
 images. Background properties allow authors to position a background image,
 repeat it, and declare whether it should be fixed with respect
 to the <a href="visuren.html#viewport">viewport</a> or scrolled
 along with the document.
-
-<P> See the section on <a href="./syndata.html#color-units">color units</a>
+</p>
+<p> See the section on <a href="./syndata.html#color-units">color units</a>
 for the syntax of valid color values. 
-
+</p>
 <H2><a name="colors">Foreground color</a>: the <span
 class="propinst-color">'color'</span> property</H2>
 
@@ -44,8 +51,7 @@ href="box.html#box-padding-area">padding</a> and <a
 href="box.html#box-border-area">border</a> areas. Border colors
 and styles are set with the <a
 href="box.html#border-properties">border properties</a>.  Margins
-are always transparent so the background of the parent box always
-shines through.
+are always transparent.
 
 <P>Background properties are not inherited, but the parent box's
 background will shine through by default because of the initial
@@ -76,7 +82,7 @@ HTML document will have a "marble" background:
   &lt;HEAD&gt;
     &lt;TITLE&gt;Setting the canvas background&lt;/TITLE&gt;
     &lt;STYLE type="text/css"&gt;
-       BODY { background: url("http://style.com/marble.png") }
+       BODY { background: url("http://example.com/marble.png") }
     &lt;/STYLE&gt;
   &lt;/HEAD&gt;
   &lt;BODY&gt;
@@ -123,6 +129,7 @@ the color is visible in the transparent parts of the image).
 title="&lt;uri&gt;"><span
 class="value-inst-uri">&lt;uri&gt;</span></span>, to specify the
 image, or 'none', when no image is used.
+</P>
 
 <div class="example"><P>
 <PRE>
@@ -133,12 +140,18 @@ p { background-image: none }
 
 <!-- #include src=properties/background-repeat.srb -->
 
-<P>If a background image is specified, this property specifies whether
+<p>If a background image is specified, this property specifies whether
 the image is repeated (tiled), and how.  All tiling covers the <a
 href="box.html#box-content-area">content</a>, <a
 href="box.html#box-padding-area">padding</a> and <a
 href="box.html#box-border-area">border</a> areas of a box.
-Values have the following meanings:</p>
+<ins class="proposed">
+The tiling and positioning of the 
+background-image on inline elements is undefined in this specification. 
+A future level of CSS may define the tiling and positioning of the 
+background-image on inline elements. 
+</ins>
+<p>Values have the following meanings:</p>
 
 <dl>
 <dt><strong>repeat</strong>
@@ -171,14 +184,15 @@ the element.
 
 <!-- #include src=properties/background-attachment.srb -->
 
-<P>If a background image is specified, this property specifies
+<p>If a background image is specified, this property specifies
 whether it is fixed with regard to the <a
-href="visuren.html#viewport">viewport</a> ('fixed') or scrolls along with the
-document ('scroll').
+href="visuren.html#viewport">viewport</a> ('fixed') or scrolls along
+with the containing block ('scroll').</p>
 
-<p>Note that there is only one viewport per view. If an element has a
-scrolling mechanism (see 'overflow'), a 'fixed' background doesn't
-move with it.
+<p>Note that there is only one viewport per view. If an element has
+a scrolling mechanism (see 'overflow'), a 'fixed' background doesn't
+move with the element, and a 'scroll' background doesn't move with
+the scrolling mechanism.</p>
 
 <p>Even if the image is fixed, it is still only visible when it is in
 the background, padding or border area of the element. Thus, unless
@@ -195,10 +209,29 @@ body {
 </PRE>
 </div>
 
-<P>User agents may treat 'fixed' as 'scroll'. However, it is
+<del class="current">
+<p>
+User agents may treat 'fixed' as 'scroll'. However, it is
 recommended they interpret 'fixed' correctly, at least for the HTML and
 BODY elements, since there is no way for an author to provide an image
-only for those browsers that support 'fixed'. See the section on <a
+only for those browsers that support 'fixed'. 
+</p>
+</del>
+<ins class="proposed">
+<p>
+User agents that do not support 'fixed' backgrounds (for example due
+to limitations of the hardware platform) should ignore declarations
+with the keyword 'fixed'. For example:
+</p>
+<pre>
+body {
+  background: white url(paper.png) scroll; /* for all UAs */
+  background: white url(ledger.png) fixed; /* for UAs that do fixed backgrounds */
+}
+</pre>
+</ins>
+<p>
+See the section on <a
 href="conform.html#conformance">conformance</a> for details.
 
 <!-- #include src=properties/background-position.srb -->
@@ -223,8 +256,8 @@ across and 84% down the padding area.
 class="value-inst-length"><strong>&lt;length&gt;</strong></span></span>
  <span class="index-inst" title="&lt;length&gt;"><span
 class="value-inst-length"><strong>&lt;length&gt;</strong></span></span>
-<dd> With a value pair of '2cm 2cm', the upper left corner of the image
-is placed 2cm to the right and 2cm below the upper left corner of the
+<dd> With a value pair of '2cm 1cm', the upper left corner of the image
+is placed 2cm to the right and 1cm below the upper left corner of the
 padding area.
 <dt>
 <dt><strong>top left</strong> and <strong>left top</strong>
@@ -254,14 +287,14 @@ padding area.
 <dd>Same as '100% 100%'.
 </dl>
 
-<P> If only one percentage or length value is given, it sets the
-horizontal position only, the vertical position will be 50%. If two
+<p> If only one percentage or length value is given, it sets the
+horizontal position only, and the vertical position will be 50%. If two
 values are given, the horizontal position comes first. Combinations of
 length and percentage values are allowed, (e.g., '50% 2cm'). Negative
 positions are allowed. Keywords cannot be combined with percentage
 values or length values (all possible combinations are given above).
-
-<div class="example"><P>
+</p>
+<div class="example">
 
 <PRE>
 body { background: url("banner.jpeg") right top }    /* 100%   0% */
@@ -353,7 +386,7 @@ on current platforms is:
 converted to R'=R<SUP>gamma</SUP>, G'=G<SUP>gamma</SUP>,
 B'=B<SUP>gamma</SUP>, before being handed to the OS.
 
-<P>This may rapidly be done by building a 256-element lookup table
+<P>This may be done rapidly by building a 256-element lookup table
 once per browser invocation thus:
 
 <PRE>
 
@@ -1,49 +1,56 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
         "http://www.w3.org/TR/1998/REC-html40-19980424/loose.dtd">
 <html lang="en">
-<!-- $Id: fonts.src,v 2.68 2002-08-02 19:30:33 bbos Exp $ -->
+<!-- $Id: fonts.src,v 2.69 2002-11-17 19:28:45 bbos Exp $ -->
 <HEAD>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <TITLE>Fonts</TITLE>
+<!-- Changed by: Tantek Celik, 2002-11-16 -->
 <style type="text/css">
 #AutoNumber2 td { text-align:center }
 </style>
-<!-- Changed by: Tantek Celik, 2002-06-09 -->
+<style type="text/css">
+.current,.proposed { background:#feb }
+ins.proposed { background:#bfb }
+del.proposed { background:#fbb }
+body>del,body>ins {display:block}
+</style>
 </HEAD>
 <BODY>
 
 <h1>Fonts</h1>
 
 <h2>Introduction</h2>
 
-<P>Setting font properties will be among the most common uses of style
+<p>Setting font properties will be among the most common uses of style
 sheets. Unfortunately, there exists no well-defined and universally
 accepted taxonomy for classifying fonts, and terms that apply to one
 font family may not be appropriate for others. E.g. 'italic' is
 commonly used to label slanted text, but slanted text may also be
 labeled as being <EM>Oblique, Slanted, Incline, Cursive</EM> or
 <EM>Kursiv</EM>. Therefore it is not a simple problem to map typical
 font selection properties to a specific font.
+</p>
 
 <h2><a name="algorithm">Font matching algorithm</a></h2>
 
-<P>Because there is no accepted, universal taxonomy of font
+<p>Because there is no accepted, universal taxonomy of font
 properties, matching of properties to font faces must be done
 carefully. The properties are matched in a well-defined order to
 insure that the results of this matching process are as consistent as
 possible across UAs (assuming that the same library of font faces is
 presented to each of them).
+</p>
 
 <OL>
 
 <LI>The User Agent makes (or accesses) a database of relevant CSS&nbsp;2.1
-properties of all the fonts of which the UA is aware. The UA may be
-aware of a font because it has been installed locally or it has been
-previously downloaded over the web. If there are two fonts with
+properties of all the fonts of which the UA is aware. 
+If there are two fonts with 
 exactly the same properties, one of them is ignored.
 
 <LI>At a given element and for each character in that element, the UA
-assembles the font-properties applicable to that element. Using the
+assembles the font properties applicable to that element. Using the
 complete set of properties, the UA uses the 'font-family' property to
 choose a tentative font family. The remaining properties are tested
 against the family according to the matching criteria described with
@@ -98,8 +105,9 @@ never fail. (See 'font-weight' below.)
 UA-dependent margin of tolerance. (Typically, sizes for scalable fonts
 are rounded to the nearest whole pixel, while the tolerance for
 bitmapped fonts could be as large as 20%.) Further computations, e.g.
-by 'em' values in other properties, are based on the 'font-size' value
-that is used, not the one that is specified.
+by 'em' values in other properties, are based on 
+the computed value of 'font-size'.
+
 
 </OL>
 
@@ -113,21 +121,27 @@ family names. Unlike most other CSS properties, values are separated
 by a comma to indicate that they are alternatives:
 
 <PRE>
-body { font-family: gill, helvetica, sans-serif }
+body { font-family: Gill, Helvetica, sans-serif }
 </PRE>
 
 <P>Although many fonts provide the "missing character" glyph,
   typically an open box, as its name implies this should not be
-  considered a match.
+  considered a match
+  <del class="current">.</del>
+  <ins class="proposed">
+  for characters that cannot be found in the font. (It should,
+however, be considered a match for U+FFFD, the "missing character"
+character's code point).
+</ins>
 
 <P>There are two types of font family names:
 
 <DL>
 
 <dt><a name="value-def-family-name">&lt;family-name&gt;</a>
 
-<DD>The name of a font family of choice. In the last example, "gill"
-and "helvetica" are font families.
+<DD>The name of a font family of choice. In the last example, "Gill"
+and "Helvetica" are font families.
 
 <dt><a name="value-def-generic-family">&lt;generic-family&gt;</a>
 
@@ -149,14 +163,14 @@ following generic families are defined:
 </UL>
 
 <P>Style sheet designers are encouraged to offer a generic font family
-as a last alternative.
+as a last alternative.  Generic font family names are keywords and must NOT be quoted.
 
 </DL>
 
 <P>Font names containing whitespace should be quoted:
 
 <PRE>
-body { font-family: "new century schoolbook", serif }
+body { font-family: "New Century Schoolbook", serif }
 
 &lt;BODY STYLE="font-family: 'My own font', fantasy"&gt;
 </PRE>
@@ -213,7 +227,8 @@ characters. As a last resort, uppercase letters will be used as
 replacement for a small-caps font.
 
 <P>The following example results in an 'H3' element in small-caps,
-with emphasized words in oblique small-caps:
+with any emphasized words in oblique, and any emphasized words within 
+an 'H3' oblique small-caps:
 
 <PRE>
 h3 { font-variant: small-caps }
@@ -259,8 +274,8 @@ strong { font-weight: bolder }
 values are names that are descriptive of the "weight" of a font. There
 is no accepted, universal meaning to these weight names. Their primary
 role is to distinguish faces of differing darkness within a single
-font family. Usage across font families is quite variant; for example
-a font that you might think of as being bold might be described as
+font family. Usage across font families is quite variant; for example, 
+a font that one might think of as being bold might be described as
 being <EM>Regular, Roman, Book, Medium, Semi-</EM> or <EM>DemiBold,
 Bold,</EM> or <EM>Black,</EM> depending on how black the "normal" face
 of the font is within the design. Because there is no standard usage
@@ -364,7 +379,7 @@ the next lighter numerical value (and keeps the font unchanged).
 
 <P>There is no guarantee that there will be a darker face for each of
 the 'font-weight' values; for example, some fonts may have only a
-normal and a bold face, others may have eight different face weights.
+normal and a bold face, while others may have eight face weights.
 There is no guarantee on how a UA will map font faces within a family
 to weight values. The only guarantee is that a face of a given value
 will be no less dark than the faces of lighter values.
@@ -446,7 +461,7 @@ to another.
 
 <p class="note"><em><strong>Note 1.</strong> To preserve readability, a UA applying 
 these guidelines should nevertheless avoid creating font-size resulting
- in less than 9 pixels per EM unit on a computer display .</em></p>
+ in less than 9 pixels per EM unit on a computer display.</em></p>
 
 <p class="note"><em><strong>Note 2.</strong> In CSS1, the suggested
 scaling factor between adjacent indexes was 1.5 which user experience
@@ -476,8 +491,8 @@ into account when calculating the font size of the element.
 <P>Negative values are not allowed.
 
 <P>On all other properties, 'em' and 'ex' length values refer to the
-font size of the current element. On the 'font-size' property, these
-length units refer to the font size of the parent element.
+computed font size of the current element. On the 'font-size' property, these
+length units refer to the computed font size of the parent element.
 
 <P>Note that an application may reinterpret an explicit size,
 depending on the context. E.g., inside a VR scene a font may get a
@@ -522,7 +537,7 @@ For a definition of allowed and initial values, see the previously defined prope
 <PRE>
 p { font: 12px/14px sans-serif }
 p { font: 80% sans-serif }
-p { font: x-large/110% "new century schoolbook", serif }
+p { font: x-large/110% "New Century Schoolbook", serif }
 p { font: bold italic large Palatino, serif }
 p { font: normal small-caps 120%/120% fantasy }
 </PRE>
@@ -562,7 +577,8 @@ fonts">system fonts</span>:</p>
 </dl>
 
 <P>System fonts may only be set as a whole; that is, the font
-family, size, weight, style, etc. are all set at the same time.These values may then be altered individually if desired.  If no
+family, size, weight, style, etc. are all set at the same time. 
+These values may then be altered individually if desired.  If no
 font with the indicated characteristics exists on a given platform,
 the user agent should either intelligently substitute (e.g., a smaller
 version of the 'caption' font might be used for the 'small-caption'
@@ -600,6 +616,7 @@ to its initial value, this has the same effect as this declaration:
 
 <pre>
 button p {
+  font-family: Charcoal;
   font-style: normal;
   font-variant: normal;
   font-weight: 600;