We encourage translations of the documentation into other languages. If you would like to assist in translating the docs, please start by reading the general documentation project information , and subscribing to the documentation project mailing list. The documentation project participants are usually very willing to help you with any questions or technical difficulties that may arise during your work.
There are several efforts underway to translate the documentation into other languages. These include:
|Chinese (Traditional)||SkyBlue < firstname.lastname@example.org >|
|French||Website , Lucien Gentis, Vincent Deffontaines|
|German||Astrid Stolper < email@example.com >|
|Russian||Ilia Soldis < firstname.lastname@example.org >|
|Turkish||Website , Nilgün Belma Bugüner|
The available translations in the Trunk documentation may be seen here. Also, you may notice directives in various translation docs that state that a directive hasn't been translated yet.
To get started translating a particular document, you'll need to do the following.
Join the docs mailing list by sending a message to email@example.com.
If there is no existing translation of the document you want to work on, get the English version as a starting point. You can either:
Recommended: Get it directly from svn by checking out the
Or download a copy of just the one file from svn starting here.
See more about using svn here.
Then, make a copy of that file with the two-letter file extension
representing your language. For example, for a Spanish translation, you'd
Translate all textual portions of the document, leaving directives, examples, and other literal code portions unchanged.
Send your results - either complete files, or the output of
svn diff to
the docs mailing list, and someone can commit it to the repository.
Eventually, you can do this step yourself.
Please note the following documents. They give you further information which may be helpful.
Because English is the main development language of the Apache HTTP Server, it is difficult for the developers to check the quality of documentation submitted in other languages. Therefore, we require that all translated documentation be reviewed by another fluent speaker of the relevant language, before it can be accepted. Each commit message should list the reviewer. If the translator is not the same as the committer, the translator should also be named in the commit message.
We also encourage you to place the name of the translator in a comment at the top of the file, like this:
<!-- ===================================================== Translated by: Nilgün Belma Bugüner <nilgun belgeler.org> Reviewed by: Orhan Berent <berent belgeler.org> ========================================================== -->
The build system keeps track of the svn revision number of the equivalent English version, so that future translators have an idea of where they need to start.