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

[Yavor Doganov]

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   09/01/29 09:52:45

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

Log message:
        (Disadvantages): Update as the build runs twice daily now.  Explain
        the drawback resulting from errors during the build.
        (Invoking GNUN): Explicitly state that GNU make is required.
        (triggers): Update crontab example; the official GNUN build is run in
        parallel.
        (New Translation): Simplify the msgcat example for line wrapping.

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

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/ChangeLog,v
retrieving revision 1.125
retrieving revision 1.126
diff -u -b -r1.125 -r1.126
--- ChangeLog   28 Jan 2009 10:11:24 -0000      1.125
+++ ChangeLog   29 Jan 2009 09:52:45 -0000      1.126
@@ -1,3 +1,13 @@
+2009-01-29  Yavor Doganov  <address@hidden>
+
+       * doc/gnun.texi (Disadvantages): Update as the build runs twice
+       daily now.  Explain the drawback resulting from errors during the
+       build.
+       (Invoking GNUN): Explicitly state that GNU make is required.
+       (triggers): Update crontab example; the official GNUN build is run
+       in parallel.
+       (New Translation): Simplify the msgcat example for line wrapping.
+
 2009-01-28  Yavor Doganov  <address@hidden>
 
        * GNUmakefile:

Index: doc/gnun.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/gnun.texi,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- doc/gnun.texi       26 Jan 2009 11:20:48 -0000      1.2
+++ doc/gnun.texi       29 Jan 2009 09:52:45 -0000      1.3
@@ -355,12 +355,13 @@
 prepared to check the CVS history of the original article.
 
 @item
-We plan to invoke a build once a day, because doing it more often will
-potentially generate more messages to the mailing list in the form of
-commit notifications.  This has its drawback, since translators will
-have to wait for a day until their PO files are updated, and another
-day for the @address@hidden articles to get generated, after
-they commit the updated POs.
+The official build is invoked twice daily, because doing it more often
+will potentially generate more messages to the mailing list in the form
+of commit notifications.  This has its drawback, since translators have
+to wait 12 hours until their PO files are updated, and another period
+for the @address@hidden articles to get generated, after they
+commit the updated POs.  Additionally, any errors interrupt the build so
+they have to be fixed before the next articles are processed.
 @end itemize
 
 @node Usage
@@ -406,16 +407,15 @@
 @cindex invoking
 @cindex triggering, build
 
-The central part of @acronym{GNU}nited Nations is a makefile; actually
-a @file{GNUmakefile} since it heavily relies on features and
-extensions available in @acronym{GNU} Make.  Thus, invoking a build
-consists of typing @command{make} on the command line, or within cron.
-If you are deploying the software on a non-GNU machine, probably
address@hidden Make is installed and available as @command{gmake}.  If
-not, you should seriously consider installing it, since as far as we
-know, the build will fail otherwise.  See
address@hidden://www.gnu.org/software/make} for information how to
-download and install @acronym{GNU} Make.
+The central part of @acronym{GNU}nited Nations is a makefile; actually a
address@hidden since it heavily relies on features and extensions
+available in @acronym{GNU} Make.  Thus, invoking a build consists of
+typing @command{make} on the command line, or within cron.  If you are
+deploying the software on a non-GNU machine, probably @acronym{GNU} Make
+is installed and available as @command{gmake} or @command{gnumake}.  If
+not, you should consider installing it, since the build will fail
+otherwise.  See @uref{http://www.gnu.org/software/make} for information
+how to download and install @acronym{GNU} Make.
 
 If you don't specify a target, @command{make} by default builds the
 target @code{all}, which in this case is to rebuild all translations
@@ -672,7 +672,7 @@
 @example
 @group
 25 4,16 * * *  cd $HOME/projects/www ; cvs -q update &>/dev/null ; \
-                 make -C server/gnun VCS=yes VALIDATE=yes NOTIFY=yes \
+                 make -j4 -C server/gnun VCS=yes VALIDATE=yes NOTIFY=yes \
                  VERBOSE=yes GRACE=30 ; cvs commit -m \
                  "Automatic update by GNUnited Nations." ; \
                  make -C server/gnun triggers
@@ -972,7 +972,7 @@
 @code{msgstr}'s.  If that happens, long lines make reading subsequent
 diffs harder, and are generally annoying for most people.  If this issue
 bothers you, you can ``normalize'' the already finished PO translation
-by executing on the command line @code{cat @var{file}.po | msgcat - -o
+by executing on the command line @code{msgcat -o @var{file}.po
 @var{file}.po}, before installing it in the repository.  Either way, the
 build system will treat it is a valid PO file.