[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
trans-coord/manual/web-trans index.html web-tra...
|
From: |
Pavel Kharitonov |
|
Subject: |
trans-coord/manual/web-trans index.html web-tra... |
|
Date: |
Sat, 29 Sep 2012 06:53:49 +0000 |
CVSROOT: /web/trans-coord
Module name: trans-coord
Changes by: Pavel Kharitonov <ineiev> 12/09/29 06:53:49
Modified files:
manual/web-trans: index.html web-trans.dvi.gz web-trans.html
web-trans.html.gz web-trans.html_node.tar.gz
web-trans.info.tar.gz web-trans.pdf
web-trans.ps.gz web-trans.texi.tar.gz
web-trans.txt web-trans.txt.gz
manual/web-trans/html_node: New-Team.html
Log message:
Regenerate.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/index.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.dvi.gz?cvsroot=trans-coord&rev=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.html.gz?cvsroot=trans-coord&rev=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.html_node.tar.gz?cvsroot=trans-coord&rev=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.info.tar.gz?cvsroot=trans-coord&rev=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.pdf?cvsroot=trans-coord&rev=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.ps.gz?cvsroot=trans-coord&rev=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.texi.tar.gz?cvsroot=trans-coord&rev=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.txt?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.txt.gz?cvsroot=trans-coord&rev=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/New-Team.html?cvsroot=trans-coord&r1=1.8&r2=1.9
Patches:
Index: index.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/index.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- index.html 28 Jun 2012 21:04:18 -0000 1.9
+++ index.html 29 Sep 2012 06:53:48 -0000 1.10
@@ -1,10 +1,10 @@
<!--#include virtual="/server/header.html" -->
-<title> - GNU Project - Free Software Foundation (FSF)</title>
+<title>GNU Web Translators Manual - GNU Project - Free Software Foundation
(FSF)</title>
<!--#include virtual="/server/banner.html" -->
-<h2></h2>
+<h2>GNU Web Translators Manual</h2>
<address>Free Software Foundation</address>
-<address>last updated June 29, 2012</address>
+<address>last updated September 29, 2012</address>
<p>This manual (web-trans) is available in the following formats:</p>
@@ -22,17 +22,17 @@
<li><a href="web-trans.info.tar.gz">Info document
(36K bytes gzipped tar file)</a>.</li>
<li><a href="web-trans.txt">ASCII text
- (100K bytes)</a>.</li>
+ (96K bytes)</a>.</li>
<li><a href="web-trans.txt.gz">ASCII text compressed
(36K bytes gzipped)</a>.</li>
<li><a href="web-trans.dvi.gz">TeX dvi file
- (60K bytes gzipped)</a>.</li>
+ (56K bytes gzipped)</a>.</li>
<li><a href="web-trans.ps.gz">PostScript file
- (264K bytes gzipped)</a>.</li>
+ (260K bytes gzipped)</a>.</li>
<li><a href="web-trans.pdf">PDF file
(348K bytes)</a>.</li>
<li><a href="web-trans.texi.tar.gz">Texinfo source
- (72K bytes gzipped tar file).</a></li>
+ (68K bytes gzipped tar file).</a></li>
</ul>
<p>You can <a href="http://shop.fsf.org/";>buy printed copies of
Index: web-trans.dvi.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.dvi.gz,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
Binary files /tmp/cvs3LwEpc and /tmp/cvsaLBWmg differ
Index: web-trans.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans.html 28 Jun 2012 21:04:18 -0000 1.9
+++ web-trans.html 29 Sep 2012 06:53:48 -0000 1.10
@@ -515,12 +515,16 @@
and technical skills, and devotion. The only “bonus” team leaders
have is more work and more responsibilities.
- <p>You should read most of the philosophy-related articles and <em>all</em>
-the documentation related to the translation process before you decide
-to form a new team, or take over an orphaned team. Once you have the
-internal feeling that having a gnu.org translation team for your
-language is a must, and you are the one for this job, follow these
-steps:
+ <p>You should read and <em>all</em> the documentation related to the
+translation process at the very least all important philosophy-related
+articles listed on
+<a
href="http://gnu.org/server/standards/README.translations.html";>http://gnu.org/server/standards/README.translations.html</a>
+and
+<a
href="http://gnu.org/server/standards/translations/priorities.html";>http://gnu.org/server/standards/translations/priorities.html</a>
+before you decide to form a new team, or take over an orphaned team.
+Once you have the internal feeling that having a gnu.org translation
+team for your language is a must, and you are the one for this job,
+follow these steps:
<ol type=1 start=1>
<li>If you do not have a Savannah account, register at
@@ -546,18 +550,31 @@
<p>As you have probably observed, every directory that contains
translatable articles has a <samp><span class="file">/po</span></samp>
sub-directory, which is where the
-new canonical source format of the translations is stored.
+canonical source format of the translations is stored.
- <li>Assuming you have already read the GNUN manual entirely (as
recommended
-in the beginning of this section), check if your language code is
+ <li>Submit your first message stating that you would like to establish a
new
+team to <a href="mailto:address@hidden";>address@hidden</a>; please mention
that you have
+read all the documentation and list the issues that remain unclear for
+you. The Translation Managers will answer your questions and send you
+the standard questionnaire for new team leaders. It is short and
+shouldn't take more than 10–30 minutes to complete. This questionnaire
+is important, as we consider it crucial for any translation team
+co-ordinator to have a good understanding of the philosophy of the free
+software movement.
+
+ <li>Check if your language code is
present in the variable <code>TEMPLATE_LINGUAS</code> at
<samp><span class="file">server/gnun/gnun.mk</span></samp>. If it is not, the
first thing to do is to
translate and submit to <a href="mailto:address@hidden";>address@hidden</a> the
following
files (all in the <samp><span class="file">server/po/</span></samp> directory):
<samp><span class="file">head-include-2.</span><var>lang</var><span
class="file">.po</span></samp>,
-<samp><span class="file">body-include-1.</span><var>lang</var><span
class="file">.po</span></samp>, <samp><span
class="file">body-include-2.</span><var>lang</var><span
class="file">.po</span></samp>
-and <samp><span class="file">footer-text.</span><var>lang</var><span
class="file">.po</span></samp>, together with your first message
-stating that you would like to establish a new team. See <a
href="gnun.html#New-Translation">New Translation</a>.
+<samp><span class="file">body-include-1.</span><var>lang</var><span
class="file">.po</span></samp>,
+<samp><span class="file">body-include-2.</span><var>lang</var><span
class="file">.po</span></samp>
+<samp><span class="file">footer-text.</span><var>lang</var><span
class="file">.po</span></samp>,
+<samp><span class="file">outdated.</span><var>lang</var><span
class="file">.po</span></samp>,
+<samp><span class="file">skip-translations.</span><var>lang</var><span
class="file">.po</span></samp>,
+and <samp><span class="file">top-addendum.</span><var>lang</var><span
class="file">.po</span></samp>.
+See <a href="gnun.html#New-Translation">New Translation</a>.
<ul>
<li>The language code (<var>lang</var>) should be the ISO 639-1 code of the
@@ -602,15 +619,6 @@
submit a corrected file. In any event, please take into account the
remarks in future work.
- <li>Once the Translation Managers determine that you are doing well and
-about to complete the process, they will send you the standard
-questionnaire for new team leaders. It is relevantly short and it
-shouldn't take more than 10-30 minutes to complete. This questionnaire
-is important, as we consider it crucial any translation team
-co-ordinator to have a good understanding of the philosophy of the free
-software movement. It is not unusual energetic people who complete all
-technical steps without trouble to fail here.
-
<li>If all goes well, you will receive a response inviting you to apply
for
a new translation project at Savannah. The project name should be
‘<samp><span class="samp">www-</span><var>lang</var></samp>’ where
<var>lang</var> is, unsurprisingly, the language
Index: web-trans.html.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.html.gz,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
Binary files /tmp/cvsGHot1a and /tmp/cvsFtsK1e differ
Index: web-trans.html_node.tar.gz
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/web-trans.html_node.tar.gz,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
Binary files /tmp/cvsaFcwwb and /tmp/cvsm8fSxf differ
Index: web-trans.info.tar.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.info.tar.gz,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
Binary files /tmp/cvskk6Dpe and /tmp/cvsZAs3ri differ
Index: web-trans.pdf
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.pdf,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
Binary files /tmp/cvshxZ6Ve and /tmp/cvswFPB1i differ
Index: web-trans.ps.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.ps.gz,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
Binary files /tmp/cvsOh38ih and /tmp/cvsPdLErl differ
Index: web-trans.texi.tar.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.texi.tar.gz,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
Binary files /tmp/cvs67XOMf and /tmp/cvsymaVWj differ
Index: web-trans.txt
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.txt,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans.txt 28 Jun 2012 21:04:19 -0000 1.9
+++ web-trans.txt 29 Sep 2012 06:53:48 -0000 1.10
@@ -346,11 +346,14 @@
and technical skills, and devotion. The only "bonus" team leaders have
is more work and more responsibilities.
- You should read most of the philosophy-related articles and _all_
-the documentation related to the translation process before you decide
-to form a new team, or take over an orphaned team. Once you have the
-internal feeling that having a gnu.org translation team for your
-language is a must, and you are the one for this job, follow these
+ You should read and _all_ the documentation related to the
+translation process at the very least all important philosophy-related
+articles listed on
+`http://gnu.org/server/standards/README.translations.html' and
+`http://gnu.org/server/standards/translations/priorities.html' before
+you decide to form a new team, or take over an orphaned team. Once you
+have the internal feeling that having a gnu.org translation team for
+your language is a must, and you are the one for this job, follow these
steps:
1. If you do not have a Savannah account, register at
@@ -377,18 +380,27 @@
As you have probably observed, every directory that contains
translatable articles has a `/po' sub-directory, which is where the
- new canonical source format of the translations is stored.
+ canonical source format of the translations is stored.
- 3. Assuming you have already read the GNUN manual entirely (as
- recommended in the beginning of this section), check if your
- language code is present in the variable `TEMPLATE_LINGUAS' at
- `server/gnun/gnun.mk'. If it is not, the first thing to do is to
- translate and submit to <address@hidden> the following
- files (all in the `server/po/' directory):
- `head-include-2.LANG.po', `body-include-1.LANG.po',
- `body-include-2.LANG.po' and `footer-text.LANG.po', together with
- your first message stating that you would like to establish a new
- team. *Note New Translation: (gnun)New Translation.
+ 3. Submit your first message stating that you would like to establish
+ a new team to <address@hidden>; please mention that you
+ have read all the documentation and list the issues that remain
+ unclear for you. The Translation Managers will answer your
+ questions and send you the standard questionnaire for new team
+ leaders. It is short and shouldn't take more than 10-30 minutes
+ to complete. This questionnaire is important, as we consider it
+ crucial for any translation team co-ordinator to have a good
+ understanding of the philosophy of the free software movement.
+
+ 4. Check if your language code is present in the variable
+ `TEMPLATE_LINGUAS' at `server/gnun/gnun.mk'. If it is not, the
+ first thing to do is to translate and submit to
+ <address@hidden> the following files (all in the
+ `server/po/' directory): `head-include-2.LANG.po',
+ `body-include-1.LANG.po', `body-include-2.LANG.po'
+ `footer-text.LANG.po', `outdated.LANG.po',
+ `skip-translations.LANG.po', and `top-addendum.LANG.po'. *Note
+ New Translation: (gnun)New Translation.
- The language code (LANG) should be the ISO 639-1 code of the
language, for example `hy' for Armenian or `el' for Greek. If
@@ -405,7 +417,7 @@
there is `ü' and this is a character from the alphabet
of your language, just write it as `u"' directly.
- 4. Any prospective team leader should submit a few translations first.
+ 5. Any prospective team leader should submit a few translations first.
This is a process of pointing errors and omissions (which are
expected and natural); it's an important thing to do as the leader
is going to carry out these checks on her own, once the team is
@@ -416,7 +428,7 @@
find -name \*.LANG.html
- 5. Submit at least two translations of your own. We maintain a list
+ 6. Submit at least two translations of your own. We maintain a list
with priority articles at
`http://www.gnu.org/server/standards/translations/priorities.html',
although it is probably hard to start with one of them. Choose
@@ -426,22 +438,12 @@
parties in the process. As usual, send the completed translation
to <address@hidden>.
- 6. The Translation Managers will review your translations, and
+ 7. The Translation Managers will review your translations, and
eventually comment on them (mostly technical details if there is
no one among them speaking your language). Depending on the case,
it might be required to submit a corrected file. In any event,
please take into account the remarks in future work.
- 7. Once the Translation Managers determine that you are doing well and
- about to complete the process, they will send you the standard
- questionnaire for new team leaders. It is relevantly short and it
- shouldn't take more than 10-30 minutes to complete. This
- questionnaire is important, as we consider it crucial any
- translation team co-ordinator to have a good understanding of the
- philosophy of the free software movement. It is not unusual
- energetic people who complete all technical steps without trouble
- to fail here.
-
8. If all goes well, you will receive a response inviting you to
apply for a new translation project at Savannah. The project name
should be `www-LANG' where LANG is, unsurprisingly, the language
Index: web-trans.txt.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.txt.gz,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
Binary files /tmp/cvsBLaX7j and /tmp/cvseBaHko differ
Index: html_node/New-Team.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/New-Team.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- html_node/New-Team.html 28 Jun 2012 21:04:21 -0000 1.8
+++ html_node/New-Team.html 29 Sep 2012 06:53:49 -0000 1.9
@@ -53,12 +53,16 @@
and technical skills, and devotion. The only “bonus” team leaders
have is more work and more responsibilities.
- <p>You should read most of the philosophy-related articles and <em>all</em>
-the documentation related to the translation process before you decide
-to form a new team, or take over an orphaned team. Once you have the
-internal feeling that having a gnu.org translation team for your
-language is a must, and you are the one for this job, follow these
-steps:
+ <p>You should read and <em>all</em> the documentation related to the
+translation process at the very least all important philosophy-related
+articles listed on
+<a
href="http://gnu.org/server/standards/README.translations.html";>http://gnu.org/server/standards/README.translations.html</a>
+and
+<a
href="http://gnu.org/server/standards/translations/priorities.html";>http://gnu.org/server/standards/translations/priorities.html</a>
+before you decide to form a new team, or take over an orphaned team.
+Once you have the internal feeling that having a gnu.org translation
+team for your language is a must, and you are the one for this job,
+follow these steps:
<ol type=1 start=1>
<li>If you do not have a Savannah account, register at
@@ -84,18 +88,31 @@
<p>As you have probably observed, every directory that contains
translatable articles has a <samp><span class="file">/po</span></samp>
sub-directory, which is where the
-new canonical source format of the translations is stored.
+canonical source format of the translations is stored.
- <li>Assuming you have already read the GNUN manual entirely (as
recommended
-in the beginning of this section), check if your language code is
+ <li>Submit your first message stating that you would like to establish a
new
+team to <a href="mailto:address@hidden";>address@hidden</a>; please mention
that you have
+read all the documentation and list the issues that remain unclear for
+you. The Translation Managers will answer your questions and send you
+the standard questionnaire for new team leaders. It is short and
+shouldn't take more than 10–30 minutes to complete. This questionnaire
+is important, as we consider it crucial for any translation team
+co-ordinator to have a good understanding of the philosophy of the free
+software movement.
+
+ <li>Check if your language code is
present in the variable <code>TEMPLATE_LINGUAS</code> at
<samp><span class="file">server/gnun/gnun.mk</span></samp>. If it is not, the
first thing to do is to
translate and submit to <a href="mailto:address@hidden";>address@hidden</a> the
following
files (all in the <samp><span class="file">server/po/</span></samp> directory):
<samp><span class="file">head-include-2.</span><var>lang</var><span
class="file">.po</span></samp>,
-<samp><span class="file">body-include-1.</span><var>lang</var><span
class="file">.po</span></samp>, <samp><span
class="file">body-include-2.</span><var>lang</var><span
class="file">.po</span></samp>
-and <samp><span class="file">footer-text.</span><var>lang</var><span
class="file">.po</span></samp>, together with your first message
-stating that you would like to establish a new team. See <a
href="../gnun/New-Translation.html#New-Translation">New Translation</a>.
+<samp><span class="file">body-include-1.</span><var>lang</var><span
class="file">.po</span></samp>,
+<samp><span class="file">body-include-2.</span><var>lang</var><span
class="file">.po</span></samp>
+<samp><span class="file">footer-text.</span><var>lang</var><span
class="file">.po</span></samp>,
+<samp><span class="file">outdated.</span><var>lang</var><span
class="file">.po</span></samp>,
+<samp><span class="file">skip-translations.</span><var>lang</var><span
class="file">.po</span></samp>,
+and <samp><span class="file">top-addendum.</span><var>lang</var><span
class="file">.po</span></samp>.
+See <a href="../gnun/New-Translation.html#New-Translation">New Translation</a>.
<ul>
<li>The language code (<var>lang</var>) should be the ISO 639-1 code of the
@@ -140,15 +157,6 @@
submit a corrected file. In any event, please take into account the
remarks in future work.
- <li>Once the Translation Managers determine that you are doing well and
-about to complete the process, they will send you the standard
-questionnaire for new team leaders. It is relevantly short and it
-shouldn't take more than 10-30 minutes to complete. This questionnaire
-is important, as we consider it crucial any translation team
-co-ordinator to have a good understanding of the philosophy of the free
-software movement. It is not unusual energetic people who complete all
-technical steps without trouble to fail here.
-
<li>If all goes well, you will receive a response inviting you to apply
for
a new translation project at Savannah. The project name should be
‘<samp><span class="samp">www-</span><var>lang</var></samp>’ where
<var>lang</var> is, unsurprisingly, the language
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- trans-coord/manual/web-trans index.html web-tra...,
Pavel Kharitonov <=