You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by lg...@apache.org on 2016/04/25 02:46:02 UTC
svn commit: r1740748 -
/httpd/site/trunk/content/docs-project/goingfurther.mdtext
Author: lgilbernabe
Date: Mon Apr 25 00:46:02 2016
New Revision: 1740748
URL: http://svn.apache.org/viewvc?rev=1740748&view=rev
Log:
markdown formating
Modified:
httpd/site/trunk/content/docs-project/goingfurther.mdtext
Modified: httpd/site/trunk/content/docs-project/goingfurther.mdtext
URL: http://svn.apache.org/viewvc/httpd/site/trunk/content/docs-project/goingfurther.mdtext?rev=1740748&r1=1740747&r2=1740748&view=diff
==============================================================================
--- httpd/site/trunk/content/docs-project/goingfurther.mdtext (original)
+++ httpd/site/trunk/content/docs-project/goingfurther.mdtext Mon Apr 25 00:46:02 2016
@@ -26,13 +26,13 @@ changes to your existing translated file
able to build locally the doc (transform it to HTML files) in order to see how
your changes look like.
-Doc manual is divided in branches :
+Doc manual is divided in branches:
-- <b>trunk</b> : it's the development branch ; in other words, 2.4 branch plus new
+- <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.
-- <b>2.4</b> : It's the current stable branch, recommended for a prod server
-- <b>2.2</b> : it's the older branch still maintained.
+- <b>2.4:</b> It's the current stable branch, recommended for a prod server
+- <b>2.2:</b> It's the older branch still maintained.
Good to see [what has already been
translated](http://people.apache.org/~takashi/translation-status/test.html) and
@@ -40,23 +40,23 @@ whether it's up to date or not.
# Downloading svn repository #
-In order to work properly, you have to download the doc tree (svn repository) onto
-your computer :
+In order to work properly, you have to download the `doc` tree (svn repository) onto
+your computer:
-- Create a directory called <b>"httpd-doc"</b> on your computer : <em>mkdir
- httpd-doc</em>
-- cd to this directory : <em>cd httpd-doc</em>
-- Download svn repository :
+- Create a directory called <b>"httpd-doc"</b> on your computer : `mkdir
+ httpd-doc`
+- cd to this directory: <em>`cd httpd-doc`</em>
+- Download svn repository:
- `svn co https://svn.apache.org/repos/asf/httpd/httpd/trunk/docs
httpd-trunk`
- - <em>svn co
+ - `svn co
https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/docs
- httpd-2.4</em>
- - <em>svn co
+ httpd-2.4`
+ - `svn co
https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/docs
- httpd-2.2</em>
-- Note : svn is a powerful program; see more [here](svn.html) and of course
- "svn --help".
+ httpd-2.2`
+<b>Note:</b> SVN is a powerful program; see more [here](svn.html) and of course
+ "`svn --help`" or "`man svn`" if you are under Linux.
# New translations #
@@ -66,24 +66,24 @@ document](translations.html).
# Maintaining your translations #
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.
- cd to your repository root <b>"httpd-doc"</b>
-- Create a directory called <b>"working"</b> ; it will be use later : <em>mkdir
- working</em>
+- Create a directory called <b>"working"</b>; it will be use later: `mkdir
+ working`
- Create a directory called <b>"sav"</b> (reference directory for updates detection -
- see below) : <em>mkdir sav</em>
-- Copy svn repository you downloaded above in <b>"sav"</b> directory :
- - <em>cp -a httpd-trunk sav</em>
- - <em>cp -a httpd-2.4 sav</em>
- - <em>cp -a httpd-2.2 sav</em>
+ see below): `mkdir sav`
+- Copy svn repository you downloaded above in <b>"sav"</b> directory:
+ - `cp -a httpd-trunk sav`
+ - `cp -a httpd-2.4 sav`
+ - `cp -a httpd-2.2 sav`
- 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.
- Say a week later, you wish to see if doc gurus have made some changes : cd to
your repository root <b>"httpd-doc"</b> which contains the different branches
@@ -92,18 +92,17 @@ will help you to get started.
from there.
Modifications will be displayed for each branch.
-- Suppose modifications for 2.4 branch contain this line :<br />
+- Suppose modifications for 2.4 branch contains this line:<br />
- <b>U manual/bind.xml</b><br />
+ <b>U manual/bind.xml</b><br/>
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 />
- <em>diff sav/httpd-2.4/manual/bind.xml httpd-2.4/manual/bind.xml >
-working/diff-bind</em>
+ `diff sav/httpd-2.4/manual/bind.xml httpd-2.4/manual/bind.xml > working/diff-bind`
- working/diff-bind file covers now all modifications you have to transfer after
translation to your own bind.xml.ll (ll-> Local Languaje), say bind.xml.fr for a (good) example.