trans-coord-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

trans-coord/gnun/server/gnun ChangeLog doc/web-...


From: Pavel Kharitonov
Subject: trans-coord/gnun/server/gnun ChangeLog doc/web-...
Date: Sat, 29 Sep 2012 05:42:20 +0000

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Pavel Kharitonov <ineiev>       12/09/29 05:42:20

Modified files:
        gnun/server/gnun: ChangeLog 
        gnun/server/gnun/doc: web-trans.texi 

Log message:
        (New Team): Update (move the step
        with questionnaire up; add POs of new templates).

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/ChangeLog?cvsroot=trans-coord&r1=1.294&r2=1.295
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/web-trans.texi?cvsroot=trans-coord&r1=1.34&r2=1.35

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/ChangeLog,v
retrieving revision 1.294
retrieving revision 1.295
diff -u -b -r1.294 -r1.295
--- ChangeLog   28 Sep 2012 10:27:59 -0000      1.294
+++ ChangeLog   29 Sep 2012 05:42:19 -0000      1.295
@@ -1,3 +1,8 @@
+2012-09-29  Pavel Kharitonov  <address@hidden>
+
+       * doc/web-trans.texi (New Team): Update (move the step
+       with questionnaire up; add POs of new templates).
+
 2012-09-28  Pavel Kharitonov  <address@hidden>
 
        * GNUmakefile (generate-proto): Recognize the

Index: doc/web-trans.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/web-trans.texi,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -b -r1.34 -r1.35
--- doc/web-trans.texi  28 Jun 2012 19:09:53 -0000      1.34
+++ doc/web-trans.texi  29 Sep 2012 05:42:20 -0000      1.35
@@ -383,12 +383,16 @@
 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 @emph{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
-steps:
+You should read and @emph{all} the documentation related to the
+translation process at the very least all important philosophy-related
+articles listed on
address@hidden://gnu.org/@/server/@/standards/@/README.translations.html}
+and
address@hidden://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:
 
 @enumerate
 @item
@@ -416,20 +420,33 @@
 
 As you have probably observed, every directory that contains
 translatable articles has a @file{/po} sub-directory, which is where the
-new canonical source format of the translations is stored.
+canonical source format of the translations is stored.
+
address@hidden
+Submit your first message stating that you would like to establish a new
+team to @email{web-translators@@gnu.org}; 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.
 
 @item
-Assuming you have already read the GNUN manual entirely (as recommended
-in the beginning of this section), check if your language code is
+Check if your language code is
 present in the variable @code{TEMPLATE_LINGUAS} at
 @file{server/gnun/gnun.mk}.  If it is not, the first thing to do is to
 translate and submit to @email{web-translators@@gnu.org} the following
 files (all in the @file{server/po/} directory):
 @address@hidden,
address@hidden@var{lang}.po}, @address@hidden
-and @address@hidden, together with your first message
-stating that you would like to establish a new team.  @xref{New
-Translation, , , gnun, The GNUnited Nations Manual}.
address@hidden@var{lang}.po},
address@hidden@var{lang}.po}
address@hidden@var{lang}.po},
address@hidden@var{lang}.po},
address@hidden@var{lang}.po},
+and @address@hidden
address@hidden Translation, , , gnun, The GNUnited Nations Manual}.
 
 @itemize @minus
 @item
@@ -483,16 +500,6 @@
 remarks in future work.
 
 @item
-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.
-
address@hidden
 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
 @address@hidden where @var{lang} is, unsurprisingly, the language



reply via email to

[Prev in Thread] Current Thread [Next in Thread]