W3C home > Mailing lists > Public > www-archive@w3.org > June 2009

Re: Spelling changes

From: L. David Baron <dbaron@dbaron.org>
Date: Mon, 8 Jun 2009 10:10:50 -0400
To: Bert Bos <bert@w3.org>, fantasai@inkedblade.net
Message-ID: <20090608141050.GA9927@pickering.dbaron.org>
On Thursday 2009-06-04 18:11 +0200, L. David Baron wrote:
> Here is my current spelling fixes diff, but I want to research a few
> of these a bit more.

OK, I think these are correct.  Is it OK if I check them in, or
should I let someone else do that?

(Also, my inclination is to leave the misspelled named anchor
("about.html#acknowledgements") misspelled rather than fixing it.)

-David

> Index: box.src
> ===================================================================
> RCS file: /w3ccvs/WWW/Style/Group/css2-src/box.src,v
> retrieving revision 1.74
> diff -p -u -1 -2 -r1.74 box.src
> --- box.src	3 Feb 2009 11:24:59 -0000	1.74
> +++ box.src	4 Jun 2009 16:10:20 -0000
> @@ -433,26 +433,26 @@ blockquote { padding-top: 0.3em }
>  
>  <!-- #include src=properties/padding.srb -->
>  
>  <P> The <span class="propinst-padding">'padding'</span> property is a
>  shorthand property for setting <span
>  class="propinst-padding-top">'padding-top'</span>, <span
>  class="propinst-padding-right">'padding-right'</span>, <span
>  class="propinst-padding-bottom">'padding-bottom'</span>, and <span
>  class="propinst-padding-left">'padding-left'</span> at the same place
>  in the style sheet.
>  
>  <P> If there is only one value, it applies to all
> -sides. If there are two values, the top and bottom paddings
> -are set to the first value and the right and left paddings are
> +sides. If there are two values, the top and bottom padding
> +are set to the first value and the right and left puddings are
>  set to the second. If there are three values, the top is
>  set to the first value, the left and right are set to the
>  second, and the bottom is set to the third. If there are
>  four values, they apply to the top, right, bottom, and left,
>  respectively.
>  
>  <P> The surface color or image of the padding area is specified via
>  the <span class="propinst-background">'background'</span> property:
>  
>  <div class="example"><P>
>  <PRE>
>  h1 { 
> @@ -761,25 +761,25 @@ blockquote {
>  while the other borders are red. This is due to <span
>  class="propinst-border-left">'border-left'</span> setting the
>  width, style, and color. Since the color value is not given by the
>  <span class="propinst-border-left">'border-left'</span> property, it
>  will be taken from the <span class="propinst-color">'color'</span>
>  property. The fact that the <span
>  class="propinst-color">'color'</span> property is set after the <span
>  class="propinst-border-left">'border-left'</span> property is not
>  relevant.
>  </div>
>  
>  
> -<h2><a name="bidi-box-model">The box model for inline elements in bidirection context</a></h2>
> +<h2><a name="bidi-box-model">The box model for inline elements in bidirectional context</a></h2>
>  
>  <p>For each line box, UAs must take the inline boxes generated for
>  each element and render the margins, borders and padding in visual
>  order (not logical order).
>  
>  <p>When the element's <span
>  class=propinst-direction>'direction'</span> property is 'ltr', the
>  left-most generated box of the first line box in which the element
>  appears has the left margin, left border and left padding, and the
>  right-most generated box of the last line box in which the element
>  appears has the right padding, right border and right margin.
>  
> Index: cascade.src
> ===================================================================
> RCS file: /w3ccvs/WWW/Style/Group/css2-src/cascade.src,v
> retrieving revision 2.67
> diff -p -u -1 -2 -r2.67 cascade.src
> --- cascade.src	19 May 2009 17:25:35 -0000	2.67
> +++ cascade.src	4 Jun 2009 16:10:20 -0000
> @@ -72,25 +72,25 @@ cannot be determined until the width of 
>  determined. The <dfn id="usedValue">used value</dfn> is the result of
>  taking the computed value and resolving any remaining dependencies
>  into an absolute value.
>  
>  <h3><span class="index-def" title="actual value">
>  <a name="actual-value">Actual values</a></span></h3>
>  
>  <p>A used value is in principle the value used for rendering, but a
>  user agent may not be able to make use of the value in a given
>  environment. For example, a user agent may only be able to render
>  borders with integer pixel widths and may therefore have to
>  approximate the computed width, or the user agent may be forced to
> -use only black and white shades instead of full colour. The actual
> +use only black and white shades instead of full color. The actual
>  value is the used value after any approximations have been applied.
>  
>  
>  <h2><a name="inheritance">Inheritance</a></h2>
>  
>  <p>Some values are inherited by the children of an element in the <a
>  href="conform.html#doctree">document tree</a>, as described <a
>  href="#specified-value">above</a>. Each property <a
>  href="about.html#property-defs">defines</a> whether it is inherited or
>  not.
>  
>  <div class="html-example"><P>
> Index: changes.src
> ===================================================================
> RCS file: /w3ccvs/WWW/Style/Group/css2-src/changes.src,v
> retrieving revision 2.111
> diff -p -u -1 -2 -r2.111 changes.src
> --- changes.src	20 May 2009 14:15:28 -0000	2.111
> +++ changes.src	4 Jun 2009 16:10:20 -0000
> @@ -83,25 +83,25 @@ in property definitions to be non-normat
>  
>  <p>A new line is added to each property definition specifying what the computed
>  values are for the property. (This defines what level of computation is done to
>  a property value before inheritance and before certain other calculations.)</p>
>  
>  <h3 id="c1.4.4"><a href="about.html#notes-and-examples">Section 1.4.4 Notes and examples</a></h3>
>  
>  <p>This section (formerly 1.3.4) now specifies that HTML examples lacking DOCTYPE
>  declarations are SGML Text Entities conforming to the HTML 4.01 Strict DTD [HTML4].
>  The markup for many examples has been reformulated to either include a DOCTYPE or
>  conform to this definition.</p>
>  
> -<h3 id="c1.5"><a href="about.html#acknowledgements">Section 1.5 Acknowledgements</a></h3>
> +<h3 id="c1.5"><a href="about.html#acknowledgements">Section 1.5 Acknowledgments</a></h3>
>  
>  <p>This section (formerly 1.4) has been updated to reflect contributions to CSS2.1
>  and has been marked non-normative.<p>
>  
>  <h3 id="c3.2"><a href="conform.html#conformance">Section 3.2
>  Conformance</a></h3>
>  
>  <p>Support for user style sheets is now required (in most cases),
>  rather than just recommended.
>  
>  <p>Support for turning of author style sheets is now required.</p>
>  
> @@ -120,25 +120,25 @@ in most cases.</p>
>  <p>Added INVALID token and rules for its definition.</p>
>  
>  <p>An optional hyphen, "-", is now allowed at the beginning of an "ident"
>  for vendor extensions. (See section 4.1.2.1)</p>
>  
>  <p id="underscore">The underscore character
>  ("_") is allowed in identifiers. The definitions of the lexical
>  macros "nmstart" and "nmchar" now include it. See also section
>  4.1.2.1 (Vendor extensions).</p>
>  
>  <p>The "escape" macro has been modified to allow the escaping of any
>  character except newlines, form feeds, and hex digits (to avoid
> -conflict with unicode escapes).</p>
> +conflict with Unicode escapes).</p>
>  
>  <p>Modified "string1" and "string2" macros by defining allowed characters
>  through excluding disallowed characters. This allows invisible ASCII
>  characters to be included in a string.</p>
>  
>  <h3 id="c4.1.3"><a href="syndata.html#characters">Section 4.1.3
>  Characters and case</a></h3>
>  
>  <p>Updated prose about identifiers (second bullet point) to match changes
>  in the tokenization (above).</p>
>  
>  <p>Excluded null (0x0) character from CSS numerical escapes and indicate that
> @@ -171,25 +171,25 @@ have been moved to the informative Appen
>  Lengths</a></h3>
>  
>  <p>Added a paragraph on heuristics for finding the x-height of a font.</p>
>  
>  <h3 id="c4.3.4"><a href="syndata.html#uri">Section 4.3.4
>  URLs and URIs</a></h3>
>  
>  <p>Updated URI references to RFC3986.</p>
>  
>  <h3 id="c4.3.5"><a href="syndata.html#counter">Section 4.3.5
>  Counters</a></h3>
>  
> -<p>Changed "Counters are denoted by identifiers" to "ounters are
> +<p>Changed "Counters are denoted by identifiers" to "Counters are
>  denoted by <ins>case-sensitive</ins> identifiers" (see also the
>  change to case-sensitivity in <a href="#c4.1.3">4.1.3</a>).
>  
>  <h3 id="c4.3.6"><a href="syndata.html#color-units">Section 4.3.6
>  Colors</a></h3>
>  
>  <p>Defined the numeric values corresponding to color keywords instead
>  of referencing HTML4 for those values.</p>
>  
>  <p>UAs are now allowed to intelligently map colors outside the gamut
>  into the gamut instead of simply clipping them into the range of the
>  gamut.</p>
> @@ -391,25 +391,25 @@ collapse.
>  padding, then the resulting layout is undefined in CSS 2.1.</p>
>  
>  <h3 id="c8.5.2"><a href="box.html#border-color-properties">Section 8.5.2 Border color</a></h3>
>  
>  <p>'transparent' can now be specified independently for each border side,
>  on par with &lt;color>.</p>
>  
>  <h3 id="c8.5.3"><a href="box.html#border-style-properties">Section 8.5.3 Border style</a></h3>
>  
>  <p>3D border styles ('groove', 'ridge', 'inset', 'outset') now depend on the
>  corresponding border-color rather than on 'color'.</p>
>  
> -<h3 id="c8.6"><a href="box.html#bidi-box-model">Section 8.6 The box model for inline elements in bidirection context</a></h3>
> +<h3 id="c8.6"><a href="box.html#bidi-box-model">Section 8.6 The box model for inline elements in bidirectional context</a></h3>
>  
>  <p>Added this new section to specify layout of inline boxes when affected by bidi.</p>
>  
>  <h3 id="c9.1.2"><a href="visuren.html#containing-block">Section 9.1.2
>  Containing blocks</a></h3>
>  
>  <p>Removed paragraphs about the initial containing block, as this is
>  now defined differently. (See <a href="#initial-containing-block">changes
>  to section 10.1</a>.)</p>
>  
>  <h3 id="c9.2.1.1"><a href="visuren.html#anonymous-block-level">Section 9.2.1.1
>  Anonymous block boxes</a></h3>
> @@ -689,25 +689,25 @@ absolutely positioned element.
>  in resulting in a negative margin on the start edge.</p>
>  
>  <h3 id="c10.4"><a href="visudet.html#min-max-widths">Section 10.4
>  Minimum and maximum widths</a></h3>
>  
>  <p>Specified that if the containing block's width is negative, the
>  used value of a percentage min/max width is zero.</p>
>  
>  <p>Specified that if the min/max width is specified in percentages and
>  the containing block's width depends on this element's width, then the
>  resulting layout is undefined in CSS 2.1.</p>
>  
> -<p>The UA is no longer allowed to select an aribtrary minimum width.</p>
> +<p>The UA is no longer allowed to select an arbitrary minimum width.</p>
>  
>  <p>The used width of replaced elements with an intrinsic ratio and both
>  'width' and 'height' specified as 'auto' is now calculated according to
>  a table designed to preserve the intrinsic ratio as much as possible
>  within the given constraints.</p>
>  
>  <h3 id="c10.5"><a href="visudet.html#the-height-property">Section 10.5
>  Content height</a></h3>
>  
>  <p>Removed mention of 'line-height' for inline elements since their
>  content box height no longer depends on 'line-height'.</p>
>  
> @@ -721,25 +721,25 @@ to the initial containing block.</p>
>  <h3 id="c10.6"><a href="visudet.html#Computing_heights_and_margins">Section 10.6
>  Calculating heights and margins</a></h3>
>  
>  <p>The computed values of 'top' and 'bottom' for are now defined in
>  <a href="visuren.html#position-props">section 9.3.2</a>. The value
>  'auto' does not always compute to zero.</p>
>  
>  <p>Added section 10.6.6 to cover cases that are no longer covered under
>  the previous sections.</p>
>  
>  <p>Added section 10.6.7 to define 'auto' heights for block formatting
>  context roots. (Unlike other block boxes, the height of these boxes
> -increases to accomodate any normal-flow descendant floats.)</p>
> +increases to accommodate any normal-flow descendant floats.)</p>
>  
>  <h3 id="c10.6.1"><a href="visudet.html#inline-non-replaced">Section 10.6.1
>  Inline, non-replaced elements</a></h3>
>  
>  <p>The height of an inline box is no longer given by the 'line-height'
>  property and is now undefined. This section now suggests that the
>  height of the box can be based on the font.</p>
>  
>  <h3 id="c10.6.2"><a href="visudet.html#inline-replaced-height">Section 10.6.2
>  Inline replaced elements, block-level replaced elements in normal flow,
>  'inline-block' replaced elements in normal flow and floating replaced elements</a></h3>
>  
> @@ -837,25 +837,25 @@ property on the HTML BODY element instea
>  <p>The width of any scrollbars is no longer included in the width of
>  the containing block. (And consequently, all text in section?10.3 that
>  subtracts the scrollbar width from the containing block width has been
>  removed.)
>  
>  <h3 id="c11.1.2"><a href="visufx.html#clipping">Section 11.1.2 Clipping:
>  the 'clip' property</a></h3>
>  
>  <p>The 'clip' property now applies only to absolutely positioned elements.
>  Furthermore, it applies to those elements even when their 'overflow' is
>  'visible'.</p>
>  
> -<p>The default value of 'clip', 'auto', now indiciates no clipping
> +<p>The default value of 'clip', 'auto', now indicates no clipping
>  rather than clipping to the element's border box.</p>
>  
>  <p>Values of "rect()" should be separated by commas. UAs are
>  required to support this syntax, but may also support a space-separated
>  syntax since CSS2 was not clear about this.</p>
>  
>  <p>While CSS2 specified that values of "rect()" give offsets from the
>  respective sides of the box, current implementations interpret values
>  with respect to the top and left edges for <em>all</em> four values
>  (top, right, bottom, and left). This is now the specified
>  interpretation.
>  
> @@ -924,25 +924,25 @@ scope explicitly.)</p>
>  
>  <h3 id="c12.5"><a href="generate.html#lists">Section 12.5
>  Lists</a></h3>
>  
>  <p>Removed text in section 12.5 (formerly 12.6) relating to the
>  'marker' display value.</p>
>  
>  <p>Removed the 'marker-offset' property (and thus former section 12.6.1).</p>
>  
>  <h3 id="c12.5.1"><a href="generate.html#list-style">Section 12.5.1
>  Lists</a></h3>
>  
> -<p>The list styles 'hebrew', 'armenian', 'georgian', 'cjk-ideographs',
> +<p>The list styles 'hebrew', 'armenian', 'georgian', 'cjk-ideographic',
>  'hiragana', 'katakana', 'hiragana-iroha' and 'katakana-iroha' have
>  been removed due to lack of implementation experience. (They are
>  expected to return in the CSS3 Lists module.)</p>
>  
>  <p>Removed the sentence that said that an unknown value for
>  'list-style-type' should cause the value 'decimal' to be used instead. 
>  Instead, normal parsing rules apply and cause the rule to be
>  ignored.</p>
>  
>  <p>The size of list style markers without an intrinsic size is now
>  defined.
>  
> @@ -1008,26 +1008,26 @@ defined.
>  <h3 id="c15"><a href="fonts.html">Chapter 15 Fonts</a></h3>
>  
>  <p>The 'font-stretch' and 'font-size-adjust' properties have
>  been removed in CSS&nbsp;2.1.</p>
>  
>  <p>Font descriptors, the '@font-face' declaration, and all
>  associated parts of the font matching algorithm have been
>  removed in CSS&nbsp;2.1.</p>
>  
>  <h3 id="c15.2"><a href="fonts.html#algorithm">Section 15.2
>  Font matching algorithm</a></h3>
>  
> -<p>In this section (previously 15.5), in step 5 (prevously 8)
> -of the font matching algorith, the UA is now allowed to use
> +<p>In this section (previously 15.5), in step 5 (previously 8)
> +of the font matching algorithm, the UA is now allowed to use
>  multiple default fallback fonts to find a glyph for a given
>  character.</p>
>  
>  <p>In the per-property rule 2, specified that if there is only
>  a small-caps font in a given family, then that font will be
>  selected by 'normal'.</p>
>  
>  <h3 id="c15.3"><a href="fonts.html#font-family-prop">Section 15.2.2 Font family</a></h3>
>  
>  <p>The "missing character" glyph is no longer considered a match
>  for the last font in a font set, but is now considered a match
>  for U+FFFD.</p>
> @@ -1216,25 +1216,25 @@ Automatic table layout</a></h3>
>  
>  <p>Restricted inputs to the table layout algorithm for 'table-layout: auto',
>  whether or not the algorithm described in this section is used, to the
>  width of the containing block and the content of, and any CSS properties
>  set on, the table and any of its descendants.</p>
>  
>  <p>Added rule 4 to include the column group's width in the algorithm
>  for determining column widths.</p>
>  
>  <h3 id="c17.5.3"><a href="tables.html#height-layout">Section 17.5.3
>  Table height algorithms</a></h3>
>  
> -<p>The 'height' property on tables is now treated as a mininimum
> +<p>The 'height' property on tables is now treated as a minimum
>  height; the UA no longer has the option of using 'height' to
>  constrain the size of the table to be smaller than its contents.</p>
>  
>  <p>Percentage heights on table cells, rows, and row groups now
>  compute to 'auto'.</p>
>  
>  <p>The baseline of a cell is now defined much more precisely.</p>
>  
>  <p>Defined the baseline of a row with no baseline-aligned cells.</p>
>  
>  <h3 id="c17.5.4"><a href="tables.html#column-alignment">Section 17.5.4
>  Horizontal alignment in a column</a></h3>
> @@ -1402,25 +1402,25 @@ anyway, it was redundant.</p>
>  
>  <p>Corrected "unicode" macro to treat CRLF as a single character.</p>
>  
>  <p>Corrected "block" production to allow white space between declarations.</p>
>  
>  <p>In the rule for "any" (in the core syntax), corrected "FUNCTION"
>  to "FUNCTION any* ')'".</p>
>  
>  <h3 id="x4.1.3"><a href="syndata.html#characters">Section 4.1.3
>  Characters and case</a></h3>
>  
>  <p>Corrected third paragraph to say that an '@import' rule can only be
> -preceeded by an '@charset' rule or other '@import' rules.</p>
> +preceded by an '@charset' rule or other '@import' rules.</p>
>  
>  <h3 id="x4.3"><a href="syndata.html#values">Section 4.3 (Double sign problem)</a></h3>
>  
>  <p>Several values described in subsections of this section
>  incorrectly allowed two "+" or "-" signs at their beginnings. 
>  
>  <h3 id="x4.3.2"><a href="syndata.html#length-units">Section 4.3.2
>  Lengths</a></h3>
>  
>  <p>Fixed double sign error in definition of &lt;length&gt;.
>  (&lt;number&gt; already has a sign.)</p>
>  
> @@ -1495,25 +1495,25 @@ established by the box." For information
>  blocks, consult <a href="visudet.html#containing-block-details">
>  Section 10.1</a>.</p>
>  
>  <h3 id="x8.2"><a href="box.html#mpb-examples">Section 8.2 Example of margins, padding, and borders</a></h3>
>  
>  <p>The colors in the example HTML did not match the colors in the
>  image.
>  
>  <h3 id="x8.5.4"><a
>  href="box.html#border-shorthand-properties">Section 8.5.4
>  Border shorthand properties</a></h3>
>  
> -<p>Changedvarious border shorthands' syntax definitions to use the
> +<p>Changed various border shorthands' syntax definitions to use the
>  &lt;border-width&gt;, &lt;border-style&gt; and &lt;'border-top-color'&gt;
>  value types as appropriate.</p>
>  
>  <h3 id="x9.2.1"><a href="visuren.html#containing-block">Section 9.2.1
>  Block-level elements and block boxes</a></h3>
>  
>  <p>Excepted table elements from second paragraph about principal block
>  boxes and their contents.</p>
>  
>  <p>Corrected sentence to say "either only block boxes or only inline
>  boxes" instead of "only block boxes".</p>
>  
> @@ -2063,25 +2063,25 @@ document's DTD.
>  </blockquote>
>  
>  <h3 id="r7.2.1"><a href="media.html#at-media-rule">Section 7.2.1
>  The @media rule</a></h3>
>  
>  <p>Clarify that Style rules outside of @media rules apply to the same
>  media types that the style sheet itself applies to.</p>
>  
>  <h3 id="r7.3"><a href="media.html#media-types">Section 7.3 Recognized
>  media types</a></h3>
>  
>  <p>Added text to clarify that media types are mutually exclusive,
> -but a UA can render simulatenously to canvases with different
> +but a UA can render simultaneously to canvases with different
>  media types.</p>
>  
>  <h3 id="r7.3.1"><a href="media.html#media-groups">Section 7.3.1
>  Media groups</a></h3>
>  
>  <p>Split "aural" media group into "audio" and "speech".</p>
>  
>  <h3 id="r8.1"><a href="box.html#box-dimensions">Section 8.1 Box dimensions</a></h3>
>  
>  <ul>
>  <li>The terms "content box", "padding box", "border box", and "margin box"
>  have been defined.
> @@ -2429,25 +2429,25 @@ reverted to its CSS1 format.</p>
>  <p>Clarified that when "font-variant: small-caps" results in the
>  substitution of full-caps, the behavior is the same as for
>  text-transform.</p>
>  
>  <h3 id="r15.6"><a href="fonts.html#font-boldness">Section 15.6
>  Font boldness</a></h3>
>  
>  <p>The text for this section (formerly part of 15.2.3) has been
>  reverted to its CSS1 format. Also, discussion of font-weight from
>  other parts of the Fonts chapter has been aggregated under this
>  section.</p>
>  
> -<p>Removed statemnt that says "User agents must map names to values
> +<p>Removed statement that says "User agents must map names to values
>  in a way that preserves visual order; a face mapped to a value
>  must not be lighter than faces mapped to lower values." This is
>  otherwise implied by "The only guarantee is that a face of a given
>  value will be no less dark than the faces of lighter values."</p>
>  
>  <h3 id="r15.7"><a href="fonts.html#font-size-props">Section 15.7
>  Font size</a></h3>
>  
>  <p>Clarified relationship of font size to em squares.</p>
>  
>  <p>Added a totally irrelevant note about font sizes virtual reality
>  scenes.</p>
> @@ -3814,25 +3814,25 @@ HTML, <del>and in generated content</del
>  p          { white-space: normal }
>  td[nowrap] { white-space: nowrap }
>  <del>:before,:after { white-space: pre-line }</del></pre>
>  </blockquote>
>  
>  <!--========================== issue 91 ===========================-->
>  
>  <h3 id="s.16.6.1"><a
>  href="/TR/2007/CR-CSS21-20070719/text.html#white-space-model">
>  Section&nbsp;16.6.1 The 'white-space' processing model</a></h3>
>  
>  <p><span class=date>[2009-02-02]</span> Collapsing of white space does
> -not remove any line breaking oppportunities. Add the following
> +not remove any line breaking opportunities. Add the following
>  clarification:
>  
>  <blockquote>
>  <p>Then, the entire block is rendered. Inlines are laid out, taking
>  bidi reordering into account, and wrapping as specified by the
>  'white-space' property. <ins>When wrapping, line breaking
>  opportunities are determined based on the text prior to the white
>  space collapsing steps above.</ins>
>  </blockquote>
>  
>  <!--========================== issue 11a ==========================-->
>  
> @@ -4047,21 +4047,21 @@ Appendix&nbsp;I. Index</a></h3>
>  <p>These are the errata for <a
>  href="http://www.w3.org/TR/2009/CR-CSS2-20090423">CSS level 2
>  revision 1, CR version of 23 April 2009.</a> These corrections have the
>  status of a draft.
>  
>  <!--========================== issue 72 ==========================-->
>  
>  <h3 id="s.17.5.2.1"><a
>  href="/TR/2009/CR-CSS2-20090423/tables.html#fixed-table-layout">
>  Section&nbsp;17.5.2.1 Fixed table layout</a></h3>
>  
>  <p><span class=date>[2009-05-20]</span> UAs <em>may</em> render extra
> -columns if there are unexpect columns in later rows of a 'fixed' table
> +columns if there are unexpected columns in later rows of a 'fixed' table
>  layout. In that case, the width of the columns and of the table is
>  undefined.
>  
>  <!--===============================================================-->
>  
>  </BODY>
>  </HTML>
>  
> Index: syndata.src
> ===================================================================
> RCS file: /w3ccvs/WWW/Style/Group/css2-src/syndata.src,v
> retrieving revision 2.169
> diff -p -u -1 -2 -r2.169 syndata.src
> --- syndata.src	15 May 2009 17:31:39 -0000	2.169
> +++ syndata.src	4 Jun 2009 16:10:20 -0000
> @@ -1266,25 +1266,25 @@ inside double quotes, unless escaped (e.
>  'this is a \'string\''
>  </pre>
>  </div>
>  
>  <p>A string cannot directly contain a <span class="index-inst"
>  title="newline">newline</span>. 
>  To include a newline in a string, use an escape representing the line feed 
>  character in ISO-10646 (U+000A), such as "\A" or "\00000a". 
>  This character represents the generic notion of "newline" in CSS.
>  See the <span
>  class="propinst-content">'content'</span> property for an example.
>  </p>
> -<p>It is possible to break strings over several lines, for esthetic
> +<p>It is possible to break strings over several lines, for aesthetic
>  or other reasons, but in such a case the newline itself has to be
>  escaped with a backslash (\). For instance, the following two
>  selectors are exactly the same:
>  </p>
>  <div class="example">
>  <pre><code class="css">
>  a[title="a not s\
>  o very long title"] {/*...*/}
>  a[title="a not so very long title"] {/*...*/}
>  </code></pre>
>  </div>
>  
> Index: tables.src
> ===================================================================
> RCS file: /w3ccvs/WWW/Style/Group/css2-src/tables.src,v
> retrieving revision 2.113
> diff -p -u -1 -2 -r2.113 tables.src
> --- tables.src	20 May 2009 14:15:41 -0000	2.113
> +++ tables.src	4 Jun 2009 16:10:20 -0000
> @@ -734,25 +734,25 @@ cases, what is optimal is a matter of ta
>  constraints that user agents must respect when laying out a table.
>  User agents may use any algorithm they wish to do so, and are free to
>  prefer rendering speed over precision, except when the "fixed layout
>  algorithm" is selected.
>  
>  <p>Note that this section overrides the rules that apply to
>  calculating widths as described in <a
>  href="visudet.html#Computing_widths_and_margins">section 10.3</a>. In
>  particular, if the margins of a table are set to '0' and the width to
>  'auto', the table will not automatically size to fill its containing
>  block. However, once the calculated value of 'width' for the table is
>  found (using the algorithms given below or, when appropriate, some
> -other UA dependant algorithm) then the other parts of section 10.3 do
> +other UA dependent algorithm) then the other parts of section 10.3 do
>  apply. Therefore a table <em>can</em> be centered using left and right
>  'auto' margins, for instance.
>  
>  <p>Future updates of CSS may introduce ways of making tables
>  automatically fit their containing blocks.
>  
>  
>  <!-- #include src=properties/table-layout.srb -->
>  
>  <p>The <span class="propinst-table-layout">'table-layout'</span>
>  property controls the algorithm used to lay out the table cells, rows,
>  and columns. Values have the following meaning:
> Index: text.src
> ===================================================================
> RCS file: /w3ccvs/WWW/Style/Group/css2-src/text.src,v
> retrieving revision 2.69
> diff -p -u -1 -2 -r2.69 text.src
> --- text.src	19 May 2009 17:25:35 -0000	2.69
> +++ text.src	4 Jun 2009 16:10:20 -0000
> @@ -68,25 +68,25 @@ whether such text that overflows the blo
>  
>  
>  <div class="example"><p>
>  The following example causes a '3em' text indent.
>  </p>
>  <pre><code class="css">
>  p { text-indent: 3em }
>  </code></pre>
>  </div>
>  
>  <p class="note">
>  Note: Since the 'text-indent' property inherits, when specified on
> -a block element, it will affect descendent inline-block elements. 
> +a block element, it will affect descendant inline-block elements. 
>  For this reason, it is often wise to specify '<code>text-indent: 0</code>' 
>  on elements that are specified '<code>display:inline-block</code>'.
>  </p>
>  
>  <h2><a name="alignment-prop">Alignment:</a> the <span
>  class="propinst-text-align">'text-align'</span> property</h2>
>  
>  <!-- #include src=properties/text-align.srb -->
>  
>  <p>This property describes how inline content of a block is aligned.  Values
>  have the following meanings:</p>
>  
> @@ -420,25 +420,25 @@ td[nowrap] { white-space: nowrap }
>  </p>
>  <pre><code class="css">
>  pre[wrap]  { white-space: pre-wrap }
>  </code></pre>
>  </div>
>  
>  <h3><a name="white-space-model">The 'white-space' processing model</a></h3>
>  <p>
>  Any text that is directly contained inside a block element (not inside an
>  inline element) should be treated as an anonymous inline element.
>  </p>
>  <p>
> -For each inline element (including anonymous inlines elements), the
> +For each inline element (including anonymous inline elements), the
>  following steps are performed, treating bidi formatting characters as if
>  they were not there:
>  </p>
>  <ol>
>  <li>
>  Each tab (U+0009), carriage return (U+000D), or space (U+0020) 
>  character surrounding a linefeed (U+000A) character is removed if 
>  'white-space' is set to 'normal', 'nowrap', or 'pre-line'.
>       </li>
>  <li>If 'white-space' is set to 'pre' or 'pre-wrap', any sequence of
>       spaces (U+0020) unbroken by an element boundary is treated as a
>       sequence of non-breaking spaces. However, for 'pre-wrap', a line breaking
> @@ -465,25 +465,25 @@ reordering into account, and wrapping as
>  When wrapping, line breaking opportunities are determined based
>  on the text prior to the white space collapsing steps above.
>  </p>
>  <p>
>  As each line is laid out,
>  </p>
>  <ol>
>  <li>If a space (U+0020) at the beginning of a line has 'white-space'
>       set to 'normal', 'nowrap', or 'pre-line', it is removed.
>       </li>
>  <li>All tabs (U+0009) are rendered as a horizontal shift that lines
>       up the start edge of the next glyph with the next tab stop. Tab
> -     stops occur at points that are mutiples of 8 times the width of
> +     stops occur at points that are multiples of 8 times the width of
>       a space (U+0020) rendered in the block's font from the block's
>       starting content edge.
>       </li>
>  <li>If a space (U+0020) at the end of a line has 'white-space' set to
>       'normal', 'nowrap', or 'pre-line', it is also removed.
>       </li>
>  <li>If spaces (U+0020) or tabs (U+0009) at the end of a line have
>       'white-space' set to 'pre-wrap', UAs may visually collapse them.
>  </ol>
>  
>  <p>
>  A float should not introduce a line break opportunity.
> Index: visufx.src
> ===================================================================
> RCS file: /w3ccvs/WWW/Style/Group/css2-src/visufx.src,v
> retrieving revision 2.56
> diff -p -u -1 -2 -r2.56 visufx.src
> --- visufx.src	19 May 2009 17:25:35 -0000	2.56
> +++ visufx.src	4 Jun 2009 16:10:20 -0000
> @@ -29,28 +29,28 @@ block box.
>  </li>
>  <li>A block-level box is too wide for the containing block. This may
>  happen when an
>  element's <span class="propinst-width">'width'</span> property has a
>  value that causes the generated block box to spill over
>  sides of the containing block.
>  </li>
>  <li>An element's height exceeds an explicit height assigned to the containing
>  block (i.e., the containing block's height is determined by the <span
>  class="propinst-height">'height'</span> property, not by content
>  height).
>  </li>
> -<li>A descendent box is <a href="visuren.html#absolute-positioning">positioned
> +<li>A descendant box is <a href="visuren.html#absolute-positioning">positioned
>  absolutely</a>, partly outside the box.  Such boxes are not always clipped by the overflow property on their ancestors.
>  </li>
> -<li>A descendent box has <a href="box.html#margin-properties">negative margins</a>, causing it
> +<li>A descendant box has <a href="box.html#margin-properties">negative margins</a>, causing it
>  to be positioned partly outside the box.
>  </li>
>  <li>The 'text-indent' property causes an inline box to hang off either the left or right edge of the block box.
>  </li>
>  </ul>
>  
>  <p>Whenever overflow occurs, the <span
>  class="propinst-overflow">'overflow'</span> property specifies 
>  whether a box is clipped to its padding edge, and if so, whether 
>  a scrolling mechanism is provided to access any clipped out content.
>  </p>
>  
> @@ -341,25 +341,25 @@ class="propinst-visibility">'visibility'
>  <p>The <span class="propinst-visibility">'visibility'</span> property
>  specifies whether the boxes generated by an element are
>  rendered. Invisible boxes still affect layout (set the <span
>  class="propinst-display">'display'</span> property to 'none' to
>  suppress box generation altogether).  Values have the following
>  meanings:</p>
>  
>  <dl>
>  <dt><strong>visible</strong></dt>
>  <dd>The generated box is visible.</dd> 
>  <dt><strong>hidden</strong></dt>
>  <dd>The generated box is invisible (fully transparent, nothing is drawn), but still
> -affects layout. Furthermore, descendents of the element will
> +affects layout. Furthermore, descendants of the element will
>  be visible if they have 'visibility: visible'.</dd>
>  <dt><strong>collapse</strong></dt>
>  <dd>Please consult the section on 
>  <a href="tables.html#dynamic-effects">dynamic row and column
>  effects</a> in tables. If used on elements other than rows, row groups, columns, or column groups,
>  'collapse' has the same meaning as 'hidden'.
>  </dd>
>  </dl>
>  
>  <p>This property may be used in conjunction with scripts to create
>  dynamic effects.
>  </p>
> Index: visuren.src
> ===================================================================
> RCS file: /w3ccvs/WWW/Style/Group/css2-src/visuren.src,v
> retrieving revision 2.154
> diff -p -u -1 -2 -r2.154 visuren.src
> --- visuren.src	19 May 2009 17:25:35 -0000	2.154
> +++ visuren.src	4 Jun 2009 16:10:21 -0000
> @@ -2090,25 +2090,25 @@ opens an additional level of embedding w
>  bidirectional algorithm. The direction of this embedding level is
>  given by the <span class="propinst-direction">'direction'</span>
>  property. Inside the element, reordering is done implicitly. This
>  corresponds to adding a LRE (U+202A; for 'direction: ltr') or RLE
>  (U+202B; for 'direction: rtl') at the start of the element and a PDF
>  (U+202C) at the end of the element.
>  </dd>
>  <dt><strong>bidi-override</strong></dt>
>  
>  <dd>
>  For inline-level elements this creates an override. 
>  For block-level, table-cell, table-caption, or inline-block elements 
> -this creates an override for inline-level descendents not within 
> +this creates an override for inline-level descendants not within 
>  another block-level, table-cell, table-caption, or inline-block 
>  element.
>  This means that inside the element, reordering is strictly in sequence
>  according to the <span class="propinst-direction">'direction'</span>
>  property; the implicit part of the bidirectional algorithm is
>  ignored. This corresponds to adding a LRO (U+202D; for 'direction:
>  ltr') or RLO (U+202E; for 'direction: rtl') at the start of the
>  element or at the start of each anonymous child block box, if any, and
>  a PDF (U+202C) at the end of the element.
>  </dd>
>  </dl>
>  


-- 
L. David Baron                                 http://dbaron.org/
Mozilla Corporation                       http://www.mozilla.com/
Received on Monday, 8 June 2009 14:19:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 November 2012 14:18:25 GMT