trans-coord/gnun/server/gnun ChangeLog TODO gnu...

[Yavor Doganov]

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   08/02/20 09:15:38

Modified files:
        gnun/server/gnun: ChangeLog TODO gnun.texi 

Log message:
        (Usage, Runtime Variables, New Translation, generic.LANG.html):
        Amend the location prep/gnun to server/gnun.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/ChangeLog?cvsroot=trans-coord&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/TODO?cvsroot=trans-coord&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/gnun.texi?cvsroot=trans-coord&r1=1.1&r2=1.2

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/ChangeLog,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- ChangeLog   20 Feb 2008 09:11:07 -0000      1.1
+++ ChangeLog   20 Feb 2008 09:15:37 -0000      1.2
@@ -3,6 +3,8 @@
        * gnun.texi (Advantages): Clarify the usefulness of `urgent'
        notices propagation.
        (Concepts): Use double quotes for po4a's meaning.
+       (Usage, Runtime Variables, New Translation, generic.LANG.html):
+       Amend the location prep/gnun to server/gnun.
 
 2008-02-19  Yavor Doganov  <address@hidden>
            Kaloian Doganov  <address@hidden>

Index: TODO
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/TODO,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- TODO        20 Feb 2008 09:11:08 -0000      1.1
+++ TODO        20 Feb 2008 09:15:38 -0000      1.2
@@ -87,7 +87,7 @@
   messages will be used in the next run.
 
 ** Figure out how to "inject" a language-specific warning, possibly
-   from /prep/i18n/outdated.xx.html that will be displayed when the
+   from /server/i18n/outdated.xx.html that will be displayed when the
    page has 20% (or more) messages untranslated.  We have to think
    also about a deprecation plan for all gnu.org translated pages, and
    whether this software can help sorting all issues out.  Idea: We

Index: gnun.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/gnun.texi,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- gnun.texi   20 Feb 2008 09:11:08 -0000      1.1
+++ gnun.texi   20 Feb 2008 09:15:38 -0000      1.2
@@ -183,9 +183,9 @@
 next run.
 
 Arrows denote dependency relation between files, where a change in one
-file will affect the other.  Those automatic changes will be applied
-by running @samp{make -C prep/gnun}.  This is the primary way to
-invoke @acronym{GNUN}, since it is implemented as a set of recipes for
+file will affect the other.  Those automatic changes will be applied by
+running @samp{make -C server/gnun}.  This is the primary way to invoke
address@hidden, since it is implemented as a set of recipes for
 @acronym{GNU} @code{make}.
 
 First, @acronym{GNUN} extracts all translatable strings from the
@@ -375,18 +375,18 @@
 
 @acronym{GNUN} currently consists of a few makefiles, scripts and
 optional @address@hidden files, intended to contain
-article-independent but team-specific information.  They are designed
-to reside in the @file{prep/gnun/} directory, but this may change.  In
-all examples in this manual, ``invoking'' means executing on the
-command line @command{make -C prep/gnun/ address@hidden
address@hidden@var{value} @dots{}]} while the working directory is
-the root in the `www' web repository.  For the purpose of brevity, we
-will refer to the above command as simply @command{make}, which is
-equivalent to @command{cd prep/gnun ; make}.  It is desirable never to
-invoke @command{make} with the @option{-k} (@option{--keep-going})
-option, because an eventual error in only one make recipe might create
-a mess in many articles, both original and translated.  Do this with
-caution, and generally only when debugging in a safe environment.
+article-independent but team-specific information.  They are designed to
+reside in the @file{server/gnun} directory, but this may change.  In all
+examples in this manual, ``invoking'' means executing on the command
+line @command{make -C server/gnun address@hidden
address@hidden@var{value} @dots{}]} while the working directory is the
+root in the `www' web repository.  For the purpose of brevity, we will
+refer to the above command as simply @command{make}, which is equivalent
+to @command{cd server/gnun ; make}.  It is desirable never to invoke
address@hidden with the @option{-k} (@option{--keep-going}) option,
+because an eventual error in only one make recipe might create a mess in
+many articles, both original and translated.  Do this with caution, and
+generally only when debugging in a safe environment.
 
 The build process is intended to be invoked by a cron job, although
 manual intervention to a certain degree is possible.
@@ -444,7 +444,7 @@
 Automatically add any new files in the repository.  These are any POT
 files, if they are generated for the first time, and the translated
 articles (@address@hidden) in HTML format.  In addition, if
-there is no @file{prep/gnun/address@hidden file for the
+there is no @file{server/gnun/address@hidden file for the
 specific language an article is being generated, an empty file will be
 added.  Finally, any missing PO and their HTML counterparts of the
 server templates will be added, computed on the basis of the
@@ -649,18 +649,17 @@
 @node New Translation
 @subsection Starting a New Translation
 
-To start a new translation, the easiest way is to copy the existing
-POT as @address@hidden, where @var{lang} is your language
-code.  For example, to prepare for a new translation of the essay
address@hidden://www.gnu.org/philosophy/freedom-or-copyright.html}, you
-can simply do @command{cd philosophy/po ; cp freedom-or-copyright.pot
+To start a new translation, the easiest way is to copy the existing POT
+as @address@hidden, where @var{lang} is your language code.
+For example, to prepare for a new translation of the essay
address@hidden://www.gnu.org/philosophy/freedom-or-copyright.html}, you can
+simply do @command{cd philosophy/po ; cp freedom-or-copyright.pot
 address@hidden and then edit the latter.  If
address@hidden does not exist it is because either
-the article is not yet ``templated'' (i.e. migrated to the new style),
-or the @acronym{GNUN} maintainers have not yet added it to the value
-of the appropriate variable in @file{prep/gnun/gnun.mk}.  In that
-case, just ask them to do the necessary in order the POT to be
-generated.
address@hidden does not exist it is because either the
+article is not yet ``templated'' (i.e. migrated to the new style), or
+the @acronym{GNUN} maintainers have not yet added it to the value of the
+appropriate variable in @file{server/gnun/gnun.mk}.  In that case, just
+ask them to do the necessary in order the POT to be generated.
 
 You could also use the @command{msginit} utility that would populate
 the PO file header with the right information, provided your
@@ -817,12 +816,12 @@
 @node generic.LANG.html
 @subsection The @address@hidden file
 
-The files @file{prep/gnun/address@hidden are special: if no
+The files @file{server/gnun/address@hidden are special: if no
 such file exists for your language, an empty file will will be created
-(and added to the repository if specified @code{VCS=yes}).  This file
-is optional, and should contain a short message in your native
-language, ideally providing more information about the translation
-team or where to report bugs.  For example:
+(and added to the repository if specified @code{VCS=yes}).  This file is
+optional, and should contain a short message in your native language,
+ideally providing more information about the translation team or where
+to report bugs.  For example:
 
 @example
 <p>To join the Fooish translation team, see <a