httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r986515 - in /websites/staging/httpd/trunk/content: ./ docs-project/translations.html
Date Sun, 24 Apr 2016 23:46:58 GMT
Author: buildbot
Date: Sun Apr 24 23:46:57 2016
New Revision: 986515

Log:
Staging update by buildbot for httpd

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

Propchange: websites/staging/httpd/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Apr 24 23:46:57 2016
@@ -1 +1 @@
-1739839
+1740743

Modified: websites/staging/httpd/trunk/content/docs-project/translations.html
==============================================================================
--- websites/staging/httpd/trunk/content/docs-project/translations.html (original)
+++ websites/staging/httpd/trunk/content/docs-project/translations.html Sun Apr 24 23:46:57
2016
@@ -95,88 +95,97 @@ h2:hover > .headerlink, h3:hover > .head
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
-<h1 id="translations-of-the-documentation">Translations of the Documentation<a class="headerlink"
href="#translations-of-the-documentation" title="Permanent link">&para;</a></h1>
-<p>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 <a href="./">documentation project information</a> , and subscribing
to the
-<a href="http://mail-archives.apache.org/mod_mbox/httpd-docs/">documentation project
mailing
-list</a>. The
-documentation project participants are usually very willing to help you
-with any questions or technical difficulties that may arise during your
-work.</p>
+<h1 id="welcome">Welcome !<a class="headerlink" href="#welcome" title="Permanent
link">&para;</a></h1>
+<p>We encourage translations of the documentation into other languages and thank
+you in advance for your contribution. If you would like to assist in translating
+the docs, please start by reading the general <a href="./">documentation project
+information</a> , and subscribing to the <a href="http://mail-archives.apache.org/mod_mbox/httpd-docs/">documentation
project mailing
+list</a>. The documentation
+project participants are usually very willing to help you with any questions or
+technical difficulties that may arise during your work.</p>
 <h1 id="getting-started">Getting Started<a class="headerlink" href="#getting-started"
title="Permanent link">&para;</a></h1>
-<p>To get started translating a particular document, you'll need to do the
-following.</p>
+<p>To get started translating whole or part(s) of the doc and keep it up to date,
+you'll need to do the following.</p>
 <ul>
 <li>
 <p>Join the docs mailing list by sending a message to
-<a href="mailto:docs-subscribe@httpd.apache.org">docs-subscribe@httpd.apache.org</a>.</p>
+  <a href="mailto:docs-subscribe@httpd.apache.org">docs-subscribe@httpd.apache.org</a>.</p>
 </li>
 <li>
-<p>Look to see <a href="http://people.apache.org/~takashi/translation-status/test.html#trunk">what
has already been translated</a>
-and whether it's up to date.</p>
+<p>Send a message to the list above to say that you wish to get involved in
+  translating the doc into your language. Maybe there's already in place a
+  translation team for your language that will help you in your work.</p>
 </li>
 <li>
-<p>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:</p>
-<ul>
-<li>
-<p>Recommended: Get it directly from svn by checking out the
-documentation repository: <code>svn co
-https://svn.apache.org/repos/asf/httpd/httpd/trunk/docs httpd-docs</code> </p>
+<p>Let's suppose you look at http://httpd.apache.org/docs/trunk/configuring.html
+  and see that there's no version of this page in your language.</p>
 </li>
 <li>
