[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
trans-coord/manual gnun/gnun.dvi.gz gnun/gnun.h...
|
From: |
Pavel Kharitonov |
|
Subject: |
trans-coord/manual gnun/gnun.dvi.gz gnun/gnun.h... |
|
Date: |
Thu, 27 Dec 2012 14:45:43 +0000 |
CVSROOT: /web/trans-coord
Module name: trans-coord
Changes by: Pavel Kharitonov <ineiev> 12/12/27 14:45:42
Modified files:
manual/gnun : gnun.dvi.gz gnun.html gnun.html.gz
gnun.html_node.tar.gz gnun.info.tar.gz gnun.pdf
gnun.texi.tar.gz gnun.txt gnun.txt.gz
index.html
manual/gnun/html_node: Advantages.html Bugs.html
Comments-for-Translators.html
Compendia.html Concepts.html
Copying-This-Manual.html
Credits-Slot.html Disadvantages.html
GNU-News.html
GNUmakefile_002eteam-Targets.html
GNUmakefile_002eteam-Variables.html
GNUmakefile_002eteam-and-Cron.html
GRACE.html Index.html Internals.html
Introduction.html Invoking-GNUN.html
Localized-URLs.html Main-Variables.html
Migrating.html
Modifying-Boilerplates.html
New-Translation.html Notes-Slot.html
Overview.html PO-Files-and-Team.html
PO-Files.html PO-Tips.html
Runtime-Variables.html Scripts.html
Special-Targets.html
Splitting-Long-Passages.html Usage.html
Validation.html Webmaster-Tips.html
extra_002dtemplates.html
generic_002eLANG_002ehtml.html
gnun_002dadd_002dfuzzy_002ddiff.html
gnun_002dclear_002dprevious.html
gnun_002ddiff_002dpo.html
gnun_002dinit_002dpo.html
gnun_002dmerge_002dpreconverted.html
gnun_002dpreconvert.html
gnun_002dreport.html
gnun_002dvalidate_002dhtml.html
index.html languages_002etxt.html
mailfail.html no_002dgrace_002ditems.html
optional_002dtemplates.html report.html
sync.html triggers.html
update_002dlocalized_002dURLs.html
validate_002dall.html
validate_002dhtml_002dnotify.html
manual/web-trans: index.html web-trans.dvi.gz web-trans.html
web-trans.html.gz web-trans.html_node.tar.gz
web-trans.info.tar.gz web-trans.pdf
web-trans.texi.tar.gz web-trans.txt
web-trans.txt.gz
manual/web-trans/html_node: CSS.html Capitalization.html
Co_002dleaders.html Commits.html
Copying-This-Manual.html
Distribution-Terms.html
Introduction.html Joining.html
Leaders.html Mailing-Lists.html
Managing.html Members.html
Migrating.html New-Team.html
Priorities.html RTL.html
Reports.html Review.html SSI.html
Savannah-Bugs.html
Savannah-Homepage.html
Savannah-Mailing-Lists.html
Savannah-Members.html
Savannah-News.html
Savannah-Projects.html
Savannah-Support.html
Savannah-Tasks.html
Savannah-VCS.html Savannah.html
Stepping-Down.html
Submitting-as-PO.html
Submitting-as-Plain-Text.html
Submitting.html Summary.html
Terminology.html Tracking-Tasks.html
Translation-Managers.html
Translation-Tips.html
Unreviewed-Translations.html
index.html topbanner.html
Added files:
manual/gnun/html_node: Files-and-Directories.html
GNUN-Slots.html publish.html
report-in-GNUmakefile_002eteam.html
manual/web-trans/html_node: Leaving-a-Team.html PO-Files.html
Log message:
Regenerate.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.dvi.gz?cvsroot=trans-coord&rev=1.18
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.html?cvsroot=trans-coord&r1=1.17&r2=1.18
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.html.gz?cvsroot=trans-coord&rev=1.18
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.html_node.tar.gz?cvsroot=trans-coord&rev=1.18
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.info.tar.gz?cvsroot=trans-coord&rev=1.18
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.pdf?cvsroot=trans-coord&rev=1.18
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.texi.tar.gz?cvsroot=trans-coord&rev=1.18
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.txt?cvsroot=trans-coord&r1=1.17&r2=1.18
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.txt.gz?cvsroot=trans-coord&rev=1.18
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/index.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Advantages.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Bugs.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Comments-for-Translators.html?cvsroot=trans-coord&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Compendia.html?cvsroot=trans-coord&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Concepts.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Copying-This-Manual.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Credits-Slot.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Disadvantages.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GNU-News.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GNUmakefile_002eteam-Targets.html?cvsroot=trans-coord&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GNUmakefile_002eteam-Variables.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GNUmakefile_002eteam-and-Cron.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GRACE.html?cvsroot=trans-coord&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Index.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Internals.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Introduction.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Invoking-GNUN.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Localized-URLs.html?cvsroot=trans-coord&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Main-Variables.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Migrating.html?cvsroot=trans-coord&r1=1.17&r2=1.18
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Modifying-Boilerplates.html?cvsroot=trans-coord&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/New-Translation.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Notes-Slot.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Overview.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/PO-Files-and-Team.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/PO-Files.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/PO-Tips.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Runtime-Variables.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Scripts.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Special-Targets.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Splitting-Long-Passages.html?cvsroot=trans-coord&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Usage.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Validation.html?cvsroot=trans-coord&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Webmaster-Tips.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/extra_002dtemplates.html?cvsroot=trans-coord&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/generic_002eLANG_002ehtml.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dadd_002dfuzzy_002ddiff.html?cvsroot=trans-coord&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dclear_002dprevious.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002ddiff_002dpo.html?cvsroot=trans-coord&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dinit_002dpo.html?cvsroot=trans-coord&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dmerge_002dpreconverted.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dpreconvert.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dreport.html?cvsroot=trans-coord&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dvalidate_002dhtml.html?cvsroot=trans-coord&r1=1.12&r2=1.13
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/index.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/languages_002etxt.html?cvsroot=trans-coord&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/mailfail.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/no_002dgrace_002ditems.html?cvsroot=trans-coord&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/optional_002dtemplates.html?cvsroot=trans-coord&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/report.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/sync.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/triggers.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/update_002dlocalized_002dURLs.html?cvsroot=trans-coord&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/validate_002dall.html?cvsroot=trans-coord&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/validate_002dhtml_002dnotify.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Files-and-Directories.html?cvsroot=trans-coord&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GNUN-Slots.html?cvsroot=trans-coord&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/publish.html?cvsroot=trans-coord&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/report-in-GNUmakefile_002eteam.html?cvsroot=trans-coord&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/index.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.dvi.gz?cvsroot=trans-coord&rev=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.html.gz?cvsroot=trans-coord&rev=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.html_node.tar.gz?cvsroot=trans-coord&rev=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.info.tar.gz?cvsroot=trans-coord&rev=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.pdf?cvsroot=trans-coord&rev=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.texi.tar.gz?cvsroot=trans-coord&rev=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.txt?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.txt.gz?cvsroot=trans-coord&rev=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/CSS.html?cvsroot=trans-coord&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Capitalization.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Co_002dleaders.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Commits.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Copying-This-Manual.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Distribution-Terms.html?cvsroot=trans-coord&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Introduction.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Joining.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Leaders.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Mailing-Lists.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Managing.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Members.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Migrating.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/New-Team.html?cvsroot=trans-coord&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Priorities.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/RTL.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Reports.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Review.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/SSI.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Bugs.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Homepage.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Mailing-Lists.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Members.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-News.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Projects.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Support.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Tasks.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-VCS.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Stepping-Down.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Submitting-as-PO.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Submitting-as-Plain-Text.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Submitting.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Summary.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Terminology.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Tracking-Tasks.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Translation-Managers.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Translation-Tips.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Unreviewed-Translations.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/index.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/topbanner.html?cvsroot=trans-coord&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Leaving-a-Team.html?cvsroot=trans-coord&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/PO-Files.html?cvsroot=trans-coord&rev=1.1
Patches:
Index: gnun/gnun.dvi.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.dvi.gz,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
Binary files /tmp/cvsIqGIZ2 and /tmp/cvs2ZP5su differ
Index: gnun/gnun.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- gnun/gnun.html 4 Dec 2012 16:24:18 -0000 1.17
+++ gnun/gnun.html 27 Dec 2012 14:45:31 -0000 1.18
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations</title>
@@ -75,8 +75,8 @@
<ul class="no-bullet">
<li><a name="toc-Introduction-to-GNUnited-Nations" href="#Introduction">1
Introduction to GNUnited Nations</a>
<ul class="no-bullet">
- <li><a name="toc-Why-GNUN-is-Being-Developed" href="#Overview">1.1 Why
GNUN is Being Developed</a></li>
- <li><a name="toc-What-GNUnited-Nations-is-and-Should-be"
href="#Concepts">1.2 What GNUnited Nations is and Should be</a></li>
+ <li><a name="toc-Why-GNUN-Is-Being-Developed" href="#Overview">1.1 Why
GNUN Is Being Developed</a></li>
+ <li><a name="toc-What-GNUnited-Nations-Is-and-Should-Be"
href="#Concepts">1.2 What GNUnited Nations Is and Should Be</a></li>
<li><a name="toc-Major-Advantages-of-GNUN" href="#Advantages">1.3 Major
Advantages of GNUN</a></li>
<li><a name="toc-Known-Bugs-and-Limitations" href="#Disadvantages">1.4
Known Bugs and Limitations</a></li>
</ul></li>
@@ -95,7 +95,7 @@
<li><a name="toc-The-validate_002dall-Target"
href="#validate_002dall">2.1.2.6 The <code>validate-all</code> Target</a></li>
</ul></li>
</ul></li>
- <li><a name="toc-Defining-Articles-to-be-Built" href="#Main-Variables">2.2
Defining Articles to be Built</a></li>
+ <li><a name="toc-Defining-Articles-to-Be-Built" href="#Main-Variables">2.2
Defining Articles to Be Built</a></li>
<li><a name="toc-Working-with-PO-Files" href="#PO-Files">2.3 Working with
PO Files</a>
<ul class="no-bullet">
<li><a name="toc-Starting-a-New-Translation"
href="#New-Translation">2.3.1 Starting a New Translation</a>
@@ -103,18 +103,18 @@
<li><a name="toc-The-Special-Slot-for-Translator_0027s-Notes"
href="#Notes-Slot">2.3.1.1 The Special Slot for Translator’s
Notes</a></li>
<li><a name="toc-The-Special-Slot-for-Translator_0027s-Credits"
href="#Credits-Slot">2.3.1.2 The Special Slot for Translator’s
Credits</a></li>
</ul></li>
- <li><a name="toc-Transforming-Existing-Translation-in-PO-Format"
href="#Migrating">2.3.2 Transforming Existing Translation in PO Format</a></li>
- <li><a name="toc-Special-Handling-for-GNU-News" href="#GNU-News">2.3.3
Special Handling for GNU News</a></li>
- <li><a name="toc-Useful-Hints-for-Editing-PO-Files"
href="#PO-Tips">2.3.4 Useful Hints for Editing PO Files</a></li>
- <li><a name="toc-The-generic_002elang_002ehtml-File"
href="#generic_002eLANG_002ehtml">2.3.5 The
<samp>generic.<var>lang</var>.html</samp> File</a></li>
- <li><a name="toc-The-languages_002etxt-File"
href="#languages_002etxt">2.3.6 The <samp>languages.txt</samp> File</a></li>
- <li><a name="toc-Maintaining-Translations-in-Your-Team_0027s-Repository"
href="#PO-Files-and-Team">2.3.7 Maintaining Translations in Your Team’s
Repository</a>
+ <li><a name="toc-Useful-Hints-for-Editing-PO-Files"
href="#PO-Tips">2.3.2 Useful Hints for Editing PO Files</a></li>
+ <li><a name="toc-Transforming-Existing-Translation-in-PO-Format"
href="#Migrating">2.3.3 Transforming Existing Translation in PO Format</a></li>
+ <li><a name="toc-The-generic_002elang_002ehtml-File"
href="#generic_002eLANG_002ehtml">2.3.4 The
<samp>generic.<var>lang</var>.html</samp> File</a></li>
+ <li><a name="toc-The-languages_002etxt-File"
href="#languages_002etxt">2.3.5 The <samp>languages.txt</samp> File</a></li>
+ <li><a name="toc-Maintaining-Translations-in-Your-Team_0027s-Repository"
href="#PO-Files-and-Team">2.3.6 Maintaining Translations in Your Team’s
Repository</a>
<ul class="no-bullet">
- <li><a name="toc-Adopting-GNUmakefile_002eteam-for-a-Specific-Team"
href="#GNUmakefile_002eteam-Variables">2.3.7.1 Adopting
<samp>GNUmakefile.team</samp> for a Specific Team</a></li>
- <li><a name="toc-Targets-in-GNUmakefile_002eteam"
href="#GNUmakefile_002eteam-Targets">2.3.7.2 Targets in
<samp>GNUmakefile.team</samp></a></li>
- <li><a name="toc-Automatic-Synchronization-and-Status-Reports"
href="#GNUmakefile_002eteam-and-Cron">2.3.7.3 Automatic Synchronization and
Status Reports</a></li>
+ <li><a name="toc-Adopting-GNUmakefile_002eteam-for-a-Specific-Team"
href="#GNUmakefile_002eteam-Variables">2.3.6.1 Adopting
<samp>GNUmakefile.team</samp> for a Specific Team</a></li>
+ <li><a name="toc-Targets-in-GNUmakefile_002eteam"
href="#GNUmakefile_002eteam-Targets">2.3.6.2 Targets in
<samp>GNUmakefile.team</samp></a></li>
+ <li><a name="toc-Automatic-Synchronization-and-Status-Reports"
href="#GNUmakefile_002eteam-and-Cron">2.3.6.3 Automatic Synchronization and
Status Reports</a></li>
</ul></li>
- <li><a name="toc-Using-Compendia" href="#Compendia">2.3.8 Using
Compendia</a></li>
+ <li><a name="toc-Using-Compendia" href="#Compendia">2.3.7 Using
Compendia</a></li>
+ <li><a name="toc-Special-Handling-for-GNU-News" href="#GNU-News">2.3.8
Special Handling for GNU News</a></li>
</ul></li>
<li><a name="toc-Tips-and-Hints-for-Webmasters" href="#Webmaster-Tips">2.4
Tips and Hints for Webmasters</a>
<ul class="no-bullet">
@@ -127,20 +127,20 @@
</ul></li>
<li><a name="toc-Unexciting-Information-for-GNUN_0027s-Operation"
href="#Internals">3 Unexciting Information for GNUN’s Operation</a>
<ul class="no-bullet">
- <li><a name="toc-GNUN-Scripts" href="#Scripts">3.1 GNUN Scripts</a>
+ <li><a name="toc-Files-and-Directories-1"
href="#Files-and-Directories">3.1 Files and Directories</a></li>
+ <li><a name="toc-GNUN-Scripts" href="#Scripts">3.2 GNUN Scripts</a>
<ul class="no-bullet">
- <li><a name="toc-The-gnun_002dadd_002dfuzzy_002ddiff-Script"
href="#gnun_002dadd_002dfuzzy_002ddiff">3.1.1 The
<code>gnun-add-fuzzy-diff</code> Script</a></li>
- <li><a name="toc-The-gnun_002ddiff_002dpo-Script"
href="#gnun_002ddiff_002dpo">3.1.2 The <code>gnun-diff-po</code> Script</a></li>
- <li><a name="toc-The-gnun_002dinit_002dpo-Script"
href="#gnun_002dinit_002dpo">3.1.3 The <code>gnun-init-po</code> Script</a></li>
- <li><a name="toc-The-gnun_002dpreconvert-Script"
href="#gnun_002dpreconvert">3.1.4 The <code>gnun-preconvert</code>
Script</a></li>
- <li><a name="toc-The-gnun_002dmerge_002dpreconverted-Script"
href="#gnun_002dmerge_002dpreconverted">3.1.5 The
<code>gnun-merge-preconverted</code> Script</a></li>
- <li><a name="toc-The-gnun_002dreport-Script"
href="#gnun_002dreport">3.1.6 The <code>gnun-report</code> Script</a></li>
- <li><a name="toc-The-gnun_002dvalidate_002dhtml-Script"
href="#gnun_002dvalidate_002dhtml">3.1.7 The <code>gnun-validate-html</code>
Script</a></li>
- <li><a name="toc-The-mailfail-Script" href="#mailfail">3.1.8 The
<code>mailfail</code> Script</a></li>
- <li><a name="toc-The-validate_002dhtml_002dnotify-Script"
href="#validate_002dhtml_002dnotify">3.1.9 The
<code>validate-html-notify</code> Script</a></li>
- <li><a name="toc-The-gnun_002dclear_002dprevious-Script"
href="#gnun_002dclear_002dprevious">3.1.10 The <code>gnun-clear-previous</code>
Script</a></li>
+ <li><a name="toc-The-gnun_002dadd_002dfuzzy_002ddiff-Script"
href="#gnun_002dadd_002dfuzzy_002ddiff">3.2.1 The
<code>gnun-add-fuzzy-diff</code> Script</a></li>
+ <li><a name="toc-The-gnun_002ddiff_002dpo-Script"
href="#gnun_002ddiff_002dpo">3.2.2 The <code>gnun-diff-po</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dinit_002dpo-Script"
href="#gnun_002dinit_002dpo">3.2.3 The <code>gnun-init-po</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dpreconvert-Script"
href="#gnun_002dpreconvert">3.2.4 The <code>gnun-preconvert</code>
Script</a></li>
+ <li><a name="toc-The-gnun_002dmerge_002dpreconverted-Script"
href="#gnun_002dmerge_002dpreconverted">3.2.5 The
<code>gnun-merge-preconverted</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dreport-Script"
href="#gnun_002dreport">3.2.6 The <code>gnun-report</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dvalidate_002dhtml-Script"
href="#gnun_002dvalidate_002dhtml">3.2.7 The <code>gnun-validate-html</code>
Script</a></li>
+ <li><a name="toc-The-mailfail-Script" href="#mailfail">3.2.8 The
<code>mailfail</code> Script</a></li>
+ <li><a name="toc-The-validate_002dhtml_002dnotify-Script"
href="#validate_002dhtml_002dnotify">3.2.9 The
<code>validate-html-notify</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dclear_002dprevious-Script"
href="#gnun_002dclear_002dprevious">3.2.10 The <code>gnun-clear-previous</code>
Script</a></li>
</ul></li>
- <li><a name="toc-How-The-Recipes-Work" href="#Rules">3.2 How The Recipes
Work</a></li>
</ul></li>
<li><a name="toc-Reporting-Bugs" href="#Bugs">4 Reporting Bugs</a></li>
<li><a name="toc-Index-1" href="#Index">Index</a></li>
@@ -158,7 +158,7 @@
<a name="GNUnited-Nations"></a>
<h1 class="top">GNUnited Nations</h1>
-<p>This manual (updated 3 December 2012) is for GNUnited Nations (version
+<p>This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.<br>
</p><br>
@@ -199,7 +199,7 @@
<a name="Introduction-to-GNUnited-Nations"></a>
<h2 class="chapter">1 Introduction to GNUnited Nations</h2>
-<p>GNUnited Nations (abbreviated GNUN) is a collection of makefiles and
+<p>GNUnited Nations (abbreviated GNUN) is a collection of
scripts that are supposed to make the life of <a
href="http://gnu.org";>http://gnu.org</a>
translators easier. Although it is specifically developed for the GNU
Project’s website, it could be customized, at least in theory, to fit
@@ -243,8 +243,8 @@
<p>
Next: <a href="#Concepts" accesskey="n" rel="next">Concepts</a>, Up: <a
href="#Introduction" accesskey="u" rel="up">Introduction</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<a name="Why-GNUN-is-Being-Developed"></a>
-<h3 class="section">1.1 Why GNUN is Being Developed</h3>
+<a name="Why-GNUN-Is-Being-Developed"></a>
+<h3 class="section">1.1 Why GNUN Is Being Developed</h3>
<p>The GNU Project’s website, <a
href="http://www.gnu.org";>http://www.gnu.org</a>, has become
considerably large over the years. Maintaining it requires significant
@@ -274,8 +274,8 @@
<p>
Next: <a href="#Advantages" accesskey="n" rel="next">Advantages</a>, Previous:
<a href="#Overview" accesskey="p" rel="previous">Overview</a>, Up: <a
href="#Introduction" accesskey="u" rel="up">Introduction</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<a name="What-GNUnited-Nations-is-and-Should-be"></a>
-<h3 class="section">1.2 What GNUnited Nations is and Should be</h3>
+<a name="What-GNUnited-Nations-Is-and-Should-Be"></a>
+<h3 class="section">1.2 What GNUnited Nations Is and Should Be</h3>
<p>The basic concept behind GNUN is that localization of HTML articles is
similar to localization of computer programs<a name="DOCF1"
href="#FOOT1"><sup>1</sup></a>. In articles, like in programs, not every
string is considered
@@ -331,8 +331,8 @@
particular language.
</p>
<p>The first time though, there is no
<samp><var>article</var>.<var>lang</var>.po</samp>
-yet, so a translator must manually copy <samp><var>article</var>.pot</samp> to
-<samp><var>article</var>.<var>lang</var>.po</samp>, where <var>lang</var>
represents the
+yet, so a translator must make
<samp><var>article</var>.<var>lang</var>.po</samp> from
+<samp><var>article</var>.pot</samp>, where <var>lang</var> represents the
target language. See <a href="#New-Translation">New Translation</a>, for
details.
</p>
<p>Then comes the initial translation of messages in
@@ -362,7 +362,7 @@
articles. If the original article changes, GNUN will automatically
rebuild <samp><var>article</var>.pot</samp>, and will merge the changes to
<samp><var>article</var>.<var>lang</var>.po</samp>. Any outdated translations
will be
-marked as fuzzy, any new strings will be added with empty translations,
+marked as “fuzzy,” any new strings will be added with empty
translations,
waiting to be translated. In the same run
<samp><var>article</var>.<var>lang</var>.html</samp> will be rebuilt so the
relevant
strings in the translation will be substituted with the original English
@@ -370,19 +370,20 @@
<samp><var>article</var>.<var>lang</var>.po</samp>.
</p>
<p>Those changes in the original article that do not affect the
-translatable strings will not lead to changes in
+translatable strings (or just delete whole strings) will not lead
+to changes in
<samp><var>article</var>.<var>lang</var>.po</samp>. Thus, no actions from
translators
will be needed. <samp><var>article</var>.<var>lang</var>.html</samp> will be
automatically regenerated to reflect the changes.
</p>
-
<p>The POT for every article under GNUN’s control is kept in the
‘www’
repository under a special directory <samp>po/</samp>, which is a
sub-directory of the relevant directory in the ‘www’ tree. So, for
‘<code>http://www.gnu.org/philosophy/free-sw.html</code>’ that is
<samp>philosophy/po/</samp>. Except <samp>free-sw.pot</samp>, this directory
holds
the canonical source of every translation, like <samp>free-sw.bg.po</samp>,
-<samp>free-sw.ca.po</samp>, etc.
+<samp>free-sw.ca.po</samp>, etc. For more details,
+See <a href="#Files-and-Directories">Files and Directories</a>.
</p>
<p>Several additional features are implemented, like automatic update of
the list of the available translations. For example, if a new
@@ -479,6 +480,11 @@
feasible with current build server hardware. Additionally, any errors
interrupt the build so they have to be fixed before the next articles
are processed.
+
+</li><li> In some rare cases (most notably, for alphabetically sorted lists)
+the structure of the translation should diverge from the structure
+of the original document. So far, our system has developped no means
+of taking such issues into account.
</li></ul>
<hr>
@@ -497,9 +503,8 @@
—O’Rielly’s Law
</p><br>
-<p>GNUN currently consists of a few makefiles, scripts and optional
-<samp>generic.<var>lang</var>.html</samp> files, intended to contain
-article-independent but team-specific information. They are designed
+<p>GNUN currently consists of a few makefiles, scripts and template files.
+They are designed
to reside in the <samp>server/gnun</samp> directory, but this may change.
In all examples in this manual, “invoking” means executing on the
command line <code>make -C server/gnun [<var>target</var>]
@@ -657,8 +662,7 @@
</dd>
<dt>‘<samp>VALIDATE=no</samp>’</dt>
<dt>‘<samp>…</samp>’</dt>
-<dd><p>Does not perform validation of the HTML articles and PO files. This
-is the default, and not defining this variable has the same effect.
+<dd><p>Skips validation of the HTML articles and generated translations.
</p>
</dd>
<dt>‘<samp>VALIDATE=yes</samp>’</dt>
@@ -669,12 +673,14 @@
fix the errors that are reported as a result of enforcing validation.
</p>
<p>Articles defined in the variable <code>no-validate-articles</code> are never
-checked for HTML validity. Its purpose was to skip validation of HTML
-5 articles, until the command-line validation tools are updated to
+checked for HTML validity. Its purpose was to skip validation of HTML5
+articles, until the command-line validation tools are updated to
parse files that comply with this new standard. As of version 0.5
-GNUN supports HTML 5, so resorting to <code>no-validate-articles</code>
+GNUN supports HTML5, so resorting to <code>no-validate-articles</code>
should not be necessary.
</p>
+<p>This is the default, and not defining this variable has the same effect.
+</p>
<a name="index-NOTIFY"></a>
<a name="index-mail_002c-notifications"></a>
</dd>
@@ -724,7 +730,7 @@
<a name="index-deferred-generation-of-articles"></a>
<a name="GRACE"></a></dd>
<dt>‘<samp>GRACE=<var>days</var></samp>’</dt>
-<dd><p>If defined, ordinary articles that have fuzzy strings and are not older
+<dd><p>If defined, ordinary articles that have “fuzzy” strings and
are not older
than <var>days</var> will not be regenerated. This functionality is
implemented specifically to prevent gratuitous replacement of translated
strings with the English text when there are only minor formatting
@@ -763,7 +769,7 @@
<code>cvs|svn|bzr add</code>-ing all necessary files.
</p>
<a name="index-validation-1"></a>
-<p>When validation is enabled (i.e. with <code>VALIDATE=yes</code>), the
+<p>When validation is enabled, the
original English articles are validated first, before any commands
that generate the other files, and <code>make</code> exits with an error
on the first encountered article. This is done on purpose, to prevent
@@ -834,8 +840,8 @@
server templates, gnunews, and all articles defined in the variable
<code>no-grace-articles</code> (see <a href="#GRACE">grace period</a>).
</p>
-<p>This target can be rebuilt more often than <code>all</code>; however, it is
-currently not used.
+<p>This target can be rebuilt more often than <code>all</code>; however,
+currently it is not used.
</p>
<hr>
<a name="update_002dlocalized_002dURLs"></a>
@@ -933,7 +939,9 @@
all other translations are reported as less important.
</p>
<p>There is also a script, <code>gnun-report</code>, to generate HTML reports.
-See <a href="#gnun_002dreport">gnun-report</a>.
+See <a href="#gnun_002dreport">gnun-report</a>. GNUmakefile.team profides
another <code>report</code>
+target, which produces a more detailed report.
+See <a href="#report-in-GNUmakefile_002eteam">report in GNUmakefile.team</a>.
</p>
<hr>
<a name="triggers"></a>
@@ -971,7 +979,7 @@
<p>To summarize, for effective operation GNUN should be invoked
automatically as <code>make; cvs|svn|bzr commit -m …; make
triggers</code>. To illustrate this, here is a concrete example showing the
-official job running at fencepost.gnu.org:
+official job once running at fencepost.gnu.org<a name="DOCF4"
href="#FOOT4"><sup>4</sup></a>:
</p>
<div class="example">
<pre class="example">25 4,12,20 * * * cd $HOME/projects/www; cvs -q update
&>/dev/null; \
@@ -1017,8 +1025,8 @@
<p>
Next: <a href="#PO-Files" accesskey="n" rel="next">PO Files</a>, Previous: <a
href="#Invoking-GNUN" accesskey="p" rel="previous">Invoking GNUN</a>, Up: <a
href="#Usage" accesskey="u" rel="up">Usage</a> [<a href="#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a href="#Index"
title="Index" rel="index">Index</a>]</p>
</div>
-<a name="Defining-Articles-to-be-Built"></a>
-<h3 class="section">2.2 Defining Articles to be Built</h3>
+<a name="Defining-Articles-to-Be-Built"></a>
+<h3 class="section">2.2 Defining Articles to Be Built</h3>
<a name="index-variables-1"></a>
<a name="index-gnun_002emk-1"></a>
@@ -1030,12 +1038,18 @@
<p>There are two types of variables, which are specifically separated in
order to make translators’ life easier: variables that translators are
free to modify and variables that are modified by the web-translators
-staff<a name="DOCF4" href="#FOOT4"><sup>4</sup></a>, ideally after performing
some local tests. A
+staff<a name="DOCF5" href="#FOOT5"><sup>5</sup></a>, ideally after performing
some local tests. A
translation team leader should update only <code>FUZZY_DIFF_LINGUAS</code>,
<code>TEMPLATE_LINGUAS</code>; everything else is supposed to be built
automagically, without manual intervention. If not, that is a bug that
should be reported and fixed.
</p>
+<p>You can also request building files separately this way:
+</p>
+<div class="example">
+<pre class="example">make -C server/gnun ../../philosophy/not-ipr.bg.html
+</pre></div>
+
<dl compact="compact">
<dd><a name="index-TEMPLATE_005fLINGUAS"></a>
<a name="index-templates_002c-defining"></a>
@@ -1095,7 +1109,7 @@
</dd>
<dt>‘<samp>FUZZY_DIFF_LINGUAS</samp>’</dt>
<dd><p>Add your language code here if you want GNUN to add differences to
-previous <code>msgid</code>s in your PO files. The differences are shown in
+“previous” <code>msgid</code>s in your PO files. The differences
are shown in
the default <code>wdiff</code> format. See <a
href="http://www.gnu.org/software/wdiff/manual/wdiff.html#wdiff";>The word
difference finder</a> in <cite>GNU wdiff</cite>, for more information.
</p>
@@ -1138,74 +1152,29 @@
</div>
<a name="Working-with-PO-Files"></a>
<h3 class="section">2.3 Working with PO Files</h3>
-<a name="index-PO_002c-editing"></a>
-<p>We anticipate that some gnu.org translators will find this format odd
-or inconvenient, if they never happened to work with PO files before.
-Don’t worry, you will soon get accustomed to it. It is the
-established format for translations in the Free World, and you should
-have no problems if you have translated software before.
-</p>
-<p>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 it valid. Here is a list of widely used PO editors:
+<p>This section provides GNUN-specific information about woking
+with PO files. For general information, see <a
href="http://www.gnu.org/software/trans-coord/manual/web-trans/web-trans.html#PO-Files";>Working
with PO Files</a> in <cite>GNU Web Translators Manual</cite>.
</p>
-<ul>
-<li> <a name="index-PO-editors"></a>
-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 <samp>.po</samp> file you visit should automatically
-switch to PO mode. You can enable/disable it with <code>M-x po-mode
-<span class="key">RET</span></code>. On some GNU/Linux distros such as
gNewSense, PO mode is
-available in a separate package, <code>gettext-el</code>. See
-<a
href="http://www.gnu.org/software/gettext";>http://www.gnu.org/software/gettext</a>.
-
-</li><li> Gtranslator—the GNOME PO editor. See
-<a
href="http://projects.gnome.org/gtranslator/";>http://projects.gnome.org/gtranslator/</a>.
-
-</li><li> Lokalize—the KDE 4 editor. See
-<a
href="http://userbase.kde.org/Lokalize";>http://userbase.kde.org/Lokalize</a>.
-
-</li><li> KBabel—the KDE 3 editor. No longer supported, but might be
-available on some old systems.
-
-</li><li> Poedit—another popular editor that is based on the
<code>wxWidgets</code>
-graphical toolkit. See <a
href="http://www.poedit.net";>http://www.poedit.net</a>.
-
-</li><li> Virtaal—a relevantly new editor that supports also the XLIFF
format
-and uses the Translate Toolkit API. See
-<a
href="http://translate.sourceforge.net/wiki/virtaal";>http://translate.sourceforge.net/wiki/virtaal</a>.
-
-</li><li> po.vim—ftplugin for the Vim editor. The best option for
people who
-use Vim as their editor. See
-<a
href="http://www.vim.org/scripts/script.php?script_id=2530";>http://www.vim.org/scripts/script.php?script_id=2530</a>.
-
-</li><li> Various web-based editors. See <a
href="http://www.gnu.org/software/trans-coord/manual/web-trans/web-trans.html#Savannah-VCS";>Savannah
VCS</a> in <cite>GNU Web
-Translators Manual</cite>.
-</li></ul>
-
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top">• <a href="#New-Translation"
accesskey="1">New Translation</a>:</td><td> </td><td align="left"
valign="top">How to start a new translation.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Migrating"
accesskey="2">Migrating</a>:</td><td> </td><td align="left"
valign="top">How to migrate an existing translation to a PO
- format under GNUN’s control.
-</td></tr>
-<tr><td align="left" valign="top">• <a href="#GNU-News" accesskey="3">GNU
News</a>:</td><td> </td><td align="left" valign="top">How to handle
“whatsnew” (a.k.a. “gnunews”).
+<tr><td align="left" valign="top">• <a href="#PO-Tips" accesskey="2">PO
Tips</a>:</td><td> </td><td align="left" valign="top">Tips and hints
for translators.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#PO-Tips" accesskey="4">PO
Tips</a>:</td><td> </td><td align="left" valign="top">Tips and hints
for translators.
+<tr><td align="left" valign="top">• <a href="#Migrating"
accesskey="3">Migrating</a>:</td><td> </td><td align="left"
valign="top">How to migrate an existing translation to a PO
+ format under GNUN’s control.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#generic_002eLANG_002ehtml"
accesskey="5">generic.LANG.html</a>:</td><td> </td><td align="left"
valign="top">Specifying information that will propagate in
+<tr><td align="left" valign="top">• <a href="#generic_002eLANG_002ehtml"
accesskey="4">generic.LANG.html</a>:</td><td> </td><td align="left"
valign="top">Specifying information that will propagate in
every translation in a certain language.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#languages_002etxt"
accesskey="6">languages.txt</a>:</td><td> </td><td align="left"
valign="top">Specifying canonical names for languages.
+<tr><td align="left" valign="top">• <a href="#languages_002etxt"
accesskey="5">languages.txt</a>:</td><td> </td><td align="left"
valign="top">Specifying canonical names for languages.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#PO-Files-and-Team"
accesskey="7">PO Files and Team</a>:</td><td> </td><td align="left"
valign="top">How to maintain translations in the team’s
+<tr><td align="left" valign="top">• <a href="#PO-Files-and-Team"
accesskey="6">PO Files and Team</a>:</td><td> </td><td align="left"
valign="top">How to maintain translations in the team’s
repository.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Compendia"
accesskey="8">Compendia</a>:</td><td> </td><td align="left"
valign="top">Using translation memory.
+<tr><td align="left" valign="top">• <a href="#Compendia"
accesskey="7">Compendia</a>:</td><td> </td><td align="left"
valign="top">Using translation memory.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#GNU-News" accesskey="8">GNU
News</a>:</td><td> </td><td align="left" valign="top">Obsolete: How
to handle “whatsnew”.
</td></tr>
<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
</pre></th></tr></table>
@@ -1214,7 +1183,7 @@
<a name="New-Translation"></a>
<div class="header">
<p>
-Next: <a href="#Migrating" accesskey="n" rel="next">Migrating</a>, Up: <a
href="#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#PO-Tips" accesskey="n" rel="next">PO Tips</a>, Up: <a
href="#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Starting-a-New-Translation"></a>
<h4 class="subsection">2.3.1 Starting a New Translation</h4>
@@ -1346,27 +1315,32 @@
<p>It is recommended that you wrap all lines in the comments to be less
than 80 lines; that looks better from a purely aesthetic point of view
and improves the performance of <samp>GNUmakefile.team</samp>’s
<code>publish</code>
-rule (see <a href="#GNUmakefile_002eteam-Variables">GNUmakefile.team
Variables</a>).
+rule (see <a href="#publish">publish</a>).
</p>
<p>There are some special messages that appear in the POT and PO:
</p>
<dl compact="compact">
<dd><a name="index-notes_002c-translators"></a>
<a name="index-translators_0027-notes"></a>
-</dd>
+<a name="GNUN-Slots"></a></dd>
<dt>‘<samp>*GNUN-SLOT: TRANSLATOR'S NOTES*</samp>’</dt>
<dd><p>This is for translator’s notes that are injected in the resulting
translation. See <a href="#Notes-Slot">Notes Slot</a>, for more information.
If your
translation does not have notes, you <em>must</em> translate this as a
-space, that is, <tt class="key">SPC</tt>.
+space:
</p>
+<div class="example">
+<pre class="example">msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
+msgstr " "
+</pre></div>
+
<a name="index-credits_002c-translators"></a>
<a name="index-translators_0027-credits"></a>
</dd>
<dt>‘<samp>*GNUN-SLOT: TRANSLATOR'S CREDITS*</samp>’</dt>
<dd><p>This is again optional, and should contain the name (and address) of
the person who made the translation. “Translate” this string as a
-space (<tt class="key">SPC</tt>) if you do not want your name to appear there.
+space if you do not want your name to appear there.
See <a href="#Credits-Slot">Credits Slot</a>.
</p></dd>
</dl>
@@ -1517,13 +1491,94 @@
Style Sheet when adding URIs or other information.
</p>
<hr>
+<a name="PO-Tips"></a>
+<div class="header">
+<p>
+Next: <a href="#Migrating" accesskey="n" rel="next">Migrating</a>, Previous:
<a href="#New-Translation" accesskey="p" rel="previous">New Translation</a>,
Up: <a href="#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Useful-Hints-for-Editing-PO-Files"></a>
+<h4 class="subsection">2.3.2 Useful Hints for Editing PO Files</h4>
+<a name="index-tips_002c-translators"></a>
+<a name="index-recommendations_002c-PO-files"></a>
+
+<p>This section contains additional explanations, some in the form of
+advices and recommendations; not all of them are strictly related to
+PO files editing.
+</p>
+<ul>
+<li> When you install a new translation of an article (that is different
+from a server template), all you need to do is to add
+your PO file in the appropriate <samp>/po</samp> sub-directory.
+
+<p>In the next build, your
<samp><var>article</var>.<var>lang</var>.html</samp> will be
+built and the link to it will be added to the list of translations
+and propagate to all translations, provided
+that they are under GNUN’s control.
+</p>
+</li><li> If you don’t feel comfortable editing <samp>gnun.mk</samp>, do
not worry.
+Someone from the GNUN maintainers will notice and will amend
+<code>TEMPLATE_LINGUAS</code> for you, as appropriate.
+
+</li><li> Dealing with obsolete strings. Elements which are removed from the
+original articles appear in the PO files as “obsolete”
strings—the
+translation is not lost, but they are marked in a special way at the
+end of the PO file. You don’t have to update a PO file if it contains
+obsolete strings—do this only if it has “fuzzy” or
+“untranslated”, and of course when you want to improve the existing
+translated ones. Sometimes these obsolete strings are useful, and
+they can save time. For example, if you anticipate that the deleted
+text may reappear some time in the future, you can preserve the string
+and hopefully it would be marked as “fuzzy” when this happens.
+Failing that, you can still copy it and yank it at the appropriate
+place.
+
+</li><li> You can add comments to every message in a PO file—for example
if
+you want to remember that you have to do something, or to remind you
+why this particular message is translated in a special way. These
+comments do not appear in the generated HTML source.
+
+</li><li> Sometimes, especially when the original message contains many links,
+it is easier to copy it to <code>msgstr</code> and edit the latter by
+translating the English text. In PO mode, this is done by <kbd>C-j</kbd>.
+This is useful also for large chunks of text in <code><pre></code>
elements,
+which normally you would want to preserve verbatim.
+
+</li><li> If you translate “Free Software Foundation, Inc.” in
your native
+language in the copyright notice, then please prepend the English name
+to the <code><address></code>; otherwise it looks awkward in most
+languages. Example:
+
+<div class="example">
+<pre class="example"># type: Content of: <div><address>
+msgid "51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA"
+msgstr ""
+"Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, "
+"Boston, MA 02110-1301, USA"
+</pre></div>
+
+</li><li> 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;</samp>’ and this is a character from the
alphabet of your
+language, just write it as ‘<samp>ü</samp>’ directly.
+
+</li><li> Wrapping of <code>msgstr</code> using <kbd>M-q</kbd> in Emacs (or
other means) is
+considered harmful. It is best to leave GNUN (or more precisely, Po4a)
+to do the wrapping—that way all generated HTML translations will have
+predictable results. This will help tremendously for the conversion to
+other formats, like Texinfo. Also, note that not all elements are
+wrapped by default, so deliberately wrapping the text inside the
+<code>msgstr</code> could lead to an invalid page or a page that is valid, but
+is rendered incorrectly by the web browser.
+</li></ul>
+
+<hr>
<a name="Migrating"></a>
<div class="header">
<p>
-Next: <a href="#GNU-News" accesskey="n" rel="next">GNU News</a>, Previous: <a
href="#New-Translation" accesskey="p" rel="previous">New Translation</a>, Up:
<a href="#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#generic_002eLANG_002ehtml" accesskey="n"
rel="next">generic.LANG.html</a>, Previous: <a href="#PO-Tips" accesskey="p"
rel="previous">PO Tips</a>, Up: <a href="#PO-Files" accesskey="u" rel="up">PO
Files</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<a name="Transforming-Existing-Translation-in-PO-Format"></a>
-<h4 class="subsection">2.3.2 Transforming Existing Translation in PO
Format</h4>
+<h4 class="subsection">2.3.3 Transforming Existing Translation in PO
Format</h4>
<a name="index-migration_002c-translations"></a>
<a name="index-conversion-of-existing-translations"></a>
@@ -1573,7 +1628,7 @@
<p>You get <samp>foo.<var>lang</var>.po</samp> where all messages are marked as
“fuzzy” (unless you use a compendium); you still should make sure
that
the translations correspond to the original and remove those
“fuzzy”
-marks. The script adds differences against previous <code>msgid</code>s to
+marks. The script adds differences against “previous”
<code>msgid</code>s to
facilitate checking.
</p>
<p>There is no need to delete the existing HTML translation, GNUN will
@@ -1600,131 +1655,13 @@
translator returned in 2008 and continued maintaining it.
</p>
<hr>
-<a name="GNU-News"></a>
-<div class="header">
-<p>
-Next: <a href="#PO-Tips" accesskey="n" rel="next">PO Tips</a>, Previous: <a
href="#Migrating" accesskey="p" rel="previous">Migrating</a>, Up: <a
href="#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
-</div>
-<a name="Special-Handling-for-GNU-News"></a>
-<h4 class="subsection">2.3.3 Special Handling for GNU News</h4>
-<a name="index-gnunews"></a>
-<a name="index-whatsnew"></a>
-<a name="index-gnusflashes"></a>
-
-<p><strong>Pay attention:</strong> The practice of news handling that is
-described here has been obsolete for some time now, as they are being
-fed automatically from Planet GNU (<a
href="http://planet.gnu.org";>http://planet.gnu.org</a>).
-Nevertheless, the information below is accurate to the extent that the
-support for the old-fashioned way is still available.
-</p>
-<p>The GNU website has infrastructure for supporting “What’s
New”, also
-known as “GNU News”. Entries are added in a special plain text
-file, <samp>server/whatsnew.txt</samp> and are used to build
-<samp>server/whatsnew.include</samp> and <samp>gnusflashes.include</samp>. The
-former is used by <samp>server/whatsnew.html</samp>, while the latter was
-included in the homepage.
-</p>
-<p>GNUN has additional rules for building <samp>whatsnew.pot</samp>, which
-contains a combination of all necessary strings for
-<samp>server/whatsnew.<var>lang</var>.html</samp>,
-<samp>server/whatsnew.<var>lang</var>.include</samp> and
-<samp>gnusflashes.<var>lang</var>.include</samp>. There is nothing unusual in
this
-POT file, so it should be translated like any other. When you commit
-<samp>whatsnew.<var>lang</var>.po</samp>, it will be used to generate all three
-localized files.
-</p>
-<p>Note that localized RSS feeds are not supported on purpose, as it would
-be annoying for subscribers if new items appear in English and then once
-again translated.
-</p>
-<hr>
-<a name="PO-Tips"></a>
-<div class="header">
-<p>
-Next: <a href="#generic_002eLANG_002ehtml" accesskey="n"
rel="next">generic.LANG.html</a>, Previous: <a href="#GNU-News" accesskey="p"
rel="previous">GNU News</a>, Up: <a href="#PO-Files" accesskey="u" rel="up">PO
Files</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
-</div>
-<a name="Useful-Hints-for-Editing-PO-Files"></a>
-<h4 class="subsection">2.3.4 Useful Hints for Editing PO Files</h4>
-<a name="index-tips_002c-translators"></a>
-<a name="index-recommendations_002c-PO-files"></a>
-
-<p>This section contains additional explanations, some in the form of
-advices and recommendations; not all of them are strictly related to
-PO files editing.
-</p>
-<ul>
-<li> When you install a new translation of an article (that is different
-from a server template), all you need to do is to add
-your PO file in the appropriate <samp>/po</samp> sub-directory.
-
-<p>In the next build, your
<samp><var>article</var>.<var>lang</var>.html</samp> will be
-built and the link to it will be added to the list of translations
-and propagate to all translations, provided
-that they are under GNUN’s control.
-</p>
-</li><li> If you don’t feel comfortable editing <samp>gnun.mk</samp>, do
not worry.
-Someone from the GNUN maintainers will notice and will amend
-<code>TEMPLATE_LINGUAS</code> for you, as appropriate.
-
-</li><li> Dealing with obsolete strings. Elements which are removed from the
-original articles appear in the PO files as “obsolete”
strings—the
-translation is not lost, but they are marked in a special way at the
-end of the PO file. You don’t have to update a PO file if it contains
-obsolete strings—do this only if it has “fuzzy” or
-“untranslated”, and of course when you want to improve the existing
-translated ones. Sometimes these obsolete strings are useful, and
-they can save time. For example, if you anticipate that the deleted
-text may reappear some time in the future, you can preserve the string
-and hopefully it would be marked as “fuzzy” when this happens.
-Failing that, you can still copy it and yank it at the appropriate
-place.
-
-</li><li> You can add comments to every message in a PO file—for example
if
-you want to remember that you have to do something, or to remind you
-why this particular message is translated in a special way. These
-comments do not appear in the generated HTML source.
-
-</li><li> Sometimes, especially when the original message contains many links,
-it is easier to copy it to <code>msgstr</code> and edit the latter by
-translating the English text. In PO mode, this is done by <kbd>C-j</kbd>.
-This is useful also for large chunks of text in <code><pre></code>
elements,
-which normally you would want to preserve verbatim.
-
-</li><li> If you translate “Free Software Foundation, Inc.” in
your native
-language in the copyright notice, then please prepend the English name
-to the <code><address></code>; otherwise it looks awkward in most
-languages. Example:
-
-<div class="example">
-<pre class="example"># type: Content of: <div><address>
-msgid "51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA"
-msgstr ""
-"Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, "
-"Boston, MA 02110-1301, USA"
-</pre></div>
-
-</li><li> There is absolutely no reason to use HTML entities in translations
as a
-replacement for common non-ASCII characters. They are harder to write
-and serve no purpose.
-
-</li><li> Wrapping of <code>msgstr</code> using <kbd>M-q</kbd> in Emacs (or
other means) is
-considered harmful. It is best to leave GNUN (or more precisely, Po4a)
-to do the wrapping—that way all generated HTML translations will have
-predictable results. This will help tremendously for the conversion to
-other formats, like Texinfo. Also, note that not all elements are
-wrapped by default, so deliberately wrapping the text inside the
-<code>msgstr</code> could lead to an invalid page or a page that is valid, but
-is rendered incorrectly by the web browser.
-</li></ul>
-
-<hr>
<a name="generic_002eLANG_002ehtml"></a>
<div class="header">
<p>
-Next: <a href="#languages_002etxt" accesskey="n" rel="next">languages.txt</a>,
Previous: <a href="#PO-Tips" accesskey="p" rel="previous">PO Tips</a>, Up: <a
href="#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#languages_002etxt" accesskey="n" rel="next">languages.txt</a>,
Previous: <a href="#Migrating" accesskey="p" rel="previous">Migrating</a>, Up:
<a href="#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="The-generic_002elang_002ehtml-File"></a>
-<h4 class="subsection">2.3.5 The <samp>generic.<var>lang</var>.html</samp>
File</h4>
+<h4 class="subsection">2.3.4 The <samp>generic.<var>lang</var>.html</samp>
File</h4>
<a name="index-team-information"></a>
<a name="index-generic-notice_002c-translations"></a>
@@ -1760,7 +1697,7 @@
Next: <a href="#PO-Files-and-Team" accesskey="n" rel="next">PO Files and
Team</a>, Previous: <a href="#generic_002eLANG_002ehtml" accesskey="p"
rel="previous">generic.LANG.html</a>, Up: <a href="#PO-Files" accesskey="u"
rel="up">PO Files</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<a name="The-languages_002etxt-File"></a>
-<h4 class="subsection">2.3.6 The <samp>languages.txt</samp> File</h4>
+<h4 class="subsection">2.3.5 The <samp>languages.txt</samp> File</h4>
<p>The file <samp>server/gnun/languages.txt</samp> is used when generating
lists of translations; those lists are subsequently included in all
@@ -1801,7 +1738,7 @@
Next: <a href="#Compendia" accesskey="n" rel="next">Compendia</a>, Previous:
<a href="#languages_002etxt" accesskey="p" rel="previous">languages.txt</a>,
Up: <a href="#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Maintaining-Translations-in-Your-Team_0027s-Repository"></a>
-<h4 class="subsection">2.3.7 Maintaining Translations in Your Team’s
Repository</h4>
+<h4 class="subsection">2.3.6 Maintaining Translations in Your Team’s
Repository</h4>
<a name="index-project-repository"></a>
<a name="index-repository_002c-translation-project"></a>
<a name="index-team-maintenance"></a>
@@ -1841,11 +1778,12 @@
</pre></div>
<p>All members and the team leader commit in their project’s
-repository—when a translation is ready, the leader checks it in in the
-official ‘www’ repository. If an original article changes,
-a build could be invoked to synchronize (i.e. merge) the changes and
+repository—when a translation is ready, the leader checks it in the
+official ‘www’ repository. If an original article changes, a build
+could be invoked to synchronize (i.e. merge) the changes and
optionally automatically commit them so that the draft PO files are
-updated. A translator would then normally update the PO file, and
+updated; at the same time, automatic notifications are sent to the
+persons interested in particular translations<a name="DOCF6"
href="#FOOT6"><sup>6</sup></a>. A translator would then normally update the PO
file, and
commit it again in the project’s Sources repository, from where the
coordinator will pick it up and install it in ‘www’.
</p>
@@ -1882,10 +1820,6 @@
+--…
</pre></div>
-<a name="index-priorities_002emk-2"></a>
-<p>Add <samp>priorities.mk</samp> in order to make the <code>report</code>
target sort
-the files by priority.
-</p>
<p>The next sections explain how to adopt the makefile for your team and
how to invoke a “build”.
</p>
@@ -1905,13 +1839,15 @@
Next: <a href="#GNUmakefile_002eteam-Targets" accesskey="n"
rel="next">GNUmakefile.team Targets</a>, Up: <a href="#PO-Files-and-Team"
accesskey="u" rel="up">PO Files and Team</a> [<a href="#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a href="#Index"
title="Index" rel="index">Index</a>]</p>
</div>
<a name="Adopting-GNUmakefile_002eteam-for-a-Specific-Team"></a>
-<h4 class="subsubsection">2.3.7.1 Adopting <samp>GNUmakefile.team</samp> for a
Specific Team</h4>
+<h4 class="subsubsection">2.3.6.1 Adopting <samp>GNUmakefile.team</samp> for a
Specific Team</h4>
-<p>To adjust the makefile for your team, you need to edit two variables.
+<p>To adjust the makefile for your team, you need to edit the next
+variables.
</p>
<dl compact="compact">
<dt>‘<samp>TEAM</samp>’</dt>
<dd><p>Set this to the language code, like <code>bg</code> or
<code>pt-br</code>.
+It is autodetected if not defined.
</p>
</dd>
<dt>‘<samp>wwwdir</samp>’</dt>
@@ -1921,7 +1857,22 @@
repository at <samp>~/projects/www</samp>, the value of <code>wwwdir</code>
should
be <code>../www/</code> or <samp>/home/<var>user</var>/projects/www/</samp>.
Note the
slash at the end, it is important.
-</p></dd>
+</p>
+</dd>
+<dt>‘<samp>TEAM_URL_PREFIX</samp>’</dt>
+<dt>‘<samp>TEAM_URL_POSTFIX</samp>’</dt>
+<dd><p>These variables are used to transform the path to a file in team’s
+working copy into a URL for this file; they are only needed for
+automatic email notifications. It is expected that typically
+the URL will point to some sort of Web interface for the repository,
+for example,
+</p>
+<div class="example">
+<pre class="example">TEAM_URL_PREFIX :=
http://cvs.savannah.gnu.org/viewvc/*checkout*/www-bg/
+TEAM_URL_POSTFIX := ?root=www-bg
+</pre></div>
+
+</dd>
</dl>
<p>If two variants of one language share the same project and repository
@@ -1933,6 +1884,32 @@
of the build process.
</p>
<dl compact="compact">
+<dt>‘<samp>ADD_FUZZY_DIFF</samp>’</dt>
+<dd><p>The program to manage differences to “previous”
<code>msgid</code>s added to
+“fuzzy” translations when merging PO files. When undefined,
+the makefile tries to find <code>gnun-add-fuzzy-diff</code> and assigns
+the result to this variable. See <a
href="#gnun_002dadd_002dfuzzy_002ddiff">gnun-add-fuzzy-diff</a>.
+</p>
+<p>Define to empty string to disable the feature.
+</p>
+</dd>
+<dt>‘<samp>NOTIFICATION_PERIOD=<var>days</var></samp>’</dt>
+<dd><a name="index-NOTIFICATION_005fPERIOD"></a>
+<a name="index-reminder-period_002c-default"></a>
+<a name="index-notification-period_002c-default"></a>
+<p>Default period of reminders sent by the <code>notify</code> target.
+</p>
+<a name="index-mail_002c-notifications-1"></a>
+<a name="index-NOTIFY-1"></a>
+</dd>
+<dt>‘<samp>NOTIFY=yes</samp>’</dt>
+<dd><p>Make the <code>notify</code> target actually send notifications.
+</p>
+</dd>
+<dt>‘<samp>NOTIFY=no</samp>’</dt>
+<dd><p>Do not send email notifications about errors. This is the default.
+</p>
+</dd>
<dt>‘<samp>VERBOSE=yes</samp>’</dt>
<dd><p>Print more information from <code>cvs</code>, <code>svn</code> and
<code>msgmerge</code>; off by default. Note that <code>VERBOSE</code> can be
@@ -1960,7 +1937,7 @@
Next: <a href="#GNUmakefile_002eteam-and-Cron" accesskey="n"
rel="next">GNUmakefile.team and Cron</a>, Previous: <a
href="#GNUmakefile_002eteam-Variables" accesskey="p"
rel="previous">GNUmakefile.team Variables</a>, Up: <a href="#PO-Files-and-Team"
accesskey="u" rel="up">PO Files and Team</a> [<a href="#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a href="#Index"
title="Index" rel="index">Index</a>]</p>
</div>
<a name="Targets-in-GNUmakefile_002eteam"></a>
-<h4 class="subsubsection">2.3.7.2 Targets in <samp>GNUmakefile.team</samp></h4>
+<h4 class="subsubsection">2.3.6.2 Targets in <samp>GNUmakefile.team</samp></h4>
<dl compact="compact">
<dt><code>update</code></dt>
@@ -1976,8 +1953,98 @@
</p>
</dd>
<dt><code>report</code></dt>
-<dd><p>Verifies which translations are complete, and prints a list (with
-statistics) of those that need to be updated.
+<dd><a name="report-in-GNUmakefile_002eteam"></a><p>Verifies which
translations are complete, and prints a list (with
+statistics) of those that need to be updated. Also, it reports
+the translations that are not consistent with the revisions from
+<em>www</em> repository.
+</p>
+<p>More fine-grained notifications are implemented as the <code>notify</code>
+target.
+</p>
+</dd>
+<dt><code>notify</code></dt>
+<dd><a name="index-outdated-translations_002c-notifications"></a>
+<p>Invokes the <code>report</code> target, filters its output for different
+translators and sends them notifications.
+</p>
+<p>As an addition to the output of the <code>report</code> target, URLs for
+relevant files are written; also, when <em>www</em> and team revisions
+are not consistent, their differences generated with
+<code>gnun-diff-po</code> are optionally attached (see <a
href="#gnun_002ddiff_002dpo">gnun-diff-po</a>,
+for more details).
+</p>
+<a name="index-nottab"></a>
+<p>The list of files to report against are configured with <samp>nottab</samp>
+file. The lines of this file that begin with ‘#’ are ignored;
+other lines should contain two fields separated by ‘:’.
+</p>
+<p>The first field is an extended grep regular expression; the files are
+selected for the report if their names match this expression.
+See <a
href="http://www.gnu.org/software/grep/manual/grep.html#Regular-Expressions";>Regular
Expressions</a> in <cite>GNU Grep manual</cite>.
+</p>
+<p>The second field is a space-separated list of single-word translators’
+identifiers for which the line applies. The file may look like this:
+</p>
+<div class="example">
+<pre class="example">^gnu/gnu-history: alice bob carol
+^distros/(common-distros|distros|screenshot): dan alice
+^(licenses|philosophy)/: eve bob frank
+^licenses/: dan
+</pre></div>
+
+<a name="index-email_002daliases"></a>
+<p>Email addresses of the translators are kept in a separate file,
+<samp>email-aliases</samp>. Like <samp>nottab</samp>, this file contains lines
+separated by ‘:’; the lines beginning with ‘#’ are
ignored.
+</p>
+<p>The first field is translators’ identifier, the second is
+space-separated list of translators’ email addresses. These two
+fields are mandatory.
+</p>
+<a name="index-reminder-period"></a>
+<a name="index-notification-period"></a>
+<p>The third field is the personal reminder period in days. After that
+period the message is sent again even though its contents don’t
+change. Otherwise, the <code>notify</code> target only sends messages when
+something changes. Naturally, no message is sent when no action
+is needed in the requested set of translations.
+</p>
+<p>The team-wide default period is defined in its GNUmakefile.team using
+the <code>NOTIFICATION_PERIOD</code> variable.
+</p>
+<p>The fourth field provides comma-separated options for the report.
+Currently recognized options are:
+</p>
+<dl compact="compact">
+<dt><code>no-diffs</code></dt>
+<dd><p>Disables sending <em>www</em> vs. <em>www-<var>lang</var></em>
differences
+as attachments.
+</p>
+</dd>
+<dt><code>www</code></dt>
+<dd><p>Report cases that suggest actions by the team leader, that is,
+when the translation in the team repository is full whereas
+in <em>www</em> it is incomplete or absent.
+</p></dd>
+</dl>
+
+<p>This is an example of <samp>email-aliases</samp>:
+</p>
+<div class="example">
+<pre class="example">alice:address@hidden address@hidden
+# Disable `dan' temporarily.
+#dan:address@hidden:5:no-diffs,www
+bob:address@hidden:3
+# Note that the third field is empty; the default value for period
+# will be used.
+carol:address@hidden address@hidden::no-diffs
+eve:address@hidden:2:www
+frank:address@hidden:1:www,no-diffs
+</pre></div>
+
+<p>The <samp>email-aliases</samp> file should be kept privately because it
+may contain personal email addresses of people. How to do this
+is out of scope of GNUN and this manual.
</p>
</dd>
<dt><code>format</code></dt>
@@ -1997,7 +2064,7 @@
</p>
</dd>
<dt><code>publish</code></dt>
-<dd><p>The <code>publish</code> rule’s task is to copy all modified
files to the
+<dd><a name="publish"></a><p>The <code>publish</code> rule’s task is to
copy all modified files to the
official <em>www</em> repository. It depends on the <code>format</code> target
to ensure that all files are re-wrapped to the standard line length
limit, but deliberately does not depend on <code>sync VCS=yes</code>.
@@ -2005,7 +2072,7 @@
files are in a satisfactory condition to be published, and this rule is
just a convenience to avoid multiple manual <code>cp</code> invocations.
As a rule of thumb, before running this rule it is sane to run
-<code>sync</code> and correct any <em>fuzzy</em> messages and other problems,
if
+<code>sync</code> and correct any “fuzzy” messages and other
problems, if
necessary.
</p>
<p>The <code>publish</code> rule does not depend on <code>sync</code>
explicitly,
@@ -2037,9 +2104,7 @@
</dd>
<dt><code>clean</code></dt>
-<dd><p>Deletes all backup and auto-generated files that some PO editors leave
-behind, namely—<samp><var>file</var>.po~</samp>,
<samp><var>file</var>.po.bak</samp> and
-<samp><var>file</var>.mo</samp>.
+<dd><p>Deletes all backup and auto-generated files.
</p></dd>
</dl>
@@ -2047,14 +2112,11 @@
To check the status of the translations, run <code>make report</code>.
</p>
<p>Feel free to replace all strings with equivalents in your native
-language and of course—do not hesitate to extend this file and modify
-it as much as you like. For example, useful extra functionality would
-be a target that will check which files have not yet been committed in
-the official repository, or which files have to be updated there
-(i.e. they were updated by the team members but not installed by the
-coordinator). Either way, if you come up with something interesting, it
-would be nice to send a message to <a
href="mailto:address@hidden";>address@hidden</a>, so that
-<samp>GNUmakefile.team</samp> gets updated for all teams’ benefit.
+language and of course—do not hesitate to extend this file and
+modify it as much as you like. If you come up with
+something interesting, it would be nice to send a message to
+<a href="mailto:address@hidden";>address@hidden</a>, so that
<samp>GNUmakefile.team</samp> gets
+updated for all teams’ benefit.
</p>
<hr>
<a name="GNUmakefile_002eteam-and-Cron"></a>
@@ -2063,7 +2125,7 @@
Previous: <a href="#GNUmakefile_002eteam-Targets" accesskey="p"
rel="previous">GNUmakefile.team Targets</a>, Up: <a href="#PO-Files-and-Team"
accesskey="u" rel="up">PO Files and Team</a> [<a href="#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a href="#Index"
title="Index" rel="index">Index</a>]</p>
</div>
<a name="Automatic-Synchronization-and-Status-Reports"></a>
-<h4 class="subsubsection">2.3.7.3 Automatic Synchronization and Status
Reports</h4>
+<h4 class="subsubsection">2.3.6.3 Automatic Synchronization and Status
Reports</h4>
<a name="index-team-maintenance_002c-cron"></a>
<a name="index-cron_002c-team-maintenance"></a>
@@ -2098,10 +2160,10 @@
<a name="Compendia"></a>
<div class="header">
<p>
-Previous: <a href="#PO-Files-and-Team" accesskey="p" rel="previous">PO Files
and Team</a>, Up: <a href="#PO-Files" accesskey="u" rel="up">PO Files</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
+Next: <a href="#GNU-News" accesskey="n" rel="next">GNU News</a>, Previous: <a
href="#PO-Files-and-Team" accesskey="p" rel="previous">PO Files and Team</a>,
Up: <a href="#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Using-Compendia"></a>
-<h4 class="subsection">2.3.8 Using Compendia</h4>
+<h4 class="subsection">2.3.7 Using Compendia</h4>
<a name="index-compendia"></a>
<a name="index-translation-memory"></a>
<a name="index-exclude_002epot"></a>
@@ -2148,6 +2210,44 @@
contains the string, it won’t be added to <samp>compendium.pot</samp>.
</p>
<hr>
+<a name="GNU-News"></a>
+<div class="header">
+<p>
+Previous: <a href="#Compendia" accesskey="p" rel="previous">Compendia</a>, Up:
<a href="#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Special-Handling-for-GNU-News"></a>
+<h4 class="subsection">2.3.8 Special Handling for GNU News</h4>
+<a name="index-gnunews"></a>
+<a name="index-whatsnew"></a>
+<a name="index-gnusflashes"></a>
+
+<p><strong>Pay attention:</strong> The practice of news handling that is
+described here has been obsolete for some time now, as they are being
+fed automatically from Planet GNU (<a
href="http://planet.gnu.org";>http://planet.gnu.org</a>).
+Nevertheless, the information below is accurate to the extent that the
+support for the old-fashioned way is still available.
+</p>
+<p>The GNU website has infrastructure for supporting “What’s
New”, also
+known as “GNU News”. Entries are added in a special plain text
+file, <samp>server/whatsnew.txt</samp> and are used to build
+<samp>server/whatsnew.include</samp> and <samp>gnusflashes.include</samp>. The
+former is used by <samp>server/whatsnew.html</samp>, while the latter was
+included in the homepage.
+</p>
+<p>GNUN has additional rules for building <samp>whatsnew.pot</samp>, which
+contains a combination of all necessary strings for
+<samp>server/whatsnew.<var>lang</var>.html</samp>,
+<samp>server/whatsnew.<var>lang</var>.include</samp> and
+<samp>gnusflashes.<var>lang</var>.include</samp>. There is nothing unusual in
this
+POT file, so it should be translated like any other. When you commit
+<samp>whatsnew.<var>lang</var>.po</samp>, it will be used to generate all three
+localized files.
+</p>
+<p>Note that localized RSS feeds are not supported on purpose, as it would
+be annoying for subscribers if new items appear in English and then once
+again translated.
+</p>
+<hr>
<a name="Webmaster-Tips"></a>
<div class="header">
<p>
@@ -2167,11 +2267,10 @@
important to have as many and as better as possible translations, and
you don’t have to make titanic efforts to help.
</p>
-<p>If you plan to edit a certain page extensively, please do so within the
-period between two adjacent GNUN builds—i.e. within a day. That way,
-the POT will be regenerated only once, and translators who are quick to
-update it immediately won’t be disappointed if it changes again in the
-next run.
+<p>If you plan to edit a certain page extensively, please do so within a
+reasonable time frame, for example a day or preferably, several hours.
+That way, the translators who are quick to update it immediately won’t
+be disappointed if the POT changes again in the next GNUN run(s).
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top">• <a href="#Validation"
accesskey="1">Validation</a>:</td><td> </td><td align="left"
valign="top">How to verify the documents.
@@ -2350,20 +2449,189 @@
of programs that may also be useful for the translators.
</p>
<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top">• <a href="#Scripts"
accesskey="1">Scripts</a>:</td><td> </td><td align="left"
valign="top">Helper scripts.
+<tr><td align="left" valign="top">• <a href="#Files-and-Directories"
accesskey="1">Files and Directories</a>:</td><td> </td><td
align="left" valign="top">What, where, when.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Rules"
accesskey="2">Rules</a>:</td><td> </td><td align="left"
valign="top">The knotty rules explained.
+<tr><td align="left" valign="top">• <a href="#Scripts"
accesskey="2">Scripts</a>:</td><td> </td><td align="left"
valign="top">Helper scripts.
</td></tr>
</table>
<hr>
+<a name="Files-and-Directories"></a>
+<div class="header">
+<p>
+Next: <a href="#Scripts" accesskey="n" rel="next">Scripts</a>, Up: <a
href="#Internals" accesskey="u" rel="up">Internals</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Files-and-Directories-1"></a>
+<h3 class="section">3.1 Files and Directories</h3>
+
+<p>This is a brief diagram of <em>www</em> working copy; note that in this
+section we don’t describe the files out of GNUN control, including the
+old HTML-only translations.
+</p>
+<div class="example">
+<pre class="example">Legend:
+* The file is maintained locally, without committing it to CVS.
+# The file is edited manually.
+@ The file is regenerated automatically.
+% The file is edited both manually and automatically.
+#/@ The file is generated automatically, but outside of GNUN.
+
+</pre><pre class="example">Root/
+ |
+ +--gnu/
+ | |
+ | |
+ | +--linux-and-gnu.html #
+ | +--linux-and-gnu.<var>lang</var>.html @
+ | +--manifesto.html #
+ | +--manifesto.<var>lang</var>.html @
+ | +--…
+ | |
+ | +--------------------------po/
+ | |
+ +--home.html # +--manifesto.<var>lang</var>.po %
+ +--home.<var>lang</var>.html @ +--manifesto.pot @
+ +--planetfeeds.html #/@ +--manifesto.proto * @
+ +--planetfeeds.<var>lang</var>.html @ +--manifesto.translist @
+ +--po/ +--manifesto.<var>lang</var>.m4 * @
+ | | +--manifesto.<var>lang</var>-en.html @
+ | +--home.pot @ +--manifesto.<var>lang</var>-diff.html @
+ | +--home.proto * @ +--linux-and-gnu.<var>lang</var>.po %
+ | +--home.translist @ +--…
+ | +--home.<var>lang</var>.po %
+ | +--home.<var>lang</var>.m4 * @
+ | +--home.<var>lang</var>-en.html @
+ | +--home.<var>lang</var>-diff.html @
+ | +--planetfeeds.proto * @
+ | +--planetfeeds.pot.opt @
+ | +--planetfeeds.<var>lang</var>.po %
+ | +--…
+ |
+ +--server/
+ | |
+ | +-------------------------gnun/
+ | | |
+ | +--sitemap.html #/@ +--GNUmakefile * #
+ | +--sitemap.<var>lang</var>.html @ +--config.mk * #
+ | +--po/ +--gnun.mk #
+ | | | +--languages.txt #
+ | | +--sitemap.pot @ +--generic.<var>lang</var>.html #
+ | | +--sitemap.proto * @ +--compendia/
+ | | +--sitemap.<var>lang</var>.po % |
+ | | +--sitemap.<var>lang</var>.m4 @ +--master.<var>lang</var>.po #
+ | | +--body-include-2.pot @ +--compendium.<var>lang</var>.po @
+ | | +--body-include-2.proto * @ +--excluded.pot #
+ | | +--body-include-2.<var>lang</var>.po %
+ | | +--…
+ | |
+ | +--body-include-2.html #
+ | +--body-include-2.<var>lang</var>.html @
+ | +--…
+ +--…
+</pre></div>
+
+<p>A description of some files follows.
+</p>
+<dl compact="compact">
+<dt><samp>…/<var>file</var>.html</samp></dt>
+<dd><p>The English files.
+</p>
+</dd>
+<dt><samp>…/<var>file</var>.<var>lang</var>.html</samp></dt>
+<dd><p>The <var>lang</var> translation of
<samp>…/<var>file</var>.html</samp>.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.proto</samp></dt>
+<dd><p>Intermediate files generated from <samp><var>file</var>.html</samp>;
they are
+used only internally. Essentially, GNUN inserts its special slots and
+instructions to include the <samp>generic.<var>lang</var>.html</samp> file.
+See <a href="#GNUN-Slots">GNUN Slots</a>, and <a
href="#generic_002eLANG_002ehtml">generic.LANG.html</a>.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.translist</samp></dt>
+<dd><p>The list of trasnlations for
<samp>…/<var>file</var>.html</samp>. It is
+included in <samp>…/<var>file</var>.html</samp> all its translations.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.pot</samp></dt>
+<dd><p>PO templates for articles and included files.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.pot.opt</samp></dt>
+<dd><p>POTs of optional templates (currently,
<samp>planetfeeds.pot.opt</samp>).
+See <a href="#optional_002dtemplates">optional-templates</a>, for more details.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.<var>lang</var>.po</samp></dt>
+<dd><p>Translations of <samp><var>file</var>.pot</samp> or
<samp><var>file</var>.pot.opt</samp>
+committed by the translators and merged by GNUN.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.<var>lang</var>.m4</samp></dt>
+<dd><p>Intermediate files from which
<samp><var>file</var>.<var>lang</var>.html</samp> are
+generated.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.<var>lang</var>-en.html</samp></dt>
+<dd><p>The latest revision of the English file for which a full translation
+into <var>lang</var> language was provided.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.<var>lang</var>-diff.html</samp></dt>
+<dd><p>The highlighted differences between the current version of
+<samp>…<var>file</var>.html</samp> and
+<samp>…/po/<var>file</var>.<var>lang</var>-en.html</samp>.
+</p>
+</dd>
+<dt><samp>planetfeeds.html</samp></dt>
+<dd><p>A list of news; it is automatically generated outside of GNUN.
+For GNUN, it is an optional template.
+</p>
+</dd>
+<dt><samp>server/</samp></dt>
+<dd><p>Most template SSI files are located in this directory.
+</p>
+</dd>
+<dt><samp>server/sitemap.html</samp></dt>
+<dd><p>The sitemap; it is generated automatically by a script that is not
+included in GNUN. GNUN currently treats it like a regular article.
+</p>
+</dd>
+<dt><samp>server/gnun/</samp></dt>
+<dd><p>The directory for GNUN files.
+</p>
+</dd>
+<dt><samp>server/gnun/GNUmakefile</samp></dt>
+<dt><samp>server/gnun/config.mk</samp></dt>
+<dd><p>These files are maintained locally. They are used to rebuild the
+translations. See <a href="#Invoking-GNUN">Invoking GNUN</a>.
+</p>
+</dd>
+<dt><samp>server/gnun/gnun.mk</samp></dt>
+<dd><p>The file that defines the list of files to build. See <a
href="#Main-Variables">Main Variables</a>.
+</p>
+</dd>
+<dt><samp>server/gnun/languages.txt</samp></dt>
+<dd><p>See <a href="#languages_002etxt">languages.txt</a>.
+</p>
+</dd>
+<dt><samp>server/gnun/generic.<var>lang</var>.html</samp></dt>
+<dd><p>See <a href="#generic_002eLANG_002ehtml">generic.LANG.html</a>.
+</p>
+</dd>
+<dt><samp>server/gnun/compendia</samp></dt>
+<dd><p>The directory for compendia. See <a href="#Compendia">Compendia</a>.
+</p></dd>
+</dl>
+
+<hr>
<a name="Scripts"></a>
<div class="header">
<p>
-Next: <a href="#Rules" accesskey="n" rel="next">Rules</a>, Up: <a
href="#Internals" accesskey="u" rel="up">Internals</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="#Files-and-Directories" accesskey="p" rel="previous">Files
and Directories</a>, Up: <a href="#Internals" accesskey="u"
rel="up">Internals</a> [<a href="#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<a name="GNUN-Scripts"></a>
-<h3 class="section">3.1 GNUN Scripts</h3>
+<h3 class="section">3.2 GNUN Scripts</h3>
<p>For the time being there are several helper scripts. Some of them are
used internally as commands with certain arguments in the makefile
@@ -2372,7 +2640,7 @@
They all can be invoked separately, as stand-alone programs.
</p>
<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top">• <a
href="#gnun_002dadd_002dfuzzy_002ddiff"
accesskey="1">gnun-add-fuzzy-diff</a>:</td><td> </td><td
align="left" valign="top">Add differences to previous
+<tr><td align="left" valign="top">• <a
href="#gnun_002dadd_002dfuzzy_002ddiff"
accesskey="1">gnun-add-fuzzy-diff</a>:</td><td> </td><td
align="left" valign="top">Add differences to “previous”
<code>msgid</code>s.
</td></tr>
<tr><td align="left" valign="top">• <a href="#gnun_002ddiff_002dpo"
accesskey="2">gnun-diff-po</a>:</td><td> </td><td align="left"
valign="top">Compare two revisions of a PO file.
@@ -2403,11 +2671,11 @@
Next: <a href="#gnun_002ddiff_002dpo" accesskey="n"
rel="next">gnun-diff-po</a>, Up: <a href="#Scripts" accesskey="u"
rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<a name="The-gnun_002dadd_002dfuzzy_002ddiff-Script"></a>
-<h4 class="subsection">3.1.1 The <code>gnun-add-fuzzy-diff</code> Script</h4>
+<h4 class="subsection">3.2.1 The <code>gnun-add-fuzzy-diff</code> Script</h4>
<a name="index-previous_002c-diff-1"></a>
<p>This script adds comments with differences of current <code>msgid</code>s
-against previous ones to fuzzy translations in a PO file. To produce
+against “previous” ones to “fuzzy” translations in a
PO file. To produce
the differences <code>wdiff</code> is used. This may be useful to figure
out what has changed. In fact, it wraps around a <code>sed</code> script
used in GNUN internally.
@@ -2438,7 +2706,7 @@
Next: <a href="#gnun_002dinit_002dpo" accesskey="n"
rel="next">gnun-init-po</a>, Previous: <a
href="#gnun_002dadd_002dfuzzy_002ddiff" accesskey="p"
rel="previous">gnun-add-fuzzy-diff</a>, Up: <a href="#Scripts" accesskey="u"
rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<a name="The-gnun_002ddiff_002dpo-Script"></a>
-<h4 class="subsection">3.1.2 The <code>gnun-diff-po</code> Script</h4>
+<h4 class="subsection">3.2.2 The <code>gnun-diff-po</code> Script</h4>
<a name="index-comparing_002c-translations"></a>
<p>This script compares two versions of a PO file. It produces a HTML page
@@ -2489,7 +2757,7 @@
Next: <a href="#gnun_002dpreconvert" accesskey="n"
rel="next">gnun-preconvert</a>, Previous: <a href="#gnun_002ddiff_002dpo"
accesskey="p" rel="previous">gnun-diff-po</a>, Up: <a href="#Scripts"
accesskey="u" rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table
of contents" rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<a name="The-gnun_002dinit_002dpo-Script"></a>
-<h4 class="subsection">3.1.3 The <code>gnun-init-po</code> Script</h4>
+<h4 class="subsection">3.2.3 The <code>gnun-init-po</code> Script</h4>
<a name="index-initializing_002c-translations"></a>
<p>This script initializes a PO file using POT generated with GNUN,
@@ -2511,7 +2779,7 @@
</dd>
<dt><samp>-d</samp></dt>
<dt><samp>--disable-diffs</samp></dt>
-<dd><p>Don’t add diffs to previous messages.
+<dd><p>Don’t add diffs to “previous” messages.
</p>
</dd>
<dt><samp>-g</samp></dt>
@@ -2540,7 +2808,7 @@
</dl>
<p>The PO file name is guessed from the name of POT and language
-suffix; the file is created in current working directory.
+suffix; the file is created in the current working directory.
</p>
<hr>
<a name="gnun_002dpreconvert"></a>
@@ -2549,7 +2817,7 @@
Next: <a href="#gnun_002dmerge_002dpreconverted" accesskey="n"
rel="next">gnun-merge-preconverted</a>, Previous: <a
href="#gnun_002dinit_002dpo" accesskey="p" rel="previous">gnun-init-po</a>, Up:
<a href="#Scripts" accesskey="u" rel="up">Scripts</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="The-gnun_002dpreconvert-Script"></a>
-<h4 class="subsection">3.1.4 The <code>gnun-preconvert</code> Script</h4>
+<h4 class="subsection">3.2.4 The <code>gnun-preconvert</code> Script</h4>
<a name="index-migration_002c-translations-1"></a>
<a name="index-conversion-of-existing-translations-1"></a>
@@ -2585,13 +2853,13 @@
Next: <a href="#gnun_002dreport" accesskey="n" rel="next">gnun-report</a>,
Previous: <a href="#gnun_002dpreconvert" accesskey="p"
rel="previous">gnun-preconvert</a>, Up: <a href="#Scripts" accesskey="u"
rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<a name="The-gnun_002dmerge_002dpreconverted-Script"></a>
-<h4 class="subsection">3.1.5 The <code>gnun-merge-preconverted</code>
Script</h4>
+<h4 class="subsection">3.2.5 The <code>gnun-merge-preconverted</code>
Script</h4>
<a name="index-migration_002c-translations-2"></a>
<a name="index-conversion-of-existing-translations-2"></a>
<p>This script takes <code>po4a-gettextize</code> output, adds current
<code>msgid</code>s as “previous” values, merges the file with the
new
-POT, and adds differences against previous values like
+POT, and adds differences against “previous” values like
<code>gnun-add-fuzzy-diff</code> does.
</p>
<div class="example">
@@ -2621,7 +2889,7 @@
Next: <a href="#gnun_002dvalidate_002dhtml" accesskey="n"
rel="next">gnun-validate-html</a>, Previous: <a
href="#gnun_002dmerge_002dpreconverted" accesskey="p"
rel="previous">gnun-merge-preconverted</a>, Up: <a href="#Scripts"
accesskey="u" rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table
of contents" rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<a name="The-gnun_002dreport-Script"></a>
-<h4 class="subsection">3.1.6 The <code>gnun-report</code> Script</h4>
+<h4 class="subsection">3.2.6 The <code>gnun-report</code> Script</h4>
<a name="index-reporting-1"></a>
<a name="index-status_002c-translations-1"></a>
@@ -2630,7 +2898,7 @@
status (existing translations that need maintenance, untranslated
files, complete translations).
</p>
-<a name="index-priorities_002emk-3"></a>
+<a name="index-priorities_002emk-2"></a>
<p>The script depends on the presence of the <samp>priorities.mk</samp> file
in the <samp>server/gnun</samp> subdirectory of the working copy of
‘www’
repository.
@@ -2678,7 +2946,7 @@
Next: <a href="#mailfail" accesskey="n" rel="next">mailfail</a>, Previous: <a
href="#gnun_002dreport" accesskey="p" rel="previous">gnun-report</a>, Up: <a
href="#Scripts" accesskey="u" rel="up">Scripts</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="The-gnun_002dvalidate_002dhtml-Script"></a>
-<h4 class="subsection">3.1.7 The <code>gnun-validate-html</code> Script</h4>
+<h4 class="subsection">3.2.7 The <code>gnun-validate-html</code> Script</h4>
<a name="index-validation_002c-HTML_002c-XHTML"></a>
<p>This is a Bash script whose purpose is to “validate” both the
@@ -2730,8 +2998,8 @@
Next: <a href="#validate_002dhtml_002dnotify" accesskey="n"
rel="next">validate-html-notify</a>, Previous: <a
href="#gnun_002dvalidate_002dhtml" accesskey="p"
rel="previous">gnun-validate-html</a>, Up: <a href="#Scripts" accesskey="u"
rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<a name="The-mailfail-Script"></a>
-<h4 class="subsection">3.1.8 The <code>mailfail</code> Script</h4>
-<a name="index-mail_002c-notifications-1"></a>
+<h4 class="subsection">3.2.8 The <code>mailfail</code> Script</h4>
+<a name="index-mail_002c-notifications-2"></a>
<p>This is a helper script that runs a command, and mails the output of
that command in case it exits with a non-zero exit status.
@@ -2792,7 +3060,7 @@
Next: <a href="#gnun_002dclear_002dprevious" accesskey="n"
rel="next">gnun-clear-previous</a>, Previous: <a href="#mailfail" accesskey="p"
rel="previous">mailfail</a>, Up: <a href="#Scripts" accesskey="u"
rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<a name="The-validate_002dhtml_002dnotify-Script"></a>
-<h4 class="subsection">3.1.9 The <code>validate-html-notify</code> Script</h4>
+<h4 class="subsection">3.2.9 The <code>validate-html-notify</code> Script</h4>
<p>This script is a wrapper around <code>gnun-validate-html</code>
(see <a href="#gnun_002dvalidate_002dhtml">gnun-validate-html</a>); it is
necessary because it is hard to
@@ -2834,16 +3102,16 @@
Previous: <a href="#validate_002dhtml_002dnotify" accesskey="p"
rel="previous">validate-html-notify</a>, Up: <a href="#Scripts" accesskey="u"
rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<a name="The-gnun_002dclear_002dprevious-Script"></a>
-<h4 class="subsection">3.1.10 The <code>gnun-clear-previous</code> Script</h4>
+<h4 class="subsection">3.2.10 The <code>gnun-clear-previous</code> Script</h4>
<a name="index-previous_002c-manipulating-PO-files"></a>
<p>This simple script is not used internally in GNUN. It is merely for
convenience only, for those who find it hard to remember the various
‘<samp>gettext</samp>’ tools and their options.
</p>
-<p><code>gnun-clear-previous</code> deletes the <em>previous</em> messages in a
+<p><code>gnun-clear-previous</code> deletes the “previous”
messages in a
PO file, which is a good thing to do after the corresponding translation
-is updated and the <em>fuzzy</em> marker removed. It can also be used to
+is updated and the “fuzzy” marker removed. It can also be used to
wrap long lines in PO files.
</p>
<p>Usage:
@@ -2863,17 +3131,6 @@
</dl>
<hr>
-<a name="Rules"></a>
-<div class="header">
-<p>
-Previous: <a href="#Scripts" accesskey="p" rel="previous">Scripts</a>, Up: <a
href="#Internals" accesskey="u" rel="up">Internals</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
-</div>
-<a name="How-The-Recipes-Work"></a>
-<h3 class="section">3.2 How The Recipes Work</h3>
-
-<p>Read the source code, then please tell us :-)
-</p>
-<hr>
<a name="Bugs"></a>
<div class="header">
<p>
@@ -2978,6 +3235,7 @@
<tr><td></td><td valign="top"><a
href="#index-directories_002c-defining">directories,
defining</a>:</td><td> </td><td valign="top"><a
href="#Main-Variables">Main Variables</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Index_cp_letter-E">E</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-email_002daliases">email-aliases</a>:</td><td> </td><td
valign="top"><a href="#GNUmakefile_002eteam-Targets">GNUmakefile.team
Targets</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-exclude_002epot">exclude.pot</a>:</td><td> </td><td
valign="top"><a href="#Compendia">Compendia</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-extra_002dtemplates">extra-templates</a>:</td><td> </td><td
valign="top"><a href="#Main-Variables">Main Variables</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
@@ -3008,7 +3266,8 @@
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Index_cp_letter-M">M</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-mail_002c-notifications">mail,
notifications</a>:</td><td> </td><td valign="top"><a
href="#Runtime-Variables">Runtime Variables</a></td></tr>
-<tr><td></td><td valign="top"><a href="#index-mail_002c-notifications-1">mail,
notifications</a>:</td><td> </td><td valign="top"><a
href="#mailfail">mailfail</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-mail_002c-notifications-1">mail,
notifications</a>:</td><td> </td><td valign="top"><a
href="#GNUmakefile_002eteam-Variables">GNUmakefile.team Variables</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-mail_002c-notifications-2">mail,
notifications</a>:</td><td> </td><td valign="top"><a
href="#mailfail">mailfail</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-migration_002c-translations">migration,
translations</a>:</td><td> </td><td valign="top"><a
href="#Migrating">Migrating</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-migration_002c-translations-1">migration,
translations</a>:</td><td> </td><td valign="top"><a
href="#gnun_002dpreconvert">gnun-preconvert</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-migration_002c-translations-2">migration,
translations</a>:</td><td> </td><td valign="top"><a
href="#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a></td></tr>
@@ -3018,29 +3277,34 @@
<tr><td></td><td valign="top"><a
href="#index-new-translations_002c-notifications_002fannouncements">new
translations, notifications/announcements</a>:</td><td> </td><td
valign="top"><a href="#Runtime-Variables">Runtime Variables</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-notes_002c-translators">notes,
translators</a>:</td><td> </td><td valign="top"><a
href="#New-Translation">New Translation</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-notes_002c-translators-1">notes,
translators</a>:</td><td> </td><td valign="top"><a
href="#Notes-Slot">Notes Slot</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-notification-period">notification
period</a>:</td><td> </td><td valign="top"><a
href="#GNUmakefile_002eteam-Targets">GNUmakefile.team Targets</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-notification-period_002c-default">notification period,
default</a>:</td><td> </td><td valign="top"><a
href="#GNUmakefile_002eteam-Variables">GNUmakefile.team Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-NOTIFICATION_005fPERIOD">NOTIFICATION_PERIOD</a>:</td><td> </td><td
valign="top"><a href="#GNUmakefile_002eteam-Variables">GNUmakefile.team
Variables</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-NOTIFY">NOTIFY</a>:</td><td> </td><td valign="top"><a
href="#Runtime-Variables">Runtime Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-NOTIFY-1">NOTIFY</a>:</td><td> </td><td valign="top"><a
href="#GNUmakefile_002eteam-Variables">GNUmakefile.team Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-nottab">nottab</a>:</td><td> </td><td valign="top"><a
href="#GNUmakefile_002eteam-Targets">GNUmakefile.team Targets</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Index_cp_letter-O">O</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a
href="#index-optional_002dtemplates">optional-templates</a>:</td><td> </td><td
valign="top"><a href="#Main-Variables">Main Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-outdated-translations_002c-notifications">outdated translations,
notifications</a>:</td><td> </td><td valign="top"><a
href="#GNUmakefile_002eteam-Targets">GNUmakefile.team Targets</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-OUTDATED_002dGRACE">OUTDATED-GRACE</a>:</td><td> </td><td
valign="top"><a href="#Runtime-Variables">Runtime Variables</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-output_002c-detailed">output,
detailed</a>:</td><td> </td><td valign="top"><a
href="#Runtime-Variables">Runtime Variables</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Index_cp_letter-P">P</a></th><td></td><td></td></tr>
-<tr><td></td><td valign="top"><a href="#index-PO-editors">PO
editors</a>:</td><td> </td><td valign="top"><a href="#PO-Files">PO
Files</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-PO-headers">PO
headers</a>:</td><td> </td><td valign="top"><a href="#New-Translation">New
Translation</a></td></tr>
-<tr><td></td><td valign="top"><a href="#index-PO_002c-editing">PO,
editing</a>:</td><td> </td><td valign="top"><a href="#PO-Files">PO
Files</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-POT-generation_002c-articles">POT generation,
articles</a>:</td><td> </td><td valign="top"><a
href="#Main-Variables">Main Variables</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-previous_002c-diff">previous,
diff</a>:</td><td> </td><td valign="top"><a href="#Main-Variables">Main
Variables</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-previous_002c-diff-1">previous,
diff</a>:</td><td> </td><td valign="top"><a
href="#gnun_002dadd_002dfuzzy_002ddiff">gnun-add-fuzzy-diff</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-previous_002c-manipulating-PO-files">previous, manipulating PO
files</a>:</td><td> </td><td valign="top"><a
href="#gnun_002dclear_002dprevious">gnun-clear-previous</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-priorities_002emk">priorities.mk</a>:</td><td> </td><td
valign="top"><a href="#Invoking-GNUN">Invoking GNUN</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-priorities_002emk-1">priorities.mk</a>:</td><td> </td><td
valign="top"><a href="#report">report</a></td></tr>
-<tr><td></td><td valign="top"><a
href="#index-priorities_002emk-2">priorities.mk</a>:</td><td> </td><td
valign="top"><a href="#PO-Files-and-Team">PO Files and Team</a></td></tr>
-<tr><td></td><td valign="top"><a
href="#index-priorities_002emk-3">priorities.mk</a>:</td><td> </td><td
valign="top"><a href="#gnun_002dreport">gnun-report</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-priorities_002emk-2">priorities.mk</a>:</td><td> </td><td
valign="top"><a href="#gnun_002dreport">gnun-report</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-project-repository">project
repository</a>:</td><td> </td><td valign="top"><a
href="#PO-Files-and-Team">PO Files and Team</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Index_cp_letter-R">R</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a
href="#index-recommendations_002c-PO-files">recommendations, PO
files</a>:</td><td> </td><td valign="top"><a href="#PO-Tips">PO
Tips</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-reminder-period">reminder
period</a>:</td><td> </td><td valign="top"><a
href="#GNUmakefile_002eteam-Targets">GNUmakefile.team Targets</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-reminder-period_002c-default">reminder period,
default</a>:</td><td> </td><td valign="top"><a
href="#GNUmakefile_002eteam-Variables">GNUmakefile.team Variables</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-reporting">reporting</a>:</td><td> </td><td valign="top"><a
href="#report">report</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-reporting-1">reporting</a>:</td><td> </td><td valign="top"><a
href="#gnun_002dreport">gnun-report</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-reporting-bugs">reporting
bugs</a>:</td><td> </td><td valign="top"><a href="#Bugs">Bugs</a></td></tr>
@@ -3632,9 +3896,19 @@
manually (or via cron) to take care of effectively adding them to the
public repository. See <a href="#triggers">triggers</a>, for a short
explanation.</p>
<h3><a name="FOOT4" href="#DOCF4">(4)</a></h3>
+<p>These days we
+run a more complicated script instead of this cron job in order
+to address some exceptional situations like concurrent builds.</p>
+<h3><a name="FOOT5" href="#DOCF5">(5)</a></h3>
<p>Only because presumably, they are more familiar with
GNUnited Nations’ internals. From a purely technical point of view,
there is no difference.</p>
+<h3><a name="FOOT6" href="#DOCF6">(6)</a></h3>
+<p>The following
+sections describe in more details how to setup these automatic
+actions; however, if you have any difficulties with that, please ask
+the GNU Web Translation Managers to make it for your team using our
+server.</p>
</div>
<hr>
Index: gnun/gnun.html.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.html.gz,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
Binary files /tmp/cvsLET2j5 and /tmp/cvsNZe3Rw differ
Index: gnun/gnun.html_node.tar.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.html_node.tar.gz,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
Binary files /tmp/cvsTPRIW5 and /tmp/cvsd395vx differ
Index: gnun/gnun.info.tar.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.info.tar.gz,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
Binary files /tmp/cvspa3tj4 and /tmp/cvs4b83Tv differ
Index: gnun/gnun.pdf
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.pdf,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
Binary files /tmp/cvsLUASR4 and /tmp/cvsLTJaxw differ
Index: gnun/gnun.texi.tar.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.texi.tar.gz,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
Binary files /tmp/cvsst63Y6 and /tmp/cvsFyioGy differ
Index: gnun/gnun.txt
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.txt,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- gnun/gnun.txt 4 Dec 2012 16:24:20 -0000 1.17
+++ gnun/gnun.txt 27 Dec 2012 14:45:32 -0000 1.18
@@ -1,7 +1,7 @@
GNUnited Nations
1 Introduction to GNUnited Nations
- 1.1 Why GNUN is Being Developed
- 1.2 What GNUnited Nations is and Should be
+ 1.1 Why GNUN Is Being Developed
+ 1.2 What GNUnited Nations Is and Should Be
1.3 Major Advantages of GNUN
1.4 Known Bugs and Limitations
2 General Usage
@@ -14,21 +14,21 @@
2.1.2.4 The 'report' Target
2.1.2.5 The 'triggers' Target
2.1.2.6 The 'validate-all' Target
- 2.2 Defining Articles to be Built
+ 2.2 Defining Articles to Be Built
2.3 Working with PO Files
2.3.1 Starting a New Translation
2.3.1.1 The Special Slot for Translator's Notes
2.3.1.2 The Special Slot for Translator's Credits
- 2.3.2 Transforming Existing Translation in PO Format
- 2.3.3 Special Handling for GNU News
- 2.3.4 Useful Hints for Editing PO Files
- 2.3.5 The 'generic.LANG.html' File
- 2.3.6 The 'languages.txt' File
- 2.3.7 Maintaining Translations in Your Team's Repository
- 2.3.7.1 Adopting 'GNUmakefile.team' for a Specific Team
- 2.3.7.2 Targets in 'GNUmakefile.team'
- 2.3.7.3 Automatic Synchronization and Status Reports
- 2.3.8 Using Compendia
+ 2.3.2 Useful Hints for Editing PO Files
+ 2.3.3 Transforming Existing Translation in PO Format
+ 2.3.4 The 'generic.LANG.html' File
+ 2.3.5 The 'languages.txt' File
+ 2.3.6 Maintaining Translations in Your Team's Repository
+ 2.3.6.1 Adopting 'GNUmakefile.team' for a Specific Team
+ 2.3.6.2 Targets in 'GNUmakefile.team'
+ 2.3.6.3 Automatic Synchronization and Status Reports
+ 2.3.7 Using Compendia
+ 2.3.8 Special Handling for GNU News
2.4 Tips and Hints for Webmasters
2.4.1 Validation
2.4.2 Comments for Translators
@@ -36,25 +36,25 @@
2.4.4 Localized URLs
2.4.5 Splitting Long Passages
3 Unexciting Information for GNUN's Operation
- 3.1 GNUN Scripts
- 3.1.1 The 'gnun-add-fuzzy-diff' Script
- 3.1.2 The 'gnun-diff-po' Script
- 3.1.3 The 'gnun-init-po' Script
- 3.1.4 The 'gnun-preconvert' Script
- 3.1.5 The 'gnun-merge-preconverted' Script
- 3.1.6 The 'gnun-report' Script
- 3.1.7 The 'gnun-validate-html' Script
- 3.1.8 The 'mailfail' Script
- 3.1.9 The 'validate-html-notify' Script
- 3.1.10 The 'gnun-clear-previous' Script
- 3.2 How The Recipes Work
+ 3.1 Files and Directories
+ 3.2 GNUN Scripts
+ 3.2.1 The 'gnun-add-fuzzy-diff' Script
+ 3.2.2 The 'gnun-diff-po' Script
+ 3.2.3 The 'gnun-init-po' Script
+ 3.2.4 The 'gnun-preconvert' Script
+ 3.2.5 The 'gnun-merge-preconverted' Script
+ 3.2.6 The 'gnun-report' Script
+ 3.2.7 The 'gnun-validate-html' Script
+ 3.2.8 The 'mailfail' Script
+ 3.2.9 The 'validate-html-notify' Script
+ 3.2.10 The 'gnun-clear-previous' Script
4 Reporting Bugs
Index
Appendix A GNU Free Documentation License
GNUnited Nations
****************
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org essays and
other articles.
@@ -71,14 +71,14 @@
1 Introduction to GNUnited Nations
**********************************
-GNUnited Nations (abbreviated GNUN) is a collection of makefiles and
-scripts that are supposed to make the life of <http://gnu.org>
-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
-development, but if it proves useful, and if there is sufficient
-interest (and time), it is possible to develop a robust configuration
-interface that would be appropriate for general usage.
+GNUnited Nations (abbreviated GNUN) is a collection of scripts that are
+supposed to make the life of <http://gnu.org> 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 development, but if
+it proves useful, and if there is sufficient interest (and time), it is
+possible to develop a robust configuration interface that would be
+appropriate for general usage.
It is vitally important to understand that GNUN is _not_ a silver
bullet that solves all problems. If we have to be honest, deploying
@@ -99,7 +99,7 @@
redistribute it under the terms of the GNU Free Documentation License.
*Note GNU Free Documentation License: Copying This Manual.
-1.1 Why GNUN is Being Developed
+1.1 Why GNUN Is Being Developed
===============================
The GNU Project's website, <http://www.gnu.org>, has become considerably
@@ -124,7 +124,7 @@
that lead to the inception of GNU gettext, or GNOME Documentation
Utilities ('gnome-doc-utils') some years later.
-1.2 What GNUnited Nations is and Should be
+1.2 What GNUnited Nations Is and Should Be
==========================================
The basic concept behind GNUN is that localization of HTML articles is
@@ -177,9 +177,8 @@
yet oriented towards any particular language.
The first time though, there is no 'ARTICLE.LANG.po' yet, so a
-translator must manually copy 'ARTICLE.pot' to 'ARTICLE.LANG.po', where
-LANG represents the target language. *Note New Translation::, for
-details.
+translator must make 'ARTICLE.LANG.po' from 'ARTICLE.pot', where LANG
+represents the target language. *Note New Translation::, for details.
Then comes the initial translation of messages in 'ARTICLE.LANG.po'.
Translation in itself is a whole matter, whose complexity far overwhelms
@@ -203,23 +202,25 @@
dynamic in nature, like ones containing news entries or a list of other
articles. If the original article changes, GNUN will automatically
rebuild 'ARTICLE.pot', and will merge the changes to 'ARTICLE.LANG.po'.
-Any outdated translations will be marked as fuzzy, any new strings will
-be added with empty translations, waiting to be translated. In the same
-run 'ARTICLE.LANG.html' will be rebuilt so the relevant strings in the
-translation will be substituted with the original English text, until
-the translation teams update them in 'ARTICLE.LANG.po'.
+Any outdated translations will be marked as "fuzzy," any new strings
+will be added with empty translations, waiting to be translated. In the
+same run 'ARTICLE.LANG.html' will be rebuilt so the relevant strings in
+the translation will be substituted with the original English text,
+until the translation teams update them in 'ARTICLE.LANG.po'.
Those changes in the original article that do not affect the
-translatable strings will not lead to changes in 'ARTICLE.LANG.po'.
-Thus, no actions from translators will be needed. 'ARTICLE.LANG.html'
-will be automatically regenerated to reflect the changes.
+translatable strings (or just delete whole strings) will not lead to
+changes in 'ARTICLE.LANG.po'. Thus, no actions from translators will be
+needed. 'ARTICLE.LANG.html' will be automatically regenerated to
+reflect the changes.
The POT for every article under GNUN's control is kept in the 'www'
repository under a special directory 'po/', which is a sub-directory of
the relevant directory in the 'www' tree. So, for
'http://www.gnu.org/philosophy/free-sw.html' that is 'philosophy/po/'.
Except 'free-sw.pot', this directory holds the canonical source of every
-translation, like 'free-sw.bg.po', 'free-sw.ca.po', etc.
+translation, like 'free-sw.bg.po', 'free-sw.ca.po', etc. For more
+details, *Note Files and Directories::.
Several additional features are implemented, like automatic update of
the list of the available translations. For example, if a new
@@ -313,6 +314,11 @@
errors interrupt the build so they have to be fixed before the next
articles are processed.
+ * In some rare cases (most notably, for alphabetically sorted lists)
+ the structure of the translation should diverge from the structure
+ of the original document. So far, our system has developped no
+ means of taking such issues into account.
+
2 General Usage
***************
@@ -322,16 +328,15 @@
Murphy is an optimist.
--O'Rielly's Law
- GNUN currently consists of a few makefiles, scripts and optional
-'generic.LANG.html' files, intended to contain article-independent but
-team-specific information. They are designed to reside in the
-'server/gnun' directory, but this may change. In all examples in this
-manual, "invoking" means executing on the command line 'make -C
-server/gnun [TARGET] [VARIABLE=VALUE ...]' while the working directory
-is the root in the 'www' web repository. For the purpose of brevity, we
-will refer to the above command as simply 'make', which is equivalent to
-'cd server/gnun; make'. It is desirable never to invoke 'make' with the
-'-k' ('--keep-going') option, because an eventual error in only one make
+ GNUN currently consists of a few makefiles, scripts and template
+files. They are designed to reside in the 'server/gnun' directory, but
+this may change. In all examples in this manual, "invoking" means
+executing on the command line 'make -C server/gnun [TARGET]
+[VARIABLE=VALUE ...]' while the working directory is the root in the
+'www' web repository. For the purpose of brevity, we will refer to the
+above command as simply 'make', which is equivalent to 'cd server/gnun;
+make'. It is desirable never to invoke 'make' with the '-k'
+('--keep-going') option, because an eventual error in only one make
recipe might create a mess in many articles, both original and
translated. Do this with caution, and generally only when debugging in
a safe environment.
@@ -421,9 +426,7 @@
'VALIDATE=no'
'...'
- Does not perform validation of the HTML articles and PO files.
- This is the default, and not defining this variable has the same
- effect.
+ Skips validation of the HTML articles and generated translations.
'VALIDATE=yes'
Validates all original articles before generating the POTs, to
@@ -435,10 +438,13 @@
Articles defined in the variable 'no-validate-articles' are never
checked for HTML validity. Its purpose was to skip validation of
- HTML 5 articles, until the command-line validation tools are
- updated to parse files that comply with this new standard. As of
- version 0.5 GNUN supports HTML 5, so resorting to
- 'no-validate-articles' should not be necessary.
+ HTML5 articles, until the command-line validation tools are updated
+ to parse files that comply with this new standard. As of version
+ 0.5 GNUN supports HTML5, so resorting to 'no-validate-articles'
+ should not be necessary.
+
+ This is the default, and not defining this variable has the same
+ effect.
'NOTIFY=no'
'...'
@@ -474,7 +480,7 @@
variables.
'GRACE=DAYS'
- If defined, ordinary articles that have fuzzy strings and are not
+ If defined, ordinary articles that have "fuzzy" strings and are not
older than DAYS will not be regenerated. This functionality is
implemented specifically to prevent gratuitous replacement of
translated strings with the English text when there are only minor
@@ -505,12 +511,11 @@
'TEMPLATE_LINGUAS' and will perform additional check at the end,
'cvs|svn|bzr add'-ing all necessary files.
- When validation is enabled (i.e. with 'VALIDATE=yes'), the original
-English articles are validated first, before any commands that generate
-the other files, and 'make' exits with an error on the first encountered
-article. This is done on purpose, to prevent the propagation of an
-eventual error in the markup of the original article to all
-translations.
+ When validation is enabled, the original English articles are
+validated first, before any commands that generate the other files, and
+'make' exits with an error on the first encountered article. This is
+done on purpose, to prevent the propagation of an eventual error in the
+markup of the original article to all translations.
Validation of the translated '.LANG.html' is performed after it is
preliminarily generated as a temporary file. When no errors are found,
@@ -552,8 +557,8 @@
gnunews, and all articles defined in the variable 'no-grace-articles'
(*note grace period: GRACE.).
- This target can be rebuilt more often than 'all'; however, it is
-currently not used.
+ This target can be rebuilt more often than 'all'; however, currently
+it is not used.
2.1.2.2 The 'update-localized-URLs' Target
..........................................
@@ -623,7 +628,9 @@
reported as less important.
There is also a script, 'gnun-report', to generate HTML reports.
-*Note gnun-report::.
+*Note gnun-report::. GNUmakefile.team profides another 'report' target,
+which produces a more detailed report. *Note report in
+GNUmakefile.team::.
2.1.2.5 The 'triggers' Target
.............................
@@ -653,7 +660,7 @@
To summarize, for effective operation GNUN should be invoked
automatically as 'make; cvs|svn|bzr commit -m ...; make triggers'. To
illustrate this, here is a concrete example showing the official job
-running at fencepost.gnu.org:
+once running at fencepost.gnu.org(1):
25 4,12,20 * * * cd $HOME/projects/www; cvs -q update &>/dev/null; \
make -j1 -C server/gnun VCS=yes VALIDATE=yes; \
@@ -674,6 +681,12 @@
In the future, this target may be extended further to do other useful
things that should be "triggered" after the main build.
+ ---------- Footnotes ----------
+
+ (1) These days we run a more complicated script instead of this cron
+job in order to address some exceptional situations like concurrent
+builds.
+
2.1.2.6 The 'validate-all' Target
.................................
@@ -683,7 +696,7 @@
This target is invoked once a day by the official GNUN cron job.
-2.2 Defining Articles to be Built
+2.2 Defining Articles to Be Built
=================================
The file 'gnun.mk' contains variable definitions, based on which almost
@@ -699,6 +712,10 @@
everything else is supposed to be built automagically, without manual
intervention. If not, that is a bug that should be reported and fixed.
+ You can also request building files separately this way:
+
+ make -C server/gnun ../../philosophy/not-ipr.bg.html
+
'TEMPLATE_LINGUAS'
A space-separated list with languages. Add here your language code
_if and only if_ you have all the SSI templates translated, and
@@ -738,7 +755,7 @@
'FUZZY_DIFF_LINGUAS'
Add your language code here if you want GNUN to add differences to
- previous 'msgid's in your PO files. The differences are shown in
+ "previous" 'msgid's in your PO files. The differences are shown in
the default 'wdiff' format. *Note wdiff: (wdiff)wdiff, for more
information.
@@ -770,48 +787,9 @@
2.3 Working with PO Files
=========================
-We anticipate that some gnu.org translators will find this format odd or
-inconvenient, if they never happened to work with PO files before.
-Don't worry, you will soon get accustomed to it. It is the established
-format for translations in the Free World, and you should have no
-problems if you have translated software before.
-
- 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 it valid. Here is a list of widely used PO editors:
-
- * 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 '.po' file you visit should
- automatically switch to PO mode. You can enable/disable it with
- 'M-x po-mode <RET>'. On some GNU/Linux distros such as gNewSense,
- PO mode is available in a separate package, 'gettext-el'. See
- <http://www.gnu.org/software/gettext>.
-
- * Gtranslator--the GNOME PO editor. See
- <http://projects.gnome.org/gtranslator/>.
-
- * Lokalize--the KDE 4 editor. See
- <http://userbase.kde.org/Lokalize>.
-
- * KBabel--the KDE 3 editor. No longer supported, but might be
- available on some old systems.
-
- * Poedit--another popular editor that is based on the 'wxWidgets'
- graphical toolkit. See <http://www.poedit.net>.
-
- * Virtaal--a relevantly new editor that supports also the XLIFF
- format and uses the Translate Toolkit API. See
- <http://translate.sourceforge.net/wiki/virtaal>.
-
- * po.vim--ftplugin for the Vim editor. The best option for people
- who use Vim as their editor. See
- <http://www.vim.org/scripts/script.php?script_id=2530>.
-
- * Various web-based editors. *Note (web-trans)Savannah VCS::.
+This section provides GNUN-specific information about woking with PO
+files. For general information, *note Working with PO Files:
+(web-trans)PO Files.
2.3.1 Starting a New Translation
--------------------------------
@@ -920,7 +898,7 @@
It is recommended that you wrap all lines in the comments to be less
than 80 lines; that looks better from a purely aesthetic point of view
and improves the performance of 'GNUmakefile.team''s 'publish' rule
-(*note GNUmakefile.team Variables::).
+(*note publish::).
There are some special messages that appear in the POT and PO:
@@ -928,13 +906,16 @@
This is for translator's notes that are injected in the resulting
translation. *Note Notes Slot::, for more information. If your
translation does not have notes, you _must_ translate this as a
- space, that is, <SPC>.
+ space:
+
+ msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
+ msgstr " "
'*GNUN-SLOT: TRANSLATOR'S CREDITS*'
This is again optional, and should contain the name (and address)
of the person who made the translation. "Translate" this string as
- a space (<SPC>) if you do not want your name to appear there.
- *Note Credits Slot::.
+ a space if you do not want your name to appear there. *Note
+ Credits Slot::.
Most of the PO editors do not wrap long lines that inevitably appear
in 'msgstr's. If that happens, long lines make reading subsequent diffs
@@ -1049,7 +1030,75 @@
meets the linking criteria for gnu.org. Please follow the FSF HTML
Style Sheet when adding URIs or other information.
-2.3.2 Transforming Existing Translation in PO Format
+2.3.2 Useful Hints for Editing PO Files
+---------------------------------------
+
+This section contains additional explanations, some in the form of
+advices and recommendations; not all of them are strictly related to PO
+files editing.
+
+ * When you install a new translation of an article (that is different
+ from a server template), all you need to do is to add your PO file
+ in the appropriate '/po' sub-directory.
+
+ In the next build, your 'ARTICLE.LANG.html' will be built and the
+ link to it will be added to the list of translations and propagate
+ to all translations, provided that they are under GNUN's control.
+
+ * If you don't feel comfortable editing 'gnun.mk', do not worry.
+ Someone from the GNUN maintainers will notice and will amend
+ 'TEMPLATE_LINGUAS' for you, as appropriate.
+
+ * Dealing with obsolete strings. Elements which are removed from the
+ original articles appear in the PO files as "obsolete" strings--the
+ translation is not lost, but they are marked in a special way at
+ the end of the PO file. You don't have to update a PO file if it
+ contains obsolete strings--do this only if it has "fuzzy" or
+ "untranslated", and of course when you want to improve the existing
+ translated ones. Sometimes these obsolete strings are useful, and
+ they can save time. For example, if you anticipate that the
+ deleted text may reappear some time in the future, you can preserve
+ the string and hopefully it would be marked as "fuzzy" when this
+ happens. Failing that, you can still copy it and yank it at the
+ appropriate place.
+
+ * You can add comments to every message in a PO file--for example if
+ you want to remember that you have to do something, or to remind
+ you why this particular message is translated in a special way.
+ These comments do not appear in the generated HTML source.
+
+ * Sometimes, especially when the original message contains many
+ links, it is easier to copy it to 'msgstr' and edit the latter by
+ translating the English text. In PO mode, this is done by 'C-j'.
+ This is useful also for large chunks of text in '<pre>' elements,
+ which normally you would want to preserve verbatim.
+
+ * If you translate "Free Software Foundation, Inc." in your native
+ language in the copyright notice, then please prepend the English
+ name to the '<address>'; otherwise it looks awkward in most
+ languages. Example:
+
+ # type: Content of: <div><address>
+ msgid "51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA"
+ msgstr ""
+ "Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, "
+ "Boston, MA 02110-1301, USA"
+
+ * 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
+ 'ü' and this is a character from the alphabet of your
+ language, just write it as 'u"' directly.
+
+ * Wrapping of 'msgstr' using 'M-q' in Emacs (or other means) is
+ considered harmful. It is best to leave GNUN (or more precisely,
+ Po4a) to do the wrapping--that way all generated HTML translations
+ will have predictable results. This will help tremendously for the
+ conversion to other formats, like Texinfo. Also, note that not all
+ elements are wrapped by default, so deliberately wrapping the text
+ inside the 'msgstr' could lead to an invalid page or a page that is
+ valid, but is rendered incorrectly by the web browser.
+
+2.3.3 Transforming Existing Translation in PO Format
----------------------------------------------------
Migrating an existing translation to a PO file format is basically
@@ -1093,7 +1142,7 @@
You get 'foo.LANG.po' where all messages are marked as "fuzzy"
(unless you use a compendium); you still should make sure that the
translations correspond to the original and remove those "fuzzy" marks.
-The script adds differences against previous 'msgid's to facilitate
+The script adds differences against "previous" 'msgid's to facilitate
checking.
There is no need to delete the existing HTML translation, GNUN will
@@ -1117,100 +1166,7 @@
translation, Jero^me made some changes in 2007, and the original
translator returned in 2008 and continued maintaining it.
-2.3.3 Special Handling for GNU News
------------------------------------
-
-*Pay attention:* The practice of news handling that is described here
-has been obsolete for some time now, as they are being fed automatically
-from Planet GNU (<http://planet.gnu.org>). Nevertheless, the
-information below is accurate to the extent that the support for the
-old-fashioned way is still available.
-
- The GNU website has infrastructure for supporting "What's New", also
-known as "GNU News". Entries are added in a special plain text file,
-'server/whatsnew.txt' and are used to build 'server/whatsnew.include'
-and 'gnusflashes.include'. The former is used by
-'server/whatsnew.html', while the latter was included in the homepage.
-
- GNUN has additional rules for building 'whatsnew.pot', which contains
-a combination of all necessary strings for 'server/whatsnew.LANG.html',
-'server/whatsnew.LANG.include' and 'gnusflashes.LANG.include'. There is
-nothing unusual in this POT file, so it should be translated like any
-other. When you commit 'whatsnew.LANG.po', it will be used to generate
-all three localized files.
-
- Note that localized RSS feeds are not supported on purpose, as it
-would be annoying for subscribers if new items appear in English and
-then once again translated.
-
-2.3.4 Useful Hints for Editing PO Files
----------------------------------------
-
-This section contains additional explanations, some in the form of
-advices and recommendations; not all of them are strictly related to PO
-files editing.
-
- * When you install a new translation of an article (that is different
- from a server template), all you need to do is to add your PO file
- in the appropriate '/po' sub-directory.
-
- In the next build, your 'ARTICLE.LANG.html' will be built and the
- link to it will be added to the list of translations and propagate
- to all translations, provided that they are under GNUN's control.
-
- * If you don't feel comfortable editing 'gnun.mk', do not worry.
- Someone from the GNUN maintainers will notice and will amend
- 'TEMPLATE_LINGUAS' for you, as appropriate.
-
- * Dealing with obsolete strings. Elements which are removed from the
- original articles appear in the PO files as "obsolete" strings--the
- translation is not lost, but they are marked in a special way at
- the end of the PO file. You don't have to update a PO file if it
- contains obsolete strings--do this only if it has "fuzzy" or
- "untranslated", and of course when you want to improve the existing
- translated ones. Sometimes these obsolete strings are useful, and
- they can save time. For example, if you anticipate that the
- deleted text may reappear some time in the future, you can preserve
- the string and hopefully it would be marked as "fuzzy" when this
- happens. Failing that, you can still copy it and yank it at the
- appropriate place.
-
- * You can add comments to every message in a PO file--for example if
- you want to remember that you have to do something, or to remind
- you why this particular message is translated in a special way.
- These comments do not appear in the generated HTML source.
-
- * Sometimes, especially when the original message contains many
- links, it is easier to copy it to 'msgstr' and edit the latter by
- translating the English text. In PO mode, this is done by 'C-j'.
- This is useful also for large chunks of text in '<pre>' elements,
- which normally you would want to preserve verbatim.
-
- * If you translate "Free Software Foundation, Inc." in your native
- language in the copyright notice, then please prepend the English
- name to the '<address>'; otherwise it looks awkward in most
- languages. Example:
-
- # type: Content of: <div><address>
- msgid "51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA"
- msgstr ""
- "Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, "
- "Boston, MA 02110-1301, USA"
-
- * There is absolutely no reason to use HTML entities in translations
- as a replacement for common non-ASCII characters. They are harder
- to write and serve no purpose.
-
- * Wrapping of 'msgstr' using 'M-q' in Emacs (or other means) is
- considered harmful. It is best to leave GNUN (or more precisely,
- Po4a) to do the wrapping--that way all generated HTML translations
- will have predictable results. This will help tremendously for the
- conversion to other formats, like Texinfo. Also, note that not all
- elements are wrapped by default, so deliberately wrapping the text
- inside the 'msgstr' could lead to an invalid page or a page that is
- valid, but is rendered incorrectly by the web browser.
-
-2.3.5 The 'generic.LANG.html' File
+2.3.4 The 'generic.LANG.html' File
----------------------------------
The files 'server/gnun/generic.LANG.html' are special: if no such file
@@ -1235,7 +1191,7 @@
all '.LANG.html', including the homepage), will be modified to include
the contents of this special file.
-2.3.6 The 'languages.txt' File
+2.3.5 The 'languages.txt' File
------------------------------
The file 'server/gnun/languages.txt' is used when generating lists of
@@ -1266,7 +1222,7 @@
</div> <!-- id="translations" -->
<!-- end translinks file -->
-2.3.7 Maintaining Translations in Your Team's Repository
+2.3.6 Maintaining Translations in Your Team's Repository
--------------------------------------------------------
GNUN operates on the "official" Web repository of the Savannah project
@@ -1300,13 +1256,14 @@
Leader `---Member B
All members and the team leader commit in their project's
-repository--when a translation is ready, the leader checks it in in the
+repository--when a translation is ready, the leader checks it in the
official 'www' repository. If an original article changes, a build
could be invoked to synchronize (i.e. merge) the changes and optionally
-automatically commit them so that the draft PO files are updated. A
-translator would then normally update the PO file, and commit it again
-in the project's Sources repository, from where the coordinator will
-pick it up and install it in 'www'.
+automatically commit them so that the draft PO files are updated; at the
+same time, automatic notifications are sent to the persons interested in
+particular translations(1). A translator would then normally update the
+PO file, and commit it again in the project's Sources repository, from
+where the coordinator will pick it up and install it in 'www'.
To take advantage of this semi-automation, rename this template
'GNUmakefile.team' as 'GNUmakefile' and install it in the root of your
@@ -1339,19 +1296,25 @@
|
+--...
- Add 'priorities.mk' in order to make the 'report' target sort the
-files by priority.
-
The next sections explain how to adopt the makefile for your team and
how to invoke a "build".
-2.3.7.1 Adopting 'GNUmakefile.team' for a Specific Team
+ ---------- Footnotes ----------
+
+ (1) The following sections describe in more details how to setup
+these automatic actions; however, if you have any difficulties with
+that, please ask the GNU Web Translation Managers to make it for your
+team using our server.
+
+2.3.6.1 Adopting 'GNUmakefile.team' for a Specific Team
.......................................................
-To adjust the makefile for your team, you need to edit two variables.
+To adjust the makefile for your team, you need to edit the next
+variables.
'TEAM'
- Set this to the language code, like 'bg' or 'pt-br'.
+ Set this to the language code, like 'bg' or 'pt-br'. It is
+ autodetected if not defined.
'wwwdir'
The relative or absolute path to the working copy of the master
@@ -1361,6 +1324,17 @@
'../www/' or '/home/USER/projects/www/'. Note the slash at the
end, it is important.
+'TEAM_URL_PREFIX'
+'TEAM_URL_POSTFIX'
+ These variables are used to transform the path to a file in team's
+ working copy into a URL for this file; they are only needed for
+ automatic email notifications. It is expected that typically the
+ URL will point to some sort of Web interface for the repository,
+ for example,
+
+ TEAM_URL_PREFIX :=
http://cvs.savannah.gnu.org/viewvc/*checkout*/www-bg/
+ TEAM_URL_POSTFIX := ?root=www-bg
+
If two variants of one language share the same project and repository
(such as 'zh-cn' and 'zh-tw'), they should maintain two directories with
two 'GNUmakefile's and each directory having its own tree.
@@ -1368,6 +1342,23 @@
Some variables are specified on the command line, and alter the
behavior of the build process.
+'ADD_FUZZY_DIFF'
+ The program to manage differences to "previous" 'msgid's added to
+ "fuzzy" translations when merging PO files. When undefined, the
+ makefile tries to find 'gnun-add-fuzzy-diff' and assigns the result
+ to this variable. *Note gnun-add-fuzzy-diff::.
+
+ Define to empty string to disable the feature.
+
+'NOTIFICATION_PERIOD=DAYS'
+ Default period of reminders sent by the 'notify' target.
+
+'NOTIFY=yes'
+ Make the 'notify' target actually send notifications.
+
+'NOTIFY=no'
+ Do not send email notifications about errors. This is the default.
+
'VERBOSE=yes'
Print more information from 'cvs', 'svn' and 'msgmerge'; off by
default. Note that 'VERBOSE' can be defined to any string, it will
@@ -1385,7 +1376,7 @@
better to use a separate working copy dedicated solely for this
purpose.
-2.3.7.2 Targets in 'GNUmakefile.team'
+2.3.6.2 Targets in 'GNUmakefile.team'
.....................................
'update'
@@ -1400,7 +1391,83 @@
'report'
Verifies which translations are complete, and prints a list (with
- statistics) of those that need to be updated.
+ statistics) of those that need to be updated. Also, it reports the
+ translations that are not consistent with the revisions from "www"
+ repository.
+
+ More fine-grained notifications are implemented as the 'notify'
+ target.
+
+'notify'
+ Invokes the 'report' target, filters its output for different
+ translators and sends them notifications.
+
+ As an addition to the output of the 'report' target, URLs for
+ relevant files are written; also, when "www" and team revisions are
+ not consistent, their differences generated with 'gnun-diff-po' are
+ optionally attached (*note gnun-diff-po::, for more details).
+
+ The list of files to report against are configured with 'nottab'
+ file. The lines of this file that begin with '#' are ignored;
+ other lines should contain two fields separated by ':'.
+
+ The first field is an extended grep regular expression; the files
+ are selected for the report if their names match this expression.
+ *Note Regular Expressions: (grep)Regular Expressions.
+
+ The second field is a space-separated list of single-word
+ translators' identifiers for which the line applies. The file may
+ look like this:
+
+ ^gnu/gnu-history: alice bob carol
+ ^distros/(common-distros|distros|screenshot): dan alice
+ ^(licenses|philosophy)/: eve bob frank
+ ^licenses/: dan
+
+ Email addresses of the translators are kept in a separate file,
+ 'email-aliases'. Like 'nottab', this file contains lines separated
+ by ':'; the lines beginning with '#' are ignored.
+
+ The first field is translators' identifier, the second is
+ space-separated list of translators' email addresses. These two
+ fields are mandatory.
+
+ The third field is the personal reminder period in days. After
+ that period the message is sent again even though its contents
+ don't change. Otherwise, the 'notify' target only sends messages
+ when something changes. Naturally, no message is sent when no
+ action is needed in the requested set of translations.
+
+ The team-wide default period is defined in its GNUmakefile.team
+ using the 'NOTIFICATION_PERIOD' variable.
+
+ The fourth field provides comma-separated options for the report.
+ Currently recognized options are:
+
+ 'no-diffs'
+ Disables sending "www" vs. "www-LANG" differences as
+ attachments.
+
+ 'www'
+ Report cases that suggest actions by the team leader, that is,
+ when the translation in the team repository is full whereas in
+ "www" it is incomplete or absent.
+
+ This is an example of 'email-aliases':
+
+ alice:address@hidden address@hidden
+ # Disable `dan' temporarily.
+ #dan:address@hidden:5:no-diffs,www
+ bob:address@hidden:3
+ # Note that the third field is empty; the default value for period
+ # will be used.
+ carol:address@hidden address@hidden::no-diffs
+ eve:address@hidden:2:www
+ frank:address@hidden:1:www,no-diffs
+
+ The 'email-aliases' file should be kept privately because it may
+ contain personal email addresses of people. How to do this is out
+ of scope of GNUN and this manual.
'format'
A convenience rule to re-wrap all files upto the standard length.
@@ -1456,23 +1523,18 @@
$ cvs commit -m "Some descriptive message."
'clean'
- Deletes all backup and auto-generated files that some PO editors
- leave behind, namely--'FILE.po~', 'FILE.po.bak' and 'FILE.mo'.
+ Deletes all backup and auto-generated files.
'make VCS=yes' is the recommended command to be run periodically. To
check the status of the translations, run 'make report'.
Feel free to replace all strings with equivalents in your native
language and of course--do not hesitate to extend this file and modify
-it as much as you like. For example, useful extra functionality would
-be a target that will check which files have not yet been committed in
-the official repository, or which files have to be updated there (i.e.
-they were updated by the team members but not installed by the
-coordinator). Either way, if you come up with something interesting, it
+it as much as you like. If you come up with something interesting, it
would be nice to send a message to <address@hidden>, so that
'GNUmakefile.team' gets updated for all teams' benefit.
-2.3.7.3 Automatic Synchronization and Status Reports
+2.3.6.3 Automatic Synchronization and Status Reports
....................................................
It is convenient to invoke such synchronization automatically, for
@@ -1498,7 +1560,7 @@
as a line continuation character--the example shown is made that way for
better readability.
-2.3.8 Using Compendia
+2.3.7 Using Compendia
---------------------
Compendium is a PO file including translations for common strings; it is
@@ -1536,6 +1598,32 @@
specific file, 'exclude.pot', and when that file contains the string, it
won't be added to 'compendium.pot'.
+2.3.8 Special Handling for GNU News
+-----------------------------------
+
+*Pay attention:* The practice of news handling that is described here
+has been obsolete for some time now, as they are being fed automatically
+from Planet GNU (<http://planet.gnu.org>). Nevertheless, the
+information below is accurate to the extent that the support for the
+old-fashioned way is still available.
+
+ The GNU website has infrastructure for supporting "What's New", also
+known as "GNU News". Entries are added in a special plain text file,
+'server/whatsnew.txt' and are used to build 'server/whatsnew.include'
+and 'gnusflashes.include'. The former is used by
+'server/whatsnew.html', while the latter was included in the homepage.
+
+ GNUN has additional rules for building 'whatsnew.pot', which contains
+a combination of all necessary strings for 'server/whatsnew.LANG.html',
+'server/whatsnew.LANG.include' and 'gnusflashes.LANG.include'. There is
+nothing unusual in this POT file, so it should be translated like any
+other. When you commit 'whatsnew.LANG.po', it will be used to generate
+all three localized files.
+
+ Note that localized RSS feeds are not supported on purpose, as it
+would be annoying for subscribers if new items appear in English and
+then once again translated.
+
2.4 Tips and Hints for Webmasters
=================================
@@ -1548,11 +1636,10 @@
important to have as many and as better as possible translations, and
you don't have to make titanic efforts to help.
- If you plan to edit a certain page extensively, please do so within
-the period between two adjacent GNUN builds--i.e. within a day. That
-way, the POT will be regenerated only once, and translators who are
-quick to update it immediately won't be disappointed if it changes again
-in the next run.
+ If you plan to edit a certain page extensively, please do so within a
+reasonable time frame, for example a day or preferably, several hours.
+That way, the translators who are quick to update it immediately won't
+be disappointed if the POT changes again in the next GNUN run(s).
2.4.1 Validation
----------------
@@ -1662,7 +1749,146 @@
front-end, except the section about scripts that includes descriptions
of programs that may also be useful for the translators.
-3.1 GNUN Scripts
+3.1 Files and Directories
+=========================
+
+This is a brief diagram of "www" working copy; note that in this section
+we don't describe the files out of GNUN control, including the old
+HTML-only translations.
+
+ Legend:
+ * The file is maintained locally, without committing it to CVS.
+ # The file is edited manually.
+ @ The file is regenerated automatically.
+ % The file is edited both manually and automatically.
+ #/@ The file is generated automatically, but outside of GNUN.
+
+ Root/
+ |
+ +--gnu/
+ | |
+ | |
+ | +--linux-and-gnu.html #
+ | +--linux-and-gnu.LANG.html @
+ | +--manifesto.html #
+ | +--manifesto.LANG.html @
+ | +--...
+ | |
+ | +--------------------------po/
+ | |
+ +--home.html # +--manifesto.LANG.po %
+ +--home.LANG.html @ +--manifesto.pot @
+ +--planetfeeds.html #/@ +--manifesto.proto * @
+ +--planetfeeds.LANG.html @ +--manifesto.translist @
+ +--po/ +--manifesto.LANG.m4 * @
+ | | +--manifesto.LANG-en.html @
+ | +--home.pot @ +--manifesto.LANG-diff.html @
+ | +--home.proto * @ +--linux-and-gnu.LANG.po %
+ | +--home.translist @ +--...
+ | +--home.LANG.po %
+ | +--home.LANG.m4 * @
+ | +--home.LANG-en.html @
+ | +--home.LANG-diff.html @
+ | +--planetfeeds.proto * @
+ | +--planetfeeds.pot.opt @
+ | +--planetfeeds.LANG.po %
+ | +--...
+ |
+ +--server/
+ | |
+ | +-------------------------gnun/
+ | | |
+ | +--sitemap.html #/@ +--GNUmakefile * #
+ | +--sitemap.LANG.html @ +--config.mk * #
+ | +--po/ +--gnun.mk #
+ | | | +--languages.txt #
+ | | +--sitemap.pot @ +--generic.LANG.html #
+ | | +--sitemap.proto * @ +--compendia/
+ | | +--sitemap.LANG.po % |
+ | | +--sitemap.LANG.m4 @ +--master.LANG.po #
+ | | +--body-include-2.pot @ +--compendium.LANG.po @
+ | | +--body-include-2.proto * @ +--excluded.pot #
+ | | +--body-include-2.LANG.po %
+ | | +--...
+ | |
+ | +--body-include-2.html #
+ | +--body-include-2.LANG.html @
+ | +--...
+ +--...
+
+ A description of some files follows.
+
+'.../FILE.html'
+ The English files.
+
+'.../FILE.LANG.html'
+ The LANG translation of '.../FILE.html'.
+
+'.../po/FILE.proto'
+ Intermediate files generated from 'FILE.html'; they are used only
+ internally. Essentially, GNUN inserts its special slots and
+ instructions to include the 'generic.LANG.html' file. *Note GNUN
+ Slots::, and *note generic.LANG.html::.
+
+'.../po/FILE.translist'
+ The list of trasnlations for '.../FILE.html'. It is included in
+ '.../FILE.html' all its translations.
+
+'.../po/FILE.pot'
+ PO templates for articles and included files.
+
+'.../po/FILE.pot.opt'
+ POTs of optional templates (currently, 'planetfeeds.pot.opt').
+ *Note optional-templates::, for more details.
+
+'.../po/FILE.LANG.po'
+ Translations of 'FILE.pot' or 'FILE.pot.opt' committed by the
+ translators and merged by GNUN.
+
+'.../po/FILE.LANG.m4'
+ Intermediate files from which 'FILE.LANG.html' are generated.
+
+'.../po/FILE.LANG-en.html'
+ The latest revision of the English file for which a full
+ translation into LANG language was provided.
+
+'.../po/FILE.LANG-diff.html'
+ The highlighted differences between the current version of
+ '...FILE.html' and '.../po/FILE.LANG-en.html'.
+
+'planetfeeds.html'
+ A list of news; it is automatically generated outside of GNUN. For
+ GNUN, it is an optional template.
+
+'server/'
+ Most template SSI files are located in this directory.
+
+'server/sitemap.html'
+ The sitemap; it is generated automatically by a script that is not
+ included in GNUN. GNUN currently treats it like a regular article.
+
+'server/gnun/'
+ The directory for GNUN files.
+
+'server/gnun/GNUmakefile'
+'server/gnun/config.mk'
+ These files are maintained locally. They are used to rebuild the
+ translations. *Note Invoking GNUN::.
+
+'server/gnun/gnun.mk'
+ The file that defines the list of files to build. *Note Main
+ Variables::.
+
+'server/gnun/languages.txt'
+ See *note languages.txt::.
+
+'server/gnun/generic.LANG.html'
+ See *note generic.LANG.html::.
+
+'server/gnun/compendia'
+ The directory for compendia. *Note Compendia::.
+
+3.2 GNUN Scripts
================
For the time being there are several helper scripts. Some of them are
@@ -1671,11 +1897,11 @@
mechanical actions, like initially filling the headers in the PO files.
They all can be invoked separately, as stand-alone programs.
-3.1.1 The 'gnun-add-fuzzy-diff' Script
+3.2.1 The 'gnun-add-fuzzy-diff' Script
--------------------------------------
This script adds comments with differences of current 'msgid's against
-previous ones to fuzzy translations in a PO file. To produce the
+"previous" ones to "fuzzy" translations in a PO file. To produce the
differences 'wdiff' is used. This may be useful to figure out what has
changed. In fact, it wraps around a 'sed' script used in GNUN
internally.
@@ -1692,7 +1918,7 @@
'--help'
Display usage information and exit.
-3.1.2 The 'gnun-diff-po' Script
+3.2.2 The 'gnun-diff-po' Script
-------------------------------
This script compares two versions of a PO file. It produces a HTML page
@@ -1727,7 +1953,7 @@
'--help'
Display usage information and exit.
-3.1.3 The 'gnun-init-po' Script
+3.2.3 The 'gnun-init-po' Script
-------------------------------
This script initializes a PO file using POT generated with GNUN, and
@@ -1745,7 +1971,7 @@
'-d'
'--disable-diffs'
- Don't add diffs to previous messages.
+ Don't add diffs to "previous" messages.
'-g'
'--team="TEAM <LIST>"'
@@ -1768,9 +1994,9 @@
Display usage information and exit.
The PO file name is guessed from the name of POT and language suffix;
-the file is created in current working directory.
+the file is created in the current working directory.
-3.1.4 The 'gnun-preconvert' Script
+3.2.4 The 'gnun-preconvert' Script
----------------------------------
This script uses 'po4a-gettextize' to convert a translation from HTML to
@@ -1791,12 +2017,12 @@
'--help'
Display usage information and exit.
-3.1.5 The 'gnun-merge-preconverted' Script
+3.2.5 The 'gnun-merge-preconverted' Script
------------------------------------------
This script takes 'po4a-gettextize' output, adds current 'msgid's as
"previous" values, merges the file with the new POT, and adds
-differences against previous values like 'gnun-add-fuzzy-diff' does.
+differences against "previous" values like 'gnun-add-fuzzy-diff' does.
gnun-merge-preconverted [OPTION...] PO POT
@@ -1811,7 +2037,7 @@
'--help'
Display usage information and exit.
-3.1.6 The 'gnun-report' Script
+3.2.6 The 'gnun-report' Script
------------------------------
This script generates HTML reports about translations of a given team.
@@ -1849,7 +2075,7 @@
There is also a target in 'GNUmakefile' to generate text reports
intended for monthly messages sent to the teams. *Note report::.
-3.1.7 The 'gnun-validate-html' Script
+3.2.7 The 'gnun-validate-html' Script
-------------------------------------
This is a Bash script whose purpose is to "validate" both the original
@@ -1885,7 +2111,7 @@
'--help'
Display usage information and exit.
-3.1.8 The 'mailfail' Script
+3.2.8 The 'mailfail' Script
---------------------------
This is a helper script that runs a command, and mails the output of
@@ -1929,7 +2155,7 @@
argument is missing, the usage information is printed to the standard
output and the exit code is 1.
-3.1.9 The 'validate-html-notify' Script
+3.2.9 The 'validate-html-notify' Script
---------------------------------------
This script is a wrapper around 'gnun-validate-html' (*note
@@ -1957,7 +2183,7 @@
wrapper has a specific task and cannot be used to invoke an arbitrary
command--use 'mailfail' for that. *Note mailfail::.
-3.1.10 The 'gnun-clear-previous' Script
+3.2.10 The 'gnun-clear-previous' Script
---------------------------------------
This simple script is not used internally in GNUN. It is merely for
@@ -1979,11 +2205,6 @@
'--help'
Print usage information on stdout.
-3.2 How The Recipes Work
-========================
-
-Read the source code, then please tell us :-)
-
4 Reporting Bugs
****************
@@ -2001,133 +2222,150 @@
* Menu:
-* ALL_DIRS: Main Variables. (line 751)
-* announce: Runtime Variables. (line 455)
-* articles in root directory, defining: Main Variables. (line 744)
-* Bazaar: Runtime Variables. (line 394)
+* ALL_DIRS: Main Variables. (line 768)
+* announce: Runtime Variables. (line 461)
+* articles in root directory, defining: Main Variables. (line 761)
+* Bazaar: Runtime Variables. (line 399)
* boilerplates: Modifying Boilerplates.
- (line 1594)
-* bugs, reporting: Bugs. (line 1989)
-* bzr: Runtime Variables. (line 394)
+ (line 1681)
+* bugs, reporting: Bugs. (line 2210)
+* bzr: Runtime Variables. (line 399)
* comments for translators: Comments for Translators.
- (line 1571)
-* comparing, translations: gnun-diff-po. (line 1697)
-* compendia: Compendia. (line 1503)
-* compendium.pot: Compendia. (line 1503)
-* config.mk: Invoking GNUN. (line 359)
+ (line 1658)
+* comparing, translations: gnun-diff-po. (line 1923)
+* compendia: Compendia. (line 1565)
+* compendium.pot: Compendia. (line 1565)
+* config.mk: Invoking GNUN. (line 364)
* conventional separator for strings: Splitting Long Passages.
- (line 1635)
-* conversion of existing translations: Migrating. (line 1054)
-* conversion of existing translations <1>: gnun-preconvert. (line 1775)
+ (line 1722)
+* conversion of existing translations: Migrating. (line 1103)
+* conversion of existing translations <1>: gnun-preconvert. (line 2001)
* conversion of existing translations <2>: gnun-merge-preconverted.
- (line 1796)
-* credits, translators: New Translation. (line 932)
-* credits, translators <1>: Credits Slot. (line 1031)
+ (line 2022)
+* credits, translators: New Translation. (line 913)
+* credits, translators <1>: Credits Slot. (line 1012)
* cron, team maintenance: GNUmakefile.team and Cron.
- (line 1477)
-* CVS: Runtime Variables. (line 394)
-* deferred generation of articles: Runtime Variables. (line 475)
-* defining articles in the root dir: Main Variables. (line 744)
-* defining directories: Main Variables. (line 751)
-* defining templates: Main Variables. (line 701)
-* defining templates <1>: Main Variables. (line 716)
-* defining templates <2>: Main Variables. (line 723)
-* directories, defining: Main Variables. (line 751)
-* exclude.pot: Compendia. (line 1503)
-* extra-templates: Main Variables. (line 716)
-* fuzzy strings: Runtime Variables. (line 475)
-* FUZZY_DIFF_LINGUAS: Main Variables. (line 738)
-* generic notice, translations: generic.LANG.html. (line 1215)
-* GNUmakefile: Invoking GNUN. (line 344)
-* GNUmakefile.team: PO Files and Team. (line 1271)
-* gnun.mk: Invoking GNUN. (line 359)
-* gnun.mk <1>: Main Variables. (line 688)
-* gnunews: GNU News. (line 1122)
-* gnusflashes: GNU News. (line 1122)
-* GRACE: Runtime Variables. (line 475)
-* grace period: Runtime Variables. (line 475)
-* initializing, translations: gnun-init-po. (line 1732)
-* invocation: Invoking GNUN. (line 344)
-* invoking: Invoking GNUN. (line 344)
-* localized URLs: Localized URLs. (line 1605)
-* long lines, wrap: New Translation. (line 938)
+ (line 1539)
+* CVS: Runtime Variables. (line 399)
+* deferred generation of articles: Runtime Variables. (line 481)
+* defining articles in the root dir: Main Variables. (line 761)
+* defining directories: Main Variables. (line 768)
+* defining templates: Main Variables. (line 718)
+* defining templates <1>: Main Variables. (line 733)
+* defining templates <2>: Main Variables. (line 740)
+* directories, defining: Main Variables. (line 768)
+* email-aliases: GNUmakefile.team Targets.
+ (line 1426)
+* exclude.pot: Compendia. (line 1565)
+* extra-templates: Main Variables. (line 733)
+* fuzzy strings: Runtime Variables. (line 481)
+* FUZZY_DIFF_LINGUAS: Main Variables. (line 755)
+* generic notice, translations: generic.LANG.html. (line 1171)
+* GNUmakefile: Invoking GNUN. (line 349)
+* GNUmakefile.team: PO Files and Team. (line 1227)
+* gnun.mk: Invoking GNUN. (line 364)
+* gnun.mk <1>: Main Variables. (line 701)
+* gnunews: GNU News. (line 1603)
+* gnusflashes: GNU News. (line 1603)
+* GRACE: Runtime Variables. (line 481)
+* grace period: Runtime Variables. (line 481)
+* initializing, translations: gnun-init-po. (line 1958)
+* invocation: Invoking GNUN. (line 349)
+* invoking: Invoking GNUN. (line 349)
+* localized URLs: Localized URLs. (line 1692)
+* long lines, wrap: New Translation. (line 919)
* long passages, avoiding: Splitting Long Passages.
- (line 1635)
-* mail, notifications: Runtime Variables. (line 442)
-* mail, notifications <1>: mailfail. (line 1890)
-* migration, translations: Migrating. (line 1054)
-* migration, translations <1>: gnun-preconvert. (line 1775)
+ (line 1722)
+* mail, notifications: Runtime Variables. (line 448)
+* mail, notifications <1>: GNUmakefile.team Variables.
+ (line 1355)
+* mail, notifications <2>: mailfail. (line 2116)
+* migration, translations: Migrating. (line 1103)
+* migration, translations <1>: gnun-preconvert. (line 2001)
* migration, translations <2>: gnun-merge-preconverted.
- (line 1796)
-* new translation: New Translation. (line 818)
+ (line 2022)
+* new translation: New Translation. (line 796)
* new translations, notifications/announcements: Runtime Variables.
- (line 455)
-* notes, translators: New Translation. (line 926)
-* notes, translators <1>: Notes Slot. (line 984)
-* NOTIFY: Runtime Variables. (line 442)
-* optional-templates: Main Variables. (line 723)
-* OUTDATED-GRACE: Runtime Variables. (line 487)
-* output, detailed: Runtime Variables. (line 468)
-* PO editors: PO Files. (line 784)
-* PO headers: New Translation. (line 859)
-* PO, editing: PO Files. (line 772)
-* POT generation, articles: Main Variables. (line 755)
-* previous, diff: Main Variables. (line 738)
+ (line 461)
+* notes, translators: New Translation. (line 904)
+* notes, translators <1>: Notes Slot. (line 965)
+* notification period: GNUmakefile.team Targets.
+ (line 1434)
+* notification period, default: GNUmakefile.team Variables.
+ (line 1353)
+* NOTIFICATION_PERIOD: GNUmakefile.team Variables.
+ (line 1353)
+* NOTIFY: Runtime Variables. (line 448)
+* NOTIFY <1>: GNUmakefile.team Variables.
+ (line 1355)
+* nottab: GNUmakefile.team Targets.
+ (line 1409)
+* optional-templates: Main Variables. (line 740)
+* outdated translations, notifications: GNUmakefile.team Targets.
+ (line 1401)
+* OUTDATED-GRACE: Runtime Variables. (line 493)
+* output, detailed: Runtime Variables. (line 474)
+* PO headers: New Translation. (line 837)
+* POT generation, articles: Main Variables. (line 772)
+* previous, diff: Main Variables. (line 755)
* previous, diff <1>: gnun-add-fuzzy-diff.
- (line 1676)
+ (line 1902)
* previous, manipulating PO files: gnun-clear-previous.
- (line 1962)
-* priorities.mk: Invoking GNUN. (line 359)
-* priorities.mk <1>: report. (line 618)
-* priorities.mk <2>: PO Files and Team. (line 1341)
-* priorities.mk <3>: gnun-report. (line 1821)
-* project repository: PO Files and Team. (line 1271)
-* recommendations, PO files: PO Tips. (line 1148)
-* reporting: report. (line 605)
-* reporting <1>: gnun-report. (line 1816)
-* reporting bugs: Bugs. (line 1989)
-* repository, translation project: PO Files and Team. (line 1271)
-* ROOT: Main Variables. (line 744)
-* sanity checks: Runtime Variables. (line 421)
-* status, translations: report. (line 605)
-* status, translations <1>: gnun-report. (line 1816)
-* Subversion: Runtime Variables. (line 394)
-* SVN: Runtime Variables. (line 394)
-* synchronization, repository: sync. (line 570)
-* TEAM: Runtime Variables. (line 496)
-* team information: generic.LANG.html. (line 1215)
-* team maintenance: PO Files and Team. (line 1271)
+ (line 2188)
+* priorities.mk: Invoking GNUN. (line 364)
+* priorities.mk <1>: report. (line 623)
+* priorities.mk <2>: gnun-report. (line 2047)
+* project repository: PO Files and Team. (line 1227)
+* recommendations, PO files: PO Tips. (line 1035)
+* reminder period: GNUmakefile.team Targets.
+ (line 1434)
+* reminder period, default: GNUmakefile.team Variables.
+ (line 1353)
+* reporting: report. (line 610)
+* reporting <1>: gnun-report. (line 2042)
+* reporting bugs: Bugs. (line 2210)
+* repository, translation project: PO Files and Team. (line 1227)
+* ROOT: Main Variables. (line 761)
+* sanity checks: Runtime Variables. (line 426)
+* status, translations: report. (line 610)
+* status, translations <1>: gnun-report. (line 2042)
+* Subversion: Runtime Variables. (line 399)
+* SVN: Runtime Variables. (line 399)
+* synchronization, repository: sync. (line 575)
+* TEAM: Runtime Variables. (line 502)
+* team information: generic.LANG.html. (line 1171)
+* team maintenance: PO Files and Team. (line 1227)
* team maintenance, cron: GNUmakefile.team and Cron.
- (line 1477)
-* team workflow: PO Files and Team. (line 1289)
-* templates, additional: Main Variables. (line 716)
-* templates, defining: Main Variables. (line 701)
-* templates, optional: Main Variables. (line 723)
-* TEMPLATE_LINGUAS: Main Variables. (line 701)
-* tips, translators: PO Tips. (line 1148)
-* tips, webmasters: Webmaster Tips. (line 1541)
-* translation memory: Compendia. (line 1503)
-* translation, new: New Translation. (line 818)
-* translators' credits: New Translation. (line 932)
-* translators' credits <1>: Credits Slot. (line 1031)
-* translators' notes: New Translation. (line 926)
-* translators' notes <1>: Notes Slot. (line 984)
-* triggering, build: Invoking GNUN. (line 344)
-* VALIDATE: Runtime Variables. (line 421)
-* validation: Runtime Variables. (line 421)
-* validation <1>: Runtime Variables. (line 507)
-* validation <2>: validate-all. (line 679)
-* validation <3>: Validation. (line 1559)
-* validation, HTML, XHTML: gnun-validate-html. (line 1854)
-* variable, behavior: Runtime Variables. (line 387)
-* variable, team: Runtime Variables. (line 496)
-* variables: Runtime Variables. (line 387)
-* variables <1>: Main Variables. (line 688)
-* VCS: Runtime Variables. (line 394)
-* VERBOSE: Runtime Variables. (line 468)
-* webmaster tips: Webmaster Tips. (line 1541)
-* whatsnew: GNU News. (line 1122)
-* wrapping long lines: New Translation. (line 938)
+ (line 1539)
+* team workflow: PO Files and Team. (line 1245)
+* templates, additional: Main Variables. (line 733)
+* templates, defining: Main Variables. (line 718)
+* templates, optional: Main Variables. (line 740)
+* TEMPLATE_LINGUAS: Main Variables. (line 718)
+* tips, translators: PO Tips. (line 1035)
+* tips, webmasters: Webmaster Tips. (line 1629)
+* translation memory: Compendia. (line 1565)
+* translation, new: New Translation. (line 796)
+* translators' credits: New Translation. (line 913)
+* translators' credits <1>: Credits Slot. (line 1012)
+* translators' notes: New Translation. (line 904)
+* translators' notes <1>: Notes Slot. (line 965)
+* triggering, build: Invoking GNUN. (line 349)
+* VALIDATE: Runtime Variables. (line 426)
+* validation: Runtime Variables. (line 426)
+* validation <1>: Runtime Variables. (line 513)
+* validation <2>: validate-all. (line 692)
+* validation <3>: Validation. (line 1646)
+* validation, HTML, XHTML: gnun-validate-html. (line 2080)
+* variable, behavior: Runtime Variables. (line 392)
+* variable, team: Runtime Variables. (line 502)
+* variables: Runtime Variables. (line 392)
+* variables <1>: Main Variables. (line 701)
+* VCS: Runtime Variables. (line 399)
+* VERBOSE: Runtime Variables. (line 474)
+* webmaster tips: Webmaster Tips. (line 1629)
+* whatsnew: GNU News. (line 1603)
+* wrapping long lines: New Translation. (line 919)
Appendix A GNU Free Documentation License
*****************************************
Index: gnun/gnun.txt.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.txt.gz,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
Binary files /tmp/cvsnqk6V8 and /tmp/cvswYygHA differ
Index: gnun/index.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/index.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/index.html 4 Dec 2012 16:24:20 -0000 1.18
+++ gnun/index.html 27 Dec 2012 14:45:33 -0000 1.19
@@ -4,33 +4,31 @@
<h2>GNU GNUN manual</h2>
<address>Free Software Foundation</address>
-<address>last updated December 04, 2012</address>
+<address>last updated December 27, 2012</address>
<p>This manual (gnun) is available in the following formats:</p>
<ul>
<li><a href="gnun.html">HTML
- (196K bytes)</a> - entirely on one web page.</li>
+ (208K bytes)</a> - entirely on one web page.</li>
<li><a href="html_node/index.html">HTML</a> - with one web page per
node.</li>
<li><a href="gnun.html.gz">HTML compressed
- (48K gzipped characters)</a> - entirely on
+ (52K gzipped characters)</a> - entirely on
one web page.</li>
<li><a href="gnun.html_node.tar.gz">HTML compressed
- (60K gzipped tar file)</a> -
+ (64K gzipped tar file)</a> -
with one web page per node.</li>
<li><a href="gnun.info.tar.gz">Info document
- (40K bytes gzipped tar file)</a>.</li>
+ (44K bytes gzipped tar file)</a>.</li>
<li><a href="gnun.txt">ASCII text
- (120K bytes)</a>.</li>
+ (128K bytes)</a>.</li>
<li><a href="gnun.txt.gz">ASCII text compressed
(40K bytes gzipped)</a>.</li>
<li><a href="gnun.dvi.gz">TeX dvi file
- (64K bytes gzipped)</a>.</li>
-<li><a href="gnun.ps.gz">PostScript file
- (292K bytes gzipped)</a>.</li>
+ (68K bytes gzipped)</a>.</li>
<li><a href="gnun.pdf">PDF file
- (400K bytes)</a>.</li>
+ (416K bytes)</a>.</li>
<li><a href="gnun.texi.tar.gz">Texinfo source
(68K bytes gzipped tar file).</a></li>
</ul>
Index: gnun/html_node/Advantages.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Advantages.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Advantages.html 4 Dec 2012 16:24:21 -0000 1.16
+++ gnun/html_node/Advantages.html 27 Dec 2012 14:45:34 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Advantages</title>
Index: gnun/html_node/Bugs.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Bugs.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Bugs.html 4 Dec 2012 16:24:21 -0000 1.16
+++ gnun/html_node/Bugs.html 27 Dec 2012 14:45:34 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Bugs</title>
@@ -30,7 +30,7 @@
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="index.html#Top" rel="up" title="Top">
<link href="Index.html#Index" rel="next" title="Index">
-<link href="Rules.html#Rules" rel="previous" title="Rules">
+<link href="gnun_002dclear_002dprevious.html#gnun_002dclear_002dprevious"
rel="previous" title="gnun-clear-previous">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
Index: gnun/html_node/Comments-for-Translators.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/Comments-for-Translators.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- gnun/html_node/Comments-for-Translators.html 4 Dec 2012 16:24:21
-0000 1.6
+++ gnun/html_node/Comments-for-Translators.html 27 Dec 2012 14:45:34
-0000 1.7
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Comments for Translators</title>
Index: gnun/html_node/Compendia.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Compendia.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- gnun/html_node/Compendia.html 4 Dec 2012 16:24:21 -0000 1.5
+++ gnun/html_node/Compendia.html 27 Dec 2012 14:45:34 -0000 1.6
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Compendia</title>
@@ -29,7 +29,7 @@
<link href="Index.html#Index" rel="index" title="Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="PO-Files.html#PO-Files" rel="up" title="PO Files">
-<link href="Webmaster-Tips.html#Webmaster-Tips" rel="next" title="Webmaster
Tips">
+<link href="GNU-News.html#GNU-News" rel="next" title="GNU News">
<link href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron"
rel="previous" title="GNUmakefile.team and Cron">
<style type="text/css">
<!--
@@ -67,11 +67,11 @@
<a name="Compendia"></a>
<div class="header">
<p>
-Previous: <a href="PO-Files-and-Team.html#PO-Files-and-Team" accesskey="p"
rel="previous">PO Files and Team</a>, Up: <a href="PO-Files.html#PO-Files"
accesskey="u" rel="up">PO Files</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="GNU-News.html#GNU-News" accesskey="n" rel="next">GNU News</a>,
Previous: <a href="PO-Files-and-Team.html#PO-Files-and-Team" accesskey="p"
rel="previous">PO Files and Team</a>, Up: <a href="PO-Files.html#PO-Files"
accesskey="u" rel="up">PO Files</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="Using-Compendia"></a>
-<h4 class="subsection">2.3.8 Using Compendia</h4>
+<h4 class="subsection">2.3.7 Using Compendia</h4>
<a name="index-compendia"></a>
<a name="index-translation-memory"></a>
<a name="index-exclude_002epot"></a>
@@ -120,7 +120,7 @@
<hr>
<div class="header">
<p>
-Previous: <a href="PO-Files-and-Team.html#PO-Files-and-Team" accesskey="p"
rel="previous">PO Files and Team</a>, Up: <a href="PO-Files.html#PO-Files"
accesskey="u" rel="up">PO Files</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="GNU-News.html#GNU-News" accesskey="n" rel="next">GNU News</a>,
Previous: <a href="PO-Files-and-Team.html#PO-Files-and-Team" accesskey="p"
rel="previous">PO Files and Team</a>, Up: <a href="PO-Files.html#PO-Files"
accesskey="u" rel="up">PO Files</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
Index: gnun/html_node/Concepts.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Concepts.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Concepts.html 4 Dec 2012 16:24:21 -0000 1.16
+++ gnun/html_node/Concepts.html 27 Dec 2012 14:45:34 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Concepts</title>
@@ -70,8 +70,8 @@
Next: <a href="Advantages.html#Advantages" accesskey="n"
rel="next">Advantages</a>, Previous: <a href="Overview.html#Overview"
accesskey="p" rel="previous">Overview</a>, Up: <a
href="Introduction.html#Introduction" accesskey="u" rel="up">Introduction</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<hr>
-<a name="What-GNUnited-Nations-is-and-Should-be"></a>
-<h3 class="section">1.2 What GNUnited Nations is and Should be</h3>
+<a name="What-GNUnited-Nations-Is-and-Should-Be"></a>
+<h3 class="section">1.2 What GNUnited Nations Is and Should Be</h3>
<p>The basic concept behind GNUN is that localization of HTML articles is
similar to localization of computer programs<a name="DOCF1"
href="#FOOT1"><sup>1</sup></a>. In articles, like in programs, not every
string is considered
@@ -127,8 +127,8 @@
particular language.
</p>
<p>The first time though, there is no
<samp><var>article</var>.<var>lang</var>.po</samp>
-yet, so a translator must manually copy <samp><var>article</var>.pot</samp> to
-<samp><var>article</var>.<var>lang</var>.po</samp>, where <var>lang</var>
represents the
+yet, so a translator must make
<samp><var>article</var>.<var>lang</var>.po</samp> from
+<samp><var>article</var>.pot</samp>, where <var>lang</var> represents the
target language. See <a href="New-Translation.html#New-Translation">New
Translation</a>, for details.
</p>
<p>Then comes the initial translation of messages in
@@ -158,7 +158,7 @@
articles. If the original article changes, GNUN will automatically
rebuild <samp><var>article</var>.pot</samp>, and will merge the changes to
<samp><var>article</var>.<var>lang</var>.po</samp>. Any outdated translations
will be
-marked as fuzzy, any new strings will be added with empty translations,
+marked as “fuzzy,” any new strings will be added with empty
translations,
waiting to be translated. In the same run
<samp><var>article</var>.<var>lang</var>.html</samp> will be rebuilt so the
relevant
strings in the translation will be substituted with the original English
@@ -166,19 +166,20 @@
<samp><var>article</var>.<var>lang</var>.po</samp>.
</p>
<p>Those changes in the original article that do not affect the
-translatable strings will not lead to changes in
+translatable strings (or just delete whole strings) will not lead
+to changes in
<samp><var>article</var>.<var>lang</var>.po</samp>. Thus, no actions from
translators
will be needed. <samp><var>article</var>.<var>lang</var>.html</samp> will be
automatically regenerated to reflect the changes.
</p>
-
<p>The POT for every article under GNUN’s control is kept in the
‘www’
repository under a special directory <samp>po/</samp>, which is a
sub-directory of the relevant directory in the ‘www’ tree. So, for
‘<code>http://www.gnu.org/philosophy/free-sw.html</code>’ that is
<samp>philosophy/po/</samp>. Except <samp>free-sw.pot</samp>, this directory
holds
the canonical source of every translation, like <samp>free-sw.bg.po</samp>,
-<samp>free-sw.ca.po</samp>, etc.
+<samp>free-sw.ca.po</samp>, etc. For more details,
+See <a href="Files-and-Directories.html#Files-and-Directories">Files and
Directories</a>.
</p>
<p>Several additional features are implemented, like automatic update of
the list of the available translations. For example, if a new
Index: gnun/html_node/Copying-This-Manual.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/Copying-This-Manual.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Copying-This-Manual.html 4 Dec 2012 16:24:21 -0000
1.16
+++ gnun/html_node/Copying-This-Manual.html 27 Dec 2012 14:45:34 -0000
1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Copying This Manual</title>
Index: gnun/html_node/Credits-Slot.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Credits-Slot.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Credits-Slot.html 4 Dec 2012 16:24:21 -0000 1.16
+++ gnun/html_node/Credits-Slot.html 27 Dec 2012 14:45:34 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Credits Slot</title>
@@ -29,7 +29,7 @@
<link href="Index.html#Index" rel="index" title="Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="New-Translation.html#New-Translation" rel="up" title="New
Translation">
-<link href="Migrating.html#Migrating" rel="next" title="Migrating">
+<link href="PO-Tips.html#PO-Tips" rel="next" title="PO Tips">
<link href="Notes-Slot.html#Notes-Slot" rel="previous" title="Notes Slot">
<style type="text/css">
<!--
Index: gnun/html_node/Disadvantages.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/Disadvantages.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Disadvantages.html 4 Dec 2012 16:24:21 -0000 1.16
+++ gnun/html_node/Disadvantages.html 27 Dec 2012 14:45:34 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Disadvantages</title>
@@ -82,6 +82,11 @@
feasible with current build server hardware. Additionally, any errors
interrupt the build so they have to be fixed before the next articles
are processed.
+
+</li><li> In some rare cases (most notably, for alphabetically sorted lists)
+the structure of the translation should diverge from the structure
+of the original document. So far, our system has developped no means
+of taking such issues into account.
</li></ul>
Index: gnun/html_node/GNU-News.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/GNU-News.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/GNU-News.html 4 Dec 2012 16:24:21 -0000 1.16
+++ gnun/html_node/GNU-News.html 27 Dec 2012 14:45:35 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: GNU News</title>
@@ -29,8 +29,8 @@
<link href="Index.html#Index" rel="index" title="Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="PO-Files.html#PO-Files" rel="up" title="PO Files">
-<link href="PO-Tips.html#PO-Tips" rel="next" title="PO Tips">
-<link href="Migrating.html#Migrating" rel="previous" title="Migrating">
+<link href="Webmaster-Tips.html#Webmaster-Tips" rel="next" title="Webmaster
Tips">
+<link href="Compendia.html#Compendia" rel="previous" title="Compendia">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -67,11 +67,11 @@
<a name="GNU-News"></a>
<div class="header">
<p>
-Next: <a href="PO-Tips.html#PO-Tips" accesskey="n" rel="next">PO Tips</a>,
Previous: <a href="Migrating.html#Migrating" accesskey="p"
rel="previous">Migrating</a>, Up: <a href="PO-Files.html#PO-Files"
accesskey="u" rel="up">PO Files</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="Compendia.html#Compendia" accesskey="p"
rel="previous">Compendia</a>, Up: <a href="PO-Files.html#PO-Files"
accesskey="u" rel="up">PO Files</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="Special-Handling-for-GNU-News"></a>
-<h4 class="subsection">2.3.3 Special Handling for GNU News</h4>
+<h4 class="subsection">2.3.8 Special Handling for GNU News</h4>
<a name="index-gnunews"></a>
<a name="index-whatsnew"></a>
<a name="index-gnusflashes"></a>
Index: gnun/html_node/GNUmakefile_002eteam-Targets.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/GNUmakefile_002eteam-Targets.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- gnun/html_node/GNUmakefile_002eteam-Targets.html 4 Dec 2012 16:26:16
-0000 1.1
+++ gnun/html_node/GNUmakefile_002eteam-Targets.html 27 Dec 2012 14:45:35
-0000 1.2
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: GNUmakefile.team Targets</title>
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="Targets-in-GNUmakefile_002eteam"></a>
-<h4 class="subsubsection">2.3.7.2 Targets in <samp>GNUmakefile.team</samp></h4>
+<h4 class="subsubsection">2.3.6.2 Targets in <samp>GNUmakefile.team</samp></h4>
<dl compact="compact">
<dt><code>update</code></dt>
@@ -87,8 +87,98 @@
</p>
</dd>
<dt><code>report</code></dt>
-<dd><p>Verifies which translations are complete, and prints a list (with
-statistics) of those that need to be updated.
+<dd><a name="report-in-GNUmakefile_002eteam"></a><p>Verifies which
translations are complete, and prints a list (with
+statistics) of those that need to be updated. Also, it reports
+the translations that are not consistent with the revisions from
+<em>www</em> repository.
+</p>
+<p>More fine-grained notifications are implemented as the <code>notify</code>
+target.
+</p>
+</dd>
+<dt><code>notify</code></dt>
+<dd><a name="index-outdated-translations_002c-notifications"></a>
+<p>Invokes the <code>report</code> target, filters its output for different
+translators and sends them notifications.
+</p>
+<p>As an addition to the output of the <code>report</code> target, URLs for
+relevant files are written; also, when <em>www</em> and team revisions
+are not consistent, their differences generated with
+<code>gnun-diff-po</code> are optionally attached (see <a
href="gnun_002ddiff_002dpo.html#gnun_002ddiff_002dpo">gnun-diff-po</a>,
+for more details).
+</p>
+<a name="index-nottab"></a>
+<p>The list of files to report against are configured with <samp>nottab</samp>
+file. The lines of this file that begin with ‘#’ are ignored;
+other lines should contain two fields separated by ‘:’.
+</p>
+<p>The first field is an extended grep regular expression; the files are
+selected for the report if their names match this expression.
+See <a
href="http://www.gnu.org/software/grep/manual/html_node/Regular-Expressions.html#Regular-Expressions";>Regular
Expressions</a> in <cite>GNU Grep manual</cite>.
+</p>
+<p>The second field is a space-separated list of single-word translators’
+identifiers for which the line applies. The file may look like this:
+</p>
+<div class="example">
+<pre class="example">^gnu/gnu-history: alice bob carol
+^distros/(common-distros|distros|screenshot): dan alice
+^(licenses|philosophy)/: eve bob frank
+^licenses/: dan
+</pre></div>
+
+<a name="index-email_002daliases"></a>
+<p>Email addresses of the translators are kept in a separate file,
+<samp>email-aliases</samp>. Like <samp>nottab</samp>, this file contains lines
+separated by ‘:’; the lines beginning with ‘#’ are
ignored.
+</p>
+<p>The first field is translators’ identifier, the second is
+space-separated list of translators’ email addresses. These two
+fields are mandatory.
+</p>
+<a name="index-reminder-period"></a>
+<a name="index-notification-period"></a>
+<p>The third field is the personal reminder period in days. After that
+period the message is sent again even though its contents don’t
+change. Otherwise, the <code>notify</code> target only sends messages when
+something changes. Naturally, no message is sent when no action
+is needed in the requested set of translations.
+</p>
+<p>The team-wide default period is defined in its GNUmakefile.team using
+the <code>NOTIFICATION_PERIOD</code> variable.
+</p>
+<p>The fourth field provides comma-separated options for the report.
+Currently recognized options are:
+</p>
+<dl compact="compact">
+<dt><code>no-diffs</code></dt>
+<dd><p>Disables sending <em>www</em> vs. <em>www-<var>lang</var></em>
differences
+as attachments.
+</p>
+</dd>
+<dt><code>www</code></dt>
+<dd><p>Report cases that suggest actions by the team leader, that is,
+when the translation in the team repository is full whereas
+in <em>www</em> it is incomplete or absent.
+</p></dd>
+</dl>
+
+<p>This is an example of <samp>email-aliases</samp>:
+</p>
+<div class="example">
+<pre class="example">alice:address@hidden address@hidden
+# Disable `dan' temporarily.
+#dan:address@hidden:5:no-diffs,www
+bob:address@hidden:3
+# Note that the third field is empty; the default value for period
+# will be used.
+carol:address@hidden address@hidden::no-diffs
+eve:address@hidden:2:www
+frank:address@hidden:1:www,no-diffs
+</pre></div>
+
+<p>The <samp>email-aliases</samp> file should be kept privately because it
+may contain personal email addresses of people. How to do this
+is out of scope of GNUN and this manual.
</p>
</dd>
<dt><code>format</code></dt>
@@ -108,7 +198,7 @@
</p>
</dd>
<dt><code>publish</code></dt>
-<dd><p>The <code>publish</code> rule’s task is to copy all modified
files to the
+<dd><a name="publish"></a><p>The <code>publish</code> rule’s task is to
copy all modified files to the
official <em>www</em> repository. It depends on the <code>format</code> target
to ensure that all files are re-wrapped to the standard line length
limit, but deliberately does not depend on <code>sync VCS=yes</code>.
@@ -116,7 +206,7 @@
files are in a satisfactory condition to be published, and this rule is
just a convenience to avoid multiple manual <code>cp</code> invocations.
As a rule of thumb, before running this rule it is sane to run
-<code>sync</code> and correct any <em>fuzzy</em> messages and other problems,
if
+<code>sync</code> and correct any “fuzzy” messages and other
problems, if
necessary.
</p>
<p>The <code>publish</code> rule does not depend on <code>sync</code>
explicitly,
@@ -148,9 +238,7 @@
</dd>
<dt><code>clean</code></dt>
-<dd><p>Deletes all backup and auto-generated files that some PO editors leave
-behind, namely—<samp><var>file</var>.po~</samp>,
<samp><var>file</var>.po.bak</samp> and
-<samp><var>file</var>.mo</samp>.
+<dd><p>Deletes all backup and auto-generated files.
</p></dd>
</dl>
@@ -158,14 +246,11 @@
To check the status of the translations, run <code>make report</code>.
</p>
<p>Feel free to replace all strings with equivalents in your native
-language and of course—do not hesitate to extend this file and modify
-it as much as you like. For example, useful extra functionality would
-be a target that will check which files have not yet been committed in
-the official repository, or which files have to be updated there
-(i.e. they were updated by the team members but not installed by the
-coordinator). Either way, if you come up with something interesting, it
-would be nice to send a message to <a
href="mailto:address@hidden";>address@hidden</a>, so that
-<samp>GNUmakefile.team</samp> gets updated for all teams’ benefit.
+language and of course—do not hesitate to extend this file and
+modify it as much as you like. If you come up with
+something interesting, it would be nice to send a message to
+<a href="mailto:address@hidden";>address@hidden</a>, so that
<samp>GNUmakefile.team</samp> gets
+updated for all teams’ benefit.
</p>
<hr>
<div class="header">
Index: gnun/html_node/GNUmakefile_002eteam-Variables.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/GNUmakefile_002eteam-Variables.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/GNUmakefile_002eteam-Variables.html 4 Dec 2012 16:24:22
-0000 1.16
+++ gnun/html_node/GNUmakefile_002eteam-Variables.html 27 Dec 2012 14:45:35
-0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: GNUmakefile.team Variables</title>
@@ -71,13 +71,15 @@
</div>
<hr>
<a name="Adopting-GNUmakefile_002eteam-for-a-Specific-Team"></a>
-<h4 class="subsubsection">2.3.7.1 Adopting <samp>GNUmakefile.team</samp> for a
Specific Team</h4>
+<h4 class="subsubsection">2.3.6.1 Adopting <samp>GNUmakefile.team</samp> for a
Specific Team</h4>
-<p>To adjust the makefile for your team, you need to edit two variables.
+<p>To adjust the makefile for your team, you need to edit the next
+variables.
</p>
<dl compact="compact">
<dt>‘<samp>TEAM</samp>’</dt>
<dd><p>Set this to the language code, like <code>bg</code> or
<code>pt-br</code>.
+It is autodetected if not defined.
</p>
</dd>
<dt>‘<samp>wwwdir</samp>’</dt>
@@ -87,7 +89,22 @@
repository at <samp>~/projects/www</samp>, the value of <code>wwwdir</code>
should
be <code>../www/</code> or <samp>/home/<var>user</var>/projects/www/</samp>.
Note the
slash at the end, it is important.
-</p></dd>
+</p>
+</dd>
+<dt>‘<samp>TEAM_URL_PREFIX</samp>’</dt>
+<dt>‘<samp>TEAM_URL_POSTFIX</samp>’</dt>
+<dd><p>These variables are used to transform the path to a file in team’s
+working copy into a URL for this file; they are only needed for
+automatic email notifications. It is expected that typically
+the URL will point to some sort of Web interface for the repository,
+for example,
+</p>
+<div class="example">
+<pre class="example">TEAM_URL_PREFIX :=
http://cvs.savannah.gnu.org/viewvc/*checkout*/www-bg/
+TEAM_URL_POSTFIX := ?root=www-bg
+</pre></div>
+
+</dd>
</dl>
<p>If two variants of one language share the same project and repository
@@ -99,6 +116,32 @@
of the build process.
</p>
<dl compact="compact">
+<dt>‘<samp>ADD_FUZZY_DIFF</samp>’</dt>
+<dd><p>The program to manage differences to “previous”
<code>msgid</code>s added to
+“fuzzy” translations when merging PO files. When undefined,
+the makefile tries to find <code>gnun-add-fuzzy-diff</code> and assigns
+the result to this variable. See <a
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff">gnun-add-fuzzy-diff</a>.
+</p>
+<p>Define to empty string to disable the feature.
+</p>
+</dd>
+<dt>‘<samp>NOTIFICATION_PERIOD=<var>days</var></samp>’</dt>
+<dd><a name="index-NOTIFICATION_005fPERIOD"></a>
+<a name="index-reminder-period_002c-default"></a>
+<a name="index-notification-period_002c-default"></a>
+<p>Default period of reminders sent by the <code>notify</code> target.
+</p>
+<a name="index-mail_002c-notifications-1"></a>
+<a name="index-NOTIFY-1"></a>
+</dd>
+<dt>‘<samp>NOTIFY=yes</samp>’</dt>
+<dd><p>Make the <code>notify</code> target actually send notifications.
+</p>
+</dd>
+<dt>‘<samp>NOTIFY=no</samp>’</dt>
+<dd><p>Do not send email notifications about errors. This is the default.
+</p>
+</dd>
<dt>‘<samp>VERBOSE=yes</samp>’</dt>
<dd><p>Print more information from <code>cvs</code>, <code>svn</code> and
<code>msgmerge</code>; off by default. Note that <code>VERBOSE</code> can be
@@ -119,6 +162,11 @@
</p></dd>
</dl>
+<hr>
+<div class="header">
+<p>
+Next: <a href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets"
accesskey="n" rel="next">GNUmakefile.team Targets</a>, Up: <a
href="PO-Files-and-Team.html#PO-Files-and-Team" accesskey="u" rel="up">PO Files
and Team</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
Index: gnun/html_node/GNUmakefile_002eteam-and-Cron.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/GNUmakefile_002eteam-and-Cron.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/GNUmakefile_002eteam-and-Cron.html 4 Dec 2012 16:24:22
-0000 1.16
+++ gnun/html_node/GNUmakefile_002eteam-and-Cron.html 27 Dec 2012 14:45:35
-0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: GNUmakefile.team and Cron</title>
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="Automatic-Synchronization-and-Status-Reports"></a>
-<h4 class="subsubsection">2.3.7.3 Automatic Synchronization and Status
Reports</h4>
+<h4 class="subsubsection">2.3.6.3 Automatic Synchronization and Status
Reports</h4>
<a name="index-team-maintenance_002c-cron"></a>
<a name="index-cron_002c-team-maintenance"></a>
Index: gnun/html_node/GRACE.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/GRACE.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- gnun/html_node/GRACE.html 4 Dec 2012 16:24:22 -0000 1.2
+++ gnun/html_node/GRACE.html 27 Dec 2012 14:45:35 -0000 1.3
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<!-- This file redirects to the location of a node or anchor -->
<head>
<title>GNUnited Nations: GRACE</title>
Index: gnun/html_node/Index.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Index.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Index.html 4 Dec 2012 16:24:22 -0000 1.16
+++ gnun/html_node/Index.html 27 Dec 2012 14:45:35 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Index</title>
@@ -149,6 +149,7 @@
<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-directories_002c-defining">directories,
defining</a>:</td><td> </td><td valign="top"><a
href="Main-Variables.html#Main-Variables">Main Variables</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Index_cp_letter-E">E</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="GNUmakefile_002eteam-Targets.html#index-email_002daliases">email-aliases</a>:</td><td> </td><td
valign="top"><a
href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets">GNUmakefile.team
Targets</a></td></tr>
<tr><td></td><td valign="top"><a
href="Compendia.html#index-exclude_002epot">exclude.pot</a>:</td><td> </td><td
valign="top"><a href="Compendia.html#Compendia">Compendia</a></td></tr>
<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-extra_002dtemplates">extra-templates</a>:</td><td> </td><td
valign="top"><a href="Main-Variables.html#Main-Variables">Main
Variables</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
@@ -179,7 +180,8 @@
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Index_cp_letter-M">M</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-mail_002c-notifications">mail,
notifications</a>:</td><td> </td><td valign="top"><a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></td></tr>
-<tr><td></td><td valign="top"><a
href="mailfail.html#index-mail_002c-notifications-1">mail,
notifications</a>:</td><td> </td><td valign="top"><a
href="mailfail.html#mailfail">mailfail</a></td></tr>
+<tr><td></td><td valign="top"><a
href="GNUmakefile_002eteam-Variables.html#index-mail_002c-notifications-1">mail,
notifications</a>:</td><td> </td><td valign="top"><a
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables">GNUmakefile.team
Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="mailfail.html#index-mail_002c-notifications-2">mail,
notifications</a>:</td><td> </td><td valign="top"><a
href="mailfail.html#mailfail">mailfail</a></td></tr>
<tr><td></td><td valign="top"><a
href="Migrating.html#index-migration_002c-translations">migration,
translations</a>:</td><td> </td><td valign="top"><a
href="Migrating.html#Migrating">Migrating</a></td></tr>
<tr><td></td><td valign="top"><a
href="gnun_002dpreconvert.html#index-migration_002c-translations-1">migration,
translations</a>:</td><td> </td><td valign="top"><a
href="gnun_002dpreconvert.html#gnun_002dpreconvert">gnun-preconvert</a></td></tr>
<tr><td></td><td valign="top"><a
href="gnun_002dmerge_002dpreconverted.html#index-migration_002c-translations-2">migration,
translations</a>:</td><td> </td><td valign="top"><a
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a></td></tr>
@@ -189,29 +191,34 @@
<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-new-translations_002c-notifications_002fannouncements">new
translations, notifications/announcements</a>:</td><td> </td><td
valign="top"><a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></td></tr>
<tr><td></td><td valign="top"><a
href="New-Translation.html#index-notes_002c-translators">notes,
translators</a>:</td><td> </td><td valign="top"><a
href="New-Translation.html#New-Translation">New Translation</a></td></tr>
<tr><td></td><td valign="top"><a
href="Notes-Slot.html#index-notes_002c-translators-1">notes,
translators</a>:</td><td> </td><td valign="top"><a
href="Notes-Slot.html#Notes-Slot">Notes Slot</a></td></tr>
+<tr><td></td><td valign="top"><a
href="GNUmakefile_002eteam-Targets.html#index-notification-period">notification
period</a>:</td><td> </td><td valign="top"><a
href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets">GNUmakefile.team
Targets</a></td></tr>
+<tr><td></td><td valign="top"><a
href="GNUmakefile_002eteam-Variables.html#index-notification-period_002c-default">notification
period, default</a>:</td><td> </td><td valign="top"><a
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables">GNUmakefile.team
Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="GNUmakefile_002eteam-Variables.html#index-NOTIFICATION_005fPERIOD">NOTIFICATION_PERIOD</a>:</td><td> </td><td
valign="top"><a
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables">GNUmakefile.team
Variables</a></td></tr>
<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-NOTIFY">NOTIFY</a>:</td><td> </td><td
valign="top"><a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="GNUmakefile_002eteam-Variables.html#index-NOTIFY-1">NOTIFY</a>:</td><td> </td><td
valign="top"><a
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables">GNUmakefile.team
Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="GNUmakefile_002eteam-Targets.html#index-nottab">nottab</a>:</td><td> </td><td
valign="top"><a
href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets">GNUmakefile.team
Targets</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Index_cp_letter-O">O</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-optional_002dtemplates">optional-templates</a>:</td><td> </td><td
valign="top"><a href="Main-Variables.html#Main-Variables">Main
Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="GNUmakefile_002eteam-Targets.html#index-outdated-translations_002c-notifications">outdated
translations, notifications</a>:</td><td> </td><td valign="top"><a
href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets">GNUmakefile.team
Targets</a></td></tr>
<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-OUTDATED_002dGRACE">OUTDATED-GRACE</a>:</td><td> </td><td
valign="top"><a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></td></tr>
<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-output_002c-detailed">output,
detailed</a>:</td><td> </td><td valign="top"><a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Index_cp_letter-P">P</a></th><td></td><td></td></tr>
-<tr><td></td><td valign="top"><a href="PO-Files.html#index-PO-editors">PO
editors</a>:</td><td> </td><td valign="top"><a
href="PO-Files.html#PO-Files">PO Files</a></td></tr>
<tr><td></td><td valign="top"><a
href="New-Translation.html#index-PO-headers">PO
headers</a>:</td><td> </td><td valign="top"><a
href="New-Translation.html#New-Translation">New Translation</a></td></tr>
-<tr><td></td><td valign="top"><a
href="PO-Files.html#index-PO_002c-editing">PO,
editing</a>:</td><td> </td><td valign="top"><a
href="PO-Files.html#PO-Files">PO Files</a></td></tr>
<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-POT-generation_002c-articles">POT generation,
articles</a>:</td><td> </td><td valign="top"><a
href="Main-Variables.html#Main-Variables">Main Variables</a></td></tr>
<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-previous_002c-diff">previous,
diff</a>:</td><td> </td><td valign="top"><a
href="Main-Variables.html#Main-Variables">Main Variables</a></td></tr>
<tr><td></td><td valign="top"><a
href="gnun_002dadd_002dfuzzy_002ddiff.html#index-previous_002c-diff-1">previous,
diff</a>:</td><td> </td><td valign="top"><a
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff">gnun-add-fuzzy-diff</a></td></tr>
<tr><td></td><td valign="top"><a
href="gnun_002dclear_002dprevious.html#index-previous_002c-manipulating-PO-files">previous,
manipulating PO files</a>:</td><td> </td><td valign="top"><a
href="gnun_002dclear_002dprevious.html#gnun_002dclear_002dprevious">gnun-clear-previous</a></td></tr>
<tr><td></td><td valign="top"><a
href="Invoking-GNUN.html#index-priorities_002emk">priorities.mk</a>:</td><td> </td><td
valign="top"><a href="Invoking-GNUN.html#Invoking-GNUN">Invoking
GNUN</a></td></tr>
<tr><td></td><td valign="top"><a
href="report.html#index-priorities_002emk-1">priorities.mk</a>:</td><td> </td><td
valign="top"><a href="report.html#report">report</a></td></tr>
-<tr><td></td><td valign="top"><a
href="PO-Files-and-Team.html#index-priorities_002emk-2">priorities.mk</a>:</td><td> </td><td
valign="top"><a href="PO-Files-and-Team.html#PO-Files-and-Team">PO Files and
Team</a></td></tr>
-<tr><td></td><td valign="top"><a
href="gnun_002dreport.html#index-priorities_002emk-3">priorities.mk</a>:</td><td> </td><td
valign="top"><a
href="gnun_002dreport.html#gnun_002dreport">gnun-report</a></td></tr>
+<tr><td></td><td valign="top"><a
href="gnun_002dreport.html#index-priorities_002emk-2">priorities.mk</a>:</td><td> </td><td
valign="top"><a
href="gnun_002dreport.html#gnun_002dreport">gnun-report</a></td></tr>
<tr><td></td><td valign="top"><a
href="PO-Files-and-Team.html#index-project-repository">project
repository</a>:</td><td> </td><td valign="top"><a
href="PO-Files-and-Team.html#PO-Files-and-Team">PO Files and Team</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Index_cp_letter-R">R</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a
href="PO-Tips.html#index-recommendations_002c-PO-files">recommendations, PO
files</a>:</td><td> </td><td valign="top"><a
href="PO-Tips.html#PO-Tips">PO Tips</a></td></tr>
+<tr><td></td><td valign="top"><a
href="GNUmakefile_002eteam-Targets.html#index-reminder-period">reminder
period</a>:</td><td> </td><td valign="top"><a
href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets">GNUmakefile.team
Targets</a></td></tr>
+<tr><td></td><td valign="top"><a
href="GNUmakefile_002eteam-Variables.html#index-reminder-period_002c-default">reminder
period, default</a>:</td><td> </td><td valign="top"><a
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables">GNUmakefile.team
Variables</a></td></tr>
<tr><td></td><td valign="top"><a
href="report.html#index-reporting">reporting</a>:</td><td> </td><td
valign="top"><a href="report.html#report">report</a></td></tr>
<tr><td></td><td valign="top"><a
href="gnun_002dreport.html#index-reporting-1">reporting</a>:</td><td> </td><td
valign="top"><a
href="gnun_002dreport.html#gnun_002dreport">gnun-report</a></td></tr>
<tr><td></td><td valign="top"><a
href="Bugs.html#index-reporting-bugs">reporting
bugs</a>:</td><td> </td><td valign="top"><a
href="Bugs.html#Bugs">Bugs</a></td></tr>
Index: gnun/html_node/Internals.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Internals.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Internals.html 4 Dec 2012 16:24:22 -0000 1.16
+++ gnun/html_node/Internals.html 27 Dec 2012 14:45:35 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Internals</title>
@@ -29,7 +29,7 @@
<link href="Index.html#Index" rel="index" title="Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="index.html#Top" rel="up" title="Top">
-<link href="Scripts.html#Scripts" rel="next" title="Scripts">
+<link href="Files-and-Directories.html#Files-and-Directories" rel="next"
title="Files and Directories">
<link href="Splitting-Long-Passages.html#Splitting-Long-Passages"
rel="previous" title="Splitting Long Passages">
<style type="text/css">
<!--
@@ -79,9 +79,9 @@
of programs that may also be useful for the translators.
</p>
<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top">• <a href="Scripts.html#Scripts"
accesskey="1">Scripts</a>:</td><td> </td><td align="left"
valign="top">Helper scripts.
+<tr><td align="left" valign="top">• <a
href="Files-and-Directories.html#Files-and-Directories" accesskey="1">Files and
Directories</a>:</td><td> </td><td align="left" valign="top">What,
where, when.
</td></tr>
-<tr><td align="left" valign="top">• <a href="Rules.html#Rules"
accesskey="2">Rules</a>:</td><td> </td><td align="left"
valign="top">The knotty rules explained.
+<tr><td align="left" valign="top">• <a href="Scripts.html#Scripts"
accesskey="2">Scripts</a>:</td><td> </td><td align="left"
valign="top">Helper scripts.
</td></tr>
</table>
Index: gnun/html_node/Introduction.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Introduction.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Introduction.html 4 Dec 2012 16:24:22 -0000 1.16
+++ gnun/html_node/Introduction.html 27 Dec 2012 14:45:35 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Introduction</title>
@@ -73,7 +73,7 @@
<a name="Introduction-to-GNUnited-Nations"></a>
<h2 class="chapter">1 Introduction to GNUnited Nations</h2>
-<p>GNUnited Nations (abbreviated GNUN) is a collection of makefiles and
+<p>GNUnited Nations (abbreviated GNUN) is a collection of
scripts that are supposed to make the life of <a
href="http://gnu.org";>http://gnu.org</a>
translators easier. Although it is specifically developed for the GNU
Project’s website, it could be customized, at least in theory, to fit
Index: gnun/html_node/Invoking-GNUN.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/Invoking-GNUN.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Invoking-GNUN.html 4 Dec 2012 16:24:22 -0000 1.16
+++ gnun/html_node/Invoking-GNUN.html 27 Dec 2012 14:45:35 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Invoking GNUN</title>
Index: gnun/html_node/Localized-URLs.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/Localized-URLs.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- gnun/html_node/Localized-URLs.html 4 Dec 2012 16:24:22 -0000 1.6
+++ gnun/html_node/Localized-URLs.html 27 Dec 2012 14:45:35 -0000 1.7
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Localized URLs</title>
Index: gnun/html_node/Main-Variables.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/Main-Variables.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Main-Variables.html 4 Dec 2012 16:24:22 -0000 1.16
+++ gnun/html_node/Main-Variables.html 27 Dec 2012 14:45:35 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Main Variables</title>
@@ -70,8 +70,8 @@
Next: <a href="PO-Files.html#PO-Files" accesskey="n" rel="next">PO Files</a>,
Previous: <a href="Invoking-GNUN.html#Invoking-GNUN" accesskey="p"
rel="previous">Invoking GNUN</a>, Up: <a href="Usage.html#Usage" accesskey="u"
rel="up">Usage</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<hr>
-<a name="Defining-Articles-to-be-Built"></a>
-<h3 class="section">2.2 Defining Articles to be Built</h3>
+<a name="Defining-Articles-to-Be-Built"></a>
+<h3 class="section">2.2 Defining Articles to Be Built</h3>
<a name="index-variables-1"></a>
<a name="index-gnun_002emk-1"></a>
@@ -83,12 +83,18 @@
<p>There are two types of variables, which are specifically separated in
order to make translators’ life easier: variables that translators are
free to modify and variables that are modified by the web-translators
-staff<a name="DOCF4" href="#FOOT4"><sup>4</sup></a>, ideally after performing
some local tests. A
+staff<a name="DOCF5" href="#FOOT5"><sup>5</sup></a>, ideally after performing
some local tests. A
translation team leader should update only <code>FUZZY_DIFF_LINGUAS</code>,
<code>TEMPLATE_LINGUAS</code>; everything else is supposed to be built
automagically, without manual intervention. If not, that is a bug that
should be reported and fixed.
</p>
+<p>You can also request building files separately this way:
+</p>
+<div class="example">
+<pre class="example">make -C server/gnun ../../philosophy/not-ipr.bg.html
+</pre></div>
+
<dl compact="compact">
<dd><a name="index-TEMPLATE_005fLINGUAS"></a>
<a name="index-templates_002c-defining"></a>
@@ -148,7 +154,7 @@
</dd>
<dt>‘<samp>FUZZY_DIFF_LINGUAS</samp>’</dt>
<dd><p>Add your language code here if you want GNUN to add differences to
-previous <code>msgid</code>s in your PO files. The differences are shown in
+“previous” <code>msgid</code>s in your PO files. The differences
are shown in
the default <code>wdiff</code> format. See <a
href="http://www.gnu.org/software/wdiff/manual/html_node/wdiff.html#wdiff";>The
word
difference finder</a> in <cite>GNU wdiff</cite>, for more information.
</p>
@@ -187,7 +193,7 @@
<hr>
<h4 class="footnotes-heading">Footnotes</h4>
-<h3><a name="FOOT4" href="#DOCF4">(4)</a></h3>
+<h3><a name="FOOT5" href="#DOCF5">(5)</a></h3>
<p>Only because presumably, they are more familiar with
GNUnited Nations’ internals. From a purely technical point of view,
there is no difference.</p>
Index: gnun/html_node/Migrating.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Migrating.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- gnun/html_node/Migrating.html 4 Dec 2012 16:24:22 -0000 1.17
+++ gnun/html_node/Migrating.html 27 Dec 2012 14:45:35 -0000 1.18
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Migrating</title>
@@ -29,8 +29,8 @@
<link href="Index.html#Index" rel="index" title="Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="PO-Files.html#PO-Files" rel="up" title="PO Files">
-<link href="GNU-News.html#GNU-News" rel="next" title="GNU News">
-<link href="Credits-Slot.html#Credits-Slot" rel="previous" title="Credits
Slot">
+<link href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
rel="next" title="generic.LANG.html">
+<link href="PO-Tips.html#PO-Tips" rel="previous" title="PO Tips">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -67,11 +67,11 @@
<a name="Migrating"></a>
<div class="header">
<p>
-Next: <a href="GNU-News.html#GNU-News" accesskey="n" rel="next">GNU News</a>,
Previous: <a href="New-Translation.html#New-Translation" accesskey="p"
rel="previous">New Translation</a>, Up: <a href="PO-Files.html#PO-Files"
accesskey="u" rel="up">PO Files</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
accesskey="n" rel="next">generic.LANG.html</a>, Previous: <a
href="PO-Tips.html#PO-Tips" accesskey="p" rel="previous">PO Tips</a>, Up: <a
href="PO-Files.html#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<hr>
<a name="Transforming-Existing-Translation-in-PO-Format"></a>
-<h4 class="subsection">2.3.2 Transforming Existing Translation in PO
Format</h4>
+<h4 class="subsection">2.3.3 Transforming Existing Translation in PO
Format</h4>
<a name="index-migration_002c-translations"></a>
<a name="index-conversion-of-existing-translations"></a>
@@ -121,7 +121,7 @@
<p>You get <samp>foo.<var>lang</var>.po</samp> where all messages are marked as
“fuzzy” (unless you use a compendium); you still should make sure
that
the translations correspond to the original and remove those
“fuzzy”
-marks. The script adds differences against previous <code>msgid</code>s to
+marks. The script adds differences against “previous”
<code>msgid</code>s to
facilitate checking.
</p>
<p>There is no need to delete the existing HTML translation, GNUN will
@@ -150,7 +150,7 @@
<hr>
<div class="header">
<p>
-Next: <a href="GNU-News.html#GNU-News" accesskey="n" rel="next">GNU News</a>,
Previous: <a href="New-Translation.html#New-Translation" accesskey="p"
rel="previous">New Translation</a>, Up: <a href="PO-Files.html#PO-Files"
accesskey="u" rel="up">PO Files</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
accesskey="n" rel="next">generic.LANG.html</a>, Previous: <a
href="PO-Tips.html#PO-Tips" accesskey="p" rel="previous">PO Tips</a>, Up: <a
href="PO-Files.html#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
Index: gnun/html_node/Modifying-Boilerplates.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/Modifying-Boilerplates.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- gnun/html_node/Modifying-Boilerplates.html 4 Dec 2012 16:24:22 -0000
1.6
+++ gnun/html_node/Modifying-Boilerplates.html 27 Dec 2012 14:45:35 -0000
1.7
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Modifying Boilerplates</title>
Index: gnun/html_node/New-Translation.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/New-Translation.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/New-Translation.html 4 Dec 2012 16:24:22 -0000 1.16
+++ gnun/html_node/New-Translation.html 27 Dec 2012 14:45:35 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: New Translation</title>
@@ -67,7 +67,7 @@
<a name="New-Translation"></a>
<div class="header">
<p>
-Next: <a href="Migrating.html#Migrating" accesskey="n"
rel="next">Migrating</a>, Up: <a href="PO-Files.html#PO-Files" accesskey="u"
rel="up">PO Files</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+Next: <a href="PO-Tips.html#PO-Tips" accesskey="n" rel="next">PO Tips</a>, Up:
<a href="PO-Files.html#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<hr>
<a name="Starting-a-New-Translation"></a>
@@ -200,27 +200,32 @@
<p>It is recommended that you wrap all lines in the comments to be less
than 80 lines; that looks better from a purely aesthetic point of view
and improves the performance of <samp>GNUmakefile.team</samp>’s
<code>publish</code>
-rule (see <a
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables">GNUmakefile.team
Variables</a>).
+rule (see <a href="GNUmakefile_002eteam-Targets.html#publish">publish</a>).
</p>
<p>There are some special messages that appear in the POT and PO:
</p>
<dl compact="compact">
<dd><a name="index-notes_002c-translators"></a>
<a name="index-translators_0027-notes"></a>
-</dd>
+<a name="GNUN-Slots"></a></dd>
<dt>‘<samp>*GNUN-SLOT: TRANSLATOR'S NOTES*</samp>’</dt>
<dd><p>This is for translator’s notes that are injected in the resulting
translation. See <a href="Notes-Slot.html#Notes-Slot">Notes Slot</a>, for
more information. If your
translation does not have notes, you <em>must</em> translate this as a
-space, that is, <tt class="key">SPC</tt>.
+space:
</p>
+<div class="example">
+<pre class="example">msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
+msgstr " "
+</pre></div>
+
<a name="index-credits_002c-translators"></a>
<a name="index-translators_0027-credits"></a>
</dd>
<dt>‘<samp>*GNUN-SLOT: TRANSLATOR'S CREDITS*</samp>’</dt>
<dd><p>This is again optional, and should contain the name (and address) of
the person who made the translation. “Translate” this string as a
-space (<tt class="key">SPC</tt>) if you do not want your name to appear there.
+space if you do not want your name to appear there.
See <a href="Credits-Slot.html#Credits-Slot">Credits Slot</a>.
</p></dd>
</dl>
@@ -282,7 +287,7 @@
<hr>
<div class="header">
<p>
-Next: <a href="Migrating.html#Migrating" accesskey="n"
rel="next">Migrating</a>, Up: <a href="PO-Files.html#PO-Files" accesskey="u"
rel="up">PO Files</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+Next: <a href="PO-Tips.html#PO-Tips" accesskey="n" rel="next">PO Tips</a>, Up:
<a href="PO-Files.html#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
Index: gnun/html_node/Notes-Slot.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Notes-Slot.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Notes-Slot.html 4 Dec 2012 16:24:23 -0000 1.16
+++ gnun/html_node/Notes-Slot.html 27 Dec 2012 14:45:35 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Notes Slot</title>
Index: gnun/html_node/Overview.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Overview.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Overview.html 4 Dec 2012 16:24:23 -0000 1.16
+++ gnun/html_node/Overview.html 27 Dec 2012 14:45:35 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Overview</title>
@@ -70,8 +70,8 @@
Next: <a href="Concepts.html#Concepts" accesskey="n" rel="next">Concepts</a>,
Up: <a href="Introduction.html#Introduction" accesskey="u"
rel="up">Introduction</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
-<a name="Why-GNUN-is-Being-Developed"></a>
-<h3 class="section">1.1 Why GNUN is Being Developed</h3>
+<a name="Why-GNUN-Is-Being-Developed"></a>
+<h3 class="section">1.1 Why GNUN Is Being Developed</h3>
<p>The GNU Project’s website, <a
href="http://www.gnu.org";>http://www.gnu.org</a>, has become
considerably large over the years. Maintaining it requires significant
Index: gnun/html_node/PO-Files-and-Team.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/PO-Files-and-Team.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/PO-Files-and-Team.html 4 Dec 2012 16:24:23 -0000
1.16
+++ gnun/html_node/PO-Files-and-Team.html 27 Dec 2012 14:45:35 -0000
1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: PO Files and Team</title>
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="Maintaining-Translations-in-Your-Team_0027s-Repository"></a>
-<h4 class="subsection">2.3.7 Maintaining Translations in Your Team’s
Repository</h4>
+<h4 class="subsection">2.3.6 Maintaining Translations in Your Team’s
Repository</h4>
<a name="index-project-repository"></a>
<a name="index-repository_002c-translation-project"></a>
<a name="index-team-maintenance"></a>
@@ -111,11 +111,12 @@
</pre></div>
<p>All members and the team leader commit in their project’s
-repository—when a translation is ready, the leader checks it in in the
-official ‘www’ repository. If an original article changes,
-a build could be invoked to synchronize (i.e. merge) the changes and
+repository—when a translation is ready, the leader checks it in the
+official ‘www’ repository. If an original article changes, a build
+could be invoked to synchronize (i.e. merge) the changes and
optionally automatically commit them so that the draft PO files are
-updated. A translator would then normally update the PO file, and
+updated; at the same time, automatic notifications are sent to the
+persons interested in particular translations<a name="DOCF6"
href="#FOOT6"><sup>6</sup></a>. A translator would then normally update the PO
file, and
commit it again in the project’s Sources repository, from where the
coordinator will pick it up and install it in ‘www’.
</p>
@@ -152,10 +153,6 @@
+--…
</pre></div>
-<a name="index-priorities_002emk-2"></a>
-<p>Add <samp>priorities.mk</samp> in order to make the <code>report</code>
target sort
-the files by priority.
-</p>
<p>The next sections explain how to adopt the makefile for your team and
how to invoke a “build”.
</p>
@@ -168,6 +165,17 @@
</td></tr>
</table>
+<div class="footnote">
+<hr>
+<h4 class="footnotes-heading">Footnotes</h4>
+
+<h3><a name="FOOT6" href="#DOCF6">(6)</a></h3>
+<p>The following
+sections describe in more details how to setup these automatic
+actions; however, if you have any difficulties with that, please ask
+the GNU Web Translation Managers to make it for your team using our
+server.</p>
+</div>
<hr>
<div class="header">
<p>
Index: gnun/html_node/PO-Files.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/PO-Files.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/PO-Files.html 4 Dec 2012 16:24:23 -0000 1.16
+++ gnun/html_node/PO-Files.html 27 Dec 2012 14:45:35 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: PO Files</title>
@@ -72,83 +72,33 @@
<hr>
<a name="Working-with-PO-Files"></a>
<h3 class="section">2.3 Working with PO Files</h3>
-<a name="index-PO_002c-editing"></a>
-<p>We anticipate that some gnu.org translators will find this format odd
-or inconvenient, if they never happened to work with PO files before.
-Don’t worry, you will soon get accustomed to it. It is the
-established format for translations in the Free World, and you should
-have no problems if you have translated software before.
+<p>This section provides GNUN-specific information about woking
+with PO files. For general information, see <a
href="http://www.gnu.org/software/trans-coord/manual/web-trans/html_node/PO-Files.html#PO-Files";>Working
with PO Files</a> in <cite>GNU Web Translators Manual</cite>.
</p>
-<p>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 it valid. Here is a list of widely used PO editors:
-</p>
-<ul>
-<li> <a name="index-PO-editors"></a>
-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 <samp>.po</samp> file you visit should automatically
-switch to PO mode. You can enable/disable it with <code>M-x po-mode
-<span class="key">RET</span></code>. On some GNU/Linux distros such as
gNewSense, PO mode is
-available in a separate package, <code>gettext-el</code>. See
-<a
href="http://www.gnu.org/software/gettext";>http://www.gnu.org/software/gettext</a>.
-
-</li><li> Gtranslator—the GNOME PO editor. See
-<a
href="http://projects.gnome.org/gtranslator/";>http://projects.gnome.org/gtranslator/</a>.
-
-</li><li> Lokalize—the KDE 4 editor. See
-<a
href="http://userbase.kde.org/Lokalize";>http://userbase.kde.org/Lokalize</a>.
-
-</li><li> KBabel—the KDE 3 editor. No longer supported, but might be
-available on some old systems.
-
-</li><li> Poedit—another popular editor that is based on the
<code>wxWidgets</code>
-graphical toolkit. See <a
href="http://www.poedit.net";>http://www.poedit.net</a>.
-
-</li><li> Virtaal—a relevantly new editor that supports also the XLIFF
format
-and uses the Translate Toolkit API. See
-<a
href="http://translate.sourceforge.net/wiki/virtaal";>http://translate.sourceforge.net/wiki/virtaal</a>.
-
-</li><li> po.vim—ftplugin for the Vim editor. The best option for
people who
-use Vim as their editor. See
-<a
href="http://www.vim.org/scripts/script.php?script_id=2530";>http://www.vim.org/scripts/script.php?script_id=2530</a>.
-
-</li><li> Various web-based editors. See <a
href="http://www.gnu.org/software/trans-coord/manual/web-trans/html_node/Savannah-VCS.html#Savannah-VCS";>Savannah
VCS</a> in <cite>GNU Web
-Translators Manual</cite>.
-</li></ul>
-
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top">• <a
href="New-Translation.html#New-Translation" accesskey="1">New
Translation</a>:</td><td> </td><td align="left" valign="top">How to
start a new translation.
</td></tr>
-<tr><td align="left" valign="top">• <a href="Migrating.html#Migrating"
accesskey="2">Migrating</a>:</td><td> </td><td align="left"
valign="top">How to migrate an existing translation to a PO
- format under GNUN’s control.
-</td></tr>
-<tr><td align="left" valign="top">• <a href="GNU-News.html#GNU-News"
accesskey="3">GNU News</a>:</td><td> </td><td align="left"
valign="top">How to handle “whatsnew” (a.k.a.
“gnunews”).
+<tr><td align="left" valign="top">• <a href="PO-Tips.html#PO-Tips"
accesskey="2">PO Tips</a>:</td><td> </td><td align="left"
valign="top">Tips and hints for translators.
</td></tr>
-<tr><td align="left" valign="top">• <a href="PO-Tips.html#PO-Tips"
accesskey="4">PO Tips</a>:</td><td> </td><td align="left"
valign="top">Tips and hints for translators.
+<tr><td align="left" valign="top">• <a href="Migrating.html#Migrating"
accesskey="3">Migrating</a>:</td><td> </td><td align="left"
valign="top">How to migrate an existing translation to a PO
+ format under GNUN’s control.
</td></tr>
-<tr><td align="left" valign="top">• <a
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
accesskey="5">generic.LANG.html</a>:</td><td> </td><td align="left"
valign="top">Specifying information that will propagate in
+<tr><td align="left" valign="top">• <a
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
accesskey="4">generic.LANG.html</a>:</td><td> </td><td align="left"
valign="top">Specifying information that will propagate in
every translation in a certain language.
</td></tr>
-<tr><td align="left" valign="top">• <a
href="languages_002etxt.html#languages_002etxt"
accesskey="6">languages.txt</a>:</td><td> </td><td align="left"
valign="top">Specifying canonical names for languages.
+<tr><td align="left" valign="top">• <a
href="languages_002etxt.html#languages_002etxt"
accesskey="5">languages.txt</a>:</td><td> </td><td align="left"
valign="top">Specifying canonical names for languages.
</td></tr>
-<tr><td align="left" valign="top">• <a
href="PO-Files-and-Team.html#PO-Files-and-Team" accesskey="7">PO Files and
Team</a>:</td><td> </td><td align="left" valign="top">How to
maintain translations in the team’s
+<tr><td align="left" valign="top">• <a
href="PO-Files-and-Team.html#PO-Files-and-Team" accesskey="6">PO Files and
Team</a>:</td><td> </td><td align="left" valign="top">How to
maintain translations in the team’s
repository.
</td></tr>
-<tr><td align="left" valign="top">• <a href="Compendia.html#Compendia"
accesskey="8">Compendia</a>:</td><td> </td><td align="left"
valign="top">Using translation memory.
+<tr><td align="left" valign="top">• <a href="Compendia.html#Compendia"
accesskey="7">Compendia</a>:</td><td> </td><td align="left"
valign="top">Using translation memory.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="GNU-News.html#GNU-News"
accesskey="8">GNU News</a>:</td><td> </td><td align="left"
valign="top">Obsolete: How to handle “whatsnew”.
</td></tr>
<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
</pre></th></tr></table>
-<hr>
-<div class="header">
-<p>
-Next: <a href="Webmaster-Tips.html#Webmaster-Tips" accesskey="n"
rel="next">Webmaster Tips</a>, Previous: <a
href="Main-Variables.html#Main-Variables" accesskey="p" rel="previous">Main
Variables</a>, Up: <a href="Usage.html#Usage" accesskey="u" rel="up">Usage</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
-</div>
Index: gnun/html_node/PO-Tips.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/PO-Tips.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/PO-Tips.html 4 Dec 2012 16:24:23 -0000 1.16
+++ gnun/html_node/PO-Tips.html 27 Dec 2012 14:45:35 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: PO Tips</title>
@@ -29,8 +29,8 @@
<link href="Index.html#Index" rel="index" title="Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="PO-Files.html#PO-Files" rel="up" title="PO Files">
-<link href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
rel="next" title="generic.LANG.html">
-<link href="GNU-News.html#GNU-News" rel="previous" title="GNU News">
+<link href="Migrating.html#Migrating" rel="next" title="Migrating">
+<link href="Credits-Slot.html#Credits-Slot" rel="previous" title="Credits
Slot">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -67,11 +67,11 @@
<a name="PO-Tips"></a>
<div class="header">
<p>
-Next: <a href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
accesskey="n" rel="next">generic.LANG.html</a>, Previous: <a
href="GNU-News.html#GNU-News" accesskey="p" rel="previous">GNU News</a>, Up: <a
href="PO-Files.html#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+Next: <a href="Migrating.html#Migrating" accesskey="n"
rel="next">Migrating</a>, Previous: <a
href="New-Translation.html#New-Translation" accesskey="p" rel="previous">New
Translation</a>, Up: <a href="PO-Files.html#PO-Files" accesskey="u" rel="up">PO
Files</a> [<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<hr>
<a name="Useful-Hints-for-Editing-PO-Files"></a>
-<h4 class="subsection">2.3.4 Useful Hints for Editing PO Files</h4>
+<h4 class="subsection">2.3.2 Useful Hints for Editing PO Files</h4>
<a name="index-tips_002c-translators"></a>
<a name="index-recommendations_002c-PO-files"></a>
@@ -130,9 +130,10 @@
"Boston, MA 02110-1301, USA"
</pre></div>
-</li><li> There is absolutely no reason to use HTML entities in translations
as a
-replacement for common non-ASCII characters. They are harder to write
-and serve no purpose.
+</li><li> 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;</samp>’ and this is a character from the
alphabet of your
+language, just write it as ‘<samp>ü</samp>’ directly.
</li><li> Wrapping of <code>msgstr</code> using <kbd>M-q</kbd> in Emacs (or
other means) is
considered harmful. It is best to leave GNUN (or more precisely, Po4a)
@@ -147,7 +148,7 @@
<hr>
<div class="header">
<p>
-Next: <a href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
accesskey="n" rel="next">generic.LANG.html</a>, Previous: <a
href="GNU-News.html#GNU-News" accesskey="p" rel="previous">GNU News</a>, Up: <a
href="PO-Files.html#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+Next: <a href="Migrating.html#Migrating" accesskey="n"
rel="next">Migrating</a>, Previous: <a
href="New-Translation.html#New-Translation" accesskey="p" rel="previous">New
Translation</a>, Up: <a href="PO-Files.html#PO-Files" accesskey="u" rel="up">PO
Files</a> [<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
Index: gnun/html_node/Runtime-Variables.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/Runtime-Variables.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Runtime-Variables.html 4 Dec 2012 16:24:23 -0000
1.16
+++ gnun/html_node/Runtime-Variables.html 27 Dec 2012 14:45:35 -0000
1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Runtime Variables</title>
@@ -125,8 +125,7 @@
</dd>
<dt>‘<samp>VALIDATE=no</samp>’</dt>
<dt>‘<samp>…</samp>’</dt>
-<dd><p>Does not perform validation of the HTML articles and PO files. This
-is the default, and not defining this variable has the same effect.
+<dd><p>Skips validation of the HTML articles and generated translations.
</p>
</dd>
<dt>‘<samp>VALIDATE=yes</samp>’</dt>
@@ -137,12 +136,14 @@
fix the errors that are reported as a result of enforcing validation.
</p>
<p>Articles defined in the variable <code>no-validate-articles</code> are never
-checked for HTML validity. Its purpose was to skip validation of HTML
-5 articles, until the command-line validation tools are updated to
+checked for HTML validity. Its purpose was to skip validation of HTML5
+articles, until the command-line validation tools are updated to
parse files that comply with this new standard. As of version 0.5
-GNUN supports HTML 5, so resorting to <code>no-validate-articles</code>
+GNUN supports HTML5, so resorting to <code>no-validate-articles</code>
should not be necessary.
</p>
+<p>This is the default, and not defining this variable has the same effect.
+</p>
<a name="index-NOTIFY"></a>
<a name="index-mail_002c-notifications"></a>
</dd>
@@ -192,7 +193,7 @@
<a name="index-deferred-generation-of-articles"></a>
<a name="GRACE"></a></dd>
<dt>‘<samp>GRACE=<var>days</var></samp>’</dt>
-<dd><p>If defined, ordinary articles that have fuzzy strings and are not older
+<dd><p>If defined, ordinary articles that have “fuzzy” strings and
are not older
than <var>days</var> will not be regenerated. This functionality is
implemented specifically to prevent gratuitous replacement of translated
strings with the English text when there are only minor formatting
@@ -231,7 +232,7 @@
<code>cvs|svn|bzr add</code>-ing all necessary files.
</p>
<a name="index-validation-1"></a>
-<p>When validation is enabled (i.e. with <code>VALIDATE=yes</code>), the
+<p>When validation is enabled, the
original English articles are validated first, before any commands
that generate the other files, and <code>make</code> exits with an error
on the first encountered article. This is done on purpose, to prevent
Index: gnun/html_node/Scripts.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Scripts.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Scripts.html 4 Dec 2012 16:24:23 -0000 1.16
+++ gnun/html_node/Scripts.html 27 Dec 2012 14:45:36 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Scripts</title>
@@ -30,7 +30,7 @@
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Internals.html#Internals" rel="up" title="Internals">
<link
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff"
rel="next" title="gnun-add-fuzzy-diff">
-<link href="Internals.html#Internals" rel="previous" title="Internals">
+<link href="Files-and-Directories.html#Files-and-Directories" rel="previous"
title="Files and Directories">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -67,11 +67,11 @@
<a name="Scripts"></a>
<div class="header">
<p>
-Next: <a href="Rules.html#Rules" accesskey="n" rel="next">Rules</a>, Up: <a
href="Internals.html#Internals" accesskey="u" rel="up">Internals</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+Previous: <a href="Files-and-Directories.html#Files-and-Directories"
accesskey="p" rel="previous">Files and Directories</a>, Up: <a
href="Internals.html#Internals" accesskey="u" rel="up">Internals</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<hr>
<a name="GNUN-Scripts"></a>
-<h3 class="section">3.1 GNUN Scripts</h3>
+<h3 class="section">3.2 GNUN Scripts</h3>
<p>For the time being there are several helper scripts. Some of them are
used internally as commands with certain arguments in the makefile
@@ -80,7 +80,7 @@
They all can be invoked separately, as stand-alone programs.
</p>
<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top">• <a
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff"
accesskey="1">gnun-add-fuzzy-diff</a>:</td><td> </td><td
align="left" valign="top">Add differences to previous
+<tr><td align="left" valign="top">• <a
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff"
accesskey="1">gnun-add-fuzzy-diff</a>:</td><td> </td><td
align="left" valign="top">Add differences to “previous”
<code>msgid</code>s.
</td></tr>
<tr><td align="left" valign="top">• <a
href="gnun_002ddiff_002dpo.html#gnun_002ddiff_002dpo"
accesskey="2">gnun-diff-po</a>:</td><td> </td><td align="left"
valign="top">Compare two revisions of a PO file.
Index: gnun/html_node/Special-Targets.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/Special-Targets.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Special-Targets.html 4 Dec 2012 16:24:23 -0000 1.16
+++ gnun/html_node/Special-Targets.html 27 Dec 2012 14:45:36 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Special Targets</title>
Index: gnun/html_node/Splitting-Long-Passages.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/Splitting-Long-Passages.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- gnun/html_node/Splitting-Long-Passages.html 4 Dec 2012 16:24:23 -0000
1.2
+++ gnun/html_node/Splitting-Long-Passages.html 27 Dec 2012 14:45:36 -0000
1.3
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Splitting Long Passages</title>
Index: gnun/html_node/Usage.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Usage.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Usage.html 4 Dec 2012 16:24:23 -0000 1.16
+++ gnun/html_node/Usage.html 27 Dec 2012 14:45:36 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Usage</title>
@@ -80,9 +80,8 @@
—O’Rielly’s Law
</p><br>
-<p>GNUN currently consists of a few makefiles, scripts and optional
-<samp>generic.<var>lang</var>.html</samp> files, intended to contain
-article-independent but team-specific information. They are designed
+<p>GNUN currently consists of a few makefiles, scripts and template files.
+They are designed
to reside in the <samp>server/gnun</samp> directory, but this may change.
In all examples in this manual, “invoking” means executing on the
command line <code>make -C server/gnun [<var>target</var>]
Index: gnun/html_node/Validation.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Validation.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- gnun/html_node/Validation.html 4 Dec 2012 16:24:23 -0000 1.6
+++ gnun/html_node/Validation.html 27 Dec 2012 14:45:36 -0000 1.7
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Validation</title>
Index: gnun/html_node/Webmaster-Tips.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/Webmaster-Tips.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Webmaster-Tips.html 4 Dec 2012 16:24:23 -0000 1.16
+++ gnun/html_node/Webmaster-Tips.html 27 Dec 2012 14:45:36 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Webmaster Tips</title>
@@ -30,7 +30,7 @@
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Usage.html#Usage" rel="up" title="Usage">
<link href="Validation.html#Validation" rel="next" title="Validation">
-<link href="Compendia.html#Compendia" rel="previous" title="Compendia">
+<link href="GNU-News.html#GNU-News" rel="previous" title="GNU News">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -84,11 +84,10 @@
important to have as many and as better as possible translations, and
you don’t have to make titanic efforts to help.
</p>
-<p>If you plan to edit a certain page extensively, please do so within the
-period between two adjacent GNUN builds—i.e. within a day. That way,
-the POT will be regenerated only once, and translators who are quick to
-update it immediately won’t be disappointed if it changes again in the
-next run.
+<p>If you plan to edit a certain page extensively, please do so within a
+reasonable time frame, for example a day or preferably, several hours.
+That way, the translators who are quick to update it immediately won’t
+be disappointed if the POT changes again in the next GNUN run(s).
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top">• <a href="Validation.html#Validation"
accesskey="1">Validation</a>:</td><td> </td><td align="left"
valign="top">How to verify the documents.
Index: gnun/html_node/extra_002dtemplates.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/extra_002dtemplates.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- gnun/html_node/extra_002dtemplates.html 4 Dec 2012 16:24:23 -0000
1.2
+++ gnun/html_node/extra_002dtemplates.html 27 Dec 2012 14:45:36 -0000
1.3
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<!-- This file redirects to the location of a node or anchor -->
<head>
<title>GNUnited Nations: extra-templates</title>
Index: gnun/html_node/generic_002eLANG_002ehtml.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/generic_002eLANG_002ehtml.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/generic_002eLANG_002ehtml.html 4 Dec 2012 16:24:23
-0000 1.16
+++ gnun/html_node/generic_002eLANG_002ehtml.html 27 Dec 2012 14:45:36
-0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: generic.LANG.html</title>
@@ -30,7 +30,7 @@
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="PO-Files.html#PO-Files" rel="up" title="PO Files">
<link href="languages_002etxt.html#languages_002etxt" rel="next"
title="languages.txt">
-<link href="PO-Tips.html#PO-Tips" rel="previous" title="PO Tips">
+<link href="Migrating.html#Migrating" rel="previous" title="Migrating">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -67,11 +67,11 @@
<a name="generic_002eLANG_002ehtml"></a>
<div class="header">
<p>
-Next: <a href="languages_002etxt.html#languages_002etxt" accesskey="n"
rel="next">languages.txt</a>, Previous: <a href="PO-Tips.html#PO-Tips"
accesskey="p" rel="previous">PO Tips</a>, Up: <a href="PO-Files.html#PO-Files"
accesskey="u" rel="up">PO Files</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="languages_002etxt.html#languages_002etxt" accesskey="n"
rel="next">languages.txt</a>, Previous: <a href="Migrating.html#Migrating"
accesskey="p" rel="previous">Migrating</a>, Up: <a
href="PO-Files.html#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<hr>
<a name="The-generic_002elang_002ehtml-File"></a>
-<h4 class="subsection">2.3.5 The <samp>generic.<var>lang</var>.html</samp>
File</h4>
+<h4 class="subsection">2.3.4 The <samp>generic.<var>lang</var>.html</samp>
File</h4>
<a name="index-team-information"></a>
<a name="index-generic-notice_002c-translations"></a>
Index: gnun/html_node/gnun_002dadd_002dfuzzy_002ddiff.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/gnun_002dadd_002dfuzzy_002ddiff.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- gnun/html_node/gnun_002dadd_002dfuzzy_002ddiff.html 4 Dec 2012 16:24:23
-0000 1.6
+++ gnun/html_node/gnun_002dadd_002dfuzzy_002ddiff.html 27 Dec 2012 14:45:36
-0000 1.7
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: gnun-add-fuzzy-diff</title>
@@ -71,11 +71,11 @@
</div>
<hr>
<a name="The-gnun_002dadd_002dfuzzy_002ddiff-Script"></a>
-<h4 class="subsection">3.1.1 The <code>gnun-add-fuzzy-diff</code> Script</h4>
+<h4 class="subsection">3.2.1 The <code>gnun-add-fuzzy-diff</code> Script</h4>
<a name="index-previous_002c-diff-1"></a>
<p>This script adds comments with differences of current <code>msgid</code>s
-against previous ones to fuzzy translations in a PO file. To produce
+against “previous” ones to “fuzzy” translations in a
PO file. To produce
the differences <code>wdiff</code> is used. This may be useful to figure
out what has changed. In fact, it wraps around a <code>sed</code> script
used in GNUN internally.
Index: gnun/html_node/gnun_002dclear_002dprevious.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/gnun_002dclear_002dprevious.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- gnun/html_node/gnun_002dclear_002dprevious.html 4 Dec 2012 16:24:23
-0000 1.8
+++ gnun/html_node/gnun_002dclear_002dprevious.html 27 Dec 2012 14:45:36
-0000 1.9
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: gnun-clear-previous</title>
@@ -29,7 +29,7 @@
<link href="Index.html#Index" rel="index" title="Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Scripts.html#Scripts" rel="up" title="Scripts">
-<link href="Rules.html#Rules" rel="next" title="Rules">
+<link href="Bugs.html#Bugs" rel="next" title="Bugs">
<link href="validate_002dhtml_002dnotify.html#validate_002dhtml_002dnotify"
rel="previous" title="validate-html-notify">
<style type="text/css">
<!--
@@ -71,16 +71,16 @@
</div>
<hr>
<a name="The-gnun_002dclear_002dprevious-Script"></a>
-<h4 class="subsection">3.1.10 The <code>gnun-clear-previous</code> Script</h4>
+<h4 class="subsection">3.2.10 The <code>gnun-clear-previous</code> Script</h4>
<a name="index-previous_002c-manipulating-PO-files"></a>
<p>This simple script is not used internally in GNUN. It is merely for
convenience only, for those who find it hard to remember the various
‘<samp>gettext</samp>’ tools and their options.
</p>
-<p><code>gnun-clear-previous</code> deletes the <em>previous</em> messages in a
+<p><code>gnun-clear-previous</code> deletes the “previous”
messages in a
PO file, which is a good thing to do after the corresponding translation
-is updated and the <em>fuzzy</em> marker removed. It can also be used to
+is updated and the “fuzzy” marker removed. It can also be used to
wrap long lines in PO files.
</p>
<p>Usage:
Index: gnun/html_node/gnun_002ddiff_002dpo.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/gnun_002ddiff_002dpo.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- gnun/html_node/gnun_002ddiff_002dpo.html 4 Dec 2012 16:26:16 -0000
1.1
+++ gnun/html_node/gnun_002ddiff_002dpo.html 27 Dec 2012 14:45:36 -0000
1.2
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: gnun-diff-po</title>
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-gnun_002ddiff_002dpo-Script"></a>
-<h4 class="subsection">3.1.2 The <code>gnun-diff-po</code> Script</h4>
+<h4 class="subsection">3.2.2 The <code>gnun-diff-po</code> Script</h4>
<a name="index-comparing_002c-translations"></a>
<p>This script compares two versions of a PO file. It produces a HTML page
Index: gnun/html_node/gnun_002dinit_002dpo.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/gnun_002dinit_002dpo.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- gnun/html_node/gnun_002dinit_002dpo.html 4 Dec 2012 16:24:23 -0000
1.3
+++ gnun/html_node/gnun_002dinit_002dpo.html 27 Dec 2012 14:45:36 -0000
1.4
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: gnun-init-po</title>
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-gnun_002dinit_002dpo-Script"></a>
-<h4 class="subsection">3.1.3 The <code>gnun-init-po</code> Script</h4>
+<h4 class="subsection">3.2.3 The <code>gnun-init-po</code> Script</h4>
<a name="index-initializing_002c-translations"></a>
<p>This script initializes a PO file using POT generated with GNUN,
@@ -93,7 +93,7 @@
</dd>
<dt><samp>-d</samp></dt>
<dt><samp>--disable-diffs</samp></dt>
-<dd><p>Don’t add diffs to previous messages.
+<dd><p>Don’t add diffs to “previous” messages.
</p>
</dd>
<dt><samp>-g</samp></dt>
@@ -122,7 +122,7 @@
</dl>
<p>The PO file name is guessed from the name of POT and language
-suffix; the file is created in current working directory.
+suffix; the file is created in the current working directory.
</p>
Index: gnun/html_node/gnun_002dmerge_002dpreconverted.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/gnun_002dmerge_002dpreconverted.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- gnun/html_node/gnun_002dmerge_002dpreconverted.html 4 Dec 2012 16:24:23
-0000 1.4
+++ gnun/html_node/gnun_002dmerge_002dpreconverted.html 27 Dec 2012 14:45:36
-0000 1.5
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: gnun-merge-preconverted</title>
@@ -71,13 +71,13 @@
</div>
<hr>
<a name="The-gnun_002dmerge_002dpreconverted-Script"></a>
-<h4 class="subsection">3.1.5 The <code>gnun-merge-preconverted</code>
Script</h4>
+<h4 class="subsection">3.2.5 The <code>gnun-merge-preconverted</code>
Script</h4>
<a name="index-migration_002c-translations-2"></a>
<a name="index-conversion-of-existing-translations-2"></a>
<p>This script takes <code>po4a-gettextize</code> output, adds current
<code>msgid</code>s as “previous” values, merges the file with the
new
-POT, and adds differences against previous values like
+POT, and adds differences against “previous” values like
<code>gnun-add-fuzzy-diff</code> does.
</p>
<div class="example">
Index: gnun/html_node/gnun_002dpreconvert.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/gnun_002dpreconvert.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- gnun/html_node/gnun_002dpreconvert.html 4 Dec 2012 16:24:24 -0000
1.4
+++ gnun/html_node/gnun_002dpreconvert.html 27 Dec 2012 14:45:36 -0000
1.5
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: gnun-preconvert</title>
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-gnun_002dpreconvert-Script"></a>
-<h4 class="subsection">3.1.4 The <code>gnun-preconvert</code> Script</h4>
+<h4 class="subsection">3.2.4 The <code>gnun-preconvert</code> Script</h4>
<a name="index-migration_002c-translations-1"></a>
<a name="index-conversion-of-existing-translations-1"></a>
Index: gnun/html_node/gnun_002dreport.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/gnun_002dreport.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- gnun/html_node/gnun_002dreport.html 4 Dec 2012 16:26:16 -0000 1.1
+++ gnun/html_node/gnun_002dreport.html 27 Dec 2012 14:45:36 -0000 1.2
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: gnun-report</title>
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-gnun_002dreport-Script"></a>
-<h4 class="subsection">3.1.6 The <code>gnun-report</code> Script</h4>
+<h4 class="subsection">3.2.6 The <code>gnun-report</code> Script</h4>
<a name="index-reporting-1"></a>
<a name="index-status_002c-translations-1"></a>
@@ -80,7 +80,7 @@
status (existing translations that need maintenance, untranslated
files, complete translations).
</p>
-<a name="index-priorities_002emk-3"></a>
+<a name="index-priorities_002emk-2"></a>
<p>The script depends on the presence of the <samp>priorities.mk</samp> file
in the <samp>server/gnun</samp> subdirectory of the working copy of
‘www’
repository.
Index: gnun/html_node/gnun_002dvalidate_002dhtml.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/gnun_002dvalidate_002dhtml.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- gnun/html_node/gnun_002dvalidate_002dhtml.html 4 Dec 2012 16:24:24
-0000 1.12
+++ gnun/html_node/gnun_002dvalidate_002dhtml.html 27 Dec 2012 14:45:37
-0000 1.13
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: gnun-validate-html</title>
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-gnun_002dvalidate_002dhtml-Script"></a>
-<h4 class="subsection">3.1.7 The <code>gnun-validate-html</code> Script</h4>
+<h4 class="subsection">3.2.7 The <code>gnun-validate-html</code> Script</h4>
<a name="index-validation_002c-HTML_002c-XHTML"></a>
<p>This is a Bash script whose purpose is to “validate” both the
Index: gnun/html_node/index.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/index.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/index.html 4 Dec 2012 16:24:24 -0000 1.16
+++ gnun/html_node/index.html 27 Dec 2012 14:45:37 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: Top</title>
@@ -76,8 +76,8 @@
<ul class="no-bullet">
<li><a name="toc-Introduction-to-GNUnited-Nations"
href="Introduction.html#Introduction">1 Introduction to GNUnited Nations</a>
<ul class="no-bullet">
- <li><a name="toc-Why-GNUN-is-Being-Developed"
href="Overview.html#Overview">1.1 Why GNUN is Being Developed</a></li>
- <li><a name="toc-What-GNUnited-Nations-is-and-Should-be"
href="Concepts.html#Concepts">1.2 What GNUnited Nations is and Should
be</a></li>
+ <li><a name="toc-Why-GNUN-Is-Being-Developed"
href="Overview.html#Overview">1.1 Why GNUN Is Being Developed</a></li>
+ <li><a name="toc-What-GNUnited-Nations-Is-and-Should-Be"
href="Concepts.html#Concepts">1.2 What GNUnited Nations Is and Should
Be</a></li>
<li><a name="toc-Major-Advantages-of-GNUN"
href="Advantages.html#Advantages">1.3 Major Advantages of GNUN</a></li>
<li><a name="toc-Known-Bugs-and-Limitations"
href="Disadvantages.html#Disadvantages">1.4 Known Bugs and Limitations</a></li>
</ul></li>
@@ -96,7 +96,7 @@
<li><a name="toc-The-validate_002dall-Target"
href="validate_002dall.html#validate_002dall">2.1.2.6 The
<code>validate-all</code> Target</a></li>
</ul></li>
</ul></li>
- <li><a name="toc-Defining-Articles-to-be-Built"
href="Main-Variables.html#Main-Variables">2.2 Defining Articles to be
Built</a></li>
+ <li><a name="toc-Defining-Articles-to-Be-Built"
href="Main-Variables.html#Main-Variables">2.2 Defining Articles to Be
Built</a></li>
<li><a name="toc-Working-with-PO-Files" href="PO-Files.html#PO-Files">2.3
Working with PO Files</a>
<ul class="no-bullet">
<li><a name="toc-Starting-a-New-Translation"
href="New-Translation.html#New-Translation">2.3.1 Starting a New Translation</a>
@@ -104,18 +104,18 @@
<li><a name="toc-The-Special-Slot-for-Translator_0027s-Notes"
href="Notes-Slot.html#Notes-Slot">2.3.1.1 The Special Slot for
Translator’s Notes</a></li>
<li><a name="toc-The-Special-Slot-for-Translator_0027s-Credits"
href="Credits-Slot.html#Credits-Slot">2.3.1.2 The Special Slot for
Translator’s Credits</a></li>
</ul></li>
- <li><a name="toc-Transforming-Existing-Translation-in-PO-Format"
href="Migrating.html#Migrating">2.3.2 Transforming Existing Translation in PO
Format</a></li>
- <li><a name="toc-Special-Handling-for-GNU-News"
href="GNU-News.html#GNU-News">2.3.3 Special Handling for GNU News</a></li>
- <li><a name="toc-Useful-Hints-for-Editing-PO-Files"
href="PO-Tips.html#PO-Tips">2.3.4 Useful Hints for Editing PO Files</a></li>
- <li><a name="toc-The-generic_002elang_002ehtml-File"
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml">2.3.5 The
<samp>generic.<var>lang</var>.html</samp> File</a></li>
- <li><a name="toc-The-languages_002etxt-File"
href="languages_002etxt.html#languages_002etxt">2.3.6 The
<samp>languages.txt</samp> File</a></li>
- <li><a name="toc-Maintaining-Translations-in-Your-Team_0027s-Repository"
href="PO-Files-and-Team.html#PO-Files-and-Team">2.3.7 Maintaining Translations
in Your Team’s Repository</a>
- <ul class="no-bullet">
- <li><a name="toc-Adopting-GNUmakefile_002eteam-for-a-Specific-Team"
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables">2.3.7.1
Adopting <samp>GNUmakefile.team</samp> for a Specific Team</a></li>
- <li><a name="toc-Targets-in-GNUmakefile_002eteam"
href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets">2.3.7.2
Targets in <samp>GNUmakefile.team</samp></a></li>
- <li><a name="toc-Automatic-Synchronization-and-Status-Reports"
href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron">2.3.7.3
Automatic Synchronization and Status Reports</a></li>
+ <li><a name="toc-Useful-Hints-for-Editing-PO-Files"
href="PO-Tips.html#PO-Tips">2.3.2 Useful Hints for Editing PO Files</a></li>
+ <li><a name="toc-Transforming-Existing-Translation-in-PO-Format"
href="Migrating.html#Migrating">2.3.3 Transforming Existing Translation in PO
Format</a></li>
+ <li><a name="toc-The-generic_002elang_002ehtml-File"
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml">2.3.4 The
<samp>generic.<var>lang</var>.html</samp> File</a></li>
+ <li><a name="toc-The-languages_002etxt-File"
href="languages_002etxt.html#languages_002etxt">2.3.5 The
<samp>languages.txt</samp> File</a></li>
+ <li><a name="toc-Maintaining-Translations-in-Your-Team_0027s-Repository"
href="PO-Files-and-Team.html#PO-Files-and-Team">2.3.6 Maintaining Translations
in Your Team’s Repository</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Adopting-GNUmakefile_002eteam-for-a-Specific-Team"
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables">2.3.6.1
Adopting <samp>GNUmakefile.team</samp> for a Specific Team</a></li>
+ <li><a name="toc-Targets-in-GNUmakefile_002eteam"
href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets">2.3.6.2
Targets in <samp>GNUmakefile.team</samp></a></li>
+ <li><a name="toc-Automatic-Synchronization-and-Status-Reports"
href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron">2.3.6.3
Automatic Synchronization and Status Reports</a></li>
</ul></li>
- <li><a name="toc-Using-Compendia" href="Compendia.html#Compendia">2.3.8
Using Compendia</a></li>
+ <li><a name="toc-Using-Compendia" href="Compendia.html#Compendia">2.3.7
Using Compendia</a></li>
+ <li><a name="toc-Special-Handling-for-GNU-News"
href="GNU-News.html#GNU-News">2.3.8 Special Handling for GNU News</a></li>
</ul></li>
<li><a name="toc-Tips-and-Hints-for-Webmasters"
href="Webmaster-Tips.html#Webmaster-Tips">2.4 Tips and Hints for Webmasters</a>
<ul class="no-bullet">
@@ -128,20 +128,20 @@
</ul></li>
<li><a name="toc-Unexciting-Information-for-GNUN_0027s-Operation"
href="Internals.html#Internals">3 Unexciting Information for GNUN’s
Operation</a>
<ul class="no-bullet">
- <li><a name="toc-GNUN-Scripts" href="Scripts.html#Scripts">3.1 GNUN
Scripts</a>
+ <li><a name="toc-Files-and-Directories-1"
href="Files-and-Directories.html#Files-and-Directories">3.1 Files and
Directories</a></li>
+ <li><a name="toc-GNUN-Scripts" href="Scripts.html#Scripts">3.2 GNUN
Scripts</a>
<ul class="no-bullet">
- <li><a name="toc-The-gnun_002dadd_002dfuzzy_002ddiff-Script"
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff">3.1.1
The <code>gnun-add-fuzzy-diff</code> Script</a></li>
- <li><a name="toc-The-gnun_002ddiff_002dpo-Script"
href="gnun_002ddiff_002dpo.html#gnun_002ddiff_002dpo">3.1.2 The
<code>gnun-diff-po</code> Script</a></li>
- <li><a name="toc-The-gnun_002dinit_002dpo-Script"
href="gnun_002dinit_002dpo.html#gnun_002dinit_002dpo">3.1.3 The
<code>gnun-init-po</code> Script</a></li>
- <li><a name="toc-The-gnun_002dpreconvert-Script"
href="gnun_002dpreconvert.html#gnun_002dpreconvert">3.1.4 The
<code>gnun-preconvert</code> Script</a></li>
- <li><a name="toc-The-gnun_002dmerge_002dpreconverted-Script"
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted">3.1.5
The <code>gnun-merge-preconverted</code> Script</a></li>
- <li><a name="toc-The-gnun_002dreport-Script"
href="gnun_002dreport.html#gnun_002dreport">3.1.6 The <code>gnun-report</code>
Script</a></li>
- <li><a name="toc-The-gnun_002dvalidate_002dhtml-Script"
href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml">3.1.7 The
<code>gnun-validate-html</code> Script</a></li>
- <li><a name="toc-The-mailfail-Script"
href="mailfail.html#mailfail">3.1.8 The <code>mailfail</code> Script</a></li>
- <li><a name="toc-The-validate_002dhtml_002dnotify-Script"
href="validate_002dhtml_002dnotify.html#validate_002dhtml_002dnotify">3.1.9 The
<code>validate-html-notify</code> Script</a></li>
- <li><a name="toc-The-gnun_002dclear_002dprevious-Script"
href="gnun_002dclear_002dprevious.html#gnun_002dclear_002dprevious">3.1.10 The
<code>gnun-clear-previous</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dadd_002dfuzzy_002ddiff-Script"
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff">3.2.1
The <code>gnun-add-fuzzy-diff</code> Script</a></li>
+ <li><a name="toc-The-gnun_002ddiff_002dpo-Script"
href="gnun_002ddiff_002dpo.html#gnun_002ddiff_002dpo">3.2.2 The
<code>gnun-diff-po</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dinit_002dpo-Script"
href="gnun_002dinit_002dpo.html#gnun_002dinit_002dpo">3.2.3 The
<code>gnun-init-po</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dpreconvert-Script"
href="gnun_002dpreconvert.html#gnun_002dpreconvert">3.2.4 The
<code>gnun-preconvert</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dmerge_002dpreconverted-Script"
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted">3.2.5
The <code>gnun-merge-preconverted</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dreport-Script"
href="gnun_002dreport.html#gnun_002dreport">3.2.6 The <code>gnun-report</code>
Script</a></li>
+ <li><a name="toc-The-gnun_002dvalidate_002dhtml-Script"
href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml">3.2.7 The
<code>gnun-validate-html</code> Script</a></li>
+ <li><a name="toc-The-mailfail-Script"
href="mailfail.html#mailfail">3.2.8 The <code>mailfail</code> Script</a></li>
+ <li><a name="toc-The-validate_002dhtml_002dnotify-Script"
href="validate_002dhtml_002dnotify.html#validate_002dhtml_002dnotify">3.2.9 The
<code>validate-html-notify</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dclear_002dprevious-Script"
href="gnun_002dclear_002dprevious.html#gnun_002dclear_002dprevious">3.2.10 The
<code>gnun-clear-previous</code> Script</a></li>
</ul></li>
- <li><a name="toc-How-The-Recipes-Work" href="Rules.html#Rules">3.2 How The
Recipes Work</a></li>
</ul></li>
<li><a name="toc-Reporting-Bugs" href="Bugs.html#Bugs">4 Reporting
Bugs</a></li>
<li><a name="toc-Index-1" href="Index.html#Index">Index</a></li>
@@ -160,7 +160,7 @@
<a name="GNUnited-Nations"></a>
<h1 class="top">GNUnited Nations</h1>
-<p>This manual (updated 3 December 2012) is for GNUnited Nations (version
+<p>This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.<br>
</p><br>
Index: gnun/html_node/languages_002etxt.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/languages_002etxt.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- gnun/html_node/languages_002etxt.html 4 Dec 2012 16:24:24 -0000
1.6
+++ gnun/html_node/languages_002etxt.html 27 Dec 2012 14:45:37 -0000
1.7
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: languages.txt</title>
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-languages_002etxt-File"></a>
-<h4 class="subsection">2.3.6 The <samp>languages.txt</samp> File</h4>
+<h4 class="subsection">2.3.5 The <samp>languages.txt</samp> File</h4>
<p>The file <samp>server/gnun/languages.txt</samp> is used when generating
lists of translations; those lists are subsequently included in all
Index: gnun/html_node/mailfail.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/mailfail.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/mailfail.html 4 Dec 2012 16:24:24 -0000 1.16
+++ gnun/html_node/mailfail.html 27 Dec 2012 14:45:37 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: mailfail</title>
@@ -71,8 +71,8 @@
</div>
<hr>
<a name="The-mailfail-Script"></a>
-<h4 class="subsection">3.1.8 The <code>mailfail</code> Script</h4>
-<a name="index-mail_002c-notifications-1"></a>
+<h4 class="subsection">3.2.8 The <code>mailfail</code> Script</h4>
+<a name="index-mail_002c-notifications-2"></a>
<p>This is a helper script that runs a command, and mails the output of
that command in case it exits with a non-zero exit status.
Index: gnun/html_node/no_002dgrace_002ditems.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/no_002dgrace_002ditems.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- gnun/html_node/no_002dgrace_002ditems.html 4 Dec 2012 16:24:24 -0000
1.6
+++ gnun/html_node/no_002dgrace_002ditems.html 27 Dec 2012 14:45:37 -0000
1.7
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: no-grace-items</title>
@@ -78,8 +78,8 @@
server templates, gnunews, and all articles defined in the variable
<code>no-grace-articles</code> (see <a
href="Runtime-Variables.html#GRACE">grace period</a>).
</p>
-<p>This target can be rebuilt more often than <code>all</code>; however, it is
-currently not used.
+<p>This target can be rebuilt more often than <code>all</code>; however,
+currently it is not used.
</p>
Index: gnun/html_node/optional_002dtemplates.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/optional_002dtemplates.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- gnun/html_node/optional_002dtemplates.html 4 Dec 2012 16:24:24 -0000
1.2
+++ gnun/html_node/optional_002dtemplates.html 27 Dec 2012 14:45:37 -0000
1.3
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<!-- This file redirects to the location of a node or anchor -->
<head>
<title>GNUnited Nations: optional-templates</title>
Index: gnun/html_node/report.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/report.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/report.html 4 Dec 2012 16:24:24 -0000 1.16
+++ gnun/html_node/report.html 27 Dec 2012 14:45:37 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: report</title>
@@ -98,7 +98,9 @@
all other translations are reported as less important.
</p>
<p>There is also a script, <code>gnun-report</code>, to generate HTML reports.
-See <a href="gnun_002dreport.html#gnun_002dreport">gnun-report</a>.
+See <a href="gnun_002dreport.html#gnun_002dreport">gnun-report</a>.
GNUmakefile.team profides another <code>report</code>
+target, which produces a more detailed report.
+See <a
href="GNUmakefile_002eteam-Targets.html#report-in-GNUmakefile_002eteam">report
in GNUmakefile.team</a>.
</p>
Index: gnun/html_node/sync.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/sync.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/sync.html 4 Dec 2012 16:24:24 -0000 1.16
+++ gnun/html_node/sync.html 27 Dec 2012 14:45:37 -0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: sync</title>
Index: gnun/html_node/triggers.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/triggers.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/triggers.html 4 Dec 2012 16:24:24 -0000 1.15
+++ gnun/html_node/triggers.html 27 Dec 2012 14:45:37 -0000 1.16
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: triggers</title>
@@ -100,7 +100,7 @@
<p>To summarize, for effective operation GNUN should be invoked
automatically as <code>make; cvs|svn|bzr commit -m …; make
triggers</code>. To illustrate this, here is a concrete example showing the
-official job running at fencepost.gnu.org:
+official job once running at fencepost.gnu.org<a name="DOCF4"
href="#FOOT4"><sup>4</sup></a>:
</p>
<div class="example">
<pre class="example">25 4,12,20 * * * cd $HOME/projects/www; cvs -q update
&>/dev/null; \
@@ -124,6 +124,15 @@
<p>In the future, this target may be extended further to do other useful
things that should be “triggered” after the main build.
</p>
+<div class="footnote">
+<hr>
+<h4 class="footnotes-heading">Footnotes</h4>
+
+<h3><a name="FOOT4" href="#DOCF4">(4)</a></h3>
+<p>These days we
+run a more complicated script instead of this cron job in order
+to address some exceptional situations like concurrent builds.</p>
+</div>
<hr>
<div class="header">
<p>
Index: gnun/html_node/update_002dlocalized_002dURLs.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/update_002dlocalized_002dURLs.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- gnun/html_node/update_002dlocalized_002dURLs.html 4 Dec 2012 16:24:24
-0000 1.6
+++ gnun/html_node/update_002dlocalized_002dURLs.html 27 Dec 2012 14:45:37
-0000 1.7
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: update-localized-URLs</title>
Index: gnun/html_node/validate_002dall.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/validate_002dall.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- gnun/html_node/validate_002dall.html 4 Dec 2012 16:24:24 -0000
1.3
+++ gnun/html_node/validate_002dall.html 27 Dec 2012 14:45:37 -0000
1.4
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: validate-all</title>
Index: gnun/html_node/validate_002dhtml_002dnotify.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/validate_002dhtml_002dnotify.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/validate_002dhtml_002dnotify.html 4 Dec 2012 16:24:24
-0000 1.16
+++ gnun/html_node/validate_002dhtml_002dnotify.html 27 Dec 2012 14:45:37
-0000 1.17
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<!--
-This manual (updated 3 December 2012) is for GNUnited Nations (version
+This manual (updated 27 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,7 +15,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUnited Nations: validate-html-notify</title>
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-validate_002dhtml_002dnotify-Script"></a>
-<h4 class="subsection">3.1.9 The <code>validate-html-notify</code> Script</h4>
+<h4 class="subsection">3.2.9 The <code>validate-html-notify</code> Script</h4>
<p>This script is a wrapper around <code>gnun-validate-html</code>
(see <a
href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml">gnun-validate-html</a>);
it is necessary because it is hard to
Index: web-trans/index.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/index.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/index.html 4 Dec 2012 16:24:25 -0000 1.11
+++ web-trans/index.html 27 Dec 2012 14:45:38 -0000 1.12
@@ -4,7 +4,7 @@
<h2>GNU Web Translators Manual</h2>
<address>Free Software Foundation</address>
-<address>last updated December 04, 2012</address>
+<address>last updated December 27, 2012</address>
<p>This manual (web-trans) is available in the following formats:</p>
@@ -24,13 +24,11 @@
<li><a href="web-trans.txt">ASCII text
(96K bytes)</a>.</li>
<li><a href="web-trans.txt.gz">ASCII text compressed
- (32K bytes gzipped)</a>.</li>
+ (36K bytes gzipped)</a>.</li>
<li><a href="web-trans.dvi.gz">TeX dvi file
(56K bytes gzipped)</a>.</li>
-<li><a href="web-trans.ps.gz">PostScript file
- (264K bytes gzipped)</a>.</li>
<li><a href="web-trans.pdf">PDF file
- (348K bytes)</a>.</li>
+ (364K bytes)</a>.</li>
<li><a href="web-trans.texi.tar.gz">Texinfo source
(68K bytes gzipped tar file).</a></li>
</ul>
Index: web-trans/web-trans.dvi.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.dvi.gz,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
Binary files /tmp/cvse49dSz and /tmp/cvsh09Ku2 differ
Index: web-trans/web-trans.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/web-trans.html 4 Dec 2012 16:24:25 -0000 1.11
+++ web-trans/web-trans.html 27 Dec 2012 14:45:38 -0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual</title>
@@ -73,58 +73,61 @@
<li><a name="toc-Introduction-1" href="#Introduction">1 Introduction</a></li>
<li><a name="toc-Team-Members" href="#Members">2 Team Members</a>
<ul class="no-bullet">
- <li><a name="toc-Joining-A-Team" href="#Joining">2.1 Joining A
Team</a></li>
- <li><a name="toc-How-To-Submit-a-Translation" href="#Submitting">2.2 How
To Submit a Translation</a>
+ <li><a name="toc-Joining-a-Team" href="#Joining">2.1 Joining a
Team</a></li>
+ <li><a name="toc-How-to-Submit-a-Translation" href="#Submitting">2.2 How
to Submit a Translation</a>
<ul class="no-bullet">
- <li><a name="toc-How-To-Submit-a-Translation-in-PO-Format"
href="#Submitting-as-PO">2.2.1 How To Submit a Translation in PO Format</a></li>
- <li><a name="toc-How-To-Submit-a-Translation-as-Plain-Text"
href="#Submitting-as-Plain-Text">2.2.2 How To Submit a Translation as Plain
Text</a></li>
+ <li><a name="toc-How-to-Submit-a-Translation-in-PO-Format"
href="#Submitting-as-PO">2.2.1 How to Submit a Translation in PO Format</a></li>
+ <li><a name="toc-How-to-Submit-a-Translation-as-Plain-Text"
href="#Submitting-as-Plain-Text">2.2.2 How to Submit a Translation as Plain
Text</a></li>
</ul></li>
- <li><a name="toc-Leaving-A-Team-1" href="#Leaving-A-Team">2.3 Leaving A
Team</a></li>
+ <li><a name="toc-Leaving-a-Team-1" href="#Leaving-a-Team">2.3 Leaving a
Team</a></li>
</ul></li>
<li><a name="toc-Team-Co_002dordinators" href="#Leaders">3 Team
Co-ordinators</a>
<ul class="no-bullet">
- <li><a name="toc-How-To-Form-A-New-Team" href="#New-Team">3.1 How To Form
A New Team</a></li>
- <li><a name="toc-The-Gentle-Art-of-Managing-A-Translation-Team"
href="#Managing">3.2 The Gentle Art of Managing A Translation Team</a>
+ <li><a name="toc-How-to-Form-a-New-Team" href="#New-Team">3.1 How to Form
a New Team</a></li>
+ <li><a name="toc-The-Gentle-Art-of-Managing-a-Translation-Team"
href="#Managing">3.2 The Gentle Art of Managing a Translation Team</a>
<ul class="no-bullet">
<li><a name="toc-Peer-Review" href="#Review">3.2.1 Peer Review</a>
<ul class="no-bullet">
- <li><a name="toc-How-To-Track-Tasks-and-Bugs-Using-Savannah"
href="#Tracking-Tasks">3.2.1.1 How To Track Tasks and Bugs Using
Savannah</a></li>
- <li><a name="toc-How-To-Proceed-With-Unreviewed-Translations"
href="#Unreviewed-Translations">3.2.1.2 How To Proceed With Unreviewed
Translations</a></li>
+ <li><a name="toc-How-to-Track-Tasks-and-Bugs-Using-Savannah"
href="#Tracking-Tasks">3.2.1.1 How to Track Tasks and Bugs Using
Savannah</a></li>
+ <li><a name="toc-How-to-Proceed-with-Unreviewed-Translations"
href="#Unreviewed-Translations">3.2.1.2 How to Proceed with Unreviewed
Translations</a></li>
</ul></li>
- <li><a name="toc-CVS-Commits-And-Best-Practices" href="#Commits">3.2.2
CVS Commits And Best Practices</a></li>
- <li><a name="toc-Taking-Advantage-of-Savannah" href="#Savannah">3.2.3
Taking Advantage of Savannah</a>
+ <li><a name="toc-CVS-Commits-and-Best-Practices" href="#Commits">3.2.2
CVS Commits and Best Practices</a></li>
+ <li><a name="toc-Working-with-PO-Files" href="#PO-Files">3.2.3 Working
with PO Files</a>
<ul class="no-bullet">
- <li><a name="toc-Managing-Members" href="#Savannah-Members">3.2.3.1
Managing Members</a></li>
- <li><a name="toc-Homepage-of-The-Team"
href="#Savannah-Homepage">3.2.3.2 Homepage of The Team</a></li>
- <li><a name="toc-Support-Tracker" href="#Savannah-Support">3.2.3.3
Support Tracker</a></li>
- <li><a name="toc-Tasks-Tracker" href="#Savannah-Tasks">3.2.3.4 Tasks
Tracker</a></li>
- <li><a name="toc-Bugs-Tracker" href="#Savannah-Bugs">3.2.3.5 Bugs
Tracker</a></li>
- <li><a name="toc-Patch-Tracker" href="#Savannah-Patch">3.2.3.6 Patch
Tracker</a></li>
- <li><a name="toc-News-Tracker" href="#Savannah-News">3.2.3.7 News
Tracker</a></li>
- <li><a name="toc-Managing-Mailing-Lists"
href="#Savannah-Mailing-Lists">3.2.3.8 Managing Mailing Lists</a></li>
- <li><a name="toc-Version-Control-Systems" href="#Savannah-VCS">3.2.3.9
Version Control Systems</a></li>
+ <li><a name="toc-Web_002dbased-Systems"
href="#Web_002dbased-Systems">3.2.3.1 Web-based Systems</a></li>
</ul></li>
- <li><a name="toc-Promoting-Members-As-Co_002dleaders"
href="#Co_002dleaders">3.2.4 Promoting Members As Co-leaders</a></li>
+ <li><a name="toc-Taking-Advantage-of-Savannah" href="#Savannah">3.2.4
Taking Advantage of Savannah</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Managing-Members" href="#Savannah-Members">3.2.4.1
Managing Members</a></li>
+ <li><a name="toc-Homepage-of-the-Team"
href="#Savannah-Homepage">3.2.4.2 Homepage of the Team</a></li>
+ <li><a name="toc-Support-Tracker" href="#Savannah-Support">3.2.4.3
Support Tracker</a></li>
+ <li><a name="toc-Tasks-Tracker" href="#Savannah-Tasks">3.2.4.4 Tasks
Tracker</a></li>
+ <li><a name="toc-Bugs-Tracker" href="#Savannah-Bugs">3.2.4.5 Bugs
Tracker</a></li>
+ <li><a name="toc-News-Tracker" href="#Savannah-News">3.2.4.6 News
Tracker</a></li>
+ <li><a name="toc-Managing-Mailing-Lists"
href="#Savannah-Mailing-Lists">3.2.4.7 Managing Mailing Lists</a></li>
+ <li><a name="toc-Version-Control-Systems" href="#Savannah-VCS">3.2.4.8
Version Control Systems</a></li>
+ </ul></li>
+ <li><a name="toc-Promoting-Members-as-Co_002dleaders"
href="#Co_002dleaders">3.2.5 Promoting Members as Co-leaders</a></li>
</ul></li>
<li><a name="toc-Reporting-Team-Status" href="#Reports">3.3 Reporting Team
Status</a></li>
- <li><a name="toc-How-To-Retire-Painlessly" href="#Stepping-Down">3.4 How
To Retire Painlessly</a></li>
+ <li><a name="toc-How-to-Retire-Painlessly" href="#Stepping-Down">3.4 How
to Retire Painlessly</a></li>
</ul></li>
<li><a name="toc-trans_002dcoord-Admins" href="#Translation-Managers">4
‘<samp>trans-coord</samp>’ Admins</a></li>
- <li><a name="toc-Details-About-The-Translation-Process"
href="#Translation-Tips">5 Details About The Translation Process</a>
+ <li><a name="toc-Details-about-the-Translation-Process"
href="#Translation-Tips">5 Details about the Translation Process</a>
<ul class="no-bullet">
- <li><a name="toc-Migration-To-The-New-Style" href="#Migrating">5.1
Migration To The New Style</a></li>
+ <li><a name="toc-Migration-to-the-New-Style" href="#Migrating">5.1
Migration to the New Style</a></li>
<li><a name="toc-Summary-of-SSI-_0023includes" href="#SSI">5.2 Summary of
SSI <code>#include</code>s</a></li>
- <li><a name="toc-How-To-Use-Custom-CSS" href="#CSS">5.3 How To Use Custom
CSS</a>
+ <li><a name="toc-How-to-Use-Custom-CSS" href="#CSS">5.3 How to Use Custom
CSS</a>
<ul class="no-bullet">
- <li><a name="toc-Localizing-The-topbanner-Image" href="#topbanner">5.3.1
Localizing The <samp>topbanner</samp> Image</a></li>
+ <li><a name="toc-Localizing-the-topbanner-Image" href="#topbanner">5.3.1
Localizing the <samp>topbanner</samp> Image</a></li>
<li><a name="toc-Specific-Issues-Related-to-RTL" href="#RTL">5.3.2
Specific Issues Related to RTL</a></li>
</ul></li>
- <li><a name="toc-What-To-Translate" href="#Priorities">5.4 What To
Translate</a></li>
- <li><a name="toc-When-To-CAPITALIZE" href="#Capitalization">5.5 When To
CAPITALIZE</a></li>
+ <li><a name="toc-What-to-Translate" href="#Priorities">5.4 What to
Translate</a></li>
+ <li><a name="toc-When-to-CAPITALIZE" href="#Capitalization">5.5 When to
CAPITALIZE</a></li>
<li><a name="toc-Distribution-Terms-1" href="#Distribution-Terms">5.6
Distribution Terms</a></li>
<li><a name="toc-Language_002dspecific-Terminology"
href="#Terminology">5.7 Language-specific Terminology</a></li>
</ul></li>
- <li><a name="toc-Overview-Of-The-Translation-Process" href="#Summary">6
Overview Of The Translation Process</a>
+ <li><a name="toc-Overview-of-the-Translation-Process" href="#Summary">6
Overview of the Translation Process</a>
<ul class="no-bullet">
<li><a name="toc-Related-Mailing-Lists" href="#Mailing-Lists">6.1 Related
Mailing Lists</a></li>
<li><a name="toc-Savannah-Projects-Membership"
href="#Savannah-Projects">6.2 Savannah Projects Membership</a></li>
@@ -144,7 +147,7 @@
<h1 class="top">GNU Web Translators Manual</h1>
<p>This manual is a guide for the GNU Web Translators.<br> Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
</p><br>
<p>Copyright © 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -219,13 +222,12 @@
describe the fundamental values of the free software movement.
</p>
<p>Translators of the <a href="http://gnu.org";>http://gnu.org</a> website are
organized in
-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</samp>’ organizational project,
which is managed
-by the GNU Web Translation Managers. The manual is organized in
-chapters that follow the organizational structure of the whole
-translation project.
+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</samp>’
+organizational project, which is managed by the GNU Web Translation
+Managers. The manual is organized in chapters that follow the
+organizational structure of the whole translation project.
</p>
<p>If you wish to join a translation team or contribute a translation or
two, see <a href="#Members">Members</a>. If your intention is to form a
translation team,
@@ -254,7 +256,7 @@
</td></tr>
<tr><td align="left" valign="top">• <a href="#Submitting"
accesskey="2">Submitting</a>:</td><td> </td><td align="left"
valign="top">Submitting a translation when there is no team.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Leaving-A-Team"
accesskey="3">Leaving A Team</a>:</td><td> </td><td align="left"
valign="top">Leave when you have to.
+<tr><td align="left" valign="top">• <a href="#Leaving-a-Team"
accesskey="3">Leaving a Team</a>:</td><td> </td><td align="left"
valign="top">Leave when you have to.
</td></tr>
</table>
@@ -264,8 +266,8 @@
<p>
Next: <a href="#Submitting" accesskey="n" rel="next">Submitting</a>, Up: <a
href="#Members" accesskey="u" rel="up">Members</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-<a name="Joining-A-Team"></a>
-<h3 class="section">2.1 Joining A Team</h3>
+<a name="Joining-a-Team"></a>
+<h3 class="section">2.1 Joining a Team</h3>
<p>To join a team, please first look at the existing teams at
<a
href="http://www.gnu.org/server/standards/README.translations.html#TranslationsUnderway";>http://www.gnu.org/server/standards/README.translations.html#TranslationsUnderway</a>.
@@ -323,10 +325,10 @@
<a name="Submitting"></a>
<div class="header">
<p>
-Next: <a href="#Leaving-A-Team" accesskey="n" rel="next">Leaving A Team</a>,
Previous: <a href="#Joining" accesskey="p" rel="previous">Joining</a>, Up: <a
href="#Members" accesskey="u" rel="up">Members</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
+Next: <a href="#Leaving-a-Team" accesskey="n" rel="next">Leaving a Team</a>,
Previous: <a href="#Joining" accesskey="p" rel="previous">Joining</a>, Up: <a
href="#Members" accesskey="u" rel="up">Members</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-<a name="How-To-Submit-a-Translation"></a>
-<h3 class="section">2.2 How To Submit a Translation</h3>
+<a name="How-to-Submit-a-Translation"></a>
+<h3 class="section">2.2 How to Submit a Translation</h3>
<p>Everyone can still submit translations even if there is no translation
team formed. There are two ways to do that—following the existing
@@ -347,8 +349,8 @@
<p>
Next: <a href="#Submitting-as-Plain-Text" accesskey="n" rel="next">Submitting
as Plain Text</a>, Up: <a href="#Submitting" accesskey="u"
rel="up">Submitting</a> [<a href="#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
-<a name="How-To-Submit-a-Translation-in-PO-Format"></a>
-<h4 class="subsection">2.2.1 How To Submit a Translation in PO Format</h4>
+<a name="How-to-Submit-a-Translation-in-PO-Format"></a>
+<h4 class="subsection">2.2.1 How to Submit a Translation in PO Format</h4>
<p>All translations<a name="DOCF1" href="#FOOT1"><sup>1</sup></a> are
maintained via GNUN (see
<a
href="http://www.gnu.org/software/gnun/";>http://www.gnu.org/software/gnun/</a>),
which significantly eases
@@ -381,7 +383,7 @@
the URL for the template file of
<a
href="http://www.gnu.org/philosophy/free-sw.html";>http://www.gnu.org/philosophy/free-sw.html</a>
is
<a
href="http://www.gnu.org/philosophy/po/free-sw.pot";>http://www.gnu.org/philosophy/po/free-sw.pot</a>;
the URL for
-its <var>lang</var> PO file (when available) is
+its <var>lang</var> PO file (when available) is always
<a
href="http://www.gnu.org/philosophy/po/free-sw.lang.po";>http://www.gnu.org/philosophy/po/free-sw.lang.po</a>:
</p>
<div class="example">
@@ -391,7 +393,7 @@
</li><li> Assuming you already know the article you want to translate, you
have to
create an empty <samp><var>article</var>.<var>lang</var>.po</samp> file and
then
translate all messages with a PO editor. See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#New-Translation";>New
Translation</a> in <cite>The GNUnited Nations Manual</cite>. For an almost
complete list of PO
-editors, see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#PO-Files";>PO
Files</a> in <cite>The GNUnited Nations Manual</cite>.
+editors, see <a href="#PO-Files">PO Files</a>.
</li><li> When you are pleased with the translation, check that the PO file is
valid and submit it to <a href="mailto:address@hidden";>address@hidden</a>,
attached to
@@ -428,8 +430,8 @@
<p>
Previous: <a href="#Submitting-as-PO" accesskey="p" rel="previous">Submitting
as PO</a>, Up: <a href="#Submitting" accesskey="u" rel="up">Submitting</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-<a name="How-To-Submit-a-Translation-as-Plain-Text"></a>
-<h4 class="subsection">2.2.2 How To Submit a Translation as Plain Text</h4>
+<a name="How-to-Submit-a-Translation-as-Plain-Text"></a>
+<h4 class="subsection">2.2.2 How to Submit a Translation as Plain Text</h4>
<p>If you feel the procedure described in the previous section is too
burdensome and unfeasible for you to follow, you can still submit a
@@ -496,13 +498,13 @@
conversion process, and report them back.
</p>
<hr>
-<a name="Leaving-A-Team"></a>
+<a name="Leaving-a-Team"></a>
<div class="header">
<p>
Previous: <a href="#Submitting" accesskey="p" rel="previous">Submitting</a>,
Up: <a href="#Members" accesskey="u" rel="up">Members</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-<a name="Leaving-A-Team-1"></a>
-<h3 class="section">2.3 Leaving A Team</h3>
+<a name="Leaving-a-Team-1"></a>
+<h3 class="section">2.3 Leaving a Team</h3>
<p>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
@@ -553,8 +555,8 @@
<p>
Next: <a href="#Managing" accesskey="n" rel="next">Managing</a>, Up: <a
href="#Leaders" accesskey="u" rel="up">Leaders</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-<a name="How-To-Form-A-New-Team"></a>
-<h3 class="section">3.1 How To Form A New Team</h3>
+<a name="How-to-Form-a-New-Team"></a>
+<h3 class="section">3.1 How to Form a New Team</h3>
<p>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
@@ -564,9 +566,7 @@
</p>
<p>You should read <em>all</em> the documentation related to the
translation process and at the very least all important
-philosophy-related articles listed on
-<a
href="http://gnu.org/server/standards/README.translations.html";>http://gnu.org/server/standards/README.translations.html</a>
-and
+philosophy-related articles listed at
<a
href="http://gnu.org/server/standards/translations/priorities.html";>http://gnu.org/server/standards/translations/priorities.html</a>
before you decide to form a new team, or take over an orphaned team.
Once you have the internal feeling that having a gnu.org translation
@@ -609,20 +609,29 @@
co-ordinator to have a good understanding of the philosophy of the free
software movement.
-</li><li> Check if your language code is
-present in the variable <code>TEMPLATE_LINGUAS</code> at
-<samp>server/gnun/gnun.mk</samp>. If it is not, the first thing to do is to
-translate and submit to <a href="mailto:address@hidden";>address@hidden</a> the
following
-files (all in the <samp>server/po/</samp> directory):
-<samp>head-include-2.<var>lang</var>.po</samp>,
-<samp>body-include-1.<var>lang</var>.po</samp>,
-<samp>body-include-2.<var>lang</var>.po</samp>
-<samp>footer-text.<var>lang</var>.po</samp>,
-<samp>outdated.<var>lang</var>.po</samp>,
-<samp>skip-translations.<var>lang</var>.po</samp>,
-and <samp>top-addendum.<var>lang</var>.po</samp>.
-See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#New-Translation";>New
Translation</a> in <cite>The GNUnited Nations Manual</cite>.
+</li><li> Check if your language code is present in the variable
+<code>TEMPLATE_LINGUAS</code> in the file <samp>server/gnun/gnun.mk</samp>.
If it
+is not, the first thing to do is to translate and submit to
+<a href="mailto:address@hidden";>address@hidden</a> the following files (all in
the
+<samp>server/po/</samp> directory):
+<ul>
+<li> <samp>head-include-2.<var>lang</var>.po</samp>
+
+</li><li> <samp>body-include-1.<var>lang</var>.po</samp>
+
+</li><li> <samp>body-include-2.<var>lang</var>.po</samp>
+
+</li><li> <samp>footer-text.<var>lang</var>.po</samp>
+</li><li> <samp>outdated.<var>lang</var>.po</samp>
+
+</li><li> <samp>skip-translations.<var>lang</var>.po</samp>
+
+</li><li> <samp>top-addendum.<var>lang</var>.po</samp>
+</li></ul>
+
+<p>See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#New-Translation";>New
Translation</a> in <cite>The GNUnited Nations Manual</cite>.
+</p>
<ul class="no-bullet">
<li>- The language code (<var>lang</var>) should be the ISO 639-1 code of the
language, for example ‘<samp>hy</samp>’ for Armenian or
‘<samp>el</samp>’ for Greek. If
@@ -632,11 +641,6 @@
</li><li>- The PO file header and initial comments should be completed as
documented.
-
-</li><li>- 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;</samp>’ and this is a character from the
alphabet of your
-language, just write it as ‘<samp>ü</samp>’ directly.
</li></ul>
</li><li> Any prospective team leader should submit a few translations first.
@@ -728,8 +732,8 @@
<p>
Next: <a href="#Reports" accesskey="n" rel="next">Reports</a>, Previous: <a
href="#New-Team" accesskey="p" rel="previous">New Team</a>, Up: <a
href="#Leaders" accesskey="u" rel="up">Leaders</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-<a name="The-Gentle-Art-of-Managing-A-Translation-Team"></a>
-<h3 class="section">3.2 The Gentle Art of Managing A Translation Team</h3>
+<a name="The-Gentle-Art-of-Managing-a-Translation-Team"></a>
+<h3 class="section">3.2 The Gentle Art of Managing a Translation Team</h3>
<p>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
@@ -755,9 +759,11 @@
</td></tr>
<tr><td align="left" valign="top">• <a href="#Commits"
accesskey="2">Commits</a>:</td><td> </td><td align="left"
valign="top">What to modify, and how.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Savannah"
accesskey="3">Savannah</a>:</td><td> </td><td align="left"
valign="top">Using Savannah resources.
+<tr><td align="left" valign="top">• <a href="#PO-Files" accesskey="3">PO
Files</a>:</td><td> </td><td align="left" valign="top">Tools to edit
translations.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Co_002dleaders"
accesskey="4">Co-leaders</a>:</td><td> </td><td align="left"
valign="top">Promoting co-leaders, when necessary.
+<tr><td align="left" valign="top">• <a href="#Savannah"
accesskey="4">Savannah</a>:</td><td> </td><td align="left"
valign="top">Using Savannah resources.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Co_002dleaders"
accesskey="5">Co-leaders</a>:</td><td> </td><td align="left"
valign="top">Promoting co-leaders, when necessary.
</td></tr>
</table>
@@ -813,8 +819,8 @@
<p>
Next: <a href="#Unreviewed-Translations" accesskey="n" rel="next">Unreviewed
Translations</a>, Up: <a href="#Review" accesskey="u" rel="up">Review</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-<a name="How-To-Track-Tasks-and-Bugs-Using-Savannah"></a>
-<h4 class="subsubsection">3.2.1.1 How To Track Tasks and Bugs Using
Savannah</h4>
+<a name="How-to-Track-Tasks-and-Bugs-Using-Savannah"></a>
+<h4 class="subsubsection">3.2.1.1 How to Track Tasks and Bugs Using
Savannah</h4>
<p>The team leader has to make sure that prospective translations are
reviewed, that they do not contain obvious errors and/or confusing
@@ -905,8 +911,8 @@
<p>
Previous: <a href="#Tracking-Tasks" accesskey="p" rel="previous">Tracking
Tasks</a>, Up: <a href="#Review" accesskey="u" rel="up">Review</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-<a name="How-To-Proceed-With-Unreviewed-Translations"></a>
-<h4 class="subsubsection">3.2.1.2 How To Proceed With Unreviewed
Translations</h4>
+<a name="How-to-Proceed-with-Unreviewed-Translations"></a>
+<h4 class="subsubsection">3.2.1.2 How to Proceed with Unreviewed
Translations</h4>
<p>Sometimes a translation (typically your own) is not reviewed by anyone
else for a fairly long time. This is unfortunate, but there is no
@@ -924,10 +930,10 @@
<a name="Commits"></a>
<div class="header">
<p>
-Next: <a href="#Savannah" accesskey="n" rel="next">Savannah</a>, Previous: <a
href="#Review" accesskey="p" rel="previous">Review</a>, Up: <a href="#Managing"
accesskey="u" rel="up">Managing</a> [<a href="#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
+Next: <a href="#PO-Files" accesskey="n" rel="next">PO Files</a>, Previous: <a
href="#Review" accesskey="p" rel="previous">Review</a>, Up: <a href="#Managing"
accesskey="u" rel="up">Managing</a> [<a href="#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-<a name="CVS-Commits-And-Best-Practices"></a>
-<h4 class="subsection">3.2.2 CVS Commits And Best Practices</h4>
+<a name="CVS-Commits-and-Best-Practices"></a>
+<h4 class="subsection">3.2.2 CVS Commits and Best Practices</h4>
<p>As all team leaders have write access to the CVS repository of the
‘<samp>www</samp>’ project, this technically means that they are
able to modify
@@ -947,8 +953,8 @@
For general issues that affect more articles, or for severe problems,
please write to <a href="mailto:address@hidden";>address@hidden</a>.
</p>
-<p>It is recommended to read the entire CVS manual at least once, for a
-basic understanding of how this VCS works. See <a
href="cvs.html#Top">Concurrent
+<p>If you are not familiar with CVS, it is recommended to read CVS manual,
+for a basic understanding of how this VCS works. See <a
href="cvs.html#Top">Concurrent
Versions System</a> in <cite>Version Management with CVS</cite>. It is not
necessary to become an expert—the ‘<samp>www</samp>’ project
does not use
complex features like tags, vendor branches, merging, etc. as they are
@@ -967,7 +973,7 @@
description of the change. If you modify a file that is not an article
but a script or part of software (such as <samp>server/gnun/gnun.mk</samp>),
it would be nice to follow the GNU Coding Standards and describe the
-change precisely. See <a
href="http://www.gnu.org/prep/standards/standards.html#Change-Logs";>Change
Logs</a> in <cite>The GNU Coding Standards</cite>. For example, do not write:
+change precisely (see <a
href="http://www.gnu.org/prep/standards/standards.html#Change-Logs";>Change
Logs</a> in <cite>The GNU Coding Standards</cite>). For example, do not write:
</p>
<div class="example">
<pre class="example">Added support for Nepali.
@@ -1011,16 +1017,105 @@
disable mail delivery in Mailman’s user interface.
</p>
<hr>
+<a name="PO-Files"></a>
+<div class="header">
+<p>
+Next: <a href="#Savannah" accesskey="n" rel="next">Savannah</a>, Previous: <a
href="#Commits" accesskey="p" rel="previous">Commits</a>, Up: <a
href="#Managing" accesskey="u" rel="up">Managing</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
+</div>
+<a name="Working-with-PO-Files"></a>
+<h4 class="subsection">3.2.3 Working with PO Files</h4>
+<a name="index-PO_002c-editing"></a>
+
+<p>We anticipate that some gnu.org translators will find this format odd
+or inconvenient, if they never happened to work with PO files
+before<a name="DOCF6" href="#FOOT6"><sup>6</sup></a>.
+Don’t worry, you will soon get accustomed to it. It is the
+established format for translations in the Free World, and you should
+have no problems if you have translated software before.
+</p>
+<p>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 it valid. Here is a list of widely used PO editors:
+</p>
+<ul>
+<li> <a name="index-PO-editors"></a>
+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 <samp>.po</samp> file you visit should automatically
+switch to PO mode. You can enable/disable it with <code>M-x po-mode
+<span class="key">RET</span></code>. On some GNU/Linux distros such as
gNewSense, PO mode is
+available in a separate package, <code>gettext-el</code>. See
+<a
href="http://www.gnu.org/software/gettext";>http://www.gnu.org/software/gettext</a>.
+
+</li><li> Gtranslator—the GNOME PO editor. See
+<a
href="http://projects.gnome.org/gtranslator/";>http://projects.gnome.org/gtranslator/</a>.
+
+</li><li> Lokalize—the KDE 4 editor. See
+<a
href="http://userbase.kde.org/Lokalize";>http://userbase.kde.org/Lokalize</a>.
+
+</li><li> KBabel—the KDE 3 editor. No longer supported, but might be
+available on some old systems.
+
+</li><li> Poedit—another popular editor that is based on the
<code>wxWidgets</code>
+graphical toolkit. See <a
href="http://www.poedit.net";>http://www.poedit.net</a>.
+
+</li><li> Virtaal—a relevantly new editor that supports also the XLIFF
format
+and uses the Translate Toolkit API. See
+<a
href="http://translate.sourceforge.net/wiki/virtaal";>http://translate.sourceforge.net/wiki/virtaal</a>.
+
+</li><li> po.vim—ftplugin for the Vim editor. The best option for
people who
+use Vim as their editor. See
+<a
href="http://www.vim.org/scripts/script.php?script_id=2530";>http://www.vim.org/scripts/script.php?script_id=2530</a>.
+
+</li><li> Various web-based editors.
+</li></ul>
+
+<a name="Web_002dbased-Systems"></a>
+<h4 class="subsubsection">3.2.3.1 Web-based Systems</h4>
+
+<p>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 <samp>.po</samp> 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
+(<a
href="http://translations.launchpad.net";>http://translations.launchpad.net</a>).
+</p>
+<p>Here is a short and probably incomplete list of such systems:
+</p>
+<ul>
+<li> Pootle—<a
href="http://translate.sourceforge.net/wiki/pootle";>http://translate.sourceforge.net/wiki/pootle</a>
+
+</li><li> Vertaal—<a
href="http://code.google.com/p/vertaal";>http://code.google.com/p/vertaal</a>
+
+</li><li> Narro—<a
href="http://code.google.com/p/narro";>http://code.google.com/p/narro</a>
+
+</li><li> Launchpad—<a
href="https://dev.launchpad.net";>https://dev.launchpad.net</a>
+
+</li></ul>
+
+<p>If you decide to use such a system, please make sure that no
+translations are published in HTML format there.
+</p>
+<p>Note that to keep the <samp>.pot</samp> files regularly updated (assuming
such
+a web-based system runs <code>msgmerge</code> automatically), you’ll have
+to take care of the one-way regular sync from the
‘<samp>www</samp>’ CVS
+repository.
+</p>
+<hr>
<a name="Savannah"></a>
<div class="header">
<p>
-Next: <a href="#Co_002dleaders" accesskey="n" rel="next">Co-leaders</a>,
Previous: <a href="#Commits" accesskey="p" rel="previous">Commits</a>, Up: <a
href="#Managing" accesskey="u" rel="up">Managing</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
+Next: <a href="#Co_002dleaders" accesskey="n" rel="next">Co-leaders</a>,
Previous: <a href="#PO-Files" accesskey="p" rel="previous">PO Files</a>, Up: <a
href="#Managing" accesskey="u" rel="up">Managing</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<a name="Taking-Advantage-of-Savannah"></a>
-<h4 class="subsection">3.2.3 Taking Advantage of Savannah</h4>
+<h4 class="subsection">3.2.4 Taking Advantage of Savannah</h4>
<p>Every translation team should have a project in Savannah. There are
-some teams that use their own resources outside from Savannah; although
+some teams that use their own resources outside Savannah; although
there’s no obligation to use Savannah for team work, the need for a
Savannah project for each language is obvious: it’s a standard way to
find information for translation teams and their contacts.
@@ -1072,13 +1167,11 @@
</td></tr>
<tr><td align="left" valign="top">• <a href="#Savannah-Bugs"
accesskey="5">Savannah Bugs</a>:</td><td> </td><td align="left"
valign="top">
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Savannah-Patch"
accesskey="6">Savannah Patch</a>:</td><td> </td><td align="left"
valign="top">
-</td></tr>
-<tr><td align="left" valign="top">• <a href="#Savannah-News"
accesskey="7">Savannah News</a>:</td><td> </td><td align="left"
valign="top">
+<tr><td align="left" valign="top">• <a href="#Savannah-News"
accesskey="6">Savannah News</a>:</td><td> </td><td align="left"
valign="top">
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Savannah-Mailing-Lists"
accesskey="8">Savannah Mailing Lists</a>:</td><td> </td><td
align="left" valign="top">
+<tr><td align="left" valign="top">• <a href="#Savannah-Mailing-Lists"
accesskey="7">Savannah Mailing Lists</a>:</td><td> </td><td
align="left" valign="top">
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Savannah-VCS"
accesskey="9">Savannah VCS</a>:</td><td> </td><td align="left"
valign="top">
+<tr><td align="left" valign="top">• <a href="#Savannah-VCS"
accesskey="8">Savannah VCS</a>:</td><td> </td><td align="left"
valign="top">
</td></tr>
</table>
@@ -1089,7 +1182,7 @@
Next: <a href="#Savannah-Homepage" accesskey="n" rel="next">Savannah
Homepage</a>, Up: <a href="#Savannah" accesskey="u" rel="up">Savannah</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
<a name="Managing-Members"></a>
-<h4 class="subsubsection">3.2.3.1 Managing Members</h4>
+<h4 class="subsubsection">3.2.4.1 Managing Members</h4>
<p>You should add active translators as members of the translation team,
and remove them when they leave. Team members should have access to all
@@ -1115,8 +1208,8 @@
<p>
Next: <a href="#Savannah-Support" accesskey="n" rel="next">Savannah
Support</a>, Previous: <a href="#Savannah-Members" accesskey="p"
rel="previous">Savannah Members</a>, Up: <a href="#Savannah" accesskey="u"
rel="up">Savannah</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-<a name="Homepage-of-The-Team"></a>
-<h4 class="subsubsection">3.2.3.2 Homepage of The Team</h4>
+<a name="Homepage-of-the-Team"></a>
+<h4 class="subsubsection">3.2.4.2 Homepage of the Team</h4>
<p>Every Savannah project has a Web repository, which is, for technical and
historical reasons, only CVS. By default it is mapped to
@@ -1146,7 +1239,7 @@
Next: <a href="#Savannah-Tasks" accesskey="n" rel="next">Savannah Tasks</a>,
Previous: <a href="#Savannah-Homepage" accesskey="p" rel="previous">Savannah
Homepage</a>, Up: <a href="#Savannah" accesskey="u" rel="up">Savannah</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
<a name="Support-Tracker"></a>
-<h4 class="subsubsection">3.2.3.3 Support Tracker</h4>
+<h4 class="subsubsection">3.2.4.3 Support Tracker</h4>
<p>This tracker is supposed to be related to things about the <em>project
management</em> itself, i.e. project members may report here missing
@@ -1161,7 +1254,7 @@
Next: <a href="#Savannah-Bugs" accesskey="n" rel="next">Savannah Bugs</a>,
Previous: <a href="#Savannah-Support" accesskey="p" rel="previous">Savannah
Support</a>, Up: <a href="#Savannah" accesskey="u" rel="up">Savannah</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
<a name="Tasks-Tracker"></a>
-<h4 class="subsubsection">3.2.3.4 Tasks Tracker</h4>
+<h4 class="subsubsection">3.2.4.4 Tasks Tracker</h4>
<p>This is a way to manage all sorts of tasks. They appear in the personal
Savannah page of the assignee, so it is difficult to miss them out. It
@@ -1178,10 +1271,10 @@
<a name="Savannah-Bugs"></a>
<div class="header">
<p>
-Next: <a href="#Savannah-Patch" accesskey="n" rel="next">Savannah Patch</a>,
Previous: <a href="#Savannah-Tasks" accesskey="p" rel="previous">Savannah
Tasks</a>, Up: <a href="#Savannah" accesskey="u" rel="up">Savannah</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
+Next: <a href="#Savannah-News" accesskey="n" rel="next">Savannah News</a>,
Previous: <a href="#Savannah-Tasks" accesskey="p" rel="previous">Savannah
Tasks</a>, Up: <a href="#Savannah" accesskey="u" rel="up">Savannah</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
<a name="Bugs-Tracker"></a>
-<h4 class="subsubsection">3.2.3.5 Bugs Tracker</h4>
+<h4 class="subsubsection">3.2.4.5 Bugs Tracker</h4>
<p>The ‘<samp>Bugs</samp>’ tracker is designed for tracking bugs.
You can use for
several purposes:
@@ -1198,31 +1291,13 @@
</li></ul>
<hr>
-<a name="Savannah-Patch"></a>
-<div class="header">
-<p>
-Next: <a href="#Savannah-News" accesskey="n" rel="next">Savannah News</a>,
Previous: <a href="#Savannah-Bugs" accesskey="p" rel="previous">Savannah
Bugs</a>, Up: <a href="#Savannah" accesskey="u" rel="up">Savannah</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
-</div>
-<a name="Patch-Tracker"></a>
-<h4 class="subsubsection">3.2.3.6 Patch Tracker</h4>
-
-<p>This tracker doesn’t make much sense for translation projects, as the
-original on which the translation is based is volatile and the
-translation <em>patch</em> is 100% guaranteed not to apply cleanly very
-soon after it is submitted. Even ignoring this detail, this specific
-feature is slowly marching towards complete deprecation, as there are
-much better ways to submit patches nowadays.
-</p>
-<p>You should disable this feature, as it causes only confusion.
-</p>
-<hr>
<a name="Savannah-News"></a>
<div class="header">
<p>
-Next: <a href="#Savannah-Mailing-Lists" accesskey="n" rel="next">Savannah
Mailing Lists</a>, Previous: <a href="#Savannah-Patch" accesskey="p"
rel="previous">Savannah Patch</a>, Up: <a href="#Savannah" accesskey="u"
rel="up">Savannah</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
+Next: <a href="#Savannah-Mailing-Lists" accesskey="n" rel="next">Savannah
Mailing Lists</a>, Previous: <a href="#Savannah-Bugs" accesskey="p"
rel="previous">Savannah Bugs</a>, Up: <a href="#Savannah" accesskey="u"
rel="up">Savannah</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
<a name="News-Tracker"></a>
-<h4 class="subsubsection">3.2.3.7 News Tracker</h4>
+<h4 class="subsubsection">3.2.4.6 News Tracker</h4>
<p>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</samp>’ RSS
@@ -1243,7 +1318,7 @@
Next: <a href="#Savannah-VCS" accesskey="n" rel="next">Savannah VCS</a>,
Previous: <a href="#Savannah-News" accesskey="p" rel="previous">Savannah
News</a>, Up: <a href="#Savannah" accesskey="u" rel="up">Savannah</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
<a name="Managing-Mailing-Lists"></a>
-<h4 class="subsubsection">3.2.3.8 Managing Mailing Lists</h4>
+<h4 class="subsubsection">3.2.4.7 Managing Mailing Lists</h4>
<p>Every team should have a mailing list on lists.gnu.org and use it for
internal communications. All active translators should be on the
@@ -1268,7 +1343,7 @@
Previous: <a href="#Savannah-Mailing-Lists" accesskey="p"
rel="previous">Savannah Mailing Lists</a>, Up: <a href="#Savannah"
accesskey="u" rel="up">Savannah</a> [<a href="#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<a name="Version-Control-Systems"></a>
-<h4 class="subsubsection">3.2.3.9 Version Control Systems</h4>
+<h4 class="subsubsection">3.2.4.8 Version Control Systems</h4>
<p>An easy way to keep up with changes in the original articles and to
manage continuous contributions is to keep all translations in the
@@ -1286,46 +1361,14 @@
collaborative maintenance—if it eases only you, project members just
won’t use it so that won’t be a net win.
</p>
-<a name="Web_002dbased-Systems"></a>
-<h4 class="subsubheading">Web-based Systems</h4>
-
-<p>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 <samp>.po</samp> 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
-(<a
href="http://translations.launchpad.net";>http://translations.launchpad.net</a>).
-</p>
-<p>Here is a short and probably incomplete list of such systems:
-</p>
-<ul>
-<li> Pootle—<a
href="http://translate.sourceforge.net/wiki/pootle";>http://translate.sourceforge.net/wiki/pootle</a>
-
-</li><li> Vertaal—<a
href="http://code.google.com/p/vertaal";>http://code.google.com/p/vertaal</a>
-
-</li><li> Narro—<a
href="http://code.google.com/p/narro";>http://code.google.com/p/narro</a>
-
-</li><li> Launchpad—<a
href="https://dev.launchpad.net";>https://dev.launchpad.net</a>
-
-</li></ul>
-
-<p>If you decide to use such a system, please make sure that no
-translations are published in HTML format there.
-</p>
-<p>Note that to keep the <samp>.pot</samp> files regularly updated (assuming
such
-a web-based system runs <code>msgmerge</code> automatically), you’ll have
-to take care of the one-way regular sync from the
‘<samp>www</samp>’ CVS
-repository.
-</p>
<hr>
<a name="Co_002dleaders"></a>
<div class="header">
<p>
Previous: <a href="#Savannah" accesskey="p" rel="previous">Savannah</a>, Up:
<a href="#Managing" accesskey="u" rel="up">Managing</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-<a name="Promoting-Members-As-Co_002dleaders"></a>
-<h4 class="subsection">3.2.4 Promoting Members As Co-leaders</h4>
+<a name="Promoting-Members-as-Co_002dleaders"></a>
+<h4 class="subsection">3.2.5 Promoting Members as Co-leaders</h4>
<p>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
@@ -1368,13 +1411,13 @@
</li><li>- New members since the last report.
-</li><li>- Current active members.
-
</li><li>- Solved problems and other issues, if any. (Usual bug reports and
other
improvements/fixes to the existing translations do not count as
<em>problems</em> in this sense.)
</li></ul>
+</li><li> Current active members.
+
</li><li> Current problems (technical or social), conflicts, and ideas for
sorting
them out.
@@ -1402,8 +1445,8 @@
<p>
Previous: <a href="#Reports" accesskey="p" rel="previous">Reports</a>, Up: <a
href="#Leaders" accesskey="u" rel="up">Leaders</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-<a name="How-To-Retire-Painlessly"></a>
-<h3 class="section">3.4 How To Retire Painlessly</h3>
+<a name="How-to-Retire-Painlessly"></a>
+<h3 class="section">3.4 How to Retire Painlessly</h3>
<p>When you feel you don’t have the energy to manage the team
successfully,
or perhaps you start losing motivation, please inform
@@ -1435,8 +1478,8 @@
<p>
Next: <a href="#Summary" accesskey="n" rel="next">Summary</a>, Previous: <a
href="#Translation-Managers" accesskey="p" rel="previous">Translation
Managers</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-<a name="Details-About-The-Translation-Process"></a>
-<h2 class="chapter">5 Details About The Translation Process</h2>
+<a name="Details-about-the-Translation-Process"></a>
+<h2 class="chapter">5 Details about the Translation Process</h2>
<p>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
@@ -1471,8 +1514,8 @@
<p>
Next: <a href="#SSI" accesskey="n" rel="next">SSI</a>, Up: <a
href="#Translation-Tips" accesskey="u" rel="up">Translation Tips</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-<a name="Migration-To-The-New-Style"></a>
-<h3 class="section">5.1 Migration To The New Style</h3>
+<a name="Migration-to-the-New-Style"></a>
+<h3 class="section">5.1 Migration to the New Style</h3>
<p>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
@@ -1654,8 +1697,8 @@
<p>
Next: <a href="#Priorities" accesskey="n" rel="next">Priorities</a>, Previous:
<a href="#SSI" accesskey="p" rel="previous">SSI</a>, Up: <a
href="#Translation-Tips" accesskey="u" rel="up">Translation Tips</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-<a name="How-To-Use-Custom-CSS"></a>
-<h3 class="section">5.3 How To Use Custom CSS</h3>
+<a name="How-to-Use-Custom-CSS"></a>
+<h3 class="section">5.3 How to Use Custom CSS</h3>
<p>The CSS file <samp>layout.css</samp> gets included (with three other CSS
files)
in almost all the English articles through
@@ -1718,8 +1761,8 @@
<p>
Next: <a href="#RTL" accesskey="n" rel="next">RTL</a>, Up: <a href="#CSS"
accesskey="u" rel="up">CSS</a> [<a href="#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
-<a name="Localizing-The-topbanner-Image"></a>
-<h4 class="subsection">5.3.1 Localizing The <samp>topbanner</samp> Image</h4>
+<a name="Localizing-the-topbanner-Image"></a>
+<h4 class="subsection">5.3.1 Localizing the <samp>topbanner</samp> Image</h4>
<p>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:
@@ -1732,7 +1775,7 @@
Then with Inkscape, save the file as
<samp>graphics/topbanner.<var>lang</var>.png</samp> (File -> Export
Bitmap…).
Then open the PNG image with the GIMP and flatten it (Image -> Flatten
-Image). Don’t forget to save and <code>cvs add</code> the files<a
name="DOCF6" href="#FOOT6"><sup>6</sup></a>.
+Image). Don’t forget to save and <code>cvs add</code> the files<a
name="DOCF7" href="#FOOT7"><sup>7</sup></a>.
</li><li> Create a <samp>style.<var>lang</var>.css</samp> at the toplevel
directory, if it
doesn’t exist already. Normally, you would need only one line in it,
@@ -1790,8 +1833,8 @@
<p>
Next: <a href="#Capitalization" accesskey="n" rel="next">Capitalization</a>,
Previous: <a href="#CSS" accesskey="p" rel="previous">CSS</a>, Up: <a
href="#Translation-Tips" accesskey="u" rel="up">Translation Tips</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-<a name="What-To-Translate"></a>
-<h3 class="section">5.4 What To Translate</h3>
+<a name="What-to-Translate"></a>
+<h3 class="section">5.4 What to Translate</h3>
<p>The article
<a
href="http://www.gnu.org/server/standards/translations/priorities.html";>http://www.gnu.org/server/standards/translations/priorities.html</a>
@@ -1807,12 +1850,14 @@
<p>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. GNUN’s <code>report</code> rule can help you
to
-identify precisely which articles need updating; see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#report";>report</a>
in <cite>The GNUnited Nations Manual</cite>. There is a monthly cronjob which
-sends a verbose output to each team—by default, the address(es) used
-is the Savannah account(s) of the admin(s) of the specific translation
-project. If you want them changed, please write to
+identify precisely which articles need updating; see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#report";>report</a>
in <cite>The GNUnited Nations Manual</cite>. There is a monthly cron job which
+sends a verbose output to each team as requested by their leaders.
+If you want the addresses changed, please write to
<a href="mailto:address@hidden";>address@hidden</a>.
</p>
+<p>More detailed notifications can be arranged through
+<samp>GNUmakefile.team</samp> (see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#PO-Files-and-Team";>PO
Files and Team</a> in <cite>The GNUnited Nations Manual</cite>).
+</p>
<p>GNUN also maintains reports about current status of translations of all
active teams in <a
href="http://www.gnu.org/software/gnun/reports/";>http://www.gnu.org/software/gnun/reports/</a>.
If
the page for your team is missing there, please ask
@@ -1861,8 +1906,8 @@
<p>
Next: <a href="#Distribution-Terms" accesskey="n" rel="next">Distribution
Terms</a>, Previous: <a href="#Priorities" accesskey="p"
rel="previous">Priorities</a>, Up: <a href="#Translation-Tips" accesskey="u"
rel="up">Translation Tips</a> [<a href="#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
-<a name="When-To-CAPITALIZE"></a>
-<h3 class="section">5.5 When To CAPITALIZE</h3>
+<a name="When-to-CAPITALIZE"></a>
+<h3 class="section">5.5 When to CAPITALIZE</h3>
<p>The English language has some rules for capitalization of titles,
chapters, acronym expansions and the like. These rules are neither
@@ -1878,12 +1923,13 @@
Wolne” (Polish) or “Fondation Pour Le Logiciel Libre”
(French).
</p>
<p>Another prominent and widely spread mistake is to write your own
-language with a capital letter in the <code>translations-list</code> when
+language with a capital letter in the list of translations when
languages are written beginning with a small letter according to your
-own rules. In other words, it is right to write
‘<samp>English</samp>’ or
-‘<samp>Deutsch</samp>’ (because in English and German languages are
-capitalized), but not ‘<samp>Français</samp>’ or
‘<samp>Português</samp>’—write
-them as ‘<samp>français</samp>’ or
‘<samp>português</samp>’, respectively.
+own rules<a name="DOCF8" href="#FOOT8"><sup>8</sup></a>. In other words, it
is right to write
+‘<samp>English</samp>’ or ‘<samp>Deutsch</samp>’
(because in English and German
+languages are capitalized), but not ‘<samp>Français</samp>’
or
+‘<samp>Português</samp>’—write them as
‘<samp>français</samp>’ or
+‘<samp>português</samp>’, respectively.
</p>
<hr>
<a name="Distribution-Terms"></a>
@@ -1936,13 +1982,14 @@
Dutch language deed. We should always link to a copy of the license
deed that’s in the same language as the page itself.
</p>
-<p>Pages in languages that aren’t supported by CC should prepare their
own
-translation, use it consistently throughout pages translated to that
-language, and link to the English language deed. Also, please
-write your own translation when the translation provided by CC is
-not satisfactory for some reasons—for instance, as of May, 2012, their
-German translation uses “Content”, which is a word to use with
caution
-(see <a
href="http://www.gnu.org/philosophy/words-to-avoid.en.html#Content";>http://www.gnu.org/philosophy/words-to-avoid.en.html#Content</a>).
+<p>Pages in languages that aren’t supported by CC should prepare their
+own translation, use it consistently throughout pages translated to
+that language, and link to the English language deed. Also, please
+write your own translation when the translation provided by CC is not
+satisfactory for some reasons—for instance, as of May, 2012, their
+German translation uses “Content”, which is a word to use with
+caution (see
+<a
href="http://www.gnu.org/philosophy/words-to-avoid.en.html#Content";>http://www.gnu.org/philosophy/words-to-avoid.en.html#Content</a>).
</p>
<p>Note that translations should <em>not</em> change the jurisdiction of the
license; they should <em>always</em> link to the CC BY-ND 3.0 <em>United
@@ -1968,8 +2015,8 @@
<p>
Next: <a href="#Copying-This-Manual" accesskey="n" rel="next">Copying This
Manual</a>, Previous: <a href="#Translation-Tips" accesskey="p"
rel="previous">Translation Tips</a>, Up: <a href="#Top" accesskey="u"
rel="up">Top</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-<a name="Overview-Of-The-Translation-Process"></a>
-<h2 class="chapter">6 Overview Of The Translation Process</h2>
+<a name="Overview-of-the-Translation-Process"></a>
+<h2 class="chapter">6 Overview of the Translation Process</h2>
<p>In general, it is expected that all participants in the translation
process apply common sense for all of the decisions (important or not)
@@ -2078,13 +2125,13 @@
<dt>‘<samp>www</samp>’</dt>
<dd><p>The main project which hosts the ‘<samp>gnu.org</samp>’ Web
repository.
Administrators are the Chief Webmaster, entrusted webmasters and the
-Translation Manager (in order to approve leader’s applications). All
+Translation Manager (in order to approve leaders’ applications). All
team leaders (and co-leaders) should be members of this project.
</p>
<p>Note that this project has no direct relationship with translators,
-although anything happening in ‘<samp>www</samp>’ directly affects
them. The
-‘<samp>www</samp>’ project is managed separately and has a
different (entirely
-unrelated) process for approving contributors.
+although almost anything happening in ‘<samp>www</samp>’ directly
affects
+them. The ‘<samp>www</samp>’ project is managed separately and has
+a different (entirely unrelated) process for approving contributors.
</p>
</dd>
<dt>‘<samp>trans-coord</samp>’</dt>
@@ -2098,8 +2145,9 @@
</dd>
<dt>‘<samp>www-<var>lang</var></samp>’</dt>
<dd><p>All translation team leaders of the language <var>lang</var> should be
-members of the project ‘<samp>www-<var>lang</var></samp>’. The
admins of the project
-are the team leader and the co-leaders, if any.
+admins of the project ‘<samp>www-<var>lang</var></samp>’. The
leaders may
+also appoint some other members as
‘<samp>www-<var>lang</var></samp>’ admins
+for team’s internal reasons.
</p></dd>
</dl>
@@ -2608,8 +2656,16 @@
OS people use, but we can at least prevent this technical kind
of damage.</p>
<h3><a name="FOOT6" href="#DOCF6">(6)</a></h3>
+<p>For www.gnu.org-specific information about editing
+PO files, see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#PO-Files";>Working
with PO Files</a> in <cite>The GNUnited Nations Manual</cite>.</p>
+<h3><a name="FOOT7" href="#DOCF7">(7)</a></h3>
<p>This
advice applies to all new files, of course.</p>
+<h3><a name="FOOT8" href="#DOCF8">(8)</a></h3>
+<p>The lists of translations are generated
+automatically. The names of the languages are defined in a specific
+file, languages.txt (see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#languages_002etxt";>languages.txt</a>
in <cite>The GNUnited
+Nations Manual</cite>).</p>
</div>
<hr>
Index: web-trans/web-trans.html.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.html.gz,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
Binary files /tmp/cvsdtOy5D and /tmp/cvsAsGML6 differ
Index: web-trans/web-trans.html_node.tar.gz
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/web-trans.html_node.tar.gz,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
Binary files /tmp/cvsPz3rkC and /tmp/cvshqjV14 differ
Index: web-trans/web-trans.info.tar.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.info.tar.gz,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
Binary files /tmp/cvsc87jWC and /tmp/cvsLfwXE5 differ
Index: web-trans/web-trans.pdf
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.pdf,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
Binary files /tmp/cvsR1WhQF and /tmp/cvsXK6CC8 differ
Index: web-trans/web-trans.texi.tar.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.texi.tar.gz,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
Binary files /tmp/cvsoz2O0E and /tmp/cvs79C2O7 differ
Index: web-trans/web-trans.txt
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.txt,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/web-trans.txt 4 Dec 2012 16:24:26 -0000 1.11
+++ web-trans/web-trans.txt 27 Dec 2012 14:45:38 -0000 1.12
@@ -1,43 +1,44 @@
GNU Web Translators Manual
1 Introduction
2 Team Members
- 2.1 Joining A Team
- 2.2 How To Submit a Translation
- 2.2.1 How To Submit a Translation in PO Format
- 2.2.2 How To Submit a Translation as Plain Text
- 2.3 Leaving A Team
+ 2.1 Joining a Team
+ 2.2 How to Submit a Translation
+ 2.2.1 How to Submit a Translation in PO Format
+ 2.2.2 How to Submit a Translation as Plain Text
+ 2.3 Leaving a Team
3 Team Co-ordinators
- 3.1 How To Form A New Team
- 3.2 The Gentle Art of Managing A Translation Team
+ 3.1 How to Form a New Team
+ 3.2 The Gentle Art of Managing a Translation Team
3.2.1 Peer Review
- 3.2.1.1 How To Track Tasks and Bugs Using Savannah
- 3.2.1.2 How To Proceed With Unreviewed Translations
- 3.2.2 CVS Commits And Best Practices
- 3.2.3 Taking Advantage of Savannah
- 3.2.3.1 Managing Members
- 3.2.3.2 Homepage of The Team
- 3.2.3.3 Support Tracker
- 3.2.3.4 Tasks Tracker
- 3.2.3.5 Bugs Tracker
- 3.2.3.6 Patch Tracker
- 3.2.3.7 News Tracker
- 3.2.3.8 Managing Mailing Lists
- 3.2.3.9 Version Control Systems
- 3.2.4 Promoting Members As Co-leaders
+ 3.2.1.1 How to Track Tasks and Bugs Using Savannah
+ 3.2.1.2 How to Proceed with Unreviewed Translations
+ 3.2.2 CVS Commits and Best Practices
+ 3.2.3 Working with PO Files
+ 3.2.3.1 Web-based Systems
+ 3.2.4 Taking Advantage of Savannah
+ 3.2.4.1 Managing Members
+ 3.2.4.2 Homepage of the Team
+ 3.2.4.3 Support Tracker
+ 3.2.4.4 Tasks Tracker
+ 3.2.4.5 Bugs Tracker
+ 3.2.4.6 News Tracker
+ 3.2.4.7 Managing Mailing Lists
+ 3.2.4.8 Version Control Systems
+ 3.2.5 Promoting Members as Co-leaders
3.3 Reporting Team Status
- 3.4 How To Retire Painlessly
+ 3.4 How to Retire Painlessly
4 'trans-coord' Admins
-5 Details About The Translation Process
- 5.1 Migration To The New Style
+5 Details about the Translation Process
+ 5.1 Migration to the New Style
5.2 Summary of SSI '#include's
- 5.3 How To Use Custom CSS
- 5.3.1 Localizing The 'topbanner' Image
+ 5.3 How to Use Custom CSS
+ 5.3.1 Localizing the 'topbanner' Image
5.3.2 Specific Issues Related to RTL
- 5.4 What To Translate
- 5.5 When To CAPITALIZE
+ 5.4 What to Translate
+ 5.5 When to CAPITALIZE
5.6 Distribution Terms
5.7 Language-specific Terminology
-6 Overview Of The Translation Process
+6 Overview of the Translation Process
6.1 Related Mailing Lists
6.2 Savannah Projects Membership
Appendix A GNU Free Documentation License
@@ -45,7 +46,7 @@
**************************
This manual is a guide for the GNU Web Translators.
-Last updated on 28.06.2012, for GNUnited Nations version 0.6.
+Last updated on 25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software Foundation, Inc.
@@ -92,12 +93,12 @@
describe the fundamental values of the free software movement.
Translators of the <http://gnu.org> website are organized in 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 'trans-coord' organizational project, which is managed by
-the GNU Web Translation Managers. The manual is organized in chapters
-that follow the organizational structure of the whole translation
-project.
+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 'trans-coord' organizational project, which is managed
+by the GNU Web Translation Managers. The manual is organized in
+chapters that follow the organizational structure of the whole
+translation project.
If you wish to join a translation team or contribute a translation or
two, *note Members::. If your intention is to form a translation team,
@@ -115,7 +116,7 @@
other people's translations, participating in discussions about
terminology issues, and sometimes performing clean-up tasks.
-2.1 Joining A Team
+2.1 Joining a Team
==================
To join a team, please first look at the existing teams at
@@ -166,7 +167,7 @@
For general information about the translation process, *note
Translation Tips::.
-2.2 How To Submit a Translation
+2.2 How to Submit a Translation
===============================
Everyone can still submit translations even if there is no translation
@@ -175,7 +176,7 @@
which means more work for a limited group of volunteers (the Translation
Managers) to convert the translation in '.po' format.
-2.2.1 How To Submit a Translation in PO Format
+2.2.1 How to Submit a Translation in PO Format
----------------------------------------------
All translations(1) are maintained via GNUN (see
@@ -205,7 +206,7 @@
example, the URL for the template file of
<http://www.gnu.org/philosophy/free-sw.html> is
<http://www.gnu.org/philosophy/po/free-sw.pot>; the URL for its
- LANG PO file (when available) is
+ LANG PO file (when available) is always
<http://www.gnu.org/philosophy/po/free-sw.LANG.po>:
wget http://www.gnu.org/philosophy/po/free-sw.pot
@@ -213,7 +214,7 @@
* Assuming you already know the article you want to translate, you
have to create an empty 'ARTICLE.LANG.po' file and then translate
all messages with a PO editor. *Note (gnun)New Translation::. For
- an almost complete list of PO editors, *note (gnun)PO Files::.
+ an almost complete list of PO editors, *note PO Files::.
* When you are pleased with the translation, check that the PO file
is valid and submit it to <address@hidden>, attached to
@@ -247,7 +248,7 @@
(1) Well--not really, but the goal is to maintain all of them.
-2.2.2 How To Submit a Translation as Plain Text
+2.2.2 How to Submit a Translation as Plain Text
-----------------------------------------------
If you feel the procedure described in the previous section is too
@@ -308,7 +309,7 @@
for any errors or omissions that may have resulted from the conversion
process, and report them back.
-2.3 Leaving A Team
+2.3 Leaving a Team
==================
When you realize that you don't have time or can't devote sufficient
@@ -337,7 +338,7 @@
the goals of the project at large. Inefficient or inoperative leaders
are replaced, if necessary.
-3.1 How To Form A New Team
+3.1 How to Form a New Team
==========================
Establishing a new team is not hard, but a certain procedure ought to be
@@ -348,12 +349,11 @@
You should read _all_ the documentation related to the translation
process and at the very least all important philosophy-related articles
-listed on <http://gnu.org/server/standards/README.translations.html> and
-<http://gnu.org/server/standards/translations/priorities.html> before
-you decide to form a new team, or take over an orphaned team. Once you
-have the internal feeling that having a gnu.org translation team for
-your language is a must, and you are the one for this job, follow these
-steps:
+listed at <http://gnu.org/server/standards/translations/priorities.html>
+before you decide to form a new team, or take over an orphaned team.
+Once you have the internal feeling that having a gnu.org translation
+team for your language is a must, and you are the one for this job,
+follow these steps:
1. If you do not have a Savannah account, register at
<https://savannah.gnu.org/account/register.php>. Write access to
@@ -392,14 +392,25 @@
understanding of the philosophy of the free software movement.
4. Check if your language code is present in the variable
- 'TEMPLATE_LINGUAS' at 'server/gnun/gnun.mk'. If it is not, the
- first thing to do is to translate and submit to
+ 'TEMPLATE_LINGUAS' in the file 'server/gnun/gnun.mk'. If it is
+ not, the first thing to do is to translate and submit to
<address@hidden> the following files (all in the
- 'server/po/' directory): 'head-include-2.LANG.po',
- 'body-include-1.LANG.po', 'body-include-2.LANG.po'
- 'footer-text.LANG.po', 'outdated.LANG.po',
- 'skip-translations.LANG.po', and 'top-addendum.LANG.po'. *Note
- (gnun)New Translation::.
+ 'server/po/' directory):
+ * 'head-include-2.LANG.po'
+
+ * 'body-include-1.LANG.po'
+
+ * 'body-include-2.LANG.po'
+
+ * 'footer-text.LANG.po'
+
+ * 'outdated.LANG.po'
+
+ * 'skip-translations.LANG.po'
+
+ * 'top-addendum.LANG.po'
+
+ *Note (gnun)New Translation::.
- The language code (LANG) should be the ISO 639-1 code of the
language, for example 'hy' for Armenian or 'el' for Greek. If
@@ -410,11 +421,6 @@
- The PO file header and initial comments should be completed as
documented.
- - 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 'ü' and this is a character from the alphabet of
- your language, just write it as 'u"' directly.
-
5. Any prospective team leader should submit a few translations first.
This is a process of pointing errors and omissions (which are
expected and natural); it's an important thing to do as the leader
@@ -500,7 +506,7 @@
the person who is already carrying out the process--this is also a
verification if she can co-operate easily with others.
-3.2 The Gentle Art of Managing A Translation Team
+3.2 The Gentle Art of Managing a Translation Team
=================================================
It is not our ambition to describe all activities involved in managing a
@@ -554,7 +560,7 @@
section, *note Tracking Tasks::. One way or another, you should create
some kind of review process.
-3.2.1.1 How To Track Tasks and Bugs Using Savannah
+3.2.1.1 How to Track Tasks and Bugs Using Savannah
..................................................
The team leader has to make sure that prospective translations are
@@ -636,7 +642,7 @@
'generic.LANG.html' and advertise it on every page. *Note
(gnun)generic.LANG.html::, for details.
-3.2.1.2 How To Proceed With Unreviewed Translations
+3.2.1.2 How to Proceed with Unreviewed Translations
...................................................
Sometimes a translation (typically your own) is not reviewed by anyone
@@ -651,7 +657,7 @@
and 'Ready For Test' despite the translation being officially online.
You may also add a comment to the PO file.
-3.2.2 CVS Commits And Best Practices
+3.2.2 CVS Commits and Best Practices
------------------------------------
As all team leaders have write access to the CVS repository of the 'www'
@@ -671,11 +677,12 @@
general issues that affect more articles, or for severe problems, please
write to <address@hidden>.
- It is recommended to read the entire CVS manual at least once, for a
-basic understanding of how this VCS works. *Note Concurrent Versions
-System: (cvs)Top. It is not necessary to become an expert--the 'www'
-project does not use complex features like tags, vendor branches,
-merging, etc. as they are not very useful for a live website.
+ If you are not familiar with CVS, it is recommended to read CVS
+manual, for a basic understanding of how this VCS works. *Note
+Concurrent Versions System: (cvs)Top. It is not necessary to become an
+expert--the 'www' project does not use complex features like tags,
+vendor branches, merging, etc. as they are not very useful for a live
+website.
However, you'd probably have to learn how to use CVS for effective
work--to extract information from the history, review diffs and specific
@@ -689,8 +696,8 @@
English(1), 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
'server/gnun/gnun.mk'), it would be nice to follow the GNU Coding
-Standards and describe the change precisely. *Note Log Messages:
-(standards)Change Logs. For example, do not write:
+Standards and describe the change precisely (*note Log Messages:
+(standards)Change Logs.). For example, do not write:
Added support for Nepali.
@@ -735,11 +742,90 @@
systems--we don't dictate what OS people use, but we can at least
prevent this technical kind of damage.
-3.2.3 Taking Advantage of Savannah
+3.2.3 Working with PO Files
+---------------------------
+
+We anticipate that some gnu.org translators will find this format odd or
+inconvenient, if they never happened to work with PO files before(1).
+Don't worry, you will soon get accustomed to it. It is the established
+format for translations in the Free World, and you should have no
+problems if you have translated software before.
+
+ 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 it valid. Here is a list of widely used PO editors:
+
+ * 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 '.po' file you visit should
+ automatically switch to PO mode. You can enable/disable it with
+ 'M-x po-mode <RET>'. On some GNU/Linux distros such as gNewSense,
+ PO mode is available in a separate package, 'gettext-el'. See
+ <http://www.gnu.org/software/gettext>.
+
+ * Gtranslator--the GNOME PO editor. See
+ <http://projects.gnome.org/gtranslator/>.
+
+ * Lokalize--the KDE 4 editor. See
+ <http://userbase.kde.org/Lokalize>.
+
+ * KBabel--the KDE 3 editor. No longer supported, but might be
+ available on some old systems.
+
+ * Poedit--another popular editor that is based on the 'wxWidgets'
+ graphical toolkit. See <http://www.poedit.net>.
+
+ * Virtaal--a relevantly new editor that supports also the XLIFF
+ format and uses the Translate Toolkit API. See
+ <http://translate.sourceforge.net/wiki/virtaal>.
+
+ * po.vim--ftplugin for the Vim editor. The best option for people
+ who use Vim as their editor. See
+ <http://www.vim.org/scripts/script.php?script_id=2530>.
+
+ * Various web-based editors.
+
+3.2.3.1 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 '.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
+(<http://translations.launchpad.net>).
+
+ Here is a short and probably incomplete list of such systems:
+
+ * Pootle--<http://translate.sourceforge.net/wiki/pootle>
+
+ * Vertaal--<http://code.google.com/p/vertaal>
+
+ * Narro--<http://code.google.com/p/narro>
+
+ * Launchpad--<https://dev.launchpad.net>
+
+ 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 '.pot' files regularly updated (assuming such a
+web-based system runs 'msgmerge' automatically), you'll have to take
+care of the one-way regular sync from the 'www' CVS repository.
+
+ ---------- Footnotes ----------
+
+ (1) For www.gnu.org-specific information about editing PO files,
+*note Working with PO Files: (gnun)PO Files.
+
+3.2.4 Taking Advantage of Savannah
----------------------------------
Every translation team should have a project in Savannah. There are
-some teams that use their own resources outside from Savannah; although
+some teams that use their own resources outside Savannah; although
there's no obligation to use Savannah for team work, the need for a
Savannah project for each language is obvious: it's a standard way to
find information for translation teams and their contacts.
@@ -780,7 +866,7 @@
facilities provided by Savannah. It is not mandatory to follow them,
they are just suggestions.
-3.2.3.1 Managing Members
+3.2.4.1 Managing Members
........................
You should add active translators as members of the translation team,
@@ -801,7 +887,7 @@
the total number of members, and they appear separately on 'View
Members'.
-3.2.3.2 Homepage of The Team
+3.2.4.2 Homepage of the Team
............................
Every Savannah project has a Web repository, which is, for technical and
@@ -825,7 +911,7 @@
These locations are deprecated, and the contents will be removed without
warning.
-3.2.3.3 Support Tracker
+3.2.4.3 Support Tracker
.......................
This tracker is supposed to be related to things about the _project
@@ -834,7 +920,7 @@
Do not use it for anything else as it quickly becomes confusing. It is
OK to disable it if the team is small.
-3.2.3.4 Tasks Tracker
+3.2.4.4 Tasks Tracker
.....................
This is a way to manage all sorts of tasks. They appear in the personal
@@ -848,7 +934,7 @@
Feel free to organize the 'Tasks' management as you see fit.
-3.2.3.5 Bugs Tracker
+3.2.4.5 Bugs Tracker
....................
The 'Bugs' tracker is designed for tracking bugs. You can use for
@@ -863,19 +949,7 @@
(who is supposed to be a 'www-LANG' project member), if you have
such policy.
-3.2.3.6 Patch Tracker
-.....................
-
-This tracker doesn't make much sense for translation projects, as the
-original on which the translation is based is volatile and the
-translation "patch" is 100% guaranteed not to apply cleanly very soon
-after it is submitted. Even ignoring this detail, this specific feature
-is slowly marching towards complete deprecation, as there are much
-better ways to submit patches nowadays.
-
- You should disable this feature, as it causes only confusion.
-
-3.2.3.7 News Tracker
+3.2.4.6 News Tracker
....................
That is a way to inform newcomers and interested people (who visit the
@@ -890,7 +964,7 @@
perfectly OK to announce it here. Some teams use it to announce new
translations, which is also fine.
-3.2.3.8 Managing Mailing Lists
+3.2.4.7 Managing Mailing Lists
..............................
Every team should have a mailing list on lists.gnu.org and use it for
@@ -909,7 +983,7 @@
You can redirect all messages generated by the trackers to any list.
-3.2.3.9 Version Control Systems
+3.2.4.8 Version Control Systems
...............................
An easy way to keep up with changes in the original articles and to
@@ -927,35 +1001,7 @@
maintenance--if it eases only you, project members just won't use it so
that won't be a net win.
-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 '.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
-(<http://translations.launchpad.net>).
-
- Here is a short and probably incomplete list of such systems:
-
- * Pootle--<http://translate.sourceforge.net/wiki/pootle>
-
- * Vertaal--<http://code.google.com/p/vertaal>
-
- * Narro--<http://code.google.com/p/narro>
-
- * Launchpad--<https://dev.launchpad.net>
-
- 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 '.pot' files regularly updated (assuming such a
-web-based system runs 'msgmerge' automatically), you'll have to take
-care of the one-way regular sync from the 'www' CVS repository.
-
-3.2.4 Promoting Members As Co-leaders
+3.2.5 Promoting Members as Co-leaders
-------------------------------------
When the team grows large and it becomes hard for a single person to
@@ -991,12 +1037,12 @@
- New members since the last report.
- - Current active members.
-
- Solved problems and other issues, if any. (Usual bug reports
and other improvements/fixes to the existing translations do
not count as "problems" in this sense.)
+ * Current active members.
+
* Current problems (technical or social), conflicts, and ideas for
sorting them out.
@@ -1017,7 +1063,7 @@
If you do not wish to share some information that is in the report,
please send it to <address@hidden>.
-3.4 How To Retire Painlessly
+3.4 How to Retire Painlessly
============================
When you feel you don't have the energy to manage the team successfully,
@@ -1038,7 +1084,7 @@
This chapter is not yet written. The current admins know what to do,
hopefully.
-5 Details About The Translation Process
+5 Details about the Translation Process
***************************************
The purpose of this chapter is to summarize some odd and not so obvious
@@ -1051,7 +1097,7 @@
webmastering processes. Others are outright deficiencies (i.e.
"bugs"), but no one has stepped in to correct them so far.
-5.1 Migration To The New Style
+5.1 Migration to the New Style
==============================
Migration to the new style should be straightforward, and this is one of
@@ -1198,7 +1244,7 @@
whenever there is a change in the original English files; the 'GRACE'
variable has no effect for them. *Note (gnun)Runtime Variables::.
-5.3 How To Use Custom CSS
+5.3 How to Use Custom CSS
=========================
The CSS file 'layout.css' gets included (with three other CSS files) in
@@ -1242,7 +1288,7 @@
with appropriate explanation (which may include a demonstration of the
bug, such as a screenshot).
-5.3.1 Localizing The 'topbanner' Image
+5.3.1 Localizing the 'topbanner' Image
--------------------------------------
If you'd like the nice gnu image to be localized (i.e. "GNU Operating
@@ -1296,7 +1342,7 @@
issues that affect your language and require a general solution, write
to <address@hidden> as well, precisely describing the problem.
-5.4 What To Translate
+5.4 What to Translate
=====================
The article
@@ -1312,11 +1358,13 @@
the respective English originals. This task should be higher priority
than translating new articles. GNUN's 'report' rule can help you to
identify precisely which articles need updating; *note (gnun)report::.
-There is a monthly cronjob which sends a verbose output to each team--by
-default, the address(es) used is the Savannah account(s) of the admin(s)
-of the specific translation project. If you want them changed, please
+There is a monthly cron job which sends a verbose output to each team as
+requested by their leaders. If you want the addresses changed, please
write to <address@hidden>.
+ More detailed notifications can be arranged through
+'GNUmakefile.team' (*note (gnun)PO Files and Team::).
+
GNUN also maintains reports about current status of translations of
all active teams in <http://www.gnu.org/software/gnun/reports/>. If the
page for your team is missing there, please ask
@@ -1353,7 +1401,7 @@
"GNU News". It is deprecated since quite some time and translating
it is discouraged.
-5.5 When To CAPITALIZE
+5.5 When to CAPITALIZE
======================
The English language has some rules for capitalization of titles,
@@ -1370,11 +1418,18 @@
(Polish) or "Fondation Pour Le Logiciel Libre" (French).
Another prominent and widely spread mistake is to write your own
-language with a capital letter in the 'translations-list' when languages
-are written beginning with a small letter according to your own rules.
-In other words, it is right to write 'English' or 'Deutsch' (because in
-English and German languages are capitalized), but not 'Franc,ais' or
-'Portugue^s'--write them as 'franc,ais' or 'portugue^s', respectively.
+language with a capital letter in the list of translations when
+languages are written beginning with a small letter according to your
+own rules(1). In other words, it is right to write 'English' or
+'Deutsch' (because in English and German languages are capitalized), but
+not 'Franc,ais' or 'Portugue^s'--write them as 'franc,ais' or
+'portugue^s', respectively.
+
+ ---------- Footnotes ----------
+
+ (1) The lists of translations are generated automatically. The names
+of the languages are defined in a specific file, languages.txt (*note
+(gnun)languages.txt::).
5.6 Distribution Terms
======================
@@ -1434,7 +1489,7 @@
This is a very important topic, not yet covered by this manual.
-6 Overview Of The Translation Process
+6 Overview of the Translation Process
*************************************
In general, it is expected that all participants in the translation
@@ -1460,11 +1515,13 @@
process, and a brief description about how they relate to the various
participants in the process.
+<address@hidden>
The basic discussion list of the GNU Webmasters. All team leaders
are required to subscribe.
This is a private mailing list.
+<address@hidden>
Commits to the 'www' repository are sent here. All Translation
Managers are required to subscribe. It is strongly recommended
that team leaders subscribe--in any case they should, and mail
@@ -1473,6 +1530,7 @@
This is a public mailing list, so everyone can subscribe and review
the archives. The 'www' CVS repository is also public.
+<address@hidden>
The main discussion list for the GNU Web Translators. Team leaders
must subscribe, as errors from GNUN are mailed here. Active team
members are highly recommended to join as well, because the changes
@@ -1481,6 +1539,7 @@
This is a private mailing list.
+<address@hidden>
This is a list for notifications about gnunews and 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
@@ -1498,6 +1557,7 @@
This is a public mailing list.
+<address@hidden>
All development of GNUN happens here. Commits to the 'trans-coord'
repository are also sent to this list.
@@ -1512,14 +1572,14 @@
'www'
The main project which hosts the 'gnu.org' Web repository.
Administrators are the Chief Webmaster, entrusted webmasters and
- the Translation Manager (in order to approve leader's
+ the Translation Manager (in order to approve leaders'
applications). All team leaders (and co-leaders) should be members
of this project.
Note that this project has no direct relationship with translators,
- although anything happening in 'www' directly affects them. The
- 'www' project is managed separately and has a different (entirely
- unrelated) process for approving contributors.
+ although almost anything happening in 'www' directly affects them.
+ The 'www' project is managed separately and has a different
+ (entirely unrelated) process for approving contributors.
'trans-coord'
An organizational project especially created for co-ordination and
@@ -1531,9 +1591,9 @@
The admins of this project are the GNU Web Translation Managers.
'www-LANG'
- All translation team leaders of the language LANG should be members
- of the project 'www-LANG'. The admins of the project are the team
- leader and the co-leaders, if any.
+ All translation team leaders of the language LANG should be admins
+ of the project 'www-LANG'. The leaders may also appoint some other
+ members as 'www-LANG' admins for team's internal reasons.
Appendix A GNU Free Documentation License
*****************************************
Index: web-trans/web-trans.txt.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.txt.gz,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
Binary files /tmp/cvssQKHbH and /tmp/cvsvfqV29 differ
Index: web-trans/html_node/CSS.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/CSS.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- web-trans/html_node/CSS.html 4 Dec 2012 16:24:26 -0000 1.10
+++ web-trans/html_node/CSS.html 27 Dec 2012 14:45:39 -0000 1.11
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: CSS</title>
@@ -68,8 +68,8 @@
Next: <a href="Priorities.html#Priorities" accesskey="n"
rel="next">Priorities</a>, Previous: <a href="SSI.html#SSI" accesskey="p"
rel="previous">SSI</a>, Up: <a href="Translation-Tips.html#Translation-Tips"
accesskey="u" rel="up">Translation Tips</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="How-To-Use-Custom-CSS"></a>
-<h3 class="section">5.3 How To Use Custom CSS</h3>
+<a name="How-to-Use-Custom-CSS"></a>
+<h3 class="section">5.3 How to Use Custom CSS</h3>
<p>The CSS file <samp>layout.css</samp> gets included (with three other CSS
files)
in almost all the English articles through
Index: web-trans/html_node/Capitalization.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Capitalization.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Capitalization.html 4 Dec 2012 16:24:26 -0000
1.9
+++ web-trans/html_node/Capitalization.html 27 Dec 2012 14:45:39 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Capitalization</title>
@@ -68,8 +68,8 @@
Next: <a href="Distribution-Terms.html#Distribution-Terms" accesskey="n"
rel="next">Distribution Terms</a>, Previous: <a
href="Priorities.html#Priorities" accesskey="p" rel="previous">Priorities</a>,
Up: <a href="Translation-Tips.html#Translation-Tips" accesskey="u"
rel="up">Translation Tips</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="When-To-CAPITALIZE"></a>
-<h3 class="section">5.5 When To CAPITALIZE</h3>
+<a name="When-to-CAPITALIZE"></a>
+<h3 class="section">5.5 When to CAPITALIZE</h3>
<p>The English language has some rules for capitalization of titles,
chapters, acronym expansions and the like. These rules are neither
@@ -85,13 +85,24 @@
Wolne” (Polish) or “Fondation Pour Le Logiciel Libre”
(French).
</p>
<p>Another prominent and widely spread mistake is to write your own
-language with a capital letter in the <code>translations-list</code> when
+language with a capital letter in the list of translations when
languages are written beginning with a small letter according to your
-own rules. In other words, it is right to write
‘<samp>English</samp>’ or
-‘<samp>Deutsch</samp>’ (because in English and German languages are
-capitalized), but not ‘<samp>Français</samp>’ or
‘<samp>Português</samp>’—write
-them as ‘<samp>français</samp>’ or
‘<samp>português</samp>’, respectively.
+own rules<a name="DOCF8" href="#FOOT8"><sup>8</sup></a>. In other words, it
is right to write
+‘<samp>English</samp>’ or ‘<samp>Deutsch</samp>’
(because in English and German
+languages are capitalized), but not ‘<samp>Français</samp>’
or
+‘<samp>Português</samp>’—write them as
‘<samp>français</samp>’ or
+‘<samp>português</samp>’, respectively.
</p>
+<div class="footnote">
+<hr>
+<h4 class="footnotes-heading">Footnotes</h4>
+
+<h3><a name="FOOT8" href="#DOCF8">(8)</a></h3>
+<p>The lists of translations are generated
+automatically. The names of the languages are defined in a specific
+file, languages.txt (see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/languages_002etxt.html#languages_002etxt";>languages.txt</a>
in <cite>The GNUnited
+Nations Manual</cite>).</p>
+</div>
Index: web-trans/html_node/Co_002dleaders.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Co_002dleaders.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Co_002dleaders.html 4 Dec 2012 16:24:26 -0000
1.9
+++ web-trans/html_node/Co_002dleaders.html 27 Dec 2012 14:45:39 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Co-leaders</title>
@@ -68,8 +68,8 @@
Previous: <a href="Savannah.html#Savannah" accesskey="p"
rel="previous">Savannah</a>, Up: <a href="Managing.html#Managing" accesskey="u"
rel="up">Managing</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="Promoting-Members-As-Co_002dleaders"></a>
-<h4 class="subsection">3.2.4 Promoting Members As Co-leaders</h4>
+<a name="Promoting-Members-as-Co_002dleaders"></a>
+<h4 class="subsection">3.2.5 Promoting Members as Co-leaders</h4>
<p>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
Index: web-trans/html_node/Commits.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/Commits.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Commits.html 4 Dec 2012 16:24:26 -0000 1.9
+++ web-trans/html_node/Commits.html 27 Dec 2012 14:45:39 -0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Commits</title>
@@ -27,7 +27,7 @@
<link href="index.html#Top" rel="start" title="Top">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Managing.html#Managing" rel="up" title="Managing">
-<link href="Savannah.html#Savannah" rel="next" title="Savannah">
+<link href="PO-Files.html#PO-Files" rel="next" title="PO Files">
<link href="Unreviewed-Translations.html#Unreviewed-Translations"
rel="previous" title="Unreviewed Translations">
<style type="text/css">
<!--
@@ -65,11 +65,11 @@
<a name="Commits"></a>
<div class="header">
<p>
-Next: <a href="Savannah.html#Savannah" accesskey="n" rel="next">Savannah</a>,
Previous: <a href="Review.html#Review" accesskey="p" rel="previous">Review</a>,
Up: <a href="Managing.html#Managing" accesskey="u" rel="up">Managing</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
+Next: <a href="PO-Files.html#PO-Files" accesskey="n" rel="next">PO Files</a>,
Previous: <a href="Review.html#Review" accesskey="p" rel="previous">Review</a>,
Up: <a href="Managing.html#Managing" accesskey="u" rel="up">Managing</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="CVS-Commits-And-Best-Practices"></a>
-<h4 class="subsection">3.2.2 CVS Commits And Best Practices</h4>
+<a name="CVS-Commits-and-Best-Practices"></a>
+<h4 class="subsection">3.2.2 CVS Commits and Best Practices</h4>
<p>As all team leaders have write access to the CVS repository of the
‘<samp>www</samp>’ project, this technically means that they are
able to modify
@@ -89,8 +89,8 @@
For general issues that affect more articles, or for severe problems,
please write to <a href="mailto:address@hidden";>address@hidden</a>.
</p>
-<p>It is recommended to read the entire CVS manual at least once, for a
-basic understanding of how this VCS works. See <a
href="../cvs/index.html#Top">Concurrent
+<p>If you are not familiar with CVS, it is recommended to read CVS manual,
+for a basic understanding of how this VCS works. See <a
href="../cvs/index.html#Top">Concurrent
Versions System</a> in <cite>Version Management with CVS</cite>. It is not
necessary to become an expert—the ‘<samp>www</samp>’ project
does not use
complex features like tags, vendor branches, merging, etc. as they are
@@ -109,7 +109,7 @@
description of the change. If you modify a file that is not an article
but a script or part of software (such as <samp>server/gnun/gnun.mk</samp>),
it would be nice to follow the GNU Coding Standards and describe the
-change precisely. See <a
href="http://www.gnu.org/prep/standards/html_node/Change-Logs.html#Change-Logs";>Change
Logs</a> in <cite>The GNU Coding Standards</cite>. For example, do not write:
+change precisely (see <a
href="http://www.gnu.org/prep/standards/html_node/Change-Logs.html#Change-Logs";>Change
Logs</a> in <cite>The GNU Coding Standards</cite>). For example, do not write:
</p>
<div class="example">
<pre class="example">Added support for Nepali.
@@ -169,7 +169,7 @@
<hr>
<div class="header">
<p>
-Next: <a href="Savannah.html#Savannah" accesskey="n" rel="next">Savannah</a>,
Previous: <a href="Review.html#Review" accesskey="p" rel="previous">Review</a>,
Up: <a href="Managing.html#Managing" accesskey="u" rel="up">Managing</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
+Next: <a href="PO-Files.html#PO-Files" accesskey="n" rel="next">PO Files</a>,
Previous: <a href="Review.html#Review" accesskey="p" rel="previous">Review</a>,
Up: <a href="Managing.html#Managing" accesskey="u" rel="up">Managing</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
Index: web-trans/html_node/Copying-This-Manual.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Copying-This-Manual.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Copying-This-Manual.html 4 Dec 2012 16:24:26
-0000 1.9
+++ web-trans/html_node/Copying-This-Manual.html 27 Dec 2012 14:45:39
-0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Copying This Manual</title>
Index: web-trans/html_node/Distribution-Terms.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Distribution-Terms.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- web-trans/html_node/Distribution-Terms.html 4 Dec 2012 16:24:26 -0000
1.5
+++ web-trans/html_node/Distribution-Terms.html 27 Dec 2012 14:45:39 -0000
1.6
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Distribution Terms</title>
@@ -113,13 +113,14 @@
Dutch language deed. We should always link to a copy of the license
deed that’s in the same language as the page itself.
</p>
-<p>Pages in languages that aren’t supported by CC should prepare their
own
-translation, use it consistently throughout pages translated to that
-language, and link to the English language deed. Also, please
-write your own translation when the translation provided by CC is
-not satisfactory for some reasons—for instance, as of May, 2012, their
-German translation uses “Content”, which is a word to use with
caution
-(see <a
href="http://www.gnu.org/philosophy/words-to-avoid.en.html#Content";>http://www.gnu.org/philosophy/words-to-avoid.en.html#Content</a>).
+<p>Pages in languages that aren’t supported by CC should prepare their
+own translation, use it consistently throughout pages translated to
+that language, and link to the English language deed. Also, please
+write your own translation when the translation provided by CC is not
+satisfactory for some reasons—for instance, as of May, 2012, their
+German translation uses “Content”, which is a word to use with
+caution (see
+<a
href="http://www.gnu.org/philosophy/words-to-avoid.en.html#Content";>http://www.gnu.org/philosophy/words-to-avoid.en.html#Content</a>).
</p>
<p>Note that translations should <em>not</em> change the jurisdiction of the
license; they should <em>always</em> link to the CC BY-ND 3.0 <em>United
Index: web-trans/html_node/Introduction.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Introduction.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Introduction.html 4 Dec 2012 16:24:26 -0000
1.9
+++ web-trans/html_node/Introduction.html 27 Dec 2012 14:45:39 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Introduction</title>
@@ -104,13 +104,12 @@
describe the fundamental values of the free software movement.
</p>
<p>Translators of the <a href="http://gnu.org";>http://gnu.org</a> website are
organized in
-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</samp>’ organizational project,
which is managed
-by the GNU Web Translation Managers. The manual is organized in
-chapters that follow the organizational structure of the whole
-translation project.
+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</samp>’
+organizational project, which is managed by the GNU Web Translation
+Managers. The manual is organized in chapters that follow the
+organizational structure of the whole translation project.
</p>
<p>If you wish to join a translation team or contribute a translation or
two, see <a href="Members.html#Members">Members</a>. If your intention is to
form a translation team,
Index: web-trans/html_node/Joining.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/Joining.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Joining.html 4 Dec 2012 16:24:26 -0000 1.9
+++ web-trans/html_node/Joining.html 27 Dec 2012 14:45:39 -0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Joining</title>
@@ -68,8 +68,8 @@
Next: <a href="Submitting.html#Submitting" accesskey="n"
rel="next">Submitting</a>, Up: <a href="Members.html#Members" accesskey="u"
rel="up">Members</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="Joining-A-Team"></a>
-<h3 class="section">2.1 Joining A Team</h3>
+<a name="Joining-a-Team"></a>
+<h3 class="section">2.1 Joining a Team</h3>
<p>To join a team, please first look at the existing teams at
<a
href="http://www.gnu.org/server/standards/README.translations.html#TranslationsUnderway";>http://www.gnu.org/server/standards/README.translations.html#TranslationsUnderway</a>.
Index: web-trans/html_node/Leaders.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/Leaders.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Leaders.html 4 Dec 2012 16:24:26 -0000 1.9
+++ web-trans/html_node/Leaders.html 27 Dec 2012 14:45:39 -0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Leaders</title>
@@ -28,7 +28,7 @@
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="index.html#Top" rel="up" title="Top">
<link href="New-Team.html#New-Team" rel="next" title="New Team">
-<link href="Leaving-A-Team.html#Leaving-A-Team" rel="previous" title="Leaving
A Team">
+<link href="Leaving-a-Team.html#Leaving-a-Team" rel="previous" title="Leaving
a Team">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
Index: web-trans/html_node/Mailing-Lists.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Mailing-Lists.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Mailing-Lists.html 4 Dec 2012 16:24:26 -0000
1.9
+++ web-trans/html_node/Mailing-Lists.html 27 Dec 2012 14:45:40 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Mailing Lists</title>
Index: web-trans/html_node/Managing.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Managing.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Managing.html 4 Dec 2012 16:24:26 -0000 1.9
+++ web-trans/html_node/Managing.html 27 Dec 2012 14:45:40 -0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Managing</title>
@@ -68,8 +68,8 @@
Next: <a href="Reports.html#Reports" accesskey="n" rel="next">Reports</a>,
Previous: <a href="New-Team.html#New-Team" accesskey="p" rel="previous">New
Team</a>, Up: <a href="Leaders.html#Leaders" accesskey="u" rel="up">Leaders</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="The-Gentle-Art-of-Managing-A-Translation-Team"></a>
-<h3 class="section">3.2 The Gentle Art of Managing A Translation Team</h3>
+<a name="The-Gentle-Art-of-Managing-a-Translation-Team"></a>
+<h3 class="section">3.2 The Gentle Art of Managing a Translation Team</h3>
<p>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
@@ -95,9 +95,11 @@
</td></tr>
<tr><td align="left" valign="top">• <a href="Commits.html#Commits"
accesskey="2">Commits</a>:</td><td> </td><td align="left"
valign="top">What to modify, and how.
</td></tr>
-<tr><td align="left" valign="top">• <a href="Savannah.html#Savannah"
accesskey="3">Savannah</a>:</td><td> </td><td align="left"
valign="top">Using Savannah resources.
+<tr><td align="left" valign="top">• <a href="PO-Files.html#PO-Files"
accesskey="3">PO Files</a>:</td><td> </td><td align="left"
valign="top">Tools to edit translations.
</td></tr>
-<tr><td align="left" valign="top">• <a
href="Co_002dleaders.html#Co_002dleaders"
accesskey="4">Co-leaders</a>:</td><td> </td><td align="left"
valign="top">Promoting co-leaders, when necessary.
+<tr><td align="left" valign="top">• <a href="Savannah.html#Savannah"
accesskey="4">Savannah</a>:</td><td> </td><td align="left"
valign="top">Using Savannah resources.
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Co_002dleaders.html#Co_002dleaders"
accesskey="5">Co-leaders</a>:</td><td> </td><td align="left"
valign="top">Promoting co-leaders, when necessary.
</td></tr>
</table>
Index: web-trans/html_node/Members.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/Members.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Members.html 4 Dec 2012 16:24:26 -0000 1.9
+++ web-trans/html_node/Members.html 27 Dec 2012 14:45:40 -0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Members</title>
@@ -82,7 +82,7 @@
</td></tr>
<tr><td align="left" valign="top">• <a href="Submitting.html#Submitting"
accesskey="2">Submitting</a>:</td><td> </td><td align="left"
valign="top">Submitting a translation when there is no team.
</td></tr>
-<tr><td align="left" valign="top">• <a
href="Leaving-A-Team.html#Leaving-A-Team" accesskey="3">Leaving A
Team</a>:</td><td> </td><td align="left" valign="top">Leave when you
have to.
+<tr><td align="left" valign="top">• <a
href="Leaving-a-Team.html#Leaving-a-Team" accesskey="3">Leaving a
Team</a>:</td><td> </td><td align="left" valign="top">Leave when you
have to.
</td></tr>
</table>
Index: web-trans/html_node/Migrating.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Migrating.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Migrating.html 4 Dec 2012 16:24:27 -0000 1.9
+++ web-trans/html_node/Migrating.html 27 Dec 2012 14:45:40 -0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Migrating</title>
@@ -68,8 +68,8 @@
Next: <a href="SSI.html#SSI" accesskey="n" rel="next">SSI</a>, Up: <a
href="Translation-Tips.html#Translation-Tips" accesskey="u"
rel="up">Translation Tips</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="Migration-To-The-New-Style"></a>
-<h3 class="section">5.1 Migration To The New Style</h3>
+<a name="Migration-to-the-New-Style"></a>
+<h3 class="section">5.1 Migration to the New Style</h3>
<p>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
Index: web-trans/html_node/New-Team.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/New-Team.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- web-trans/html_node/New-Team.html 4 Dec 2012 16:24:27 -0000 1.10
+++ web-trans/html_node/New-Team.html 27 Dec 2012 14:45:40 -0000 1.11
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: New Team</title>
@@ -68,8 +68,8 @@
Next: <a href="Managing.html#Managing" accesskey="n" rel="next">Managing</a>,
Up: <a href="Leaders.html#Leaders" accesskey="u" rel="up">Leaders</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="How-To-Form-A-New-Team"></a>
-<h3 class="section">3.1 How To Form A New Team</h3>
+<a name="How-to-Form-a-New-Team"></a>
+<h3 class="section">3.1 How to Form a New Team</h3>
<p>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
@@ -79,9 +79,7 @@
</p>
<p>You should read <em>all</em> the documentation related to the
translation process and at the very least all important
-philosophy-related articles listed on
-<a
href="http://gnu.org/server/standards/README.translations.html";>http://gnu.org/server/standards/README.translations.html</a>
-and
+philosophy-related articles listed at
<a
href="http://gnu.org/server/standards/translations/priorities.html";>http://gnu.org/server/standards/translations/priorities.html</a>
before you decide to form a new team, or take over an orphaned team.
Once you have the internal feeling that having a gnu.org translation
@@ -124,20 +122,29 @@
co-ordinator to have a good understanding of the philosophy of the free
software movement.
-</li><li> Check if your language code is
-present in the variable <code>TEMPLATE_LINGUAS</code> at
-<samp>server/gnun/gnun.mk</samp>. If it is not, the first thing to do is to
-translate and submit to <a href="mailto:address@hidden";>address@hidden</a> the
following
-files (all in the <samp>server/po/</samp> directory):
-<samp>head-include-2.<var>lang</var>.po</samp>,
-<samp>body-include-1.<var>lang</var>.po</samp>,
-<samp>body-include-2.<var>lang</var>.po</samp>
-<samp>footer-text.<var>lang</var>.po</samp>,
-<samp>outdated.<var>lang</var>.po</samp>,
-<samp>skip-translations.<var>lang</var>.po</samp>,
-and <samp>top-addendum.<var>lang</var>.po</samp>.
-See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/New-Translation.html#New-Translation";>New
Translation</a> in <cite>The GNUnited Nations Manual</cite>.
+</li><li> Check if your language code is present in the variable
+<code>TEMPLATE_LINGUAS</code> in the file <samp>server/gnun/gnun.mk</samp>.
If it
+is not, the first thing to do is to translate and submit to
+<a href="mailto:address@hidden";>address@hidden</a> the following files (all in
the
+<samp>server/po/</samp> directory):
+<ul>
+<li> <samp>head-include-2.<var>lang</var>.po</samp>
+</li><li> <samp>body-include-1.<var>lang</var>.po</samp>
+
+</li><li> <samp>body-include-2.<var>lang</var>.po</samp>
+
+</li><li> <samp>footer-text.<var>lang</var>.po</samp>
+
+</li><li> <samp>outdated.<var>lang</var>.po</samp>
+
+</li><li> <samp>skip-translations.<var>lang</var>.po</samp>
+
+</li><li> <samp>top-addendum.<var>lang</var>.po</samp>
+</li></ul>
+
+<p>See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/New-Translation.html#New-Translation";>New
Translation</a> in <cite>The GNUnited Nations Manual</cite>.
+</p>
<ul class="no-bullet">
<li>- The language code (<var>lang</var>) should be the ISO 639-1 code of the
language, for example ‘<samp>hy</samp>’ for Armenian or
‘<samp>el</samp>’ for Greek. If
@@ -147,11 +154,6 @@
</li><li>- The PO file header and initial comments should be completed as
documented.
-
-</li><li>- 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;</samp>’ and this is a character from the
alphabet of your
-language, just write it as ‘<samp>ü</samp>’ directly.
</li></ul>
</li><li> Any prospective team leader should submit a few translations first.
Index: web-trans/html_node/Priorities.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Priorities.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Priorities.html 4 Dec 2012 16:24:27 -0000 1.9
+++ web-trans/html_node/Priorities.html 27 Dec 2012 14:45:40 -0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Priorities</title>
@@ -68,8 +68,8 @@
Next: <a href="Capitalization.html#Capitalization" accesskey="n"
rel="next">Capitalization</a>, Previous: <a href="CSS.html#CSS" accesskey="p"
rel="previous">CSS</a>, Up: <a href="Translation-Tips.html#Translation-Tips"
accesskey="u" rel="up">Translation Tips</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="What-To-Translate"></a>
-<h3 class="section">5.4 What To Translate</h3>
+<a name="What-to-Translate"></a>
+<h3 class="section">5.4 What to Translate</h3>
<p>The article
<a
href="http://www.gnu.org/server/standards/translations/priorities.html";>http://www.gnu.org/server/standards/translations/priorities.html</a>
@@ -85,12 +85,14 @@
<p>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. GNUN’s <code>report</code> rule can help you
to
-identify precisely which articles need updating; see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/report.html#report";>report</a>
in <cite>The GNUnited Nations Manual</cite>. There is a monthly cronjob which
-sends a verbose output to each team—by default, the address(es) used
-is the Savannah account(s) of the admin(s) of the specific translation
-project. If you want them changed, please write to
+identify precisely which articles need updating; see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/report.html#report";>report</a>
in <cite>The GNUnited Nations Manual</cite>. There is a monthly cron job which
+sends a verbose output to each team as requested by their leaders.
+If you want the addresses changed, please write to
<a href="mailto:address@hidden";>address@hidden</a>.
</p>
+<p>More detailed notifications can be arranged through
+<samp>GNUmakefile.team</samp> (see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/PO-Files-and-Team.html#PO-Files-and-Team";>PO
Files and Team</a> in <cite>The GNUnited Nations Manual</cite>).
+</p>
<p>GNUN also maintains reports about current status of translations of all
active teams in <a
href="http://www.gnu.org/software/gnun/reports/";>http://www.gnu.org/software/gnun/reports/</a>.
If
the page for your team is missing there, please ask
Index: web-trans/html_node/RTL.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/RTL.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/RTL.html 4 Dec 2012 16:24:27 -0000 1.9
+++ web-trans/html_node/RTL.html 27 Dec 2012 14:45:40 -0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: RTL</title>
Index: web-trans/html_node/Reports.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/Reports.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Reports.html 4 Dec 2012 16:24:27 -0000 1.9
+++ web-trans/html_node/Reports.html 27 Dec 2012 14:45:40 -0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Reports</title>
@@ -83,13 +83,13 @@
</li><li>- New members since the last report.
-</li><li>- Current active members.
-
</li><li>- Solved problems and other issues, if any. (Usual bug reports and
other
improvements/fixes to the existing translations do not count as
<em>problems</em> in this sense.)
</li></ul>
+</li><li> Current active members.
+
</li><li> Current problems (technical or social), conflicts, and ideas for
sorting
them out.
Index: web-trans/html_node/Review.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/Review.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Review.html 4 Dec 2012 16:24:27 -0000 1.9
+++ web-trans/html_node/Review.html 27 Dec 2012 14:45:40 -0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Review</title>
Index: web-trans/html_node/SSI.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/SSI.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/SSI.html 4 Dec 2012 16:24:27 -0000 1.9
+++ web-trans/html_node/SSI.html 27 Dec 2012 14:45:40 -0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: SSI</title>
Index: web-trans/html_node/Savannah-Bugs.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Bugs.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Savannah-Bugs.html 4 Dec 2012 16:24:27 -0000
1.9
+++ web-trans/html_node/Savannah-Bugs.html 27 Dec 2012 14:45:40 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Savannah Bugs</title>
@@ -27,7 +27,7 @@
<link href="index.html#Top" rel="start" title="Top">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Savannah.html#Savannah" rel="up" title="Savannah">
-<link href="Savannah-Patch.html#Savannah-Patch" rel="next" title="Savannah
Patch">
+<link href="Savannah-News.html#Savannah-News" rel="next" title="Savannah News">
<link href="Savannah-Tasks.html#Savannah-Tasks" rel="previous" title="Savannah
Tasks">
<style type="text/css">
<!--
@@ -65,11 +65,11 @@
<a name="Savannah-Bugs"></a>
<div class="header">
<p>
-Next: <a href="Savannah-Patch.html#Savannah-Patch" accesskey="n"
rel="next">Savannah Patch</a>, Previous: <a
href="Savannah-Tasks.html#Savannah-Tasks" accesskey="p" rel="previous">Savannah
Tasks</a>, Up: <a href="Savannah.html#Savannah" accesskey="u"
rel="up">Savannah</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
+Next: <a href="Savannah-News.html#Savannah-News" accesskey="n"
rel="next">Savannah News</a>, Previous: <a
href="Savannah-Tasks.html#Savannah-Tasks" accesskey="p" rel="previous">Savannah
Tasks</a>, Up: <a href="Savannah.html#Savannah" accesskey="u"
rel="up">Savannah</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
<hr>
<a name="Bugs-Tracker"></a>
-<h4 class="subsubsection">3.2.3.5 Bugs Tracker</h4>
+<h4 class="subsubsection">3.2.4.5 Bugs Tracker</h4>
<p>The ‘<samp>Bugs</samp>’ tracker is designed for tracking bugs.
You can use for
several purposes:
Index: web-trans/html_node/Savannah-Homepage.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Homepage.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Savannah-Homepage.html 4 Dec 2012 16:24:27 -0000
1.9
+++ web-trans/html_node/Savannah-Homepage.html 27 Dec 2012 14:45:40 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Savannah Homepage</title>
@@ -68,8 +68,8 @@
Next: <a href="Savannah-Support.html#Savannah-Support" accesskey="n"
rel="next">Savannah Support</a>, Previous: <a
href="Savannah-Members.html#Savannah-Members" accesskey="p"
rel="previous">Savannah Members</a>, Up: <a href="Savannah.html#Savannah"
accesskey="u" rel="up">Savannah</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="Homepage-of-The-Team"></a>
-<h4 class="subsubsection">3.2.3.2 Homepage of The Team</h4>
+<a name="Homepage-of-the-Team"></a>
+<h4 class="subsubsection">3.2.4.2 Homepage of the Team</h4>
<p>Every Savannah project has a Web repository, which is, for technical and
historical reasons, only CVS. By default it is mapped to
Index: web-trans/html_node/Savannah-Mailing-Lists.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Mailing-Lists.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Savannah-Mailing-Lists.html 4 Dec 2012 16:24:27
-0000 1.9
+++ web-trans/html_node/Savannah-Mailing-Lists.html 27 Dec 2012 14:45:40
-0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Savannah Mailing Lists</title>
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="Managing-Mailing-Lists"></a>
-<h4 class="subsubsection">3.2.3.8 Managing Mailing Lists</h4>
+<h4 class="subsubsection">3.2.4.7 Managing Mailing Lists</h4>
<p>Every team should have a mailing list on lists.gnu.org and use it for
internal communications. All active translators should be on the
Index: web-trans/html_node/Savannah-Members.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Members.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Savannah-Members.html 4 Dec 2012 16:24:28 -0000
1.9
+++ web-trans/html_node/Savannah-Members.html 27 Dec 2012 14:45:40 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Savannah Members</title>
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="Managing-Members"></a>
-<h4 class="subsubsection">3.2.3.1 Managing Members</h4>
+<h4 class="subsubsection">3.2.4.1 Managing Members</h4>
<p>You should add active translators as members of the translation team,
and remove them when they leave. Team members should have access to all
Index: web-trans/html_node/Savannah-News.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-News.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Savannah-News.html 4 Dec 2012 16:24:28 -0000
1.9
+++ web-trans/html_node/Savannah-News.html 27 Dec 2012 14:45:40 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Savannah News</title>
@@ -28,7 +28,7 @@
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Savannah.html#Savannah" rel="up" title="Savannah">
<link href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists" rel="next"
title="Savannah Mailing Lists">
-<link href="Savannah-Patch.html#Savannah-Patch" rel="previous" title="Savannah
Patch">
+<link href="Savannah-Bugs.html#Savannah-Bugs" rel="previous" title="Savannah
Bugs">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -65,11 +65,11 @@
<a name="Savannah-News"></a>
<div class="header">
<p>
-Next: <a href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists"
accesskey="n" rel="next">Savannah Mailing Lists</a>, Previous: <a
href="Savannah-Patch.html#Savannah-Patch" accesskey="p" rel="previous">Savannah
Patch</a>, Up: <a href="Savannah.html#Savannah" accesskey="u"
rel="up">Savannah</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
+Next: <a href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists"
accesskey="n" rel="next">Savannah Mailing Lists</a>, Previous: <a
href="Savannah-Bugs.html#Savannah-Bugs" accesskey="p" rel="previous">Savannah
Bugs</a>, Up: <a href="Savannah.html#Savannah" accesskey="u"
rel="up">Savannah</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
<hr>
<a name="News-Tracker"></a>
-<h4 class="subsubsection">3.2.3.7 News Tracker</h4>
+<h4 class="subsubsection">3.2.4.6 News Tracker</h4>
<p>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</samp>’ RSS
Index: web-trans/html_node/Savannah-Projects.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Projects.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Savannah-Projects.html 4 Dec 2012 16:24:28 -0000
1.9
+++ web-trans/html_node/Savannah-Projects.html 27 Dec 2012 14:45:41 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Savannah Projects</title>
@@ -78,13 +78,13 @@
<dt>‘<samp>www</samp>’</dt>
<dd><p>The main project which hosts the ‘<samp>gnu.org</samp>’ Web
repository.
Administrators are the Chief Webmaster, entrusted webmasters and the
-Translation Manager (in order to approve leader’s applications). All
+Translation Manager (in order to approve leaders’ applications). All
team leaders (and co-leaders) should be members of this project.
</p>
<p>Note that this project has no direct relationship with translators,
-although anything happening in ‘<samp>www</samp>’ directly affects
them. The
-‘<samp>www</samp>’ project is managed separately and has a
different (entirely
-unrelated) process for approving contributors.
+although almost anything happening in ‘<samp>www</samp>’ directly
affects
+them. The ‘<samp>www</samp>’ project is managed separately and has
+a different (entirely unrelated) process for approving contributors.
</p>
</dd>
<dt>‘<samp>trans-coord</samp>’</dt>
@@ -98,8 +98,9 @@
</dd>
<dt>‘<samp>www-<var>lang</var></samp>’</dt>
<dd><p>All translation team leaders of the language <var>lang</var> should be
-members of the project ‘<samp>www-<var>lang</var></samp>’. The
admins of the project
-are the team leader and the co-leaders, if any.
+admins of the project ‘<samp>www-<var>lang</var></samp>’. The
leaders may
+also appoint some other members as
‘<samp>www-<var>lang</var></samp>’ admins
+for team’s internal reasons.
</p></dd>
</dl>
Index: web-trans/html_node/Savannah-Support.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Support.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Savannah-Support.html 4 Dec 2012 16:24:28 -0000
1.9
+++ web-trans/html_node/Savannah-Support.html 27 Dec 2012 14:45:41 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Savannah Support</title>
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="Support-Tracker"></a>
-<h4 class="subsubsection">3.2.3.3 Support Tracker</h4>
+<h4 class="subsubsection">3.2.4.3 Support Tracker</h4>
<p>This tracker is supposed to be related to things about the <em>project
management</em> itself, i.e. project members may report here missing
Index: web-trans/html_node/Savannah-Tasks.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Tasks.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Savannah-Tasks.html 4 Dec 2012 16:24:28 -0000
1.9
+++ web-trans/html_node/Savannah-Tasks.html 27 Dec 2012 14:45:41 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Savannah Tasks</title>
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="Tasks-Tracker"></a>
-<h4 class="subsubsection">3.2.3.4 Tasks Tracker</h4>
+<h4 class="subsubsection">3.2.4.4 Tasks Tracker</h4>
<p>This is a way to manage all sorts of tasks. They appear in the personal
Savannah page of the assignee, so it is difficult to miss them out. It
Index: web-trans/html_node/Savannah-VCS.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-VCS.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Savannah-VCS.html 4 Dec 2012 16:24:28 -0000
1.9
+++ web-trans/html_node/Savannah-VCS.html 27 Dec 2012 14:45:41 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Savannah VCS</title>
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="Version-Control-Systems"></a>
-<h4 class="subsubsection">3.2.3.9 Version Control Systems</h4>
+<h4 class="subsubsection">3.2.4.8 Version Control Systems</h4>
<p>An easy way to keep up with changes in the original articles and to
manage continuous contributions is to keep all translations in the
@@ -87,43 +87,6 @@
collaborative maintenance—if it eases only you, project members just
won’t use it so that won’t be a net win.
</p>
-<a name="Web_002dbased-Systems"></a>
-<h4 class="subsubheading">Web-based Systems</h4>
-
-<p>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 <samp>.po</samp> 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
-(<a
href="http://translations.launchpad.net";>http://translations.launchpad.net</a>).
-</p>
-<p>Here is a short and probably incomplete list of such systems:
-</p>
-<ul>
-<li> Pootle—<a
href="http://translate.sourceforge.net/wiki/pootle";>http://translate.sourceforge.net/wiki/pootle</a>
-
-</li><li> Vertaal—<a
href="http://code.google.com/p/vertaal";>http://code.google.com/p/vertaal</a>
-
-</li><li> Narro—<a
href="http://code.google.com/p/narro";>http://code.google.com/p/narro</a>
-
-</li><li> Launchpad—<a
href="https://dev.launchpad.net";>https://dev.launchpad.net</a>
-
-</li></ul>
-
-<p>If you decide to use such a system, please make sure that no
-translations are published in HTML format there.
-</p>
-<p>Note that to keep the <samp>.pot</samp> files regularly updated (assuming
such
-a web-based system runs <code>msgmerge</code> automatically), you’ll have
-to take care of the one-way regular sync from the
‘<samp>www</samp>’ CVS
-repository.
-</p>
-<hr>
-<div class="header">
-<p>
-Previous: <a href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists"
accesskey="p" rel="previous">Savannah Mailing Lists</a>, Up: <a
href="Savannah.html#Savannah" accesskey="u" rel="up">Savannah</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
-</div>
Index: web-trans/html_node/Savannah.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Savannah.html 4 Dec 2012 16:24:28 -0000 1.9
+++ web-trans/html_node/Savannah.html 27 Dec 2012 14:45:41 -0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Savannah</title>
@@ -28,7 +28,7 @@
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Managing.html#Managing" rel="up" title="Managing">
<link href="Savannah-Members.html#Savannah-Members" rel="next" title="Savannah
Members">
-<link href="Commits.html#Commits" rel="previous" title="Commits">
+<link href="PO-Files.html#PO-Files" rel="previous" title="PO Files">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -65,14 +65,14 @@
<a name="Savannah"></a>
<div class="header">
<p>
-Next: <a href="Co_002dleaders.html#Co_002dleaders" accesskey="n"
rel="next">Co-leaders</a>, Previous: <a href="Commits.html#Commits"
accesskey="p" rel="previous">Commits</a>, Up: <a href="Managing.html#Managing"
accesskey="u" rel="up">Managing</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
+Next: <a href="Co_002dleaders.html#Co_002dleaders" accesskey="n"
rel="next">Co-leaders</a>, Previous: <a href="PO-Files.html#PO-Files"
accesskey="p" rel="previous">PO Files</a>, Up: <a href="Managing.html#Managing"
accesskey="u" rel="up">Managing</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<hr>
<a name="Taking-Advantage-of-Savannah"></a>
-<h4 class="subsection">3.2.3 Taking Advantage of Savannah</h4>
+<h4 class="subsection">3.2.4 Taking Advantage of Savannah</h4>
<p>Every translation team should have a project in Savannah. There are
-some teams that use their own resources outside from Savannah; although
+some teams that use their own resources outside Savannah; although
there’s no obligation to use Savannah for team work, the need for a
Savannah project for each language is obvious: it’s a standard way to
find information for translation teams and their contacts.
@@ -124,20 +124,18 @@
</td></tr>
<tr><td align="left" valign="top">• <a
href="Savannah-Bugs.html#Savannah-Bugs" accesskey="5">Savannah
Bugs</a>:</td><td> </td><td align="left" valign="top">
</td></tr>
-<tr><td align="left" valign="top">• <a
href="Savannah-Patch.html#Savannah-Patch" accesskey="6">Savannah
Patch</a>:</td><td> </td><td align="left" valign="top">
+<tr><td align="left" valign="top">• <a
href="Savannah-News.html#Savannah-News" accesskey="6">Savannah
News</a>:</td><td> </td><td align="left" valign="top">
</td></tr>
-<tr><td align="left" valign="top">• <a
href="Savannah-News.html#Savannah-News" accesskey="7">Savannah
News</a>:</td><td> </td><td align="left" valign="top">
+<tr><td align="left" valign="top">• <a
href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists"
accesskey="7">Savannah Mailing Lists</a>:</td><td> </td><td
align="left" valign="top">
</td></tr>
-<tr><td align="left" valign="top">• <a
href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists"
accesskey="8">Savannah Mailing Lists</a>:</td><td> </td><td
align="left" valign="top">
-</td></tr>
-<tr><td align="left" valign="top">• <a
href="Savannah-VCS.html#Savannah-VCS" accesskey="9">Savannah
VCS</a>:</td><td> </td><td align="left" valign="top">
+<tr><td align="left" valign="top">• <a
href="Savannah-VCS.html#Savannah-VCS" accesskey="8">Savannah
VCS</a>:</td><td> </td><td align="left" valign="top">
</td></tr>
</table>
<hr>
<div class="header">
<p>
-Next: <a href="Co_002dleaders.html#Co_002dleaders" accesskey="n"
rel="next">Co-leaders</a>, Previous: <a href="Commits.html#Commits"
accesskey="p" rel="previous">Commits</a>, Up: <a href="Managing.html#Managing"
accesskey="u" rel="up">Managing</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
+Next: <a href="Co_002dleaders.html#Co_002dleaders" accesskey="n"
rel="next">Co-leaders</a>, Previous: <a href="PO-Files.html#PO-Files"
accesskey="p" rel="previous">PO Files</a>, Up: <a href="Managing.html#Managing"
accesskey="u" rel="up">Managing</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
Index: web-trans/html_node/Stepping-Down.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Stepping-Down.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Stepping-Down.html 4 Dec 2012 16:24:28 -0000
1.9
+++ web-trans/html_node/Stepping-Down.html 27 Dec 2012 14:45:41 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Stepping Down</title>
@@ -68,8 +68,8 @@
Previous: <a href="Reports.html#Reports" accesskey="p"
rel="previous">Reports</a>, Up: <a href="Leaders.html#Leaders" accesskey="u"
rel="up">Leaders</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="How-To-Retire-Painlessly"></a>
-<h3 class="section">3.4 How To Retire Painlessly</h3>
+<a name="How-to-Retire-Painlessly"></a>
+<h3 class="section">3.4 How to Retire Painlessly</h3>
<p>When you feel you don’t have the energy to manage the team
successfully,
or perhaps you start losing motivation, please inform
Index: web-trans/html_node/Submitting-as-PO.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Submitting-as-PO.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Submitting-as-PO.html 4 Dec 2012 16:24:28 -0000
1.9
+++ web-trans/html_node/Submitting-as-PO.html 27 Dec 2012 14:45:41 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Submitting as PO</title>
@@ -68,8 +68,8 @@
Next: <a href="Submitting-as-Plain-Text.html#Submitting-as-Plain-Text"
accesskey="n" rel="next">Submitting as Plain Text</a>, Up: <a
href="Submitting.html#Submitting" accesskey="u" rel="up">Submitting</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="How-To-Submit-a-Translation-in-PO-Format"></a>
-<h4 class="subsection">2.2.1 How To Submit a Translation in PO Format</h4>
+<a name="How-to-Submit-a-Translation-in-PO-Format"></a>
+<h4 class="subsection">2.2.1 How to Submit a Translation in PO Format</h4>
<p>All translations<a name="DOCF1" href="#FOOT1"><sup>1</sup></a> are
maintained via GNUN (see
<a
href="http://www.gnu.org/software/gnun/";>http://www.gnu.org/software/gnun/</a>),
which significantly eases
@@ -102,7 +102,7 @@
the URL for the template file of
<a
href="http://www.gnu.org/philosophy/free-sw.html";>http://www.gnu.org/philosophy/free-sw.html</a>
is
<a
href="http://www.gnu.org/philosophy/po/free-sw.pot";>http://www.gnu.org/philosophy/po/free-sw.pot</a>;
the URL for
-its <var>lang</var> PO file (when available) is
+its <var>lang</var> PO file (when available) is always
<a
href="http://www.gnu.org/philosophy/po/free-sw.lang.po";>http://www.gnu.org/philosophy/po/free-sw.lang.po</a>:
</p>
<div class="example">
@@ -112,7 +112,7 @@
</li><li> Assuming you already know the article you want to translate, you
have to
create an empty <samp><var>article</var>.<var>lang</var>.po</samp> file and
then
translate all messages with a PO editor. See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/New-Translation.html#New-Translation";>New
Translation</a> in <cite>The GNUnited Nations Manual</cite>. For an almost
complete list of PO
-editors, see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/PO-Files.html#PO-Files";>PO
Files</a> in <cite>The GNUnited Nations Manual</cite>.
+editors, see <a href="PO-Files.html#PO-Files">PO Files</a>.
</li><li> When you are pleased with the translation, check that the PO file is
valid and submit it to <a href="mailto:address@hidden";>address@hidden</a>,
attached to
Index: web-trans/html_node/Submitting-as-Plain-Text.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Submitting-as-Plain-Text.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Submitting-as-Plain-Text.html 4 Dec 2012 16:24:28
-0000 1.9
+++ web-trans/html_node/Submitting-as-Plain-Text.html 27 Dec 2012 14:45:41
-0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Submitting as Plain Text</title>
@@ -27,7 +27,7 @@
<link href="index.html#Top" rel="start" title="Top">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Submitting.html#Submitting" rel="up" title="Submitting">
-<link href="Leaving-A-Team.html#Leaving-A-Team" rel="next" title="Leaving A
Team">
+<link href="Leaving-a-Team.html#Leaving-a-Team" rel="next" title="Leaving a
Team">
<link href="Submitting-as-PO.html#Submitting-as-PO" rel="previous"
title="Submitting as PO">
<style type="text/css">
<!--
@@ -68,8 +68,8 @@
Previous: <a href="Submitting-as-PO.html#Submitting-as-PO" accesskey="p"
rel="previous">Submitting as PO</a>, Up: <a href="Submitting.html#Submitting"
accesskey="u" rel="up">Submitting</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="How-To-Submit-a-Translation-as-Plain-Text"></a>
-<h4 class="subsection">2.2.2 How To Submit a Translation as Plain Text</h4>
+<a name="How-to-Submit-a-Translation-as-Plain-Text"></a>
+<h4 class="subsection">2.2.2 How to Submit a Translation as Plain Text</h4>
<p>If you feel the procedure described in the previous section is too
burdensome and unfeasible for you to follow, you can still submit a
Index: web-trans/html_node/Submitting.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Submitting.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Submitting.html 4 Dec 2012 16:24:28 -0000 1.9
+++ web-trans/html_node/Submitting.html 27 Dec 2012 14:45:41 -0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Submitting</title>
@@ -65,11 +65,11 @@
<a name="Submitting"></a>
<div class="header">
<p>
-Next: <a href="Leaving-A-Team.html#Leaving-A-Team" accesskey="n"
rel="next">Leaving A Team</a>, Previous: <a href="Joining.html#Joining"
accesskey="p" rel="previous">Joining</a>, Up: <a href="Members.html#Members"
accesskey="u" rel="up">Members</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
+Next: <a href="Leaving-a-Team.html#Leaving-a-Team" accesskey="n"
rel="next">Leaving a Team</a>, Previous: <a href="Joining.html#Joining"
accesskey="p" rel="previous">Joining</a>, Up: <a href="Members.html#Members"
accesskey="u" rel="up">Members</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="How-To-Submit-a-Translation"></a>
-<h3 class="section">2.2 How To Submit a Translation</h3>
+<a name="How-to-Submit-a-Translation"></a>
+<h3 class="section">2.2 How to Submit a Translation</h3>
<p>Everyone can still submit translations even if there is no translation
team formed. There are two ways to do that—following the existing
Index: web-trans/html_node/Summary.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/Summary.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Summary.html 4 Dec 2012 16:24:28 -0000 1.9
+++ web-trans/html_node/Summary.html 27 Dec 2012 14:45:41 -0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Summary</title>
@@ -68,8 +68,8 @@
Next: <a href="Copying-This-Manual.html#Copying-This-Manual" accesskey="n"
rel="next">Copying This Manual</a>, Previous: <a
href="Translation-Tips.html#Translation-Tips" accesskey="p"
rel="previous">Translation Tips</a>, Up: <a href="index.html#Top" accesskey="u"
rel="up">Top</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="Overview-Of-The-Translation-Process"></a>
-<h2 class="chapter">6 Overview Of The Translation Process</h2>
+<a name="Overview-of-the-Translation-Process"></a>
+<h2 class="chapter">6 Overview of the Translation Process</h2>
<p>In general, it is expected that all participants in the translation
process apply common sense for all of the decisions (important or not)
Index: web-trans/html_node/Terminology.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Terminology.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Terminology.html 4 Dec 2012 16:24:28 -0000
1.9
+++ web-trans/html_node/Terminology.html 27 Dec 2012 14:45:41 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Terminology</title>
Index: web-trans/html_node/Tracking-Tasks.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Tracking-Tasks.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Tracking-Tasks.html 4 Dec 2012 16:24:28 -0000
1.9
+++ web-trans/html_node/Tracking-Tasks.html 27 Dec 2012 14:45:41 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Tracking Tasks</title>
@@ -68,8 +68,8 @@
Next: <a href="Unreviewed-Translations.html#Unreviewed-Translations"
accesskey="n" rel="next">Unreviewed Translations</a>, Up: <a
href="Review.html#Review" accesskey="u" rel="up">Review</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="How-To-Track-Tasks-and-Bugs-Using-Savannah"></a>
-<h4 class="subsubsection">3.2.1.1 How To Track Tasks and Bugs Using
Savannah</h4>
+<a name="How-to-Track-Tasks-and-Bugs-Using-Savannah"></a>
+<h4 class="subsubsection">3.2.1.1 How to Track Tasks and Bugs Using
Savannah</h4>
<p>The team leader has to make sure that prospective translations are
reviewed, that they do not contain obvious errors and/or confusing
Index: web-trans/html_node/Translation-Managers.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Translation-Managers.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Translation-Managers.html 4 Dec 2012 16:24:28
-0000 1.9
+++ web-trans/html_node/Translation-Managers.html 27 Dec 2012 14:45:42
-0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Translation Managers</title>
Index: web-trans/html_node/Translation-Tips.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Translation-Tips.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Translation-Tips.html 4 Dec 2012 16:24:28 -0000
1.9
+++ web-trans/html_node/Translation-Tips.html 27 Dec 2012 14:45:42 -0000
1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Translation Tips</title>
@@ -68,8 +68,8 @@
Next: <a href="Summary.html#Summary" accesskey="n" rel="next">Summary</a>,
Previous: <a href="Translation-Managers.html#Translation-Managers"
accesskey="p" rel="previous">Translation Managers</a>, Up: <a
href="index.html#Top" accesskey="u" rel="up">Top</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="Details-About-The-Translation-Process"></a>
-<h2 class="chapter">5 Details About The Translation Process</h2>
+<a name="Details-about-the-Translation-Process"></a>
+<h2 class="chapter">5 Details about the Translation Process</h2>
<p>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
Index: web-trans/html_node/Unreviewed-Translations.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Unreviewed-Translations.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/Unreviewed-Translations.html 4 Dec 2012 16:24:28
-0000 1.9
+++ web-trans/html_node/Unreviewed-Translations.html 27 Dec 2012 14:45:42
-0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Unreviewed Translations</title>
@@ -68,8 +68,8 @@
Previous: <a href="Tracking-Tasks.html#Tracking-Tasks" accesskey="p"
rel="previous">Tracking Tasks</a>, Up: <a href="Review.html#Review"
accesskey="u" rel="up">Review</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="How-To-Proceed-With-Unreviewed-Translations"></a>
-<h4 class="subsubsection">3.2.1.2 How To Proceed With Unreviewed
Translations</h4>
+<a name="How-to-Proceed-with-Unreviewed-Translations"></a>
+<h4 class="subsubsection">3.2.1.2 How to Proceed with Unreviewed
Translations</h4>
<p>Sometimes a translation (typically your own) is not reviewed by anyone
else for a fairly long time. This is unfortunate, but there is no
Index: web-trans/html_node/index.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/index.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/index.html 4 Dec 2012 16:24:29 -0000 1.9
+++ web-trans/html_node/index.html 27 Dec 2012 14:45:42 -0000 1.10
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: Top</title>
@@ -74,58 +74,61 @@
<li><a name="toc-Introduction-1" href="Introduction.html#Introduction">1
Introduction</a></li>
<li><a name="toc-Team-Members" href="Members.html#Members">2 Team Members</a>
<ul class="no-bullet">
- <li><a name="toc-Joining-A-Team" href="Joining.html#Joining">2.1 Joining A
Team</a></li>
- <li><a name="toc-How-To-Submit-a-Translation"
href="Submitting.html#Submitting">2.2 How To Submit a Translation</a>
+ <li><a name="toc-Joining-a-Team" href="Joining.html#Joining">2.1 Joining a
Team</a></li>
+ <li><a name="toc-How-to-Submit-a-Translation"
href="Submitting.html#Submitting">2.2 How to Submit a Translation</a>
<ul class="no-bullet">
- <li><a name="toc-How-To-Submit-a-Translation-in-PO-Format"
href="Submitting-as-PO.html#Submitting-as-PO">2.2.1 How To Submit a Translation
in PO Format</a></li>
- <li><a name="toc-How-To-Submit-a-Translation-as-Plain-Text"
href="Submitting-as-Plain-Text.html#Submitting-as-Plain-Text">2.2.2 How To
Submit a Translation as Plain Text</a></li>
+ <li><a name="toc-How-to-Submit-a-Translation-in-PO-Format"
href="Submitting-as-PO.html#Submitting-as-PO">2.2.1 How to Submit a Translation
in PO Format</a></li>
+ <li><a name="toc-How-to-Submit-a-Translation-as-Plain-Text"
href="Submitting-as-Plain-Text.html#Submitting-as-Plain-Text">2.2.2 How to
Submit a Translation as Plain Text</a></li>
</ul></li>
- <li><a name="toc-Leaving-A-Team-1"
href="Leaving-A-Team.html#Leaving-A-Team">2.3 Leaving A Team</a></li>
+ <li><a name="toc-Leaving-a-Team-1"
href="Leaving-a-Team.html#Leaving-a-Team">2.3 Leaving a Team</a></li>
</ul></li>
<li><a name="toc-Team-Co_002dordinators" href="Leaders.html#Leaders">3 Team
Co-ordinators</a>
<ul class="no-bullet">
- <li><a name="toc-How-To-Form-A-New-Team" href="New-Team.html#New-Team">3.1
How To Form A New Team</a></li>
- <li><a name="toc-The-Gentle-Art-of-Managing-A-Translation-Team"
href="Managing.html#Managing">3.2 The Gentle Art of Managing A Translation
Team</a>
+ <li><a name="toc-How-to-Form-a-New-Team" href="New-Team.html#New-Team">3.1
How to Form a New Team</a></li>
+ <li><a name="toc-The-Gentle-Art-of-Managing-a-Translation-Team"
href="Managing.html#Managing">3.2 The Gentle Art of Managing a Translation
Team</a>
<ul class="no-bullet">
<li><a name="toc-Peer-Review" href="Review.html#Review">3.2.1 Peer
Review</a>
<ul class="no-bullet">
- <li><a name="toc-How-To-Track-Tasks-and-Bugs-Using-Savannah"
href="Tracking-Tasks.html#Tracking-Tasks">3.2.1.1 How To Track Tasks and Bugs
Using Savannah</a></li>
- <li><a name="toc-How-To-Proceed-With-Unreviewed-Translations"
href="Unreviewed-Translations.html#Unreviewed-Translations">3.2.1.2 How To
Proceed With Unreviewed Translations</a></li>
+ <li><a name="toc-How-to-Track-Tasks-and-Bugs-Using-Savannah"
href="Tracking-Tasks.html#Tracking-Tasks">3.2.1.1 How to Track Tasks and Bugs
Using Savannah</a></li>
+ <li><a name="toc-How-to-Proceed-with-Unreviewed-Translations"
href="Unreviewed-Translations.html#Unreviewed-Translations">3.2.1.2 How to
Proceed with Unreviewed Translations</a></li>
</ul></li>
- <li><a name="toc-CVS-Commits-And-Best-Practices"
href="Commits.html#Commits">3.2.2 CVS Commits And Best Practices</a></li>
- <li><a name="toc-Taking-Advantage-of-Savannah"
href="Savannah.html#Savannah">3.2.3 Taking Advantage of Savannah</a>
+ <li><a name="toc-CVS-Commits-and-Best-Practices"
href="Commits.html#Commits">3.2.2 CVS Commits and Best Practices</a></li>
+ <li><a name="toc-Working-with-PO-Files"
href="PO-Files.html#PO-Files">3.2.3 Working with PO Files</a>
<ul class="no-bullet">
- <li><a name="toc-Managing-Members"
href="Savannah-Members.html#Savannah-Members">3.2.3.1 Managing Members</a></li>
- <li><a name="toc-Homepage-of-The-Team"
href="Savannah-Homepage.html#Savannah-Homepage">3.2.3.2 Homepage of The
Team</a></li>
- <li><a name="toc-Support-Tracker"
href="Savannah-Support.html#Savannah-Support">3.2.3.3 Support Tracker</a></li>
- <li><a name="toc-Tasks-Tracker"
href="Savannah-Tasks.html#Savannah-Tasks">3.2.3.4 Tasks Tracker</a></li>
- <li><a name="toc-Bugs-Tracker"
href="Savannah-Bugs.html#Savannah-Bugs">3.2.3.5 Bugs Tracker</a></li>
- <li><a name="toc-Patch-Tracker"
href="Savannah-Patch.html#Savannah-Patch">3.2.3.6 Patch Tracker</a></li>
- <li><a name="toc-News-Tracker"
href="Savannah-News.html#Savannah-News">3.2.3.7 News Tracker</a></li>
- <li><a name="toc-Managing-Mailing-Lists"
href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists">3.2.3.8 Managing
Mailing Lists</a></li>
- <li><a name="toc-Version-Control-Systems"
href="Savannah-VCS.html#Savannah-VCS">3.2.3.9 Version Control Systems</a></li>
+ <li><a name="toc-Web_002dbased-Systems"
href="PO-Files.html#Web_002dbased-Systems">3.2.3.1 Web-based Systems</a></li>
</ul></li>
- <li><a name="toc-Promoting-Members-As-Co_002dleaders"
href="Co_002dleaders.html#Co_002dleaders">3.2.4 Promoting Members As
Co-leaders</a></li>
+ <li><a name="toc-Taking-Advantage-of-Savannah"
href="Savannah.html#Savannah">3.2.4 Taking Advantage of Savannah</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Managing-Members"
href="Savannah-Members.html#Savannah-Members">3.2.4.1 Managing Members</a></li>
+ <li><a name="toc-Homepage-of-the-Team"
href="Savannah-Homepage.html#Savannah-Homepage">3.2.4.2 Homepage of the
Team</a></li>
+ <li><a name="toc-Support-Tracker"
href="Savannah-Support.html#Savannah-Support">3.2.4.3 Support Tracker</a></li>
+ <li><a name="toc-Tasks-Tracker"
href="Savannah-Tasks.html#Savannah-Tasks">3.2.4.4 Tasks Tracker</a></li>
+ <li><a name="toc-Bugs-Tracker"
href="Savannah-Bugs.html#Savannah-Bugs">3.2.4.5 Bugs Tracker</a></li>
+ <li><a name="toc-News-Tracker"
href="Savannah-News.html#Savannah-News">3.2.4.6 News Tracker</a></li>
+ <li><a name="toc-Managing-Mailing-Lists"
href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists">3.2.4.7 Managing
Mailing Lists</a></li>
+ <li><a name="toc-Version-Control-Systems"
href="Savannah-VCS.html#Savannah-VCS">3.2.4.8 Version Control Systems</a></li>
+ </ul></li>
+ <li><a name="toc-Promoting-Members-as-Co_002dleaders"
href="Co_002dleaders.html#Co_002dleaders">3.2.5 Promoting Members as
Co-leaders</a></li>
</ul></li>
<li><a name="toc-Reporting-Team-Status" href="Reports.html#Reports">3.3
Reporting Team Status</a></li>
- <li><a name="toc-How-To-Retire-Painlessly"
href="Stepping-Down.html#Stepping-Down">3.4 How To Retire Painlessly</a></li>
+ <li><a name="toc-How-to-Retire-Painlessly"
href="Stepping-Down.html#Stepping-Down">3.4 How to Retire Painlessly</a></li>
</ul></li>
<li><a name="toc-trans_002dcoord-Admins"
href="Translation-Managers.html#Translation-Managers">4
‘<samp>trans-coord</samp>’ Admins</a></li>
- <li><a name="toc-Details-About-The-Translation-Process"
href="Translation-Tips.html#Translation-Tips">5 Details About The Translation
Process</a>
+ <li><a name="toc-Details-about-the-Translation-Process"
href="Translation-Tips.html#Translation-Tips">5 Details about the Translation
Process</a>
<ul class="no-bullet">
- <li><a name="toc-Migration-To-The-New-Style"
href="Migrating.html#Migrating">5.1 Migration To The New Style</a></li>
+ <li><a name="toc-Migration-to-the-New-Style"
href="Migrating.html#Migrating">5.1 Migration to the New Style</a></li>
<li><a name="toc-Summary-of-SSI-_0023includes" href="SSI.html#SSI">5.2
Summary of SSI <code>#include</code>s</a></li>
- <li><a name="toc-How-To-Use-Custom-CSS" href="CSS.html#CSS">5.3 How To Use
Custom CSS</a>
+ <li><a name="toc-How-to-Use-Custom-CSS" href="CSS.html#CSS">5.3 How to Use
Custom CSS</a>
<ul class="no-bullet">
- <li><a name="toc-Localizing-The-topbanner-Image"
href="topbanner.html#topbanner">5.3.1 Localizing The <samp>topbanner</samp>
Image</a></li>
+ <li><a name="toc-Localizing-the-topbanner-Image"
href="topbanner.html#topbanner">5.3.1 Localizing the <samp>topbanner</samp>
Image</a></li>
<li><a name="toc-Specific-Issues-Related-to-RTL"
href="RTL.html#RTL">5.3.2 Specific Issues Related to RTL</a></li>
</ul></li>
- <li><a name="toc-What-To-Translate" href="Priorities.html#Priorities">5.4
What To Translate</a></li>
- <li><a name="toc-When-To-CAPITALIZE"
href="Capitalization.html#Capitalization">5.5 When To CAPITALIZE</a></li>
+ <li><a name="toc-What-to-Translate" href="Priorities.html#Priorities">5.4
What to Translate</a></li>
+ <li><a name="toc-When-to-CAPITALIZE"
href="Capitalization.html#Capitalization">5.5 When to CAPITALIZE</a></li>
<li><a name="toc-Distribution-Terms-1"
href="Distribution-Terms.html#Distribution-Terms">5.6 Distribution
Terms</a></li>
<li><a name="toc-Language_002dspecific-Terminology"
href="Terminology.html#Terminology">5.7 Language-specific Terminology</a></li>
</ul></li>
- <li><a name="toc-Overview-Of-The-Translation-Process"
href="Summary.html#Summary">6 Overview Of The Translation Process</a>
+ <li><a name="toc-Overview-of-the-Translation-Process"
href="Summary.html#Summary">6 Overview of the Translation Process</a>
<ul class="no-bullet">
<li><a name="toc-Related-Mailing-Lists"
href="Mailing-Lists.html#Mailing-Lists">6.1 Related Mailing Lists</a></li>
<li><a name="toc-Savannah-Projects-Membership"
href="Savannah-Projects.html#Savannah-Projects">6.2 Savannah Projects
Membership</a></li>
@@ -146,7 +149,7 @@
<h1 class="top">GNU Web Translators Manual</h1>
<p>This manual is a guide for the GNU Web Translators.<br> Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
</p><br>
<p>Copyright © 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
Index: web-trans/html_node/topbanner.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/topbanner.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- web-trans/html_node/topbanner.html 4 Dec 2012 16:24:29 -0000 1.10
+++ web-trans/html_node/topbanner.html 27 Dec 2012 14:45:42 -0000 1.11
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-28.06.2012, for GNUnited Nations version 0.6.
+25.12.2012, for GNUnited Nations version 0.6.
Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
@@ -14,7 +14,7 @@
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
-<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Web Translators Manual: topbanner</title>
@@ -68,8 +68,8 @@
Next: <a href="RTL.html#RTL" accesskey="n" rel="next">RTL</a>, Up: <a
href="CSS.html#CSS" accesskey="u" rel="up">CSS</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
<hr>
-<a name="Localizing-The-topbanner-Image"></a>
-<h4 class="subsection">5.3.1 Localizing The <samp>topbanner</samp> Image</h4>
+<a name="Localizing-the-topbanner-Image"></a>
+<h4 class="subsection">5.3.1 Localizing the <samp>topbanner</samp> Image</h4>
<p>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:
@@ -82,7 +82,7 @@
Then with Inkscape, save the file as
<samp>graphics/topbanner.<var>lang</var>.png</samp> (File -> Export
Bitmap…).
Then open the PNG image with the GIMP and flatten it (Image -> Flatten
-Image). Don’t forget to save and <code>cvs add</code> the files<a
name="DOCF6" href="#FOOT6"><sup>6</sup></a>.
+Image). Don’t forget to save and <code>cvs add</code> the files<a
name="DOCF7" href="#FOOT7"><sup>7</sup></a>.
</li><li> Create a <samp>style.<var>lang</var>.css</samp> at the toplevel
directory, if it
doesn’t exist already. Normally, you would need only one line in it,
@@ -106,7 +106,7 @@
<hr>
<h4 class="footnotes-heading">Footnotes</h4>
-<h3><a name="FOOT6" href="#DOCF6">(6)</a></h3>
+<h3><a name="FOOT7" href="#DOCF7">(7)</a></h3>
<p>This
advice applies to all new files, of course.</p>
</div>
Index: gnun/html_node/Files-and-Directories.html
===================================================================
RCS file: gnun/html_node/Files-and-Directories.html
diff -N gnun/html_node/Files-and-Directories.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gnun/html_node/Files-and-Directories.html 27 Dec 2012 14:45:34 -0000
1.1
@@ -0,0 +1,245 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!--
+This manual (updated 27 December 2012) is for GNUnited Nations (version
+0.6), a suite for maintaining translations of www.gnu.org
+essays and other articles.
+
+
+Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Files and Directories</title>
+
+<meta name="description" content="GNUnited Nations: Files and Directories">
+<meta name="keywords" content="GNUnited Nations: Files and Directories">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Internals.html#Internals" rel="up" title="Internals">
+<link href="Scripts.html#Scripts" rel="next" title="Scripts">
+<link href="Internals.html#Internals" rel="previous" title="Internals">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
+</head>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+<a name="Files-and-Directories"></a>
+<div class="header">
+<p>
+Next: <a href="Scripts.html#Scripts" accesskey="n" rel="next">Scripts</a>, Up:
<a href="Internals.html#Internals" accesskey="u" rel="up">Internals</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
+<hr>
+<a name="Files-and-Directories-1"></a>
+<h3 class="section">3.1 Files and Directories</h3>
+
+<p>This is a brief diagram of <em>www</em> working copy; note that in this
+section we don’t describe the files out of GNUN control, including the
+old HTML-only translations.
+</p>
+<div class="example">
+<pre class="example">Legend:
+* The file is maintained locally, without committing it to CVS.
+# The file is edited manually.
+@ The file is regenerated automatically.
+% The file is edited both manually and automatically.
+#/@ The file is generated automatically, but outside of GNUN.
+
+</pre><pre class="example">Root/
+ |
+ +--gnu/
+ | |
+ | |
+ | +--linux-and-gnu.html #
+ | +--linux-and-gnu.<var>lang</var>.html @
+ | +--manifesto.html #
+ | +--manifesto.<var>lang</var>.html @
+ | +--…
+ | |
+ | +--------------------------po/
+ | |
+ +--home.html # +--manifesto.<var>lang</var>.po %
+ +--home.<var>lang</var>.html @ +--manifesto.pot @
+ +--planetfeeds.html #/@ +--manifesto.proto * @
+ +--planetfeeds.<var>lang</var>.html @ +--manifesto.translist @
+ +--po/ +--manifesto.<var>lang</var>.m4 * @
+ | | +--manifesto.<var>lang</var>-en.html @
+ | +--home.pot @ +--manifesto.<var>lang</var>-diff.html @
+ | +--home.proto * @ +--linux-and-gnu.<var>lang</var>.po %
+ | +--home.translist @ +--…
+ | +--home.<var>lang</var>.po %
+ | +--home.<var>lang</var>.m4 * @
+ | +--home.<var>lang</var>-en.html @
+ | +--home.<var>lang</var>-diff.html @
+ | +--planetfeeds.proto * @
+ | +--planetfeeds.pot.opt @
+ | +--planetfeeds.<var>lang</var>.po %
+ | +--…
+ |
+ +--server/
+ | |
+ | +-------------------------gnun/
+ | | |
+ | +--sitemap.html #/@ +--GNUmakefile * #
+ | +--sitemap.<var>lang</var>.html @ +--config.mk * #
+ | +--po/ +--gnun.mk #
+ | | | +--languages.txt #
+ | | +--sitemap.pot @ +--generic.<var>lang</var>.html #
+ | | +--sitemap.proto * @ +--compendia/
+ | | +--sitemap.<var>lang</var>.po % |
+ | | +--sitemap.<var>lang</var>.m4 @ +--master.<var>lang</var>.po #
+ | | +--body-include-2.pot @ +--compendium.<var>lang</var>.po @
+ | | +--body-include-2.proto * @ +--excluded.pot #
+ | | +--body-include-2.<var>lang</var>.po %
+ | | +--…
+ | |
+ | +--body-include-2.html #
+ | +--body-include-2.<var>lang</var>.html @
+ | +--…
+ +--…
+</pre></div>
+
+<p>A description of some files follows.
+</p>
+<dl compact="compact">
+<dt><samp>…/<var>file</var>.html</samp></dt>
+<dd><p>The English files.
+</p>
+</dd>
+<dt><samp>…/<var>file</var>.<var>lang</var>.html</samp></dt>
+<dd><p>The <var>lang</var> translation of
<samp>…/<var>file</var>.html</samp>.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.proto</samp></dt>
+<dd><p>Intermediate files generated from <samp><var>file</var>.html</samp>;
they are
+used only internally. Essentially, GNUN inserts its special slots and
+instructions to include the <samp>generic.<var>lang</var>.html</samp> file.
+See <a href="New-Translation.html#GNUN-Slots">GNUN Slots</a>, and <a
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml">generic.LANG.html</a>.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.translist</samp></dt>
+<dd><p>The list of trasnlations for
<samp>…/<var>file</var>.html</samp>. It is
+included in <samp>…/<var>file</var>.html</samp> all its translations.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.pot</samp></dt>
+<dd><p>PO templates for articles and included files.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.pot.opt</samp></dt>
+<dd><p>POTs of optional templates (currently,
<samp>planetfeeds.pot.opt</samp>).
+See <a
href="Main-Variables.html#optional_002dtemplates">optional-templates</a>, for
more details.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.<var>lang</var>.po</samp></dt>
+<dd><p>Translations of <samp><var>file</var>.pot</samp> or
<samp><var>file</var>.pot.opt</samp>
+committed by the translators and merged by GNUN.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.<var>lang</var>.m4</samp></dt>
+<dd><p>Intermediate files from which
<samp><var>file</var>.<var>lang</var>.html</samp> are
+generated.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.<var>lang</var>-en.html</samp></dt>
+<dd><p>The latest revision of the English file for which a full translation
+into <var>lang</var> language was provided.
+</p>
+</dd>
+<dt><samp>…/po/<var>file</var>.<var>lang</var>-diff.html</samp></dt>
+<dd><p>The highlighted differences between the current version of
+<samp>…<var>file</var>.html</samp> and
+<samp>…/po/<var>file</var>.<var>lang</var>-en.html</samp>.
+</p>
+</dd>
+<dt><samp>planetfeeds.html</samp></dt>
+<dd><p>A list of news; it is automatically generated outside of GNUN.
+For GNUN, it is an optional template.
+</p>
+</dd>
+<dt><samp>server/</samp></dt>
+<dd><p>Most template SSI files are located in this directory.
+</p>
+</dd>
+<dt><samp>server/sitemap.html</samp></dt>
+<dd><p>The sitemap; it is generated automatically by a script that is not
+included in GNUN. GNUN currently treats it like a regular article.
+</p>
+</dd>
+<dt><samp>server/gnun/</samp></dt>
+<dd><p>The directory for GNUN files.
+</p>
+</dd>
+<dt><samp>server/gnun/GNUmakefile</samp></dt>
+<dt><samp>server/gnun/config.mk</samp></dt>
+<dd><p>These files are maintained locally. They are used to rebuild the
+translations. See <a href="Invoking-GNUN.html#Invoking-GNUN">Invoking
GNUN</a>.
+</p>
+</dd>
+<dt><samp>server/gnun/gnun.mk</samp></dt>
+<dd><p>The file that defines the list of files to build. See <a
href="Main-Variables.html#Main-Variables">Main Variables</a>.
+</p>
+</dd>
+<dt><samp>server/gnun/languages.txt</samp></dt>
+<dd><p>See <a
href="languages_002etxt.html#languages_002etxt">languages.txt</a>.
+</p>
+</dd>
+<dt><samp>server/gnun/generic.<var>lang</var>.html</samp></dt>
+<dd><p>See <a
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml">generic.LANG.html</a>.
+</p>
+</dd>
+<dt><samp>server/gnun/compendia</samp></dt>
+<dd><p>The directory for compendia. See <a
href="Compendia.html#Compendia">Compendia</a>.
+</p></dd>
+</dl>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Scripts.html#Scripts" accesskey="n" rel="next">Scripts</a>, Up:
<a href="Internals.html#Internals" accesskey="u" rel="up">Internals</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
+
+
+
+</body>
+</html>
Index: gnun/html_node/GNUN-Slots.html
===================================================================
RCS file: gnun/html_node/GNUN-Slots.html
diff -N gnun/html_node/GNUN-Slots.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gnun/html_node/GNUN-Slots.html 27 Dec 2012 14:45:35 -0000 1.1
@@ -0,0 +1,65 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!--
+This manual (updated 27 December 2012) is for GNUnited Nations (version
+0.6), a suite for maintaining translations of www.gnu.org
+essays and other articles.
+
+
+Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
+<!-- This file redirects to the location of a node or anchor -->
+<head>
+<title>GNUnited Nations: GNUN Slots</title>
+
+<meta name="description" content="GNUnited Nations: GNUN Slots">
+<meta name="keywords" content="GNUnited Nations: GNUN Slots">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+<meta http-equiv="Refresh" content="0; url=New-Translation.html#GNUN-Slots">
+
+</head>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+
+<p>The node you are looking for is at <a
href="New-Translation.html#GNUN-Slots">GNUN Slots</a>.</p>
+</body>
Index: gnun/html_node/publish.html
===================================================================
RCS file: gnun/html_node/publish.html
diff -N gnun/html_node/publish.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gnun/html_node/publish.html 27 Dec 2012 14:45:37 -0000 1.1
@@ -0,0 +1,65 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!--
+This manual (updated 27 December 2012) is for GNUnited Nations (version
+0.6), a suite for maintaining translations of www.gnu.org
+essays and other articles.
+
+
+Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
+<!-- This file redirects to the location of a node or anchor -->
+<head>
+<title>GNUnited Nations: publish</title>
+
+<meta name="description" content="GNUnited Nations: publish">
+<meta name="keywords" content="GNUnited Nations: publish">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+<meta http-equiv="Refresh" content="0;
url=GNUmakefile_002eteam-Targets.html#publish">
+
+</head>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+
+<p>The node you are looking for is at <a
href="GNUmakefile_002eteam-Targets.html#publish">publish</a>.</p>
+</body>
Index: gnun/html_node/report-in-GNUmakefile_002eteam.html
===================================================================
RCS file: gnun/html_node/report-in-GNUmakefile_002eteam.html
diff -N gnun/html_node/report-in-GNUmakefile_002eteam.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gnun/html_node/report-in-GNUmakefile_002eteam.html 27 Dec 2012 14:45:37
-0000 1.1
@@ -0,0 +1,65 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!--
+This manual (updated 27 December 2012) is for GNUnited Nations (version
+0.6), a suite for maintaining translations of www.gnu.org
+essays and other articles.
+
+
+Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
+<!-- This file redirects to the location of a node or anchor -->
+<head>
+<title>GNUnited Nations: report in GNUmakefile.team</title>
+
+<meta name="description" content="GNUnited Nations: report in
GNUmakefile.team">
+<meta name="keywords" content="GNUnited Nations: report in GNUmakefile.team">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+<meta http-equiv="Refresh" content="0;
url=GNUmakefile_002eteam-Targets.html#report-in-GNUmakefile_002eteam">
+
+</head>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+
+<p>The node you are looking for is at <a
href="GNUmakefile_002eteam-Targets.html#report-in-GNUmakefile_002eteam">report
in GNUmakefile.team</a>.</p>
+</body>
Index: web-trans/html_node/Leaving-a-Team.html
===================================================================
RCS file: web-trans/html_node/Leaving-a-Team.html
diff -N web-trans/html_node/Leaving-a-Team.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ web-trans/html_node/Leaving-a-Team.html 27 Dec 2012 14:45:39 -0000
1.1
@@ -0,0 +1,86 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!--
+This manual is a guide for the GNU Web Translators.
+ Last updated on
+25.12.2012, for GNUnited Nations version 0.6.
+
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Leaving a Team</title>
+
+<meta name="description" content="GNU Web Translators Manual: Leaving a Team">
+<meta name="keywords" content="GNU Web Translators Manual: Leaving a Team">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Members.html#Members" rel="up" title="Members">
+<link href="Leaders.html#Leaders" rel="next" title="Leaders">
+<link href="Submitting-as-Plain-Text.html#Submitting-as-Plain-Text"
rel="previous" title="Submitting as Plain Text">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
+</head>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+<a name="Leaving-a-Team"></a>
+<div class="header">
+<p>
+Previous: <a href="Submitting.html#Submitting" accesskey="p"
rel="previous">Submitting</a>, Up: <a href="Members.html#Members" accesskey="u"
rel="up">Members</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
+</div>
+<hr>
+<a name="Leaving-a-Team-1"></a>
+<h3 class="section">2.3 Leaving a Team</h3>
+
+<p>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
+translation team co-ordinator and possibly all the rest of the
+team-mates. The team leader should always have a rough estimation about
+the available translators, even though there are no reliable means to
+establish that. Your announcement that you are stepping down
+(temporarily or permanently) may help her in this regard.
+</p>
+
+
+
+</body>
+</html>
Index: web-trans/html_node/PO-Files.html
===================================================================
RCS file: web-trans/html_node/PO-Files.html
diff -N web-trans/html_node/PO-Files.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ web-trans/html_node/PO-Files.html 27 Dec 2012 14:45:40 -0000 1.1
@@ -0,0 +1,171 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!--
+This manual is a guide for the GNU Web Translators.
+ Last updated on
+25.12.2012, for GNUnited Nations version 0.6.
+
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.92, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: PO Files</title>
+
+<meta name="description" content="GNU Web Translators Manual: PO Files">
+<meta name="keywords" content="GNU Web Translators Manual: PO Files">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Managing.html#Managing" rel="up" title="Managing">
+<link href="Savannah.html#Savannah" rel="next" title="Savannah">
+<link href="Commits.html#Commits" rel="previous" title="Commits">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
+</head>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+<a name="PO-Files"></a>
+<div class="header">
+<p>
+Next: <a href="Savannah.html#Savannah" accesskey="n" rel="next">Savannah</a>,
Previous: <a href="Commits.html#Commits" accesskey="p"
rel="previous">Commits</a>, Up: <a href="Managing.html#Managing" accesskey="u"
rel="up">Managing</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
+</div>
+<hr>
+<a name="Working-with-PO-Files"></a>
+<h4 class="subsection">3.2.3 Working with PO Files</h4>
+<a name="index-PO_002c-editing"></a>
+
+<p>We anticipate that some gnu.org translators will find this format odd
+or inconvenient, if they never happened to work with PO files
+before<a name="DOCF6" href="#FOOT6"><sup>6</sup></a>.
+Don’t worry, you will soon get accustomed to it. It is the
+established format for translations in the Free World, and you should
+have no problems if you have translated software before.
+</p>
+<p>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 it valid. Here is a list of widely used PO editors:
+</p>
+<ul>
+<li> <a name="index-PO-editors"></a>
+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 <samp>.po</samp> file you visit should automatically
+switch to PO mode. You can enable/disable it with <code>M-x po-mode
+<span class="key">RET</span></code>. On some GNU/Linux distros such as
gNewSense, PO mode is
+available in a separate package, <code>gettext-el</code>. See
+<a
href="http://www.gnu.org/software/gettext";>http://www.gnu.org/software/gettext</a>.
+
+</li><li> Gtranslator—the GNOME PO editor. See
+<a
href="http://projects.gnome.org/gtranslator/";>http://projects.gnome.org/gtranslator/</a>.
+
+</li><li> Lokalize—the KDE 4 editor. See
+<a
href="http://userbase.kde.org/Lokalize";>http://userbase.kde.org/Lokalize</a>.
+
+</li><li> KBabel—the KDE 3 editor. No longer supported, but might be
+available on some old systems.
+
+</li><li> Poedit—another popular editor that is based on the
<code>wxWidgets</code>
+graphical toolkit. See <a
href="http://www.poedit.net";>http://www.poedit.net</a>.
+
+</li><li> Virtaal—a relevantly new editor that supports also the XLIFF
format
+and uses the Translate Toolkit API. See
+<a
href="http://translate.sourceforge.net/wiki/virtaal";>http://translate.sourceforge.net/wiki/virtaal</a>.
+
+</li><li> po.vim—ftplugin for the Vim editor. The best option for
people who
+use Vim as their editor. See
+<a
href="http://www.vim.org/scripts/script.php?script_id=2530";>http://www.vim.org/scripts/script.php?script_id=2530</a>.
+
+</li><li> Various web-based editors.
+</li></ul>
+
+<a name="Web_002dbased-Systems"></a>
+<h4 class="subsubsection">3.2.3.1 Web-based Systems</h4>
+
+<p>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 <samp>.po</samp> 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
+(<a
href="http://translations.launchpad.net";>http://translations.launchpad.net</a>).
+</p>
+<p>Here is a short and probably incomplete list of such systems:
+</p>
+<ul>
+<li> Pootle—<a
href="http://translate.sourceforge.net/wiki/pootle";>http://translate.sourceforge.net/wiki/pootle</a>
+
+</li><li> Vertaal—<a
href="http://code.google.com/p/vertaal";>http://code.google.com/p/vertaal</a>
+
+</li><li> Narro—<a
href="http://code.google.com/p/narro";>http://code.google.com/p/narro</a>
+
+</li><li> Launchpad—<a
href="https://dev.launchpad.net";>https://dev.launchpad.net</a>
+
+</li></ul>
+
+<p>If you decide to use such a system, please make sure that no
+translations are published in HTML format there.
+</p>
+<p>Note that to keep the <samp>.pot</samp> files regularly updated (assuming
such
+a web-based system runs <code>msgmerge</code> automatically), you’ll have
+to take care of the one-way regular sync from the
‘<samp>www</samp>’ CVS
+repository.
+</p>
+<div class="footnote">
+<hr>
+<h4 class="footnotes-heading">Footnotes</h4>
+
+<h3><a name="FOOT6" href="#DOCF6">(6)</a></h3>
+<p>For www.gnu.org-specific information about editing
+PO files, see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/PO-Files.html#PO-Files";>Working
with PO Files</a> in <cite>The GNUnited Nations Manual</cite>.</p>
+</div>
+<hr>
+<div class="header">
+<p>
+Next: <a href="Savannah.html#Savannah" accesskey="n" rel="next">Savannah</a>,
Previous: <a href="Commits.html#Commits" accesskey="p"
rel="previous">Commits</a>, Up: <a href="Managing.html#Managing" accesskey="u"
rel="up">Managing</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
+</div>
+
+
+
+</body>
+</html>