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

[Pavel Kharitonov]

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Pavel Kharitonov <ineiev>       12/12/07 16:39:28

Modified files:
        gnun/server/gnun/doc: gnun.texi web-trans.texi 

Log message:
        Fix capitalization of titles.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/gnun.texi?cvsroot=trans-coord&r1=1.68&r2=1.69
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/web-trans.texi?cvsroot=trans-coord&r1=1.37&r2=1.38

Patches:
Index: gnun.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/gnun.texi,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -b -r1.68 -r1.69
--- gnun.texi   7 Dec 2012 13:26:06 -0000       1.68
+++ gnun.texi   7 Dec 2012 16:39:28 -0000       1.69
@@ -99,7 +99,7 @@
 @end menu
 
 @node Overview
address@hidden Why GNUN is Being Developed
address@hidden Why GNUN Is Being Developed
 
 The GNU Project's website, @uref{http://www.gnu.org}, has become
 considerably large over the years.  Maintaining it requires significant
@@ -124,7 +124,7 @@
 Utilities (@code{gnome-doc-utils}) some years later.
 
 @node Concepts
address@hidden What GNUnited Nations is and Should be
address@hidden What GNUnited Nations Is and Should Be
 
 The basic concept behind GNUN is that localization of HTML articles is
 similar to localization of computer address@hidden, it is
@@ -824,7 +824,7 @@
 This target is invoked once a day by the official GNUN cron job.
 
 @node Main Variables
address@hidden Defining Articles to be Built
address@hidden Defining Articles to Be Built
 @cindex variables
 @cindex gnun.mk
 
@@ -2416,7 +2416,7 @@
 @end table
 
 @node Rules
address@hidden How The Recipes Work
address@hidden How the Recipes Work
 
 Read the source code, then please tell us :-)
 

