Skip to content

Commit a5ed0df

Browse files
bert-githubbert-github
committed
[css2] Rephrased some sentences, as per Steven P's suggestions.
--HG-- extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%401130
1 parent e3da00b commit a5ed0df

1 file changed

Lines changed: 26 additions & 23 deletions

File tree

‎css2/intro.src‎

Lines changed: 26 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
22
<html lang="en">
3-
<!-- $Id: intro.src,v 2.14 1998-02-24 22:53:03 ijacobs Exp $ -->
3+
<!-- $Id: intro.src,v 2.15 1998-03-10 15:39:23 bbos Exp $ -->
44
<HEAD>
55
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
66
<TITLE>Introduction to CSS2</TITLE>
@@ -135,8 +135,9 @@ them. Let's look at some of the others:
135135
</PRE>
136136

137137
<P>The first thing to notice is that several declarations are grouped
138-
within a block enclosed by curly braces ({...}). This is a way to make
139-
style sheets shorter.
138+
within a block enclosed by curly braces ({...}), and separated by
139+
semicolons, though the last declaration may also be followed by a
140+
semicolon.
140141

141142
<P>The first declaration on the 'BODY' element sets
142143
the font family to "Gill Sans". If that font isn't available, the
@@ -201,13 +202,14 @@ which are block-level (i.e., cause line breaks).
201202
ARTICLE, HEADLINE, AUTHOR, LOCATION, PARA { display: block }
202203
</PRE>
203204

204-
<P>The first rule declares INSTRUMENT to be inline, and the second
205-
rule, with its comma-separated list of selectors, declares all the
206-
other elements to be block-level.
205+
<P>The first rule declares INSTRUMENT to be inline (though this rule
206+
is not strictly necessary, because 'inline' is the default), and the
207+
second rule, with its comma-separated list of selectors, declares all
208+
the other elements to be block-level.
207209

208-
<P>It's not yet clear how style sheets will be linked to XML
209-
documents, but assuming the above CSS fragment is combined with the
210-
XML fragment, a visual user agent could format the result as:
210+
<P>It has not yet been finalised how style sheets will be linked to
211+
XML documents, but assuming the above CSS fragment is combined with
212+
the XML fragment, a visual user agent could format the result as:
211213

212214
<p><img src="images/bach0.gif" alt="Example rendering">
213215

@@ -295,9 +297,10 @@ other hand, may generate more information in the rendering structure:
295297
the list element's content and list style information (e.g., a bullet
296298
image).
297299

298-
<P>Note that CSS user agents do not alter the document tree during
299-
this phase. In particular, content generated due to style sheets is
300-
not fed back to the document language processor (e.g., for reparsing).
300+
<P>Note that the CSS user agent does not alter the document tree
301+
during this phase. In particular, content generated due to style
302+
sheets is not fed back to the document language processor (e.g., for
303+
reparsing).
301304

302305
<!-- Is the next statement still true? If so, it should probably
303306
be made specific and moved to visudet.src -->
@@ -312,7 +315,7 @@ upward in the tree of rendering objects (not left, right, or down).
312315
-->
313316

314317
<li>Transfer the rendering structure to the target medium (e.g., print
315-
the results, display them on the screen, render text as speech,
318+
the results, display them on the screen, render them as speech,
316319
etc.).
317320
</ol>
318321

@@ -372,13 +375,13 @@ interface</a>).
372375
<UL>
373376

374377
<LI>
375-
<P><STRONG>Backward compatibility</STRONG>. CSS2 user agents
376-
will be able to understand CSS1 style sheets. CSS1 user agents will
377-
be able to read CSS2 style sheets and discard parts they don't
378-
understand. Also, user agents with no CSS support will be able to view
379-
style-enhanced documents. Of course, the stylistic enhancements made
380-
possible by CSS will not be rendered, but all content will be
381-
presented.</P>
378+
<P><STRONG>Forward and backward compatibility</STRONG>. CSS2 user
379+
agents will be able to understand CSS1 style sheets. CSS1 user agents
380+
will be able to read CSS2 style sheets and discard parts they don't
381+
understand. Also, user agents with no CSS support will be able to
382+
display style-enhanced documents. Of course, the stylistic
383+
enhancements made possible by CSS will not be rendered, but all
384+
content will be presented.</P>
382385
</LI>
383386

384387
<LI>
@@ -438,7 +441,7 @@ CSS2 goes a long way toward granting designers their requests.</P>
438441
</LI>
439442

440443
<LI>
441-
<P><STRONG>Alternate language bindings</STRONG>. The set of CSS
444+
<P><STRONG>Alternative language bindings</STRONG>. The set of CSS
442445
properties described in this specification form a consistent
443446
formatting model for visual and aural presentations. This formatting
444447
model can be accessed through the CSS language, but bindings to other
@@ -453,8 +456,8 @@ increase accessibility to Web documents. By retaining textual
453456
information in text form, both robots indexing Web pages and human
454457
users will have more options for digesting the content. Users can
455458
provide their personal style sheets if author-suggested style sheets
456-
hinder accessibility. The cascading mechanism negotiates between, and
457-
combines, different style sheets.</P>
459+
hinder accessibility. The cascading mechanism
460+
combines and selects from different style sheets.</P>
458461
</LI>
459462

460463
</UL>

0 commit comments

Comments
 (0)