svn commit: r42392 - head/en_US.ISO8859-1/books/fdp-primer/writing-style
Warren Block
wblock at FreeBSD.org
Tue Jul 23 00:45:09 UTC 2013
Author: wblock
Date: Tue Jul 23 00:45:09 2013
New Revision: 42392
URL: http://svnweb.freebsd.org/changeset/doc/42392
Log:
Whitespace-only fixes. Translators, please ignore.
Modified:
head/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.xml
Modified: head/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.xml Tue Jul 23 00:40:25 2013 (r42391)
+++ head/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.xml Tue Jul 23 00:45:09 2013 (r42392)
@@ -75,7 +75,7 @@
A trivial example is better than no example. A good example
is better yet. Do not give bad examples, identifiable by
apologies or sentences like <quote>but really it should never
- be done that way</quote>. Bad examples are worse than no
+ be done that way</quote>. Bad examples are worse than no
examples. Give good examples, because <emphasis>even when
warned not to use the example as shown</emphasis>, the
reader will usually just use the example as shown.</para>
@@ -197,8 +197,8 @@
<para>For example, commands:</para>
<informalexample>
- <para>Wrong: Use the command <command>svn</command> to update
- sources.</para>
+ <para>Wrong: Use the command <command>svn</command> to
+ update sources.</para>
</informalexample>
<informalexample>
@@ -219,7 +219,8 @@
</informalexample>
<para>Manual page references (the second example uses
- <sgmltag>citerefentry</sgmltag> with the <literal>&man.csh.1;</literal> entity):.</para>
+ <sgmltag>citerefentry</sgmltag> with the
+ <literal>&man.csh.1;</literal> entity):.</para>
<informalexample>
<para>Wrong: See <command>man csh</command> for more
@@ -299,13 +300,14 @@
<para>Opening tags increase the indentation level by two spaces.
Closing tags decrease the indentation level by two spaces.
- Blocks of eight spaces at the start of a line should be replaced
- with a tab. Do not use spaces in front of tabs, and do not
- add extraneous whitespace at the end of a line. Content
- within elements should be indented by two spaces if the
- content runs over more than one line.</para>
+ Blocks of eight spaces at the start of a line should be
+ replaced with a tab. Do not use spaces in front of tabs, and
+ do not add extraneous whitespace at the end of a line.
+ Content within elements should be indented by two spaces if
+ the content runs over more than one line.</para>
- <para>For example, the source for this section looks like this:</para>
+ <para>For example, the source for this section looks like
+ this:</para>
<programlisting><sgmltag class="starttag">chapter</sgmltag>
<sgmltag class="starttag">title</sgmltag>...<sgmltag class="endtag">title</sgmltag>
@@ -406,9 +408,9 @@
to content at the same time as changes to
formatting</emphasis>.</para>
- <para>When content and whitespace changes are kept separate, translation teams
- can easily see whether a change was content that must be translated
- or only whitespace.</para>
+ <para>When content and whitespace changes are kept separate,
+ translation teams can easily see whether a change was content
+ that must be translated or only whitespace.</para>
<para>For example, if two sentences have been added to a
paragraph so that the line lengths now go
@@ -477,12 +479,17 @@ GB. Hardware compression …</lite
<tbody>
<row>
<entry>CD-ROM</entry>
- <entry><sgmltag class="starttag">acronym</sgmltag><literal>CD-ROM</literal><sgmltag class="endtag">acronym</sgmltag></entry>
+
+ <entry><sgmltag
+ class="starttag">acronym</sgmltag><literal>CD-ROM</literal><sgmltag
+ class="endtag">acronym</sgmltag></entry>
</row>
<row>
<entry>DoS (Denial of Service)</entry>
- <entry><sgmltag class="starttag">acronym</sgmltag><literal>DoS</literal><sgmltag class="endtag">acronym</sgmltag></entry>
+ <entry><sgmltag
+ class="starttag">acronym</sgmltag><literal>DoS</literal><sgmltag
+ class="endtag">acronym</sgmltag></entry>
</row>
<row>
More information about the svn-doc-head
mailing list