trans-coord/gnun/prep/gnun ChangeLog gnun.texi

[Yavor Doganov]

CVSROOT:        /cvsroot/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   08/02/16 07:09:18

Modified files:
        gnun/prep/gnun : ChangeLog gnun.texi 

Log message:
        (Disadvantages, Usage, Runtime Variables, New Translation)
        (Migrating, generic.LANG.html, make-prototype): Use @var{lang}
        instead of `xx' for consistency with the gettext manual.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/prep/gnun/ChangeLog?cvsroot=trans-coord&r1=1.52&r2=1.53
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/prep/gnun/gnun.texi?cvsroot=trans-coord&r1=1.13&r2=1.14

Patches:
Index: ChangeLog
===================================================================
RCS file: /cvsroot/trans-coord/trans-coord/gnun/prep/gnun/ChangeLog,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- ChangeLog   16 Feb 2008 07:00:48 -0000      1.52
+++ ChangeLog   16 Feb 2008 07:09:16 -0000      1.53
@@ -1,6 +1,9 @@
 2008-02-16  Yavor Doganov  <address@hidden>
 
        * gnun.texi (Concepts): Typo fix.
+       (Disadvantages, Usage, Runtime Variables, New Translation)
+       (Migrating, generic.LANG.html, make-prototype): Use @var{lang}
+       instead of `xx' for consistency with the gettext manual.
 
 2008-02-15  Yavor Doganov  <address@hidden>
 

Index: gnun.texi
===================================================================
RCS file: /cvsroot/trans-coord/trans-coord/gnun/prep/gnun/gnun.texi,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- gnun.texi   16 Feb 2008 07:00:48 -0000      1.13
+++ gnun.texi   16 Feb 2008 07:09:17 -0000      1.14
@@ -257,12 +257,13 @@
 Several additional features are implemented, like automatic update of
 the list of the available translations.  For example, if a new
 translation is added and the list of translations in
address@hidden is updated, all translated @file{free-sw.xx.html}
-will be regenerated.  This saves a lot of tedious, repetitive work.
-There is a basic infrastructure to ``inject'' general information
-about a translation team---like a note how to contact the team, or how
-to report a bug/suggestion for improvement.  Translators' credits are
-also handled, as well as translators' notes, if any.
address@hidden is updated, all translated
address@hidden@var{lang}.html} will be regenerated.  This saves a lot
+of tedious, repetitive work.  There is a basic infrastructure to
+``inject'' general information about a translation team---like a note
+how to contact the team, or how to report a bug/suggestion for
+improvement.  Translators' credits are also handled, as well as
+translators' notes, if any.
 
 @acronym{GNUN} can be extended, and new features will certainly be
 added.  The @file{TODO} file currently lists some of them, but new
@@ -347,8 +348,8 @@
 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 @file{.xx.html} articles to get generated, after they
-commit the updated POs.
+day for the @address@hidden articles to get generated, after
+they commit the updated POs.
 
 @item
 Currently there is no way a translation team can take advantage of
@@ -370,7 +371,7 @@
 @sp 1
 
 @acronym{GNUN} currently consists of a few makefiles, scripts and
-optional @file{generic.xx.html} files, intended to contain
+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
@@ -439,11 +440,12 @@
 @item VCS=yes
 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 (@file{.xx.html}) in HTML format.  In addition, if there is
-no @file{prep/gnun/generic.xx.html} 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 @code{template_files} variable.
+articles (@address@hidden) in HTML format.  In addition, if
+there is no @file{prep/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
address@hidden variable.
 
 @item VCS=always
 Because @acronym{GNU} Make considers the targets up-to-date after a
@@ -560,15 +562,17 @@
 @item TEMPLATE_LINGUAS
 Add here your language code @emph{if and only if} you have all the
 server templates translated, and have committed
address@hidden/po/banner.xx.po} and @file{server/po/footer-text.xx.po},
-as well as the templates that are not under @acronym{GNUN}'s control,
-like @file{server/header.xx.html} and @file{server/footer.xx.html}.
address@hidden/po/address@hidden and
address@hidden/po/address@hidden, as well as the templates
+that are not under @acronym{GNUN}'s control, like
address@hidden/address@hidden and
address@hidden/address@hidden
 
 @item HOME_LINGUAS
 Add your language code if you have already committed