-<p>Or download a copy of just the one file from svn starting
-<a href="https://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/">here</a>.</p>
+<p>Get english version of the source file [here]
+  (https://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/manual/configuring.xml)
+  Note that you must download the .xml file, not the .html one.</p>
 </li>
 <li>
-<p>See more about using svn <a href="svn.html">here</a>.
-Then, make a copy of that file with the two-letter file extension
-representing your language. For example, for a Spanish translation, you'd
-copy <code>mod_rewrite.xml</code> to <code>mod_rewrite.xml.es</code>.</p>
-</li>
+<p>Make a copy of that file with the two-letter file extension representing your
+  language. For example, for a Spanish translation, you'd copy <code>configuring.xml</code>
+  to <code>configuring.xml.es</code>. You are now ready to start well said translation
:</p>
+<ul>
+<li>If your language contains accented and/or multi-bytes characters, set
+  your text editor encoding to "UTF-8" , and check that the first line
+  of the file is &lt;?xml version="1.0" encoding="UTF-8" ?&gt;</li>
+<li>In the header, replace the string "$LastChangedRevision:" by the
+  string "English Revision:"</li>
+<li>Make sure you put your name at the top of the file if you are
+  translating or reviewing the documentation like this: <!-- French
+  translation : <translator name> --> <!-- Reviewed by : <reviewer name>
+  --></li>
+<li>Translate all textual portions of the document, leaving directives,
+  examples, and other literal code portions unchanged.</li>
+<li>What has to be translated ? All text parts between &lt;p&gt; and
+  &lt;/p&gt;, &lt;title&gt; and &lt;/title&gt;, &lt;description&gt;
and
+  &lt;/description&gt;, &lt;name&gt; and &lt;/name&gt;,
+  &lt;compatibility&gt; and &lt;/compatibility&gt;, &lt;note&gt;
and
+  &lt;/note&gt;, &lt;li&gt; and &lt;/li&gt;, &lt;dd&gt; and
&lt;/dd&gt;.</li>
 </ul>
 </li>
 <li>
-<p>Translate all textual portions of the document, leaving directives,
-examples, and other literal code portions unchanged.</p>
-</li>
-<li>
-<p>Send your results - either complete files, or the output of <code>svn diff</code>
to
-the docs mailing list, and someone can commit it to the repository.
-Eventually, you can do this step yourself.</p>
+<p>Send your results - either complete files, or the output of <code>svn diff</code>
to the
+  docs mailing list, and someone can commit it to the repository.  Eventually,
+  you can do this step yourself.</p>
 </li>
 </ul>
+<h1 id="going-further">Going further !<a class="headerlink" href="#going-further"
title="Permanent link">&para;</a></h1>
+<p>If you wish to go further in translating of the doc, in other words maintaining
+your translations and keep them up-to-date, read <a href="goingfurther.html">this
+document</a>.</p>
 <h1 id="related-information">Related Information<a class="headerlink" href="#related-information"
title="Permanent link">&para;</a></h1>
-<p>Please note the following documents. They give you further information
-which may be helpful.</p>
+<p>Please note the following documents. They give you further information which may
+be helpful.</p>
 <ul>
 <li>The <a href="http://httpd.apache.org/docs-project/docsformat.html">Documentation
Format and
-Transformation</a> page
-gives some information about the transformation from xml to html.
-Translations of documentation for Apache version 2.0 and higher should be
-sent as xml file. Committers will take care of generating and committing
-the corresponding html file.</li>
+  Transformation</a> page
+  gives some information about the transformation from xml to html.
+  Translations of documentation for Apache version 2.0 and higher should be sent
+  as xml file. Committers will take care of generating and committing the
+  corresponding html file.</li>
 </ul>
 <h1 id="review-standards">Review Standards<a class="headerlink" href="#review-standards"
title="Permanent link">&para;</a></h1>
-<p>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.</p>
-<p>We also encourage you to place the name of the translator in a comment at
-the top of the file, like this:</p>
-<p>&lt;!-- 
-  =====================================================
-  Translated by: Nilgün Belma Bugüner &lt;nilgun belgeler.org&gt;
-  Reviewed by: Orhan Berent &lt;berent belgeler.org&gt;
-  ========================================================== 
-  --&gt;</p>
+<p>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.</p>
+<p>We also encourage you to place the name of the translator in a comment at the
+top of the file, like this:</p>
+<p>&lt;!-- ===================================================== Translated by:
+  Nilgün Belma Bugüner &lt;nilgun belgeler.org&gt; Reviewed by: Orhan
Berent
+  &lt;berent belgeler.org&gt;
+  ========================================================== --&gt;</p>
 <p>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.</p>
+English version, so that future translators have an idea of where they need to
+start.</p>
             
 
             <!-- FOOTER -->



Mime
View raw message