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

[Pavel Kharitonov]

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Pavel Kharitonov <ineiev>       14/06/29 09:03:24

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

Log message:
        * doc/web-trans.texi (Introduction): Add a reference to
        `Translation Process'.
        (PO Files): Rename to `PO Editors'.
        (Submitting as PO): Adjust the reference to `PO Editors'.
        (RTL): Minor rewording.
        (Translation Process): Change order of sections.
        * doc/gnun.texi (PO Files): Adjust the reference to
        '(web-trans)PO Editors'.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/ChangeLog?cvsroot=trans-coord&r1=1.420&r2=1.421
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/gnun.texi?cvsroot=trans-coord&r1=1.101&r2=1.102
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/web-trans.texi?cvsroot=trans-coord&r1=1.64&r2=1.65

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/ChangeLog,v
retrieving revision 1.420
retrieving revision 1.421
diff -u -b -r1.420 -r1.421
--- ChangeLog   28 Jun 2014 05:57:15 -0000      1.420
+++ ChangeLog   29 Jun 2014 09:03:23 -0000      1.421
@@ -1,3 +1,14 @@
+2014-06-29  Pavel Kharitonov  <address@hidden>
+
+       * doc/web-trans.texi (Introduction): Add a reference to
+       `Translation Process'.
+       (PO Files): Rename to `PO Editors'.
+       (Submitting as PO): Adjust the reference to `PO Editors'.
+       (RTL): Minor rewording.
+       (Translation Process): Change order of sections.
+       * doc/gnun.texi (PO Files): Adjust the reference to
+       '(web-trans)PO Editors'.
+
 2014-06-28  Pavel Kharitonov  <address@hidden>
 
        * GNUmakefile (mark-outdated): Insert SSI variables

Index: doc/gnun.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/gnun.texi,v
retrieving revision 1.101
retrieving revision 1.102
diff -u -b -r1.101 -r1.102
--- doc/gnun.texi       28 Jun 2014 05:43:16 -0000      1.101
+++ doc/gnun.texi       29 Jun 2014 09:03:23 -0000      1.102
@@ -1407,8 +1407,8 @@
 @chapter Working with PO Files
 
 This section provides technical details about working with PO files.
-For general information about PO editors, @pxref{PO Files, ,
-Working with PO Files, web-trans, GNU Web Translators Manual}.
+For general information about PO editors, @pxref{PO Editors, ,
+Editing PO Files, web-trans, GNU Web Translators Manual}.
 
 @menu
 * New Translation::     How to start a new translation.

Index: doc/web-trans.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/web-trans.texi,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -b -r1.64 -r1.65
--- doc/web-trans.texi  27 Jun 2014 16:05:05 -0000      1.64
+++ doc/web-trans.texi  29 Jun 2014 09:03:24 -0000      1.65
@@ -102,6 +102,11 @@
 The manual is organized in chapters that follow the
 organizational structure of the whole translation project.
 
+For the issues common for all translators,
address@hidden Process}. The sections of that chapter are sorted
+so that those interesting for less involved people (like occasional
+contributors) come first; the technical details tend to be at the end.
+
 If you wish to join a translation team or contribute a translation or
 two, @pxref{Members}.  If your intention is to form a translation team,
 @pxref{Leaders}.
@@ -251,7 +256,7 @@
 create an empty @address@hidden@var{lang}.po} file and then
 translate all messages with a PO editor.  @xref{New Translation, , ,
 gnun, The GNUnited Nations Manual}.  For an almost complete list of PO
-editors, @pxref{PO Files}.
+editors, @pxref{PO Editors}.
 
 @item
 When you are pleased with the translation, check that the PO file is
@@ -1195,15 +1200,15 @@
 @menu
 * Priorities::          What to translate as a priority.
 * Updating::            Keeping translations current is a priority.
+* Terminology::         Dealing with terminology issues.
 * Capitalization::      To CAPITALIZE or not?
 * Distribution Terms::  Translating distribution terms.
 * Copyright Notices::   How not to translate copyright notices.
-* Terminology::         Dealing with terminology issues.
+* PO Editors::          Working with PO files.
 * Mailing Lists::       Summary of mailing lists.
 * Savannah Projects::   Projects membership.
-* PO Files::            Working with PO files.
+* SSI::                 Overview of files included via SSI.
 * Migrating::           How to migrate to the new style.
-* SSI::                 Overview of SSI #include directives.
 * CSS::                 General advice how to use CSS.
 @end menu
 
@@ -1317,6 +1322,16 @@
 
 @end itemize
 
address@hidden Terminology
address@hidden Language-specific Terminology
+
+This is a very important topic, not yet covered by this manual.
+
address@hidden Translations README
+Some tips are given in
address@hidden://www.gnu.org/@/server/@/standards/@/README.translations.html,
+Translations README}.
+
 @node Capitalization
 @section When to CAPITALIZE
 
@@ -1424,15 +1439,100 @@
 @pxref{Copyright Notices, , , maintain, Information for maintainers of
 GNU software}.
 