address@hidden/home.xx.po}, that way the homepage for your language will be
-built.  It is not acceptable to have your language code defined in
-this variable, but not in @code{TEMPLATE_LINGUAS}.
address@hidden/address@hidden, that way the homepage for your language
+will be built.  It is not acceptable to have your language code
+defined in this variable, but not in @code{TEMPLATE_LINGUAS}.
 
 @item ROOT
 Add here articles that are in the server root, like
@@ -635,7 +639,7 @@
 * New Translation::     How to start a new translation.
 * Migrating::           How to migrate an existing translation to a PO
                           format under @acronym{GNUN}'s control.
-* generic.xx.html::     Specifying information that will propagate in
+* generic.LANG.html::   Specifying information that will propagate in
                           every translation in a certain language.
 @end menu
 
@@ -643,11 +647,11 @@
 @subsection Starting a New Translation
 
 To start a new translation, the easiest way is to copy the existing
-POT as @file{article.xx.po}, where @code{xx} is your language code.
-For example, to prepare for a new translation of the essay
+POT as @address@hidden, where @code{xx} is your language
+code.  For example, to prepare for a new translation of the essay
 @uref{http://www.gnu.org/philosophy/freedom-or-copyright.html}, you
 can simply do @command{cd philosophy/po ; cp freedom-or-copyright.pot
-freedom-or-copyright.xx.po} and then edit the latter.  If
address@hidden and then edit the latter.  If
 @file{freedom-or-copyright.pot} 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
@@ -768,9 +772,9 @@
 and/or markup from the existing translation in HTML format in the
 relevant message.
 
-Typically, you will visit @file{po/foo.xx.po} (in PO mode) and
address@hidden (in HTML mode) in another buffer.  Then you can
-copy a paragraph or an element from the latter and yank it in the
+Typically, you will visit @file{po/address@hidden (in PO mode) and
address@hidden@var{lang}.html} (in HTML mode) in another buffer.  Then you
+can copy a paragraph or an element from the latter and yank it in the
 relevant message in the former.  Be extra careful, since this is the
 time to check @emph{precisely} that the translation corresponds to the
 original.  Further changes will be reflected, but if your ``initial''
@@ -802,15 +806,15 @@
 translation, address@hidden made some changes in 2007, and the original
 translator returned in 2008 and continued maintaining it.
 
address@hidden generic.xx.html
address@hidden The @file{generic.xx.html} file
address@hidden generic.LANG.html
address@hidden The @address@hidden file
 
-The files @file{prep/gnun/generic.xx.html} 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:
+The files @file{prep/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:
 
 @example
 <p>To join the Fooish translation team, see <a
@@ -818,17 +822,17 @@
 Foo team homepage</a>.</p>
 @end example
 
-The contents of @file{generic.xx.html} is injected right after the
-translators' credits, if any, and before the timestamp.  It should be
-valid XHTML markup.
+The contents of @address@hidden is injected right after
+the translators' credits, if any, and before the timestamp.  It should
+be valid XHTML markup.
 
 When you modify this file, for example, adding a message to the
 existing empty file or changing a URL, such modification will affect
 @emph{all} articles of the language @code{xx} in
address@hidden  The next time a build occurs, all
-translations of the language code @code{xx} (i.e. all @file{.xx.html},
-including the homepage), will be modified to include the contents of
-this special file.
address@hidden@var{lang}.html}.  The next time a build occurs, all
+translations of the language code @code{xx} (i.e. all
address@hidden@var{lang}.html}, including the homepage), will be modified to
+include the contents of this special file.
 
 @node Internals
 @chapter Unexciting Information for @acronym{GNUN}'s Operation
@@ -859,11 +863,11 @@
 @subsection The @command{make-prototype} Script
 
 This is a Guile script which makes the ``prototype'' file,
address@hidden, from which the POT is generated.  @acronym{GNUN}
-is designed in such a way, because it would be no big improvement if
-links to other translations ended up in the POT---it would mean that
-translators would have to manually update their PO file when a new
-translation is added.
address@hidden@var{lang}.proto}, from which the POT is generated.
address@hidden is designed in such a way, because it would be no big
+improvement if links to other translations ended up in the POT---it
+would mean that translators would have to manually update their PO
+file when a new translation is added.
 
 In addition, @command{make-prototype} guards the timestamp (the
 @w{$}Date$ RCS keyword) in order the timestamp of the translation to
@@ -893,7 +897,7 @@
 @item -g
 @itemx address@hidden
 Common notes for a translation team; this is the
address@hidden file.  @xref{generic.xx.html}.
address@hidden@var{lang}.html} file.  @xref{generic.LANG.html}.
 
 @item -o
 @itemx address@hidden