trans-coord-devel
[Top][All Lists]
Advanced

[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, 04 Dec 2012 16:20:08 +0000

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Pavel Kharitonov <ineiev>       12/12/04 16:20:08

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

Log message:
        Minor updates of documentation.
        
        * doc/gnun.texi: Swap `Copying This Manual' with `Index' to
        make their order consistent with the menu.
        (Disadvantages): Update documented cycles:
        GNUN currently runs twice an hour.
        (no-grace-items): Document that in fact it is not used in
        GNUN cron jobs.
        (generic.LANG.html) <example>: Teams' homepages are
        .../translations/foo rather than .../translations/www-foo.
        (GNUmakefile.team Targets): Make new node and subsubsection
        from existing unnumberedsubsubsec.
        (PO Files and Team) <menu>: Add `GNUmakefile.team Targets'.
        * doc/web-trans.texi (Introduction): Mention that
        `co-ordinator' and `team leader' are equivalent terms.
        (Joining): Rephrase the reference to mailing lists as a requirement.
        (Submitting as PO): Update times (s/As of/Since/ September
        2008).  Explain how to get POTs and POs from website via
        .../po/article.pot and .../po/article.LANG.po URLs.  Replace
        the list of templates with a reference to `extra-templates'.
        (Submitting as Plain Text): Update the example.
        (New Team): Fix a typo.  Add a footnote with an estimated
        amount of work.  Remove ISO-639 example: www.gnu.org
        Multiviews-related redirections won't work with 3-letter
        codes.  Replace `characters' with `letters' in `Do not use
        HTML entities for non-ASCII characters': it still may make
        sense to use HTML entities to distinguish dashes, spaces and
        so on.  Document that new leader also becomes an admin of
        team's mailing lists.  Remove outdated comments about www-discuss.
        (Members, Tracking Tasks, Savannah Support, Priorities):
        (Savannah Projects): Minor refinements.
        (Commits): Remove reference to `other projects'; it may
        confuse the reader into thinking that all Savannah projects
        are write-accessible for co-ordinators.  Replace "your
        project's Sources repository" with "your team's
        repositories": historically, some teams keep their files in
        their Web repository.  Add an xref to GCS.  Update the note
        on the committers using incompatible nonfree systems, since
        there is no recent evidence that there are any.
        (Savannah Homepage): Don't say that deprecated pages are moved
        to `trans-coord' repository.
        (Priorities): Mention autogenerated reports in GNUN Web repository.
        (Mailing Lists): Retire address@hidden

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/gnun.texi?cvsroot=trans-coord&r1=1.66&r2=1.67
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/web-trans.texi?cvsroot=trans-coord&r1=1.36&r2=1.37
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/ChangeLog?cvsroot=trans-coord&r1=1.309&r2=1.310

Patches:
Index: doc/gnun.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/gnun.texi,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- doc/gnun.texi       26 Nov 2012 14:13:10 -0000      1.66
+++ doc/gnun.texi       4 Dec 2012 16:20:06 -0000       1.67
@@ -348,14 +348,11 @@
 
 @itemize
 @item
-The official build is invoked thrice address@hidden ``no-grace''
-items are rebuilt hourly.}, because doing it more often
-will potentially generate more messages to the mailing list in the form
-of commit notifications.  This has its drawback, since translators have
-to wait 8 hours until their PO files are updated, and another period
-for the @address@hidden articles to get generated, after they
-commit the updated POs.  Additionally, any errors interrupt the build so
-they have to be fixed before the next articles are processed.
+There is no easy way to preview the translations.  The official build
+is invoked twice an hour, because doing it much more often is not
+feasible with current build server hardware.  Additionally, any errors
+interrupt the build so they have to be fixed before the next articles
+are processed.
 @end itemize
 
 @node Usage
@@ -662,8 +659,8 @@
 server templates, gnunews, and all articles defined in the variable
 @code{no-grace-articles} (@pxref{GRACE,,grace period}).
 
-This target can be rebuilt more often than @code{all}; it is invoked
-hourly by the official GNUN cron job.
+This target can be rebuilt more often than @code{all}; however, it is
+currently not used.
 
 @node update-localized-URLs
 @subsubsection The @code{update-localized-URLs} Target
@@ -1502,7 +1499,7 @@
 
 @example
 <p>To join the Fooish translation team, see <a
-href="http://gnu.org/@/server/@/standards/@/translations/@/www-foo";>the
+href="http://gnu.org/@/server/@/standards/@/translations/@/foo";>the
 Foo team homepage</a>.</p>
 @end example
 
@@ -1648,6 +1645,7 @@
 
 @menu
 * GNUmakefile.team Variables::
+* GNUmakefile.team Targets::
 * GNUmakefile.team and Cron::
 @end menu
 
@@ -1696,7 +1694,8 @@
 purpose.
 @end table
 
address@hidden Targets in @file{GNUmakefile.team}
address@hidden GNUmakefile.team Targets
address@hidden Targets in @file{GNUmakefile.team}
 
 @table @code
 @item update
@@ -2434,16 +2433,16 @@
 do not hesitate to report them at @email{bug-gnun@@gnu.org} or
 @url{https://savannah.gnu.org/@/bugs/@/?group=gnun}.
 
address@hidden Copying This Manual
address@hidden GNU Free Documentation License
-
address@hidden fdl.texi
-
 @node Index
 @unnumbered Index
 
 @printindex cp
 
address@hidden Copying This Manual
address@hidden GNU Free Documentation License
+
address@hidden fdl.texi
+
 @bye
 
 Local Variables:

Index: doc/web-trans.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/web-trans.texi,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -b -r1.36 -r1.37
--- doc/web-trans.texi  26 Nov 2012 14:13:13 -0000      1.36
+++ doc/web-trans.texi  4 Dec 2012 16:20:06 -0000       1.37
@@ -99,7 +99,8 @@
 describe the fundamental values of the free software movement.
 
 Translators of the @uref{http://gnu.org} website are organized in
-language teams.  Each team has one or more co-ordinators, who are
+language teams.  Each team has one or more co-ordinators (a.k.a
+leaders), who are
 responsible for the respective team.  The co-ordinators participate in
 the Savannah @samp{trans-coord} organizational project, which is managed
 by the GNU Web Translation Managers.  The manual is organized in
@@ -160,7 +161,7 @@
 has its own project, named @address@hidden, with the project
 page being
 @indicateurl{https://savannah.gnu.org/@/projects/@/address@hidden
-Usually teams have mailing lists, typically in the form
+All teams should have mailing lists, typically in the form
 @address@hidden@dots{}@@gnu.org}.  Some teams have homepages,
 @indicateurl{http://gnu.org/@/server/@/standards/@/translations/@var{lang}}
 with additional contact details and procedures for team members.
@@ -210,7 +211,7 @@
 lagging behind the original.  @xref{Advantages, , , gnun, The GNUnited
 Nations Manual}.
 
-As of September 2008 all new translations at gnu.org are installed in
+Since September 2008 all new translations at gnu.org are installed in
 @file{.po} format, and the @file{.html} is generated automatically.
 Here are the steps to produce and submit such a translation:
 
@@ -232,6 +233,17 @@
 This command will fetch only the @file{/gnu} directory---in other words,
 all articles at @uref{http://gnu.org/gnu}.
 
+You can also fetch single files by their respective URLs.  For example,
+the URL for the template file of
address@hidden://www.gnu.org/@/philosophy/@/free-sw.html} is
address@hidden://www.gnu.org/@/philosophy/@/po/@/free-sw.pot}; the URL for
+its @var{lang} PO file (when available) is
address@hidden://www.gnu.org/@/philosophy/@/po/@/address@hidden:
+
address@hidden
+wget http://www.gnu.org/philosophy/po/free-sw.pot
address@hidden example
+
 @item
 Assuming you already know the article you want to translate, you have to
 create an empty @address@hidden@var{lang}.po} file and then
@@ -246,22 +258,17 @@
 ability) the translation and will install it in the repository.
 
 @item
-In order GNUN to be able to generate (and subsequently update) a
-gettextized translation, the language should have the server templates
+In order GNUN to be able to generate (and subsequently update) a fully
+translated page, the language should have the server templates
 available as PO files.  These templates are short, and translating them
 shouldn't take much time.  If the language code is present in the
 @code{TEMPLATE_LINGUAS} variable at @file{server/gnun/gnun.mk}, then you
-don't have to do anything.  If it is not, the required files are
address@hidden/@/po/@/address@hidden,
address@hidden/@/po/@/address@hidden,
address@hidden/@/po/@/address@hidden and
address@hidden/@/po/@/address@hidden can translate and
+don't have to do anything.  If it is not, the required files
+are defined via the @code{extra-templates} variable
+in @file{server/@/gnun/@/gnun.mk}---you can translate and
 submit them in the usual way, together with the translation of the
 essay.
 
-Additional templates are defined via the @code{extra-templates} variable
-in @file{server/@/gnun/@/gnun.mk}.
-
 If you don't want to translate the templates for whatever reason---do
 not worry, the web-translators will install empty templates (which means
 the English strings will be used).
@@ -300,12 +307,16 @@
 that would be:
 
 @example
-The Free Software Definition - GNU Project - Free Software Foundation (FSF)
+What is free software? - GNU Project - Free Software Foundation (FSF)
+
+What is free software?
 
-We maintain this free software address@hidden
+The Free Software Definition
+
+The free software definition address@hidden
 @dots{}
address@hidden you would like to review the complete list of changes, you can
-do so on our cvsweb interface.
address@hidden can review the complete list of changes to the page through
+the cvsweb interface.
 @end example
 
 Since web-translators do not speak all languages, it is essential to
@@ -383,9 +394,9 @@
 and technical skills, and devotion.  The only ``bonus'' team leaders
 have is more work and more responsibilities.
 
-You should read and @emph{all} the documentation related to the
-translation process at the very least all important philosophy-related
-articles listed on
+You should read @emph{all} the documentation related to the
+translation process and at the very least all important
+philosophy-related articles listed on
 @uref{http://gnu.org/@/server/@/standards/@/README.translations.html}
 and
 @uref{http://gnu.org/@/server/@/standards/@/translations/@/priorities.html}
@@ -415,7 +426,9 @@
 mapped to the URL locations, more or less.  Take a look at the most
 important materials to translate under @file{/philosophy}, @file{/gnu},
 @file{/distros}, @file{/copyleft} and @file{/licenses} directories just
-to get a rough estimate about the amount of work involved.  If you are
+to get a rough estimate about the amount of work address@hidden of
+December 2012, there are over 250 files to translate in ``important''
+directories; their volume is about 3.5 MB.}.  If you are
 still not scared and determined to go on further, excellent.
 
 As you have probably observed, every directory that contains
@@ -452,8 +465,7 @@
 @item
 The language code (@var{lang}) should be the ISO 639-1 code of the
 language, for example @samp{hy} for Armenian or @samp{el} for Greek.  If
-there is no such code, use the ISO 639-2 one---e.g. @samp{mai} for
-Maithili.  If the language is a variant such as Brazilian Portuguese or
+the language is a variant such as Brazilian Portuguese or
 Simplified Chinese, use small caps and a address@hidden and
 @samp{zh-cn} instead of @samp{pt_BR} and @samp{zh_CN}.
 
@@ -462,7 +474,7 @@
 documented.
 
 @item
-Do not use HTML entities for non-ASCII characters as in the English
+Do not use HTML entities for non-ASCII letters as in the English
 original.  They are harder to type and read.  So, if there is
 @samp{&uuml;} and this is a character from the alphabet of your
 language, just write it as @samp{@"u} directly.
@@ -504,7 +516,8 @@
 a new translation project at Savannah.  The project name should be
 @address@hidden where @var{lang} is, unsurprisingly, the language
 code.  If such a project already exists, this step will be skipped and
-you'll be made an administrator of the project.  To register the
+you'll be made an administrator of the project and its mailing lists.
+To register the
 project, go to @uref{https://savannah.gnu.org/@/register/} and make sure
 you fill in the required fields.  The ``Group type'' should be
 @samp{www.gnu.org translation team}, and ``Project
@@ -530,12 +543,11 @@
 
 @item
 trans-coord-discuss
+
address@hidden
+www-discuss
 @end itemize
 
-You'll have to request subscription to @samp{www-discuss}
-yourself---this list is managed by the GNU Webmasters, but all team
-leaders are required to subscribe in order to receive important
-site-wide announcements.
 @end enumerate
 
 The whole process should not take more than two weeks or maximum a
@@ -547,7 +559,7 @@
 Applications for new teams are sometimes processed in
 address@hidden general, we try to avoid this and direct all new
 volunteers to the person who is already carrying out the process---this
-is also a verification if she can cooperate easily with others.}---the
+is also a verification if she can co-operate easily with others.}---the
 most suitable candidate is chosen in this case.  This is, undoubtedly,
 based on a subjective judgment made by the Translation Managers, and
 many factors are important.
@@ -701,7 +713,7 @@
 Once the bugs (or at least the important bugs) are fixed, the team
 leader can make the final review and install the translation in the
 official repository, marking the task as @samp{Done}.  Bugs that are not
-resolved should remain opened, naturally.
+resolved should remain open, naturally.
 @end itemize
 
 Of course, teams can choose to manage these things using external
@@ -709,7 +721,7 @@
 Whatever you decide, please make sure that bugs can be reported using
 free software only, and that the software providing that service is
 free.  It makes an extremely bad impression if a reader has to report a
-problem about a gnu.org translation via non-free hosting platforms like
+problem about a gnu.org translation via nonfree hosting platforms like
 SourceForge.
 
 If you use a certain facility (i.e. a bug tracking system) to manage
@@ -738,8 +750,7 @@
 
 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
-every single file in it, and also those of the Web CVS repositories of
-other projects at Savannah.  This vote of confidence should never be
+every single file in it.  This vote of confidence should never be
 abused---the only files team co-ordinators should add/update are those
 relevant to their translation work.  It is OK to fix an obvious typo in
 an original article; for anything else please report to
@@ -773,11 +784,12 @@
 for 5 files about semantically the same change.  Always write commit
 logs in address@hidden advice is applicable for the @samp{www}
 repository only---feel free to write logs in your native language when
-committing in your project's Sources repository.}, providing a short
+committing in your team's repositories.}, providing a short
 description of the change.  If you modify a file that is not an article
 but a script or part of software (such as @file{server/gnun/gnun.mk}),
 it would be nice to follow the GNU Coding Standards and describe the
-change precisely.  For example, do not write:
+change precisely.  @xref{Change Logs, Log Messages, Change Logs,
+standards, The GNU Coding Standards}.  For example, do not write:
 
 @example
 Added support for Nepali.
@@ -810,10 +822,11 @@
 subsequently corrupting the file.  @xref{Substitution Modes, , , cvs,
 Version Management with CVS}.  More importantly, using @option{-kb}
 prevents corruption of the binary when people using CVS clients under
-Windoze checkout, modify the file, and then commit it with messed EOLs.
-(Unfortunately there are still committers using non-free operating
-systems---we cannot dictate what OS people use, but we can at least try
-to prevent damage.)
+infamous OS checkout, modify the file, and then commit it with
+messed ends of address@hidden years ago there still were
+committers using nonfree operating systems---we don't dictate what
+OS people use, but we can at least prevent this technical kind
+of damage.}
 
 Although not absolutely compulsory, it is recommended that every team
 leader subscribes to @email{www-commits@@gnu.org}.  It is useful to
@@ -923,17 +936,14 @@
 For historical reasons, team-specific materials were available in the
 @samp{www} repository, under ad-hoc locations as @file{/spanish},
 @file{/wwwsr}, etc.  These locations are deprecated, and the contents
-will be moved without warning to @file{/graveyard} in the
address@hidden @emph{Sources} repository, following the original
address@hidden layout (that is, if there were any sub-directories, they will
-be retained).
+will be removed without warning.
 
 @node Savannah Support
 @subsubsection Support Tracker
 
 This tracker is supposed to be related to things about the @emph{project
 management} itself, i.e. project members may report here missing
-functionality and/or features that requires the project admin(s)'s
+functionality and/or features that requires the project admin's
 action.  Do not use it for anything else as it quickly becomes
 confusing.  It is OK to disable it if the team is small.
 
@@ -1476,7 +1486,7 @@
 @file{education}, @file{distros},
 @file{copyleft} and @file{licenses} are important.  The others may be
 deferred for a time when a team completes most of the important
-translations, or they can be translated as a ``rest''--in translators'
+translations, or they can be translated as a ``rest''---in translators'
 parlance this means doing something in between which is typically easier
 to handle.
 
@@ -1490,6 +1500,11 @@
 project.  If you want them changed, please write to
 @email{web-translators@@gnu.org}.
 
+GNUN also maintains reports about current status of translations of all
+active teams in @uref{http://www.gnu.org/software/gnun/reports/}.  If
+the page for your team is missing there, please ask
address@hidden@@gnu.org} to add it to the cron job.
+
 It is strongly recommended translation teams to attempt to recruit
 native English speakers in order to improve their translation process.
 Translators sometimes misunderstand English idioms and expressions, and
@@ -1694,15 +1709,6 @@
 repository are also sent to this list.
 
 This is a public list, and @email{bug-gnun@@gnu.org} is an alias.
-
address@hidden trans-coord-logs@@gnu.org
-All build logs from the various GNUN automatic builds are sent to this
-list, so it is not a very pleasant thing to be subscribed, especially if
-you are not interested in GNUN's internals.  However, everyone can use
-the web archives to check the log why a particular article was not built
-at expected.
-
-This is a public list.
 @end table
 
 @node Savannah Projects
@@ -1724,7 +1730,7 @@
 unrelated) process for approving contributors.
 
 @item trans-coord
-An organizational project especially created for coordination and
+An organizational project especially created for co-ordination and
 improvement of the translation process.  All team leaders are required
 to be members, as bugs reported to @email{web-translators@@gnu.org} are
 often redirected to the @samp{trans-coord} @samp{Bugs} tracker.

Index: ChangeLog
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/ChangeLog,v
retrieving revision 1.309
retrieving revision 1.310
diff -u -b -r1.309 -r1.310
--- ChangeLog   3 Dec 2012 14:28:07 -0000       1.309
+++ ChangeLog   4 Dec 2012 16:20:08 -0000       1.310
@@ -1,3 +1,52 @@
+2012-12-04  Pavel Kharitonov  <address@hidden>
+
+       Minor updates of documentation.
+
+       * doc/gnun.texi: Swap `Copying This Manual' with `Index' to
+       make their order consistent with the menu.
+       (Disadvantages): Update documented cycles:
+       GNUN currently runs twice an hour.
+       (no-grace-items): Document that in fact it is not used in
+       GNUN cron jobs.
+       (generic.LANG.html) <example>: Teams' homepages are
+       .../translations/foo rather than .../translations/www-foo.
+       (GNUmakefile.team Targets): Make new node and subsubsection
+       from existing unnumberedsubsubsec.
+       (PO Files and Team) <menu>: Add `GNUmakefile.team Targets'.
+       * doc/web-trans.texi (Introduction): Mention that
+       `co-ordinator' and `team leader' are equivalent terms.
+       (Joining): Rephrase the reference to mailing lists
+       as a requirement.
+       (Submitting as PO): Update times (s/As of/Since/ September
+       2008).  Explain how to get POTs and POs from website via
+       .../po/article.pot and .../po/article.LANG.po URLs.  Replace
+       the list of templates with a reference to `extra-templates'.
+       (Submitting as Plain Text): Update the example.
+       (New Team): Fix a typo.  Add a footnote with an estimated
+       amount of work.  Remove ISO-639 example: www.gnu.org
+       Multiviews-related redirections won't work with 3-letter
+       codes.  Replace `characters' with `letters' in `Do not use
+       HTML entities for non-ASCII characters': it still may make
+       sense to use HTML entities to distinguish dashes, spaces and
+       so on.  Document that new leader also becomes an admin of
+       team's mailing lists.  Remove outdated comments about
+       www-discuss.
+       (Members, Tracking Tasks, Savannah Support, Priorities):
+       (Savannah Projects): Minor refinements.
+       (Commits): Remove reference to `other projects'; it may
+       confuse the reader into thinking that all Savannah projects
+       are write-accessible for co-ordinators.  Replace "your
+       project's Sources repository" with "your team's
+       repositories": historically, some teams keep their files in
+       their Web repository.  Add a xref to GCS.  Update the note
+       on the committers using incompatible nonfree systems, since
+       there is no recent evidence that there are any.
+       (Savannah Homepage): Don't say that deprecated pages are moved
+       to `trans-coord' repository.
+       (Priorities): Mention autogenerated reports in GNUN Web
+       repository.
+       (Mailing Lists): Retire address@hidden
+
 2012-12-03  Pavel Kharitonov  <address@hidden>
 
        * GNUmakefile (compendia/master-translated.$(1).po):



reply via email to

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