/[texi2html]/texi2html/Tests/texinfo_res/texinfo_23.html
ViewVC logotype

Diff of /texi2html/Tests/texinfo_res/texinfo_23.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.21 by pertusus, Tue Aug 9 17:19:24 2005 UTC revision 1.22 by pertusus, Tue Aug 23 23:51:16 2005 UTC
# Line 89  ul.toc {list-style: none} Line 89  ul.toc {list-style: none}
89  Write in the present tense, not in the past or the future.  Write in the present tense, not in the past or the future.
90    
91  </li><li>  </li><li>
92  Write actively!  For example, write &quot;We recommend that &hellip;&quot; rather  Write actively!  For example, write &ldquo;We recommend that &hellip;&rdquo; rather
93  than &quot;It is recommended that &hellip;&quot;.  than &ldquo;It is recommended that &hellip;&rdquo;.
94    
95  </li><li>  </li><li>
96  Use 70 or 72 as your fill column.  Longer lines are hard to read.  Use 70 or 72 as your fill column.  Longer lines are hard to read.
# Line 120  place in the document. Line 120  place in the document.
120    
121  </li><li>  </li><li>
122  Write index entries only where a topic is discussed significantly.  For  Write index entries only where a topic is discussed significantly.  For
123  example, it is not useful to index &quot;debugging information&quot; in a  example, it is not useful to index &ldquo;debugging information&rdquo; in a
124  chapter on reporting bugs.  Someone who wants to know about debugging  chapter on reporting bugs.  Someone who wants to know about debugging
125  information will certainly not find it in that chapter.  information will certainly not find it in that chapter.
126    
# Line 143  after the section command, and write the Line 143  after the section command, and write the
143  a paragraph before that paragraph.  a paragraph before that paragraph.
144    
145  <p>In the example that follows, a blank line comes after the index  <p>In the example that follows, a blank line comes after the index
146  entry for &quot;Leaping&quot;:  entry for &ldquo;Leaping&rdquo;:
147  </p>  </p>
148  <table><tr><td>&nbsp;</td><td><pre class="example">@section The Dog and the Fox  <table><tr><td>&nbsp;</td><td><pre class="example">@section The Dog and the Fox
149  @cindex Jumping, in general  @cindex Jumping, in general
# Line 157  The quick brown fox jumps over the lazy Line 157  The quick brown fox jumps over the lazy
157  </pre></td></tr></table>  </pre></td></tr></table>
158    
159  <p>(Note that the example shows entries for the same concept that are  <p>(Note that the example shows entries for the same concept that are
160  written in different ways--<samp>`Lazy dog'</samp>, and <samp>`Dog, lazy'</samp>--so  written in different ways&mdash;<samp>`Lazy dog'</samp>, and <samp>`Dog, lazy'</samp>&mdash;so
161  readers can look up the concept in different ways.)  readers can look up the concept in different ways.)
162  </p></li></ul>  </p></li></ul>
163    
# Line 210  this. Line 210  this.
210    
211  </li><li>  </li><li>
212  Write the prefatory sentence or phrase for a multi-item list or table as  Write the prefatory sentence or phrase for a multi-item list or table as
213  a complete expression.  Do not write &quot;You can set:&quot;; instead, write  a complete expression.  Do not write &ldquo;You can set:&rdquo;; instead, write
214  &quot;You can set these variables:&quot;.  The former expression sounds cut off.  &ldquo;You can set these variables:&rdquo;.  The former expression sounds cut off.
215  </li></ul>  </li></ul>
216    
217  <a name="SEC282"></a>  <a name="SEC282"></a>
# Line 251  commands. Line 251  commands.
251    
252  <ul>  <ul>
253  <li>  <li>
254  Capitalize &quot;Texinfo&quot;; it is a name.  Do not write the <samp>`x'</samp> or  Capitalize &ldquo;Texinfo&rdquo;; it is a name.  Do not write the <samp>`x'</samp> or
255  <samp>`i'</samp> in upper case.  <samp>`i'</samp> in upper case.
256    
257  </li><li>  </li><li>
258  Capitalize &quot;Info&quot;; it is a name.  Capitalize &ldquo;Info&rdquo;; it is a name.
259    
260  </li><li>  </li><li>
261  Write TeX using the <code>@TeX{}</code> command.  Note the uppercase  Write TeX using the <code>@TeX{}</code> command.  Note the uppercase
# Line 339  outside the end quotation marks: Line 339  outside the end quotation marks:
339  Introduce new terms so that a reader who does not know them can  Introduce new terms so that a reader who does not know them can
340  understand them from context; or write a definition for the term.  understand them from context; or write a definition for the term.
341    
342  <p>For example, in the following, the terms &quot;check in&quot;, &quot;register&quot; and  <p>For example, in the following, the terms &ldquo;check in&rdquo;, &ldquo;register&rdquo; and
343  &quot;delta&quot; are all appearing for the first time; the example sentence should be  &ldquo;delta&rdquo; are all appearing for the first time; the example sentence should be
344  rewritten so they are understandable.  rewritten so they are understandable.
345  </p>  </p>
346  <blockquote><p>The major function assists you in checking in a file to your  <blockquote><p>The major function assists you in checking in a file to your
# Line 410  beginning of the section that describes Line 410  beginning of the section that describes
410    
411  <p>Here are several examples of bad writing to avoid:  <p>Here are several examples of bad writing to avoid:
412  </p>  </p>
413  <p>In this example, say, &quot; &hellip; you must <code>@dfn</code>{check  <p>In this example, say, &ldquo; &hellip; you must <code>@dfn</code>{check
414  in} the new version.&quot;  That flows better.  in} the new version.&rdquo;  That flows better.
415  </p>  </p>
416  <blockquote><p>When you are done editing the file, you must perform a  <blockquote><p>When you are done editing the file, you must perform a
417  <code>@dfn</code>{check in}.  <code>@dfn</code>{check in}.
418  </p></blockquote>  </p></blockquote>
419    
420  <p>In the following example, say, &quot;&hellip; makes a unified interface such as VC  <p>In the following example, say, &ldquo;&hellip; makes a unified interface such as VC
421  mode possible.&quot;  mode possible.&rdquo;
422  </p>  </p>
423  <blockquote><p>SCCS, RCS and other version-control systems all perform similar  <blockquote><p>SCCS, RCS and other version-control systems all perform similar
424  functions in broadly similar ways (it is this resemblance which makes  functions in broadly similar ways (it is this resemblance which makes
# Line 438  everyone's changes so they do not step o Line 438  everyone's changes so they do not step o
438  <li>  <li>
439  Pronounce TeX as if the <samp>`X'</samp> were a Greek `chi', as the last  Pronounce TeX as if the <samp>`X'</samp> were a Greek `chi', as the last
440  sound in the name `Bach'.  But pronounce Texinfo as in `speck':  sound in the name `Bach'.  But pronounce Texinfo as in `speck':
441  &quot;teckinfo&quot;.  &ldquo;teckinfo&rdquo;.
442    
443  </li><li>  </li><li>
444  Write notes for yourself at the very end of a Texinfo file after the  Write notes for yourself at the very end of a Texinfo file after the

Legend:
Removed from v.1.21  
changed lines
  Added in v.1.22

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26