[Top][All Lists]

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

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

From: Pavel Kharitonov
Subject: trans-coord/gnun/server/gnun ChangeLog doc/gnun...
Date: Mon, 17 Mar 2014 12:54:08 +0000

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Pavel Kharitonov <ineiev>       14/03/17 12:54:08

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

Log message:
        Minor documentation updates and refinements.
        * doc/gnun.texi: Put `Index' after `Copying This Manual'.
        Use the second argument of `uref' and `url' where appropriate.
        * doc/web-trans.texi: Add `Index'.  Use the second argument
        of `uref' and `url' where appropriate.
        (Web-based Systems): Replace with documentation of the Pootle
        server of the GNU project.
        (Copyright Notices): Request mantaining proper copyright
        notices in translations.
        (Mailing Lists): Don't mention gnunews.  Document
        address@hidden' and address@hidden'.
        (SSI) <server/banner.html>: Update.
        (SSI) <server/generic.html>: Explain that its translations are
        not under GNUN control.
        (SSI) <server/home-pkgblurbs.html, planetfeeds.html>: New entries.
        (CSS): Recommend reporting language-independent issues to webmasters.


Index: ChangeLog
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/ChangeLog,v
retrieving revision 1.404
retrieving revision 1.405
diff -u -b -r1.404 -r1.405
--- ChangeLog   16 Mar 2014 06:28:03 -0000      1.404
+++ ChangeLog   17 Mar 2014 12:54:07 -0000      1.405
@@ -1,4 +1,26 @@
-2014-03-15  Pavel Kharitonov  <address@hidden>
+2014-03-17  Pavel Kharitonov  <address@hidden>
+       Minor documentation updates and refinements.
+       * doc/gnun.texi: Put `Index' after `Copying This Manual'.
+       Use the second argument of `uref' and `url' where appropriate.
+       * doc/web-trans.texi: Add `Index'.  Use the second argument
+       of `uref' and `url' where appropriate.
+       (Web-based Systems): Replace with documentation of the Pootle
+       server of the GNU project.
+       (Copyright Notices): Request mantaining proper copyright
+       notices in translations.
+       (Mailing Lists): Don't mention gnunews.  Document
+       address@hidden' and address@hidden'.
+       (SSI) <server/banner.html>: Update.
+       (SSI) <server/generic.html>: Explain that its translations are
+       not under GNUN control.
+       (SSI) <server/home-pkgblurbs.html, planetfeeds.html>:
+       New entries.
+       (CSS): Recommend reporting language-independent issues to
+       webmasters.
+2014-03-16  Pavel Kharitonov  <address@hidden>
        * (cmp-POs): Fix the function; affects
        the `all', `sync', `notify' and `report' targets.

Index: doc/gnun.texi
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/gnun.texi,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -b -r1.95 -r1.96
--- doc/gnun.texi       15 Mar 2014 07:58:36 -0000      1.95
+++ doc/gnun.texi       17 Mar 2014 12:54:08 -0000      1.96
@@ -61,15 +61,15 @@
 * Internals::           Dive into GNUN.
 * Bugs::                How to report bugs.
-* Index::
 * Copying This Manual:: The GNU Free Documentation License.
+* Index::
 @end menu
 @node Introduction
 @chapter Introduction to GNUnited Nations
 GNUnited Nations (abbreviated GNUN) is a collection of
-scripts that are supposed to make the life of @url{}
+scripts that are supposed to make the life of @url{}
 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
@@ -106,7 +106,7 @@
 @node Overview
 @section Why GNUN Is Being Developed
-The GNU Project's website, @uref{}, has become
+The @uref{, GNU Project's website}, has become
 considerably large over the years.  Maintaining it requires significant
 effort, and sometimes a new web standard is developed faster than the
 time required to migrate all articles to the next widely adopted one.
@@ -150,9 +150,9 @@
 @xref{Introduction, Introduction, , gettext, GNU gettext tools},
 for a basic overview.
 GNUnited Nations fills the gaps to apply this infrastructure to articles
-in @url{} web address@hidden process of converting
+in @url{} web address@hidden process of converting
 HTML to PO and the other way around is performed using po4a (``po for
-anything''), see @uref{}.}
+anything''), see @uref{, PO4A website}.}
 The following diagram summarizes the relation between the files handled
 by GNUN.  It is followed by somewhat detailed explanations, which you
@@ -410,7 +410,8 @@
 deploying the software on a non-GNU machine, probably GNU Make is
 installed and available as @command{gmake} or @command{gnumake}.  If
 not, you should consider installing it, since the build will fail
-otherwise.  See @uref{} for information
+otherwise.  See @uref{,
+GNU Make homepage} for information
 how to download and install GNU Make.
 If you don't specify a target, @command{make} by default builds the
@@ -1442,8 +1443,8 @@
 To start a new translation, the most simple way is to copy the
 existing POT as @address@hidden, where @var{lang} is your
 language code.  For example, to prepare for a new translation of the
-essay @uref{}, you can
-simply do @code{cd philosophy/po; cp free-sw.pot
+essay @uref{}, you can
+simply @code{cd philosophy/po; cp free-sw.pot
 address@hidden and then edit the latter.  If
 @file{free-sw.pot} does not exist it is because either the article is
 not yet ``templated'' (i.e. migrated to the new style), or the GNUN
@@ -1992,8 +1993,9 @@
 GNUN relies on URLs being absolute, starting from the root directory
-as required in 
+as required in the
+FSF HTML Style Sheet Guidelines}.
 And please don't forget to commit the image in its source form
 (typically, in SVG format).
@@ -2438,8 +2440,9 @@
 A cron job commits updated reports for all active teams to GNUN
 project web repository, typically twice an hour.  The links to those
-reports are provided on
+reports are provided on the
+GNUN Reports}.
 There is also a target in @file{GNUmakefile} to generate text reports
 intended for monthly messages sent to the teams.  @xref{report}.
@@ -2616,18 +2619,19 @@
 If you encounter a bug, or if you have suggestions of any kind, please
 do not hesitate to report them at @email{} or
address@hidden Index
address@hidden Index
address@hidden cp
+GNUN Bug Tracker}.
 @node Copying This Manual
 @appendix GNU Free Documentation License
 @include fdl.texi
address@hidden Index
address@hidden Index
address@hidden cp
 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.62
retrieving revision 1.63
diff -u -b -r1.62 -r1.63
--- doc/web-trans.texi  10 Jan 2014 07:16:38 -0000      1.62
+++ doc/web-trans.texi  17 Mar 2014 12:54:08 -0000      1.63
@@ -11,8 +11,8 @@
 This manual is a guide for the GNU Web address@hidden Last updated on
 @value{UPDATED}, for GNUnited Nations version @value{VERSION}.
 @sp 1
-Copyright @copyright{} 2009, 2010, 2011, 2012, 2013 Free Software
-Foundation, Inc.
+Copyright @copyright{} 2009, 2010, 2011, 2012, 2013,
+  2014 Free Software Foundation, Inc.
 Permission is granted to copy, distribute and/or modify this document
@@ -53,8 +53,8 @@
 * Members::              Information for translation team members.
 * Leaders::              Guidelines and procedures for team leaders.
 * Translation Process::  General guidelines and tips.
address@hidden * Index::
 * Copying This Manual::  The GNU Free Documentation License.
+* Index::
 @end menu
 @node Introduction
@@ -92,7 +92,7 @@
 maintain in the long term translations of the various essays that
 describe the fundamental values of the free software movement.
-Translators of the @uref{} website are organized in
+Translators of the @uref{} website are organized in
 language teams.  Each team has one or more co-ordinators, who are
 responsible for the respective team; they are also referred to as
 leaders or (when multiple in a single team) co-leaders.  The
@@ -109,6 +109,7 @@
 @node Members
 @chapter Team Members
address@hidden team members
 Being a team member means to co-operate with a group of other people,
 working under the co-ordinatorship of the appointed team leader.
 Usually, this involves translating articles and reviewing/proof-reading
@@ -124,8 +125,10 @@
 @node Joining
 @section Joining a Team
-To join a team, please first look at the existing teams at
address@hidden Translations README
+To join a team, please first look at the existing teams in
+Translations README}.
 Chances are that there is already an established team.  If there is no
 team listed for your language, this means that:
@@ -150,13 +153,15 @@
 team or become a co-ordinator of an existing one, please refer to the
 next chapter, @pxref{Leaders}.
address@hidden contacting team
address@hidden team, contacting
 Contacting the team is best done via Savannah---each translation team
 has its own project, named @address@hidden, with the project
 page being
 All teams should have mailing lists, typically in the form
 @address@hidden@dots{}}.  Some teams have homepages,
 with additional contact details and procedures for team members.
 You could also write directly to the team leader via the Savannah
@@ -197,9 +202,11 @@
 @node Submitting as PO
 @subsection How to Submit a Translation in PO Format
address@hidden GNUN
 All address@hidden really, but the goal is to maintain
-all of them.} are maintained via GNUN (see
address@hidden://}), which significantly eases
+all of them.} are maintained via
address@hidden://, GNUN}), which
+significantly eases
 maintenance and avoids the unpleasant situation where a translation is
 lagging behind the original.  @xref{Advantages, , , gnun, The GNUnited
 Nations Manual}.
@@ -210,6 +217,8 @@
address@hidden web pages, checking out
address@hidden checking out web pages
 Make a checkout of the CVS Web repository of the @samp{www} Savannah
 project.  You can find generic instructions at
 @uref{}.  All updates to the
@@ -224,7 +233,7 @@
 @end example
 This command will fetch only the @file{/gnu} directory---in other words,
-all articles at @uref{}.
+all articles at @uref{}.
 You can also fetch single files by their respective URLs.  For example,
 the URL for the template file of
@@ -251,6 +260,7 @@
 ability) the translation and will install it in the repository.
address@hidden server templates
 In order for 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
@@ -278,6 +288,7 @@
 @node Submitting as Plain Text
 @subsection How to Submit a Translation as Plain Text
address@hidden 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
 translation in plain text.  It will be manually converted to PO file by
@@ -285,6 +296,9 @@
 naturally, means more work for them and slower processing of your
address@hidden .odt files
address@hidden ODF
address@hidden encoding
 You should @emph{never} translate the HTML markup---i.e. @emph{do not}
 use the ``View Source'' functionality of your browser to translate the
 raw HTML.  Most of it is irrelevant, and automatically inherited from
@@ -294,10 +308,10 @@
 LibreOffice (the file should be saved as @file{.txt}, not
 @file{.odt}), etc.
-Translate the title, the blue heading (if it differs slightly from the
-title) and the body of the article up to the link @samp{back to top}.
-For example, for @uref{}
-that would be:
+Translate the title, the main heading and the body of the article up
+to the footer.  For example, for the
address@hidden://, Free Software
+Definition} that would be:
 What is free software? - GNU Project - Free Software Foundation
@@ -331,8 +345,8 @@
 If you wish your name to appear in the footer as a translator of the
 article, please also provide a translation of @samp{Translation:
address@hidden name in your native language}} or @samp{Translated by:
address@hidden name in your native language}}, as you prefer.  Please also
address@hidden name}} or @samp{Translated by: @var{your name}}, as you
+prefer.  Please also
 state if you wish your email address to be published (some readers
 prefer to send suggestions directly to the translator, but we certainly
 do not require that translators must publish their address).
@@ -356,6 +370,8 @@
 @node Leaders
 @chapter Team Co-ordinators
address@hidden team leaders
address@hidden co-ordinators
 A translation team leader is the person who is ultimately
 responsible for organizing and managing the team, including, but not
 limited to, having the final say on contributed translations and
@@ -393,8 +409,9 @@
 You should read @emph{all} the documentation related to the
 translation process and at the very least all important
-philosophy-related articles listed at
+philosophy-related articles listed on the
+Translation Priorities} page
 before you decide to form a new team, or take over an orphaned team.
 Once you have the internal feeling that having a translation
 team for your language is a must, and you are the one for this job,
@@ -402,6 +419,8 @@
address@hidden Savannah, registering
address@hidden Savannah account
 If you do not have a Savannah account, register at
 @uref{}.  Write access
 to the repository and project membership is handled via Savannah, so you
@@ -420,7 +439,7 @@
 Examine the layout and structure of the repository.  Basically, it is
 mapped to the URL locations, more or less.  Take a look at the most
 important materials to translate under @file{/philosophy}, @file{/gnu},
address@hidden/distros}, @file{/copyleft} and @file{/licenses} directories just
address@hidden/distros}, @file{/education} and @file{/licenses} directories just
 to get a rough estimate about the amount of work address@hidden of
 December 2013, there are over 250 files to translate in ``important''
 directories; their volume is about 4 MB.}.  If you are
@@ -474,6 +493,7 @@
 @itemize @minus
address@hidden language code
 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
 the language is a variant such as Brazilian Portuguese or
@@ -481,7 +501,7 @@
 @samp{zh-cn} instead of @samp{pt_BR} and @samp{zh_CN}.
-The PO file header and initial comments should be completed as
+The PO file header and initial comments should be filled as
 @end itemize
@@ -500,8 +520,9 @@
 Submit at least two translations of your own.  We maintain a list with
-priority articles at
+priority articles on the
+Translation Priorities} page,
 although it is probably hard to start with one of them.  Choose whatever
 you wish, provided it is an essay and not an auxiliary page.  Avoid
 translating the homepage or @file{planetfeeds.html}---they are moving
@@ -559,7 +580,7 @@
 list (don't forget to subscribe yourself!), optionally add a home
 page using Web CVS repository.
-If you are taking over an orphaned team, Translation Managers will
+If you are taking over an orphaned team, the Translation Managers will
 make you the owner of its mailing lists (if any).
 @end enumerate
@@ -609,6 +630,7 @@
 teams, and for general organizational work.  Feel free to discuss
 anything related to the translation process there.
address@hidden native English speakers
 It is strongly recommended that translation teams attempt to recruit
 native English speakers in order to improve their translation process.
 Translators sometimes misunderstand English idioms and expressions, and
@@ -619,6 +641,8 @@
 @node Review
 @section Peer Review
address@hidden translations, review
address@hidden review
 First and foremost, find at least one person for peer review.  You will
 review her translations, and she will review yours (at least in the
 beginning).  Being a team leader does not mean that you cannot make
@@ -628,7 +652,7 @@
 the translator does a final review of her own translation.
 It is good to establish a practice: Do not commit officially (i.e. in
address@hidden, which will appear online at @uref{}
address@hidden, which will appear online at @uref{}
 immediately) a translation that is not yet reviewed by someone else who
 is not the translator.  Always perform a final review yourself even if
 the translation has been checked by another member of the team.  In
@@ -657,6 +681,8 @@
 @node Tracking Tasks
 @subsection How to Track Tasks and Bugs Using Savannah
address@hidden tasks, tracking
address@hidden tracking tasks
 The team leader has to make sure that prospective translations are
 reviewed, that they do not contain obvious errors and confusing
 expressions and that they match the spirit and intention of the original
@@ -672,7 +698,7 @@
 A solution to this specific problem is to distribute the load among more
 people.  For example: Member D makes a translation of @file{foo.html}
 and uploads @address@hidden in the translation project's
-repository at Savannah, marking the relevant task as ``Ready for Test''
+repository at Savannah, marking the relevant task as ``Ready For Test''
 (of course, the equivalent is sending a message with the attached
 translation to the team's mailing list, or similar).  Then Member A, B
 and C (or only A and B if C is currently busy) review it independently
@@ -730,6 +756,7 @@
 resolved should remain open, naturally.
 @end itemize
address@hidden SourceForge
 If there are compelling reasons, teams can choose to manage these
 things using external
 resources and eventually other bug (or issue) tracking systems.
@@ -747,6 +774,8 @@
 @node Unreviewed Translations
 @subsection How to Proceed with Unreviewed Translations
address@hidden unreviewed translations
address@hidden translations, unreviewed
 Sometimes a translation (typically your own) is not reviewed by anyone
 else for a fairly long time.  This is unfortunate, but there is no
 reason to keep it in draft state forever.  If nobody reviewed it for a
@@ -762,6 +791,7 @@
 @node Commits
 @section CVS Commits and Best Practices
address@hidden CVS, using
 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.  This vote of confidence should never be
@@ -859,6 +889,7 @@
 Savannah project for each language is obvious: it's a standard way to
 find information for translation teams and their contacts.
address@hidden external resources
 Using external hosting facilities may seem justified sometimes.  Some
 teams may have already established repositories or bug tracking
 systems where usual contributors already have access.  Some team
@@ -868,8 +899,8 @@
 (@pxref{Savannah Mailing Lists}), because it is easier to pass its
 management to the new co-ordinator when the old one steps down, and it
 helps to keep the archives at one place for future members of the
-team.  Likewise, it is better to use Savannah for the team's
-repository and bugs/tasks, but this is not mandatory.
+team.  Likewise, it is better to use Savannah for team's
+repository and bugs/tasks.
 However, it is important to remember that regardless of the technical
 resources which a team decides to use, the responsibility of the team
@@ -918,6 +949,7 @@
 two and does not want to be engaged with the team on a long-term basis.
 In such situations, there is no need to add her as a member.
address@hidden team status
 It is a good idea to mark inactive members, for example if there is no
 interaction (bug reports, new translations, updates to existing
 translations, proof-reading) for at least six months.  You can do that
@@ -930,6 +962,7 @@
 @node Savannah Homepage
 @subsection Homepage of the Team
address@hidden team homepage
 Every Savannah project has a Web repository, which is, for technical and
 historical reasons, only CVS.  By default it is mapped to
@@ -941,10 +974,11 @@
 corresponding page containing these instructions, instead of repeatedly
 explaining every volunteer separately.
-All team-specific pages should follow the usual linking criteria (see
-and the FSF HTML Style Sheet
+All team-specific pages should follow the usual linking criteria in
+GNU Webmastering Guidelines}, and the
+FSF HTML Style Sheet Guidelines}.
 @node Savannah Support
 @subsection Support Tracker
@@ -992,6 +1026,7 @@
 @node Savannah News
 @subsection News Tracker
address@hidden team news
 That is a way to inform newcomers and interested people (who visit the
 project page from time to time, or subscribe to the @samp{News} RSS
 feed) about a major change or event within the project.
@@ -1007,6 +1042,7 @@
 @node Savannah Mailing Lists
 @subsection Managing Mailing Lists
address@hidden team mailing lists
 Every team should have a mailing list on and use it for
 internal communications.  All active translators should be on the
 list.  The list owner should be the co-ordinator of the team.  The
@@ -1028,6 +1064,8 @@
 @node Savannah VCS
 @subsection Version Control Systems
address@hidden VCS
address@hidden team's repository
 An easy way to keep up with changes in the original articles and to
 manage continuous contributions is to keep all translations in the
 translation project's Sources repository.  That way, it is easy to edit
@@ -1047,6 +1085,7 @@
 @node Co-leaders
 @section Promoting Members as Co-leaders
address@hidden 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 two other) people
 to help.  Note that a subsequently appointed team co-ordinator is not
@@ -1070,6 +1109,7 @@
 @node Reports
 @section Reporting Team Status
address@hidden team status
 Team leaders must send an annual report about the status of the team.  A
 good report should include:
@@ -1103,10 +1143,7 @@
 @end itemize
 The best time to send a report is near the end of the year, for example
-November.  In any case, please do not send it later than December 15th,
-as the Translation Manager has to prepare a general report to the FSF,
-and it is better if it takes into account the reports of the team
 If there is no sensitive information in the report and you feel like
 sharing it, you can send it to @email{}
@@ -1173,8 +1210,10 @@
 @node Priorities
 @section What to Translate
-The page
address@hidden translation priorities
+Web Translation Priorities} page
 lists the most important essays to translate.  In general, articles in
 the directories @file{philosophy}, @file{gnu},
 @file{education}, @file{distros},
@@ -1186,25 +1225,28 @@
 You can find links to automatic reports about current status of
 translations of all active teams sorted by their priority in
address@hidden://}.  If the page for
-your team is missing there, please ask
+GNUN Reports}.  If the page for your team is missing there, please ask
 @email{} to add it to the cron job.
 @emph{Do not} translate articles under these directories:
 @table @file
 @item software/@var{pkg}/
address@hidden web pages of GNU packages
 These pages are maintained by the respective @var{pkg} maintainers.
 GNUN does not support them for the time being, as they reside in
 separate repositories.  The procedures for contributing translations of
 such articles are not yet settled.
 @item brave-gnu-world
address@hidden Brave GNU World
 The Brave GNU World initiative has been abandoned long time ago, and
 it's in a separate repository---thus not supported by the automatic GNUN
 build job.
 @item home.html
address@hidden home.html
 There is no problem to translate this page, but don't make the mistake
 to pick it up as your first translation.  It is modified often,
 sometimes intensively, and only active team members should take that
@@ -1220,6 +1262,9 @@
 @node Updating
 @section Keeping Translations Current
address@hidden translation priorities
address@hidden translations, keeping current
address@hidden tracking changes in files
 It is very important to keep existing translations up-to-date with the
 respective English originals.  This task should be higher priority than
 translating new articles.  We developed various means to automate
@@ -1238,8 +1283,9 @@
 status of translations; @pxref{gnun-report, , , gnun, The GNUnited
 Nations Manual}.  A cron job commits updated reports for all active
 teams to GNUN project web repository, typically twice an hour.  The
-links to those reports are provided on
+links to those reports are provided on the
+GNUN Reports} page.
 @item provides a more detailed @code{report} target: unlike
@@ -1249,6 +1295,7 @@
 Nations Manual}.
address@hidden outdated translations, notification also has a means to send more detailed reports
 to specific translators; @pxref{notify in, , , gnun,
 The GNUnited Nations Manual}.  The notification facility takes the
@@ -1273,6 +1320,7 @@
 @node Capitalization
 @section When to CAPITALIZE
address@hidden capitalization
 The English language has some rules for capitalization of titles,
 chapters, acronym expansions and the like.  These rules are neither
 strict nor uniform, although the website strives to apply them
@@ -1301,6 +1349,8 @@
 @node Distribution Terms
 @section Distribution Terms
address@hidden Creative Commons
address@hidden distribution terms
 Most articles are released under the terms of
 the Creative Commons Attribution-NoDerivs 3.0 United States license.
 The exact HTML for English pages to use is:
@@ -1353,7 +1403,8 @@
 satisfactory for some reasons---for instance, as of May, 2012, their
 German translation uses ``Content'', which is a word to use with
 caution (see
+Words to Avoid (or Use with Care)}).
 Note that translations should @emph{not} change the jurisdiction of the
 license; they should @emph{always} link to the CC BY-ND 3.0 @emph{United
@@ -1365,31 +1416,41 @@
 @node Copyright Notices
 @section Copyright Notices
address@hidden copyright notices
 Don't translate the word ``Copyright'' in copyright notices; for more
 info, @pxref{--version, , , standards, The GNU Coding Standards}.
+Also, please maintain a proper copyright notice in the translation,
address@hidden Notices, , , maintain, Information for maintainers of
+GNU software}.
 @node Terminology
 @section Language-specific Terminology
 This is a very important topic, not yet covered by this manual.
-Some tips are given on
address@hidden Translations README
+Some tips are given in
+Translations README}.
 @node Mailing Lists
 @section Related Mailing Lists
address@hidden mailing lists
 Here is a summary of the mailing lists relevant to the translation
 process, and a brief description about how they relate to the various
 participants in the process.
 @table @email
 The basic discussion list of the GNU Webmasters.  All team leaders are
 required to subscribe.
 This is a private mailing list.
address@hidden tracking changes in files
 Commits to the @samp{www} repository are sent here.  All Translation
 Managers are required to subscribe.  It is strongly recommended that
@@ -1399,6 +1460,7 @@
 This is a public mailing list, so everyone can subscribe and review the
 archives.  The @samp{www} CVS repository is also public.
 The main discussion list for the GNU Web Translators.  Team leaders must
 subscribe, as errors from GNUN are mailed here.  It's highly recommended
@@ -1408,7 +1470,7 @@
 This is a private mailing list.
-This is a list for notifications about gnunews and GNUnited Nations
+This is a list for notifications about GNUnited Nations
 releases.  It is not mandatory to subscribe to it, although the traffic
 is very low.  If you want to track only GNUN release announcements,
 subscribe to the @samp{gnun} topic via Mailman's user interface.
@@ -1428,6 +1490,24 @@
 repository are also sent to this list.
 This is a public list, and @email{} is an alias.
+This is a tracker for GNU Webmasters.  It is used for bug reports and
+other suggestions for (English) web pages.
+This is a private tracker.
+This is the tracker and the primary contact of GNU Web Translation
+Managers.  It is used for bug reports against translations
+and submitting new translations for the languages lacking an active
+team, requests for help from the teams and various translation-related
+requests from GNU people.
+This is a private tracker.
 @end table
 Every team should also use at least one mailing list on Savannah,
@@ -1436,6 +1516,7 @@
 @node Savannah Projects
 @section Savannah Projects Membership
address@hidden Savannah projects
 Participants in the translation process normally have to be
 members of the following Savannah projects, depending on the case:
@@ -1483,13 +1564,15 @@
 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 it valid.
+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
+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.
@@ -1498,6 +1581,7 @@
 @cindex PO editors
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
@@ -1508,6 +1592,7 @@
 @xref{PO Mode, Emacs's PO File Editor, , gettext, GNU gettext tools}.
address@hidden Gtranslator
 Gtranslator---the GNOME PO editor.  See
@@ -1532,40 +1617,30 @@
 @c @end heresy
-Various web-based editors.
+GNU instance of Pootle, a web-based editor.
 @end itemize
 @subsection Web-based Systems
-An alternative way to maintain translations is to use one of the
-existing online editors.  There are plans to install a web-based system
-for managing @file{.po} files at Savannah, including online editing and
-statistics.  Until it happens, teams who wish to use this functionality
-may setup such a server on a host of their own, or use one of the
-existing free hosting platforms such as Launchpad
-Here is a short and probably incomplete list of such systems:
address@hidden itemize
-If you decide to use such a system, please make sure that no
-translations are published in HTML format there.
-Note that to keep the @file{.pot} files regularly updated (assuming such
-a web-based system runs @command{msgmerge} automatically), you'll have
-to take care of the one-way regular sync from the @samp{www} CVS
address@hidden web-based editing
address@hidden Pootle
+If your team would like to use a web-based editor, we recommend using
+the @uref{, official Pootle server of
+the GNU project}.  We make sure that working with it will not
+compromise your freedom via nonfree JavaScript or
+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  In order to test
+a page, log in the server and visit
address@hidden://}.  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 Migrating
 @section Migration to the New Style
@@ -1584,17 +1659,19 @@
 @node SSI
 @section Summary of SSI @code{#include}s
address@hidden SSI includes
 The GNU Project's website uses SSI (Server Side Includes) to manage some
 common parts that are the same in many of the articles.  With the help
 of GNUN their handling should be behind the scenes, but for some of them
-manual intervention is needed.  Here is a (possibly incomplete) list of
+manual intervention is needed.  Here is an incomplete list of
 the @code{#include}'s used:
 @table @file
 @item server/banner.html
 This file contains only @code{#include} directives, so the
-``translation'' should be identical, with filenames modified to have the
address@hidden extension.
+``translation'' should be almost identical, with filenames modified
+to have the @var{lang} extension.  The only other difference is
+including @file{server/address@hidden at the end.
 @item server/body-include-1.html
 Contains the top menu with useful ``skip to'' links.
@@ -1617,6 +1694,7 @@
 the FSF mission statement and the ``back to top'' link.
address@hidden generic.html
 @item server/generic.html
 This file is empty; its ``localized'' versions may contain optional
 short messages providing more information about the translation
@@ -1628,6 +1706,8 @@
 Foo team homepage</a>.</p>
 @end example
+This file is not under GNUN's control, you should edit HTML directly.
 @item server/header.html
 The declaration that is included in literally every file (unless
 the @file{html5-header.html} is used as the alternative).  It is
@@ -1643,6 +1723,7 @@
 @end example
 @item server/head-include-1.html
address@hidden encoding
 This file (included from @file{server/header.html}) is very important:
 the encoding is defined here.  Even if a specific PO file is
 deliberately encoded in another encoding, the generated HTML will
@@ -1654,6 +1735,7 @@
 the latter is not complete, and because all translated pages share
 automatically generated lists of translations.
address@hidden HTML5
 @item server/html5-header.html
 This file is included in pages using some entities introduced
 in HTML5 draft.  We have to distinguish those pages since some features
@@ -1666,15 +1748,20 @@
 @item server/head-include-2.html
 Imports the standard CSS, which can be overridden.  @xref{CSS}.
address@hidden server/home-pkgblurbs.html
+This header includes short descriptions of all GNU packages; it is
+included from the homepage and @file{manual/blurbs.html}.
 @item server/footer.html
-This is a very short and simple file (at least at the time of writing),
-containing another @code{#include} directive.  It is maintained
-manually, so just add @var{lang} to the filename, in order the localized
+This is a very short and simple file, containing another
address@hidden directive.  It is maintained manually, so just add
address@hidden to the filename, in order the localized
 @address@hidden to be included.
address@hidden outdated translations
 @item server/outdated.html
 This file is automatically included in outdated translations.  It
-contains respective message with links to the English file and
+contains a message with links to the English file and
 to a generated difference of the current revision of the English
 file against the most recent revision that has a complete translation.
 It is only included in articles affected by ``grace period'' because
@@ -1682,6 +1769,11 @@
 and it is evident without any notices that there is no complete
 and up to date translation.
address@hidden news items
address@hidden planetfeeds.html
address@hidden planetfeeds.html
+Includes automatically extracted news items.
 @item server/top-addendum.html
 The text saying that the page is a translation.
@@ -1697,6 +1789,7 @@
 them verbatim as they should not be translated.
 @end table
address@hidden server templates
 The files
 @c Use @itemize to avoid `underfull \hbox' warnings from TeX.
@@ -1725,6 +1818,7 @@
 @node CSS
 @section How to Use Custom CSS
address@hidden custom CSS
 The CSS file @file{layout.css} gets included (with three other CSS files)
 in almost all the English articles through
 @file{server/address@hidden  However, sometimes this
@@ -1744,8 +1838,12 @@
 Override only what is necessary and looks broken in your language; do
 not invent your own style.  This is important for the consistency of the website.  A typical language-specific
address@hidden@var{lang}.css} file looks like this: website.  Also, please check if the issue is
+language-independent; in this case a change for @file{layout.css}
+should be discussed with the webmasters.
+A typical language-specific @address@hidden file looks
+like this:
 .inner @{ max-width: 85em; @}
@@ -1819,6 +1917,7 @@
 @node RTL
 @subsection Specific Issues Related to RTL
address@hidden right-to-left languages
 Unfortunately, the @uref{} 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:
@@ -1850,13 +1949,10 @@
 @include fdl.texi
-FIXME: To be restored when indexing commands are added.
 @node Index
 @unnumbered Index
 @printindex cp
address@hidden ignore

reply via email to

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