address@hidden Terminology
address@hidden Language-specific Terminology
address@hidden PO Editors
address@hidden Editing PO Files
address@hidden PO, editing
 
-This is a very important topic, not yet covered by this manual.
+We anticipate that some gnu.org translators will find this format odd
+or inconvenient, if they never happened to work with PO files
address@hidden detailed information about editing
+PO files, @pxref{PO Files, , Working with PO Files, gnun,
+The GNUnited Nations Manual}.}.
+Don't worry, you will soon get accustomed to it.  It is the
+established format for translations in the Free World, and if you 
+have any problems, other translators will help you.
 
address@hidden Translations README
-Some tips are given in
address@hidden://www.gnu.org/@/server/@/standards/@/README.translations.html,
-Translations README}.
+The most efficient way to edit a PO file is using a specialized PO
+editor, because each of them represents and treats gettext messages in
+a consistent and predictable way.  It is possible to edit a PO file
+with an ordinary plain text editor, but extra effort would be
+necessary to make the result valid.
+
address@hidden SaaSS
+Note that recent versions of some PO editors (both offline
+and web-based) offer access to various translation services that
+do machine translation for their users.  Using a machine translation
+service is a clear example of SaaSS (see
address@hidden://www.gnu.org/philosophy/who-does-that-server-really-serve.html,
+Who does That Server Really Serve?}),
+so please don't use such editors unless they only submit requests
+to your (or GNU project's) own servers.
+
+Here is a list of widely used PO editors we can recommend:
+
address@hidden
address@hidden PO editors
address@hidden
address@hidden Emacs
+PO mode.  We recommend using GNU Emacs in PO mode, because Emacs is
+the program that is suitable for performing any task when it comes to
+maintaining the GNU Project's website.  Provided that you have GNU
+gettext installed, any @file{.po} file you visit should automatically
+switch to PO mode.  You can enable/disable it with @code{M-x po-mode
address@hidden  On some GNU/Linux distros such as gNewSense, PO mode is
+available in a separate package, @code{gettext-el}.
address@hidden Mode, Emacs's PO File Editor, , gettext, GNU gettext tools}.
+
address@hidden
address@hidden Gtranslator
+Gtranslator---the GNOME PO editor.  See
address@hidden://projects.gnome.org/@/gtranslator/}.
+
address@hidden
+Lokalize---the KDE 4 editor.  See
address@hidden://userbase.kde.org/@/Lokalize}.
+
address@hidden
+KBabel---the KDE 3 editor.  No longer supported, but might be
+available on some old systems.
+
address@hidden
+Poedit---another popular editor that is based on the @code{wxWidgets}
+graphical toolkit.  See @uref{http://www.poedit.net}.
+
address@hidden
address@hidden @heresy
address@hidden Please forgive them, they don't know what they are doing...
+po.vim---ftplugin for the Vim editor.  The best option for people who
+use Vim as their editor.  See
address@hidden://www.vim.org/@/scripts/@/script.php?script_id=2530}.
address@hidden @end heresy
+
address@hidden
+GNU instance of Pootle, a web-based editor.
address@hidden itemize
+
address@hidden Web-based Systems
+
address@hidden web-based editing
address@hidden Pootle
+If your team would like to use a web-based editor, we recommend using
+the @uref{https://chapters.gnu.org/pootle/, official Pootle server of
+the GNU project}.  We make sure that working with it will not
+compromise your freedom via nonfree JavaScript or
address@hidden://www.gnu.org/philosophy/who-does-that-server-really-serve.html,
+SaaSS}.  If you decide to use our server, please contact GNU Web
+Translation Managers to register your team.
+
address@hidden previewing web pages
address@hidden web pages, previewing 
+Also, that Pootle server has a simple facility to preview your
+translations as they will appear on www.gnu.org.  In order to test
+a page, log in the server and visit
address@hidden://chapters.gnu.org/pootle/gnun/test.html}.  That page
+contains a menu to upload a PO file; then the server will generate
+the translation and show you the build log (including errors), and the
+generated web page (when the build is successful).
 
 @node Mailing Lists
 @section Related Mailing Lists
@@ -1547,115 +1647,6 @@
 for team's internal reasons.
 @end table
 
address@hidden PO Files
address@hidden Working with PO Files
address@hidden PO, editing
-
-We anticipate that some gnu.org translators will find this format odd
-or inconvenient, if they never happened to work with PO files
address@hidden detailed information about editing
-PO files, @pxref{PO Files, , Working with PO Files, gnun,
-The GNUnited Nations Manual}.}.
-Don't worry, you will soon get accustomed to it.  It is the
-established format for translations in the Free World, and if you 
-have any problems, other translators will help you.
-
-The most efficient way to edit a PO file is using a specialized PO
-editor, because each of them represents and treats gettext messages in
-a consistent and predictable way.  It is possible to edit a PO file
-with an ordinary plain text editor, but extra effort would be
-necessary to make the result valid.
-
address@hidden SaaSS
-Note that recent versions of some PO editors (both offline
-and web-based) offer access to various translation services that
-do machine translation for their users.  Using a machine translation
-service is a clear example of SaaSS (see
address@hidden://www.gnu.org/philosophy/who-does-that-server-really-serve.html,
-Who does That Server Really Serve?}),
-so please don't use such editors unless they only submit requests
-to your (or GNU project's) own servers.
-
-Here is a list of widely used PO editors we can recommend:
-
address@hidden
address@hidden PO editors
address@hidden
address@hidden Emacs
-PO mode.  We recommend using GNU Emacs in PO mode, because Emacs is
-the program that is suitable for performing any task when it comes to
-maintaining the GNU Project's website.  Provided that you have GNU
-gettext installed, any @file{.po} file you visit should automatically
-switch to PO mode.  You can enable/disable it with @code{M-x po-mode
address@hidden  On some GNU/Linux distros such as gNewSense, PO mode is
-available in a separate package, @code{gettext-el}.
address@hidden Mode, Emacs's PO File Editor, , gettext, GNU gettext tools}.
-
address@hidden
address@hidden Gtranslator
-Gtranslator---the GNOME PO editor.  See
address@hidden://projects.gnome.org/@/gtranslator/}.
-
address@hidden
-Lokalize---the KDE 4 editor.  See
address@hidden://userbase.kde.org/@/Lokalize}.
-
address@hidden
-KBabel---the KDE 3 editor.  No longer supported, but might be
-available on some old systems.
-
address@hidden
-Poedit---another popular editor that is based on the @code{wxWidgets}
-graphical toolkit.  See @uref{http://www.poedit.net}.
-
address@hidden
address@hidden @heresy
address@hidden Please forgive them, they don't know what they are doing...
-po.vim---ftplugin for the Vim editor.  The best option for people who
-use Vim as their editor.  See
address@hidden://www.vim.org/@/scripts/@/script.php?script_id=2530}.
address@hidden @end heresy
-
address@hidden
-GNU instance of Pootle, a web-based editor.
address@hidden itemize
-
address@hidden Web-based Systems
-
address@hidden web-based editing
address@hidden Pootle
-If your team would like to use a web-based editor, we recommend using
-the @uref{https://chapters.gnu.org/pootle/, official Pootle server of
-the GNU project}.  We make sure that working with it will not
-compromise your freedom via nonfree JavaScript or
address@hidden://www.gnu.org/philosophy/who-does-that-server-really-serve.html,
-SaaSS}.  If you decide to use our server, please contact GNU Web
-Translation Managers to register your team.
-
address@hidden previewing web pages
address@hidden web pages, previewing 
-Also, that Pootle server has a simple facility to preview your
-translations as they will appear on www.gnu.org.  In order to test
-a page, log in the server and visit
address@hidden://chapters.gnu.org/pootle/gnun/test.html}.  That page
-contains a menu to upload a PO file; then the server will generate
-the translation and show you the build log (including errors), and the
-generated web page (when the build is successful).
-
address@hidden Migrating
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
-translations, @pxref{Migrating, , , gnun, The GNUnited Nations Manual}.
-If the old translation is HTML 2.0 (or 3.2), you still have to take care
-about the inner markup.  Overall, it is substantially easier than doing
-all of it manually.
-
-Subsequent migrations to newer HTML standards and newer look and feel
-of the website are supposed to happen semi-automatically, although
-this manual will be updated as needed.
-
 @node SSI
 @section Summary of SSI @code{#include}s
 
@@ -1815,6 +1806,20 @@
 English files change; the @code{GRACE} variable has no effect on them.
 @xref{Runtime Variables, , , gnun, The GNUnited Nations Manual}.
 
address@hidden Migrating
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
+translations, @pxref{Migrating, , , gnun, The GNUnited Nations Manual}.
+If the old translation is HTML 2.0 (or 3.2), you still have to take care
+about the inner markup.  Overall, it is substantially easier than doing
+all of it manually.
+
+Subsequent migrations to newer HTML standards and newer look and feel
+of the website are supposed to happen semi-automatically, although
+this manual will be updated as needed.
+
 @node CSS
 @section How to Use Custom CSS
 
@@ -1878,9 +1883,10 @@
 @subsection Specific Issues Related to RTL
 
 @cindex right-to-left languages
-Unfortunately, the @uref{http://gnu.org} website does not have excellent
-support for RTL (right-to-left) languages, although best efforts are
-made.  If your language is in this category, make sure to:
+Unfortunately, the @uref{https://www.gnu.org} website does not have
+excellent support for languages using right-to-left scripts,
+although best efforts are made.  If your language is in this
+category, make sure to:
 
 @itemize
 @item
@@ -1904,7 +1910,6 @@
 your language and require a general solution, write to
 @email{webmasters@@gnu.org} as well, precisely describing the problem.
 
-
 @node Copying This Manual
 @appendix GNU Free Documentation License