trans-coord/gnun/server/gnun gnun.texi

[Yavor Doganov]

CVSROOT:        /cvsroot/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   08/02/29 20:25:07

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

Log message:
        (Concepts): Move the comment about the resemblance to
        software documentation in a footnote.
        (Runtime Variables): Say `validation is enabled' rather than
        `performed'.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/gnun.texi?cvsroot=trans-coord&r1=1.5&r2=1.6

Patches:
Index: gnun.texi
===================================================================
RCS file: /cvsroot/trans-coord/trans-coord/gnun/server/gnun/gnun.texi,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- gnun.texi   25 Feb 2008 21:01:39 -0000      1.5
+++ gnun.texi   29 Feb 2008 20:25:06 -0000      1.6
@@ -4,7 +4,7 @@
 @settitle GNUnited Nations Manual
 @c FIXME: Would be nice to have it in the format `%:b %:d, %:y', but
 @c in English.
address@hidden lastupdate 25.02.2008
address@hidden lastupdate 29.02.2008
 @afourpaper
 @c %**end of header
 
@@ -136,10 +136,13 @@
 @section What @acronym{GNU}nited Nations is and Should be
 
 The basic concept behind @acronym{GNUN} is that localization of HTML
-articles is similar to localization of computer programs (or more
-precisely, of software documentation).  In articles, like in programs,
-not every string is considered translatable, so translatable strings
-must be identified first, and then collected in a file (called ``PO
+articles is similar to localization of computer programs
address@hidden, it is much more closer to localization of software
+documentation, where typically strings (also known as ``messages'' in
+gettext's context) are longer than strings in programs.  Nevertheless,
+all points raised still apply.}.  In articles, like in programs, not
+every string is considered translatable, so translatable strings must
+be identified first, and then collected in a file (called ``PO
 template'') for translation.  Articles, like programs, tend to change
 in time, but not every change in the sources calls for a translation
 update.  Sometimes the change does not affect the translatable
@@ -479,12 +482,12 @@
 specified in @code{TEMPLATE_LINGUAS} and will perform additional check
 at the end, @code{cvs add}-ing all necessary files.
 
-When validation is performed, the original English articles are
-validated first, before any commands that generate the other files,
-and @command{make} exits with an error on the first encountered
-article.  This is done on purpose, to prevent the propagation of an
-eventual error in the markup of the original article to all
-translations.
+When validation is enabled (i.e. with @code{VALIDATE=yes}), the
+original English articles are validated first, before any commands
+that generate the other files, and @command{make} exits with an error
+on the first encountered article.  This is done on purpose, to prevent
+the propagation of an eventual error in the markup of the original
+article to all translations.
 
 By contrast, validation of the translated @address@hidden is
 performed after it is generated and if @code{VCS=yes} the article will