Index: web-trans.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/web-trans.texi,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -b -r1.37 -r1.38
--- web-trans.texi      4 Dec 2012 16:20:06 -0000       1.37
+++ web-trans.texi      7 Dec 2012 16:39:28 -0000       1.38
@@ -5,7 +5,7 @@
 @settitle GNU Web Translators Manual
 @c FIXME: Would be nice to have it in the format `%:b %:d, %:y', but
 @c in English.
address@hidden lastupdate 28.06.2012
address@hidden lastupdate 07.12.2012
 @afourpaper
 @c %**end of header
 
@@ -126,11 +126,11 @@
 @menu
 * Joining::             How to join a translation team.
 * Submitting::          Submitting a translation when there is no team.
-* Leaving A Team::      Leave when you have to.
+* Leaving a Team::      Leave when you have to.
 @end menu
 
 @node Joining
address@hidden Joining A Team
address@hidden Joining a Team
 
 To join a team, please first look at the existing teams at
 
@uref{http://www.gnu.org/@/server/@/standards/@/README.translations.html#TranslationsUnderway}.
@@ -188,7 +188,7 @@
 @pxref{Translation Tips}.
 
 @node Submitting
address@hidden How To Submit a Translation
address@hidden How to Submit a Translation
 
 Everyone can still submit translations even if there is no translation
 team formed.  There are two ways to do that---following the existing
@@ -202,7 +202,7 @@
 @end menu
 
 @node Submitting as PO
address@hidden How To Submit a Translation in PO Format
address@hidden How to Submit a Translation in PO Format
 
 All address@hidden really, but the goal is to maintain
 all of them.} are maintained via GNUN (see
@@ -283,7 +283,7 @@
 complete the PO file header.
 
 @node Submitting as Plain Text
address@hidden How To Submit a Translation as Plain Text
address@hidden How to Submit a Translation as Plain Text
 
 If you feel the procedure described in the previous section is too
 burdensome and unfeasible for you to follow, you can still submit a
@@ -349,8 +349,8 @@
 check for any errors or omissions that may have resulted from the
 conversion process, and report them back.
 
address@hidden Leaving A Team
address@hidden Leaving A Team
address@hidden Leaving a Team
address@hidden Leaving a Team
 
 When you realize that you don't have time or can't devote sufficient
 resources to perform the tasks anymore, it is prudent to inform the
@@ -386,7 +386,7 @@
 @end menu
 
 @node New Team
address@hidden How To Form A New Team
address@hidden How to Form a New Team
 
 Establishing a new team is not hard, but a certain procedure ought to be
 followed.  The most important thing to realize is that this is somewhat
@@ -574,7 +574,7 @@
 willing to continue their involvement in the team.
 
 @node Managing
address@hidden The Gentle Art of Managing A Translation Team
address@hidden The Gentle Art of Managing a Translation Team
 
 It is not our ambition to describe all activities involved in managing a
 team---it's very likely that you will encounter new problems, take care
@@ -641,7 +641,7 @@
 @end menu
 
 @node Tracking Tasks
address@hidden How To Track Tasks and Bugs Using Savannah
address@hidden How to Track Tasks and Bugs Using Savannah
 
 The team leader has to make sure that prospective translations are
 reviewed, that they do not contain obvious errors and/or confusing
@@ -731,7 +731,7 @@
 details.
 
 @node Unreviewed Translations
address@hidden How To Proceed With Unreviewed Translations
address@hidden How to Proceed with Unreviewed Translations
 
 Sometimes a translation (typically your own) is not reviewed by anyone
 else for a fairly long time.  This is unfortunate, but there is no
@@ -746,7 +746,7 @@
 You may also add a comment to the PO file.
 
 @node Commits
address@hidden CVS Commits And Best Practices
address@hidden CVS Commits and Best Practices
 
 As all team leaders have write access to the CVS repository of the
 @samp{www} project, this technically means that they are able to modify
@@ -915,7 +915,7 @@
 @samp{View Members}.
 
 @node Savannah Homepage
address@hidden Homepage of The Team
address@hidden Homepage of the Team
 
 Every Savannah project has a Web repository, which is, for technical and
 historical reasons, only CVS.  By default it is mapped to
@@ -1082,7 +1082,7 @@
 repository.
 
 @node Co-leaders
address@hidden Promoting Members As Co-leaders
address@hidden Promoting Members as Co-leaders
 
 When the team grows large and it becomes hard for a single person to
 manage, there is no problem to add another (or even another two) people
@@ -1155,7 +1155,7 @@
 please send it to @email{web-translators@@gnu.org}.
 
 @node Stepping Down
address@hidden How To Retire Painlessly
address@hidden How to Retire Painlessly
 
 When you feel you don't have the energy to manage the team successfully,
 or perhaps you start losing motivation, please inform
@@ -1176,7 +1176,7 @@
 hopefully.
 
 @node Translation Tips
address@hidden Details About The Translation Process
address@hidden Details about the Translation Process
 
 The purpose of this chapter is to summarize some odd and not so obvious
 details about specific parts of the gnu.org website.  Most of them
@@ -1199,7 +1199,7 @@
 @end menu
 
 @node Migrating
address@hidden Migration To The New Style
address@hidden Migration to the New Style
 
 Migration to the new style should be straightforward, and this is one of
 the problems GNUN set out to solve.  If you have to migrate old-style
@@ -1355,7 +1355,7 @@
 Variables, , , gnun, The GNUnited Nations Manual}.
 
 @node CSS
address@hidden How To Use Custom CSS
address@hidden How to Use Custom CSS
 
 The CSS file @file{layout.css} gets included (with three other CSS files)
 in almost all the English articles through
@@ -1411,7 +1411,7 @@
 @end menu
 
 @node topbanner
address@hidden Localizing The @file{topbanner} Image
address@hidden Localizing the @file{topbanner} Image
 
 If you'd like the nice gnu image to be localized (i.e. ``GNU Operating
 System'' to appear in your native language, here are the steps:
@@ -1477,7 +1477,7 @@
 @email{webmasters@@gnu.org} as well, precisely describing the problem.
 
 @node Priorities
address@hidden What To Translate
address@hidden What to Translate
 
 The article
 @uref{http://www.gnu.org/@/server/@/standards/@/translations/@/priorities.html}
@@ -1539,7 +1539,7 @@
 @end table
 
 @node Capitalization
address@hidden When To CAPITALIZE
address@hidden When to CAPITALIZE
 
 The English language has some rules for capitalization of titles,
 chapters, acronym expansions and the like.  These rules are neither
@@ -1631,7 +1631,7 @@
 This is a very important topic, not yet covered by this manual.
 
 @node Summary
address@hidden Overview Of The Translation Process
address@hidden Overview of the Translation Process
 
 In general, it is expected that all participants in the translation
 process apply common sense for all of the decisions (important or not)