svn commit: r986522 - in /websites/staging/httpd/trunk/content: ./ docs-project/goingfurther.html

[bu...@apache.org]

Author: buildbot
Date: Mon Apr 25 00:46:06 2016
New Revision: 986522

Log:
Staging update by buildbot for httpd

Modified:
    websites/staging/httpd/trunk/content/   (props changed)
    websites/staging/httpd/trunk/content/docs-project/goingfurther.html

Propchange: websites/staging/httpd/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Apr 25 00:46:06 2016
@@ -1 +1 @@
-1740747
+1740748

Modified: websites/staging/httpd/trunk/content/docs-project/goingfurther.html
==============================================================================
--- websites/staging/httpd/trunk/content/docs-project/goingfurther.html (original)
+++ websites/staging/httpd/trunk/content/docs-project/goingfurther.html Mon Apr 25 00:46:06 2016
@@ -103,69 +103,69 @@ english files have been updated since yo
 changes to your existing translated files. Also, in this manner, you will be
 able to build locally the doc (transform it to HTML files) in order to see how
 your changes look like.</p>
-<p>Doc manual is divided in branches :</p>
+<p>Doc manual is divided in branches:</p>
 <ul>
-<li><b>trunk</b> : it's the development branch ; in other words, 2.4 branch plus new
+<li><b>trunk:</b> It's the development branch; in other words, 2.4 branch plus new
   features, changes; you allways must begin to translate files in this branch,
   then port your work to other branches.</li>
-<li><b>2.4</b> : It's the current stable branch, recommended for a prod server</li>
-<li><b>2.2</b> : it's the older branch still maintained.</li>
+<li><b>2.4:</b> It's the current stable branch, recommended for a prod server</li>
+<li><b>2.2:</b> It's the older branch still maintained.</li>
 </ul>
 <p>Good to see <a href="http://people.apache.org/~takashi/translation-status/test.html">what has already been
 translated</a> and
 whether it's up to date or not.</p>
 <h1 id="downloading-svn-repository">Downloading svn repository<a class="headerlink" href="#downloading-svn-repository" title="Permanent link">&para;</a></h1>
-<p>In order to work properly, you have to download the doc tree (svn repository) onto
-your computer :</p>
+<p>In order to work properly, you have to download the <code>doc</code> tree (svn repository) onto
+your computer:</p>
 <ul>
-<li>Create a directory called <b>"httpd-doc"</b> on your computer : <em>mkdir
-  httpd-doc</em></li>
-<li>cd to this directory : <em>cd httpd-doc</em></li>
-<li>Download svn repository :<ul>
+<li>Create a directory called <b>"httpd-doc"</b> on your computer : <code>mkdir
+  httpd-doc</code></li>
+<li>cd to this directory: <em><code>cd httpd-doc</code></em></li>
+<li>Download svn repository:<ul>
 <li><code>svn co https://svn.apache.org/repos/asf/httpd/httpd/trunk/docs
   httpd-trunk</code></li>
-<li><em>svn co
+<li><code>svn co
   https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/docs
-  httpd-2.4</em></li>
-<li><em>svn co
+  httpd-2.4</code></li>
+<li><code>svn co
   https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/docs
-  httpd-2.2</em></li>
+  httpd-2.2</code>
+<b>Note:</b> SVN is a powerful program; see more <a href="svn.html">here</a> and of course
+  "<code>svn --help</code>" or "<code>man svn</code>" if you are under Linux.   </li>
 </ul>
 </li>
-<li>Note : svn is a powerful program; see more <a href="svn.html">here</a> and of course
-  "svn --help".   </li>
 </ul>
 <h1 id="new-translations">New translations<a class="headerlink" href="#new-translations" title="Permanent link">&para;</a></h1>
 <p>Translate documents that are not yet translated as shown in <a href="translations.html">Translations
 document</a>.</p>
 <h1 id="maintaining-your-translations">Maintaining your translations<a class="headerlink" href="#maintaining-your-translations" title="Permanent link">&para;</a></h1>
 <p>There are several ways to do that.
-Here is the method I use since several years ; its probably not the best, but it
+Here is the method I use since several years; its probably not the best, but it
 will help you to get started.</p>
 <ul>
 <li>
 <p>cd to your repository root <b>"httpd-doc"</b></p>
 </li>
 <li>
-<p>Create a directory called <b>"working"</b> ; it will be use later : <em>mkdir
-  working</em></p>
+<p>Create a directory called <b>"working"</b>; it will be use later: <code>mkdir
+  working</code></p>
 </li>
 <li>
 <p>Create a directory called <b>"sav"</b> (reference directory for updates detection -
-  see below) : <em>mkdir sav</em></p>
+  see below): <code>mkdir sav</code></p>
 </li>
 <li>
-<p>Copy svn repository you downloaded above in <b>"sav"</b> directory :</p>
+<p>Copy svn repository you downloaded above in <b>"sav"</b> directory:</p>
 <ul>
-<li><em>cp -a httpd-trunk sav</em></li>
-<li><em>cp -a httpd-2.4 sav</em></li>
-<li><em>cp -a httpd-2.2 sav</em></li>
+<li><code>cp -a httpd-trunk sav</code></li>
+<li><code>cp -a httpd-2.4 sav</code></li>
+<li><code>cp -a httpd-2.2 sav</code></li>
 </ul>
 </li>
 <li>
 <p>Once you have finished to work on a file, say <b>file.xml.fr</b>, save it to
   corresponding directory in sav tree, along with its english version
-  <b>file.xml</b> ;
+  <b>file.xml</b>;
   you'll understand why in a next step.</p>
 </li>
 <li>
@@ -178,15 +178,14 @@ will help you to get started.</p>
 Modifications will be displayed for each branch.</p>
 </li>
 <li>
-<p>Suppose modifications for 2.4 branch contain this line :<br /></p>
-<p><b>U manual/bind.xml</b><br /></p>
+<p>Suppose modifications for 2.4 branch contains this line:<br /></p>
+<p><b>U manual/bind.xml</b><br/></p>
 <p>That means manual/bind.xml file has been modified since your last visit.
 In order to check these modifications, you have to compare the last version of
 manual/bind.xml with the one you have saved above into the <b>"sav"</b> directory
-during your last working session ; for
+during your last working session; for
 this purpose, you can use the diff command this way:<br /></p>
-<p><em>diff sav/httpd-2.4/manual/bind.xml httpd-2.4/manual/bind.xml &gt;
-working/diff-bind</em></p>
+<p><code>diff sav/httpd-2.4/manual/bind.xml httpd-2.4/manual/bind.xml &gt; working/diff-bind</code></p>
 </li>
 <li>
 <p>working/diff-bind file covers now all modifications you have to transfer after