[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Pavel Kharitonov
Subject: trans-coord/gnun/server/gnun doc/gnun.texi doc/...
Date: Tue, 27 Sep 2016 08:47:30 +0000 (UTC)

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Pavel Kharitonov <ineiev>       16/09/27 08:47:30

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

Log message:
        * doc/gnun.texi (Sorting Lists): Amend documentation.
        * doc/web-trans.texi (English Pages): New node.


Index: doc/gnun.texi
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/gnun.texi,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -b -r1.107 -r1.108
--- doc/gnun.texi       8 Jul 2016 15:57:23 -0000       1.107
+++ doc/gnun.texi       27 Sep 2016 08:47:30 -0000      1.108
@@ -2073,6 +2073,10 @@
 When extracting the keys, all HTML tags are removed, leading and
 trailing whitespace is trimmed.
+Since the items are reordered in translations, webmasters should
+carefully choose places for the separators: reordering shouldn't break
+the page.
 The translators can modify the sorting order using HTML comments
 if needed.  For example, let the English text say
@@ -2096,6 +2100,26 @@
 Now the item sorts like @samp{boer afrikaans}. 
+Additional care should be taken when the items have a separator like
+A |
+B |
+Y |
+<!-- GNUN-SORT-STOP -->
address@hidden example
+Note that the last item has no separator (@samp{|}).  When
+translating, make sure that the item to be last @emph{in your
+translation} has no separator, and all other items have it.
 @node Internals
 @chapter Unexciting Information for GNUN's Operation

Index: doc/web-trans.texi
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/web-trans.texi,v
retrieving revision 1.73
retrieving revision 1.74
diff -u -b -r1.73 -r1.74
--- doc/web-trans.texi  29 Jun 2016 15:54:56 -0000      1.73
+++ doc/web-trans.texi  27 Sep 2016 08:47:30 -0000      1.74
@@ -1202,14 +1202,15 @@
 * Updating::            Keeping translations current is a priority.
 * Terminology::         Dealing with terminology issues.
 * Capitalization::      To CAPITALIZE or not?
+* English Pages::       Fixing bugs on original pages.
 * Internal Links::      How to handle links to articles.
 * Distribution Terms::  Translating distribution terms.
 * Copyright Notices::   How not to translate copyright notices.
 * PO Editors::          Working with PO files.
 * Mailing Lists::       Summary of mailing lists.
-* Savannah Projects::   Projects membership.
+* Savannah Projects::   Project membership.
 * SSI::                 Overview of files included via SSI.
-* Technical pages::     Other files you may want to translate.
+* Technical Pages::     Other files you may want to translate.
 * CSS::                 General advice how to use CSS.
 * Migrating::           How to migrate to the new style.
 @end menu
@@ -1363,6 +1364,41 @@
 @address@hidden them as @samp{fran@,{c}ais} or
 @address@hidden, respectively.
address@hidden English Pages
address@hidden Fixing Bugs on Original Pages
+GNU webmasters proofread the texts before posting them and fix
+the bugs reported by visitors, but occasionally some
+mistakes do slip into the pages.  Translators are probably the people
+who read the pages most carefully, so it's them who are likely to find
+those mistakes first of all.
+There is a trend for translators to fix the bugs in their translation
+instead of the original page.  This is understandable: you have to
+contact additional people (webmasters) in order to fix it on the
+English page, so it's easier just to make the translation.  However,
+there are reasons why you shouldn't leave bugs on the English pages:
+The text may not be wrong, but you misunderstand it. (This, in turn,
+may mean that the text should be reworded to make it unambiguous.)
+It's as important to have the English version correct as your
+Some mistakes may propagate to translations in other languages.  Also,
+when the page changes, the translators have to update their
+translations, so the earlier you fix the bugs, the fewer people will
+have to update their translations.
address@hidden itemize
+The bugs are reported to @email{}; if you are
+a team leader, you can also discuss the issues on}.
 @node Internal Links
 @section How to Handle Internal Links
@@ -1654,7 +1690,7 @@
 @pxref{Savannah Mailing Lists}.
 @node Savannah Projects
address@hidden Savannah Projects Membership
address@hidden Savannah Project Membership
 @cindex Savannah projects
 Participants in the translation process normally have to be
@@ -1846,8 +1882,8 @@
 English files change; the @code{GRACE} variable has no effect on them.
 @xref{Runtime Variables, , , gnun, The GNUnited Nations Manual}.
address@hidden Technical pages
address@hidden Technical pages
address@hidden Technical Pages
address@hidden Technical Pages
 @cindex technical pages

Index: ChangeLog
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/ChangeLog,v
retrieving revision 1.450
retrieving revision 1.451
diff -u -b -r1.450 -r1.451
--- ChangeLog   17 Sep 2016 09:25:45 -0000      1.450
+++ ChangeLog   27 Sep 2016 08:47:30 -0000      1.451
@@ -1,3 +1,8 @@
+2016-09-27  Pavel Kharitonov  <address@hidden>
+       * doc/gnun.texi (Sorting Lists): Amend documentation.
+       * doc/web-trans.texi (English Pages): New node.
 2016-09-17  Pavel Kharitonov  <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]