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

[Pavel Kharitonov]

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Pavel Kharitonov <ineiev>       14/04/03 16:52:04

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

Log message:
        Documentation fixes suggested by Thérèse Godefroy.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/ChangeLog?cvsroot=trans-coord&r1=1.405&r2=1.406
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/gnun.texi?cvsroot=trans-coord&r1=1.96&r2=1.97

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/ChangeLog,v
retrieving revision 1.405
retrieving revision 1.406
diff -u -b -r1.405 -r1.406
--- ChangeLog   17 Mar 2014 12:54:07 -0000      1.405
+++ ChangeLog   3 Apr 2014 16:52:04 -0000       1.406
@@ -1,3 +1,7 @@
+2014-04-03  Thérèse Godefroy <address@hidden> (tiny change)
+
+       * doc/gnun.texi: Multiple minor fixes.
+
 2014-03-17  Pavel Kharitonov  <address@hidden>
 
        Minor documentation updates and refinements.

Index: doc/gnun.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/gnun.texi,v
retrieving revision 1.96
retrieving revision 1.97
diff -u -b -r1.96 -r1.97
--- doc/gnun.texi       17 Mar 2014 12:54:08 -0000      1.96
+++ doc/gnun.texi       3 Apr 2014 16:52:04 -0000       1.97
@@ -72,19 +72,19 @@
 scripts that are supposed to make the life of @url{https://www.gnu.org}
 translators easier.  Although it is specifically developed for the GNU
 Project's website, it could be customized, at least in theory, to fit
-the needs of other internationalized sites.  GNUN is in early stage of
+the needs of other internationalized sites.  GNUN is in an early stage of
 development, but if it proves useful, and if there is sufficient
 interest (and time), it is possible to develop a robust configuration
 interface that would be appropriate for general usage.
 
 It is vitally important to understand that GNUN is @emph{not} a silver
-bullet that solves all problems.  If we have to be honest, deploying
-GNUN in fact even does create some (@pxref{Disadvantages}).
+bullet that solves all problems.  To be honest, deploying
+GNUN in fact even does create some @ref{Disadvantages}.
 
 GNUnited Nations is free software, available under the GNU General
 Public License.
 
-This manual is organized in way that is suitable both for translators
+This manual is organized in a way that is suitable both for translators
 and GNU Web Translation Managers (plus eventually interested GNU
 Webmasters, if any).  It may also serve as an introductory material and
 reference for new GNUN developers and contributors.  Hopefully, it might
@@ -119,13 +119,13 @@
 own sets of scripts, but so far there has been no universal solution.
 
 This unpleasant situation, combined with rapid and incompatible design
-changes, have lead some teams to neglect the important work of keeping
-their translation in line with the changing original articles.  As a
+changes, have led some teams to neglect the important work of keeping
+their translations in line with the changing original articles.  As a
 consequence, the GNU Project is facing the problem of maintaining them
 in suboptimal ways, in order to keep the information updated.
 
 The reasons for developing GNUnited Nations are very similar to those
-that lead to the inception of GNU gettext, or GNOME Documentation
+that led to the inception of GNU gettext, or GNOME Documentation
 Utilities (@code{gnome-doc-utils}) some years later.
 
 @node Concepts
@@ -139,7 +139,7 @@
 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
+like programs, tend to change over time, but not every change in the
 sources calls for a translation update.  Sometimes the change does not
 affect the translatable strings, but sometimes it does.  So, translators
 must have means to identify those changes and apply the appropriate
@@ -150,8 +150,8 @@
 @xref{Introduction, Introduction, , gettext, GNU gettext tools},
 for a basic overview.
 GNUnited Nations fills the gaps to apply this infrastructure to articles
-in @url{https://www.gnu.org} web address@hidden process of converting
-HTML to PO and the other way around is performed using po4a (``po for
+in the @url{https://www.gnu.org} web address@hidden process of converting
+HTML to PO and the other way around is performed using po4a (``PO for
 anything''), see @uref{http://po4a.alioth.debian.org, PO4A website}.}
 
 The following diagram summarizes the relation between the files handled
@@ -194,19 +194,19 @@
 marks this as a Template PO file, not yet oriented towards any
 particular language.
 
-The first time though, there is no @address@hidden@var{lang}.po}
-yet, so a translator must make @address@hidden@var{lang}.po} from
+On the first run, though, there is no @address@hidden@var{lang}.po}
+yet, so a translator must create @address@hidden@var{lang}.po} from
 @address@hidden, where @var{lang} represents the
 target language.  @xref{New Translation}, for details.
 
 Then comes the initial translation of messages in
 @address@hidden@var{lang}.po}.  Translation in itself is a whole
 matter, whose complexity far overwhelms the level of this manual.
-Nevertheless, a few hints are given in some other chapter of this
+Nevertheless, a few hints are given in another chapter of this
 manual.
 
 It is possible to make GNUN get translations for common strings from
-dedicated PO files, so called compendia.  @xref{Compendia}, for more
+dedicated PO files, the so-called compendia.  @xref{Compendia}, for more
 information.
 
 You may use any compatible PO editor to add translated messages into
@@ -216,20 +216,20 @@
 When the PO file actually exists (hopefully populated with initial
 translations), GNUN generates @address@hidden@var{lang}.html} file.
 It takes its structure from the original @address@hidden, but
-all translatable strings are replaced with their translations specified
+all translatable strings are replaced with the translations specified
 in @address@hidden@var{lang}.po}.
 
 Original articles sometimes change.  A new paragraph is being added or a
 tiny change in the wording is introduced.  Also, some articles are
-dynamic in nature, like ones containing news entries or a list of other
+dynamic in nature, like the ones containing news entries or a list of other
 articles.  If the original article changes, GNUN will automatically
-rebuild @address@hidden, and will merge the changes to
+rebuild @address@hidden, and will merge the changes into
 @address@hidden@var{lang}.po}.  Any outdated translations will be
 marked as ``fuzzy,'' any new strings will be added with empty translations,
 waiting to be translated.  In the same run
address@hidden@address@hidden will be rebuilt so the relevant
address@hidden@address@hidden will be rebuilt, and consequently the relevant
 strings in the translation will be substituted with the original English
-text, until the translation teams update them in
+text until the translation teams update them in
 @address@hidden@var{lang}.po}.
 
 Those changes in the original article that do not affect the
@@ -240,13 +240,13 @@
 automatically regenerated to reflect the changes.
 
 The POT for every article under GNUN's control is kept in the `www'
-repository under a special directory @file{po/}, which is a
-sub-directory of the relevant directory in the `www' tree.  So, for
address@hidden://www.gnu.org/philosophy/free-sw.html} that is
address@hidden/po/}.  In addition to @file{free-sw.pot}, this directory holds
-the canonical source of every translation, like @file{free-sw.bg.po},
address@hidden, etc. For more details,
address@hidden and Directories}.
+repository under a special sub-directory @file{po/} of the relevant
+directory in the `www' tree.  Thus, for
address@hidden://www.gnu.org/philosophy/free-sw.html} this
+sub-directory is @file{philosophy/po/}.  In addition to
address@hidden, this directory holds the canonical source of every
+translation, such as @file{free-sw.bg.po}, @file{free-sw.ca.po}, etc.
+For more details, @pxref{Files and Directories}.
 
 Several additional features are implemented, like automatic update of
 the list of the available translations.  For example, if a new
@@ -255,7 +255,7 @@
 @address@hidden is updated.  This saves a lot of
 tedious, repetitive work and eliminates a source of mistakes.  There
 is a basic infrastructure to ``inject'' general information about a
-translation team---like a note how to contact the team, or how to
+translation team---like a note on 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.
 
@@ -273,7 +273,7 @@
 @section Major Advantages of GNUN
 
 Here is a simple list of situations where we hope this suite would
-prove to be useful.
+prove useful.
 
 @itemize
 @item
@@ -299,7 +299,7 @@
 ``urgent'' notice may not be very ``urgent'' for Urdu.  However, such
 notice will appear in all translated pages and people who usually read
 gnu.org pages in their native language will see it, so they can take
-action as necessary.  When the notice is removed, often in a week or
+action as necessary.  When the notice is removed, often within a week or
 two, it will disappear without translators' intervention, whether they
 translated it or not.
 
@@ -316,10 +316,10 @@
 basic markup, which is where most of the validation errors come from.
 
 @item
-Markup consistency site-wide---it would be substantially easier to
+Markup consistency site-wide---it will be substantially easier to
 update the site to a future standard, because translations will
 naturally follow the changes in the original articles.  This also means
-that translation teams do not have to undergo the boring process of
+that translation teams do not have to go through the boring process of
 converting their articles to the new SSI-based layout; this will be done
 automatically.
 
@@ -365,7 +365,7 @@
 ---Murphy's Law
 
 Murphy is an optimist.
----O'Rielly's Law
+---O'Reilly's Law
 @end flushright
 @sp 1
 
@@ -384,7 +384,7 @@
 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.
+manual intervention is possible to a certain degree.
 
 @menu
 * Invoking GNUN::       How to trigger a (re)build.
@@ -411,7 +411,7 @@
 installed and available as @command{gmake} or @command{gnumake}.  If
 not, you should consider installing it, since the build will fail
 otherwise.  See @uref{https://www.gnu.org/software/make,
-GNU Make homepage} for information
+GNU Make homepage} for information on
 how to download and install GNU Make.
 
 If you don't specify a target, @command{make} by default builds the
@@ -1075,7 +1075,7 @@
 persons interested in particular address@hidden following
 sections describe in more details how to setup these automatic
 actions; however, if you have any difficulties with that, please ask
-the GNU Web Translation Managers to setup them for your team on our
+the GNU Web Translation Managers to set them up for your team on our
 server.}.  A translator would then normally update the PO file, and
 commit it again in the project's Sources repository, from where the
 co-ordinator will pick it up and install it in `www'.