[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: |
Fri, 01 Feb 2013 06:06:25 +0000 |
CVSROOT: /web/trans-coord
Module name: trans-coord
Changes by: Pavel Kharitonov <ineiev> 13/02/01 06:06:24
Modified files:
manual/gnun : gnun.dvi.gz gnun.html gnun.html.gz
gnun.html_node.tar.gz gnun.info.tar.gz gnun.pdf
gnun.ps.gz 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
Files-and-Directories.html GNU-News.html
GNUN-Slots.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.html PO-Tips.html
Runtime-Variables.html Scripts.html
Sitemap.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
notify-in-GNUmakefile_002eteam.html
optional_002dtemplates.html publish.html
report-in-GNUmakefile_002eteam.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.ps.gz 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 Leaving-a-Team.html
Mailing-Lists.html Managing.html
Members.html Migrating.html
New-Team.html PO-Files.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 Terminology.html
Tracking-Tasks.html
Unreviewed-Translations.html
Updating.html index.html
topbanner.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.20
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.html?cvsroot=trans-coord&r1=1.19&r2=1.20
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.html.gz?cvsroot=trans-coord&rev=1.20
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.html_node.tar.gz?cvsroot=trans-coord&rev=1.20
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.info.tar.gz?cvsroot=trans-coord&rev=1.20
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.pdf?cvsroot=trans-coord&rev=1.20
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.ps.gz?cvsroot=trans-coord&rev=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.texi.tar.gz?cvsroot=trans-coord&rev=1.20
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.txt?cvsroot=trans-coord&r1=1.19&r2=1.20
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.txt.gz?cvsroot=trans-coord&rev=1.20
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/index.html?cvsroot=trans-coord&r1=1.20&r2=1.21
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Advantages.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Bugs.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Comments-for-Translators.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Compendia.html?cvsroot=trans-coord&r1=1.7&r2=1.8
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Concepts.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Copying-This-Manual.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Credits-Slot.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Disadvantages.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Files-and-Directories.html?cvsroot=trans-coord&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GNU-News.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GNUN-Slots.html?cvsroot=trans-coord&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GNUmakefile_002eteam-Targets.html?cvsroot=trans-coord&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GNUmakefile_002eteam-Variables.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GNUmakefile_002eteam-and-Cron.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GRACE.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Index.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Internals.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Introduction.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Invoking-GNUN.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Localized-URLs.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Main-Variables.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Migrating.html?cvsroot=trans-coord&r1=1.19&r2=1.20
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Modifying-Boilerplates.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/New-Translation.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Notes-Slot.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Overview.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/PO-Files.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/PO-Tips.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Runtime-Variables.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Scripts.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Sitemap.html?cvsroot=trans-coord&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Special-Targets.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Splitting-Long-Passages.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Usage.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Validation.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Webmaster-Tips.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/extra_002dtemplates.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/generic_002eLANG_002ehtml.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dadd_002dfuzzy_002ddiff.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dclear_002dprevious.html?cvsroot=trans-coord&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002ddiff_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_002dinit_002dpo.html?cvsroot=trans-coord&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dmerge_002dpreconverted.html?cvsroot=trans-coord&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dpreconvert.html?cvsroot=trans-coord&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dreport.html?cvsroot=trans-coord&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dvalidate_002dhtml.html?cvsroot=trans-coord&r1=1.14&r2=1.15
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/index.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/languages_002etxt.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/mailfail.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/no_002dgrace_002ditems.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/notify-in-GNUmakefile_002eteam.html?cvsroot=trans-coord&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/optional_002dtemplates.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/publish.html?cvsroot=trans-coord&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/report-in-GNUmakefile_002eteam.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.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/sync.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/triggers.html?cvsroot=trans-coord&r1=1.17&r2=1.18
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/update_002dlocalized_002dURLs.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/validate_002dall.html?cvsroot=trans-coord&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/validate_002dhtml_002dnotify.html?cvsroot=trans-coord&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/index.html?cvsroot=trans-coord&r1=1.13&r2=1.14
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.dvi.gz?cvsroot=trans-coord&rev=1.14
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.html?cvsroot=trans-coord&r1=1.13&r2=1.14
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.html.gz?cvsroot=trans-coord&rev=1.14
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.html_node.tar.gz?cvsroot=trans-coord&rev=1.14
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.info.tar.gz?cvsroot=trans-coord&rev=1.14
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.pdf?cvsroot=trans-coord&rev=1.14
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.ps.gz?cvsroot=trans-coord&rev=1.13
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.texi.tar.gz?cvsroot=trans-coord&rev=1.14
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.txt?cvsroot=trans-coord&r1=1.13&r2=1.14
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.txt.gz?cvsroot=trans-coord&rev=1.14
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/CSS.html?cvsroot=trans-coord&r1=1.12&r2=1.13
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Capitalization.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Co_002dleaders.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Commits.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Copying-This-Manual.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Distribution-Terms.html?cvsroot=trans-coord&r1=1.7&r2=1.8
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Introduction.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Joining.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Leaders.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Leaving-a-Team.html?cvsroot=trans-coord&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Mailing-Lists.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Managing.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Members.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Migrating.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/New-Team.html?cvsroot=trans-coord&r1=1.12&r2=1.13
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/PO-Files.html?cvsroot=trans-coord&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Priorities.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/RTL.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Reports.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Review.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/SSI.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Bugs.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Homepage.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Mailing-Lists.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Members.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-News.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Projects.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Support.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Tasks.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-VCS.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Stepping-Down.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Submitting-as-PO.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Submitting-as-Plain-Text.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Submitting.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Terminology.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Tracking-Tasks.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Unreviewed-Translations.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Updating.html?cvsroot=trans-coord&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/index.html?cvsroot=trans-coord&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/topbanner.html?cvsroot=trans-coord&r1=1.12&r2=1.13
Patches:
Index: gnun/gnun.dvi.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.dvi.gz,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
Binary files /tmp/cvsixlOwQ and /tmp/cvsfF1lxq differ
Index: gnun/gnun.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- gnun/gnun.html 31 Jan 2013 08:47:28 -0000 1.19
+++ gnun/gnun.html 1 Feb 2013 06:06:05 -0000 1.20
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -82,68 +82,66 @@
</ul></li>
<li><a name="toc-General-Usage" href="#Usage">2 General Usage</a>
<ul class="no-bullet">
- <li><a name="toc-Invoking-GNUN-1" href="#Invoking-GNUN">2.1 Invoking
GNUN</a>
+ <li><a name="toc-Invoking-GNUN-1" href="#Invoking-GNUN">2.1 Invoking
GNUN</a></li>
+ <li><a name="toc-Variables-to-Control-the-Build-Process"
href="#Runtime-Variables">2.2 Variables to Control the Build Process</a></li>
+ <li><a name="toc-Targets-Specified-on-the-Command-Line"
href="#Special-Targets">2.3 Targets Specified on the Command Line</a>
<ul class="no-bullet">
- <li><a name="toc-Variables-to-Control-the-Build-Process"
href="#Runtime-Variables">2.1.1 Variables to Control the Build Process</a></li>
- <li><a name="toc-Targets-Specified-on-the-Command-Line"
href="#Special-Targets">2.1.2 Targets Specified on the Command Line</a>
- <ul class="no-bullet">
- <li><a name="toc-The-no_002dgrace_002ditems-Target"
href="#no_002dgrace_002ditems">2.1.2.1 The <code>no-grace-items</code>
Target</a></li>
- <li><a name="toc-The-update_002dlocalized_002dURLs-Target"
href="#update_002dlocalized_002dURLs">2.1.2.2 The
<code>update-localized-URLs</code> Target</a></li>
- <li><a name="toc-The-sync-Target" href="#sync">2.1.2.3 The
<code>sync</code> Target</a></li>
- <li><a name="toc-The-report-Target" href="#report">2.1.2.4 The
<code>report</code> Target</a></li>
- <li><a name="toc-The-triggers-Target" href="#triggers">2.1.2.5 The
<code>triggers</code> Target</a></li>
- <li><a name="toc-The-validate_002dall-Target"
href="#validate_002dall">2.1.2.6 The <code>validate-all</code> Target</a></li>
+ <li><a name="toc-The-no_002dgrace_002ditems-Target"
href="#no_002dgrace_002ditems">2.3.1 The <code>no-grace-items</code>
Target</a></li>
+ <li><a name="toc-The-update_002dlocalized_002dURLs-Target"
href="#update_002dlocalized_002dURLs">2.3.2 The
<code>update-localized-URLs</code> Target</a></li>
+ <li><a name="toc-The-sync-Target" href="#sync">2.3.3 The
<code>sync</code> Target</a></li>
+ <li><a name="toc-The-report-Target" href="#report">2.3.4 The
<code>report</code> Target</a></li>
+ <li><a name="toc-The-triggers-Target" href="#triggers">2.3.5 The
<code>triggers</code> Target</a></li>
+ <li><a name="toc-The-validate_002dall-Target"
href="#validate_002dall">2.3.6 The <code>validate-all</code> Target</a></li>
</ul></li>
+ <li><a name="toc-Defining-Articles-to-Be-Built" href="#Main-Variables">2.4
Defining Articles to Be Built</a></li>
+ <li><a name="toc-The-generic_002elang_002ehtml-File"
href="#generic_002eLANG_002ehtml">2.5 The
<samp>generic.<var>lang</var>.html</samp> File</a></li>
+ <li><a name="toc-The-languages_002etxt-File" href="#languages_002etxt">2.6
The <samp>languages.txt</samp> File</a></li>
+ <li><a name="toc-Using-Compendia" href="#Compendia">2.7 Using
Compendia</a></li>
+ <li><a name="toc-Building-Sitemap" href="#Sitemap">2.8 Building
Sitemap</a></li>
+ <li><a name="toc-Special-Handling-for-GNU-News" href="#GNU-News">2.9
Special Handling for GNU News</a></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-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>
+ <li><a name="toc-Maintaining-Translations-in-Your-Team_0027s-Repository"
href="#Team_0027s-Repository">3 Maintaining Translations in Your Team’s
Repository</a>
<ul class="no-bullet">
- <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>
+ <li><a name="toc-Adopting-GNUmakefile_002eteam-for-a-Specific-Team"
href="#GNUmakefile_002eteam-Variables">3.1 Adopting
<samp>GNUmakefile.team</samp> for a Specific Team</a></li>
+ <li><a name="toc-Targets-in-GNUmakefile_002eteam"
href="#GNUmakefile_002eteam-Targets">3.2 Targets in
<samp>GNUmakefile.team</samp></a></li>
+ <li><a name="toc-Automatic-Synchronization-and-Status-Reports"
href="#GNUmakefile_002eteam-and-Cron">3.3 Automatic Synchronization and Status
Reports</a></li>
</ul></li>
- <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>
+ <li><a name="toc-Working-with-PO-Files" href="#PO-Files">4 Working with PO
Files</a>
<ul class="no-bullet">
- <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>
+ <li><a name="toc-Starting-a-New-Translation" href="#New-Translation">4.1
Starting a New Translation</a>
+ <ul class="no-bullet">
+ <li><a name="toc-The-Special-Slot-for-Translator_0027s-Notes"
href="#Notes-Slot">4.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">4.1.2 The Special Slot for Translator’s
Credits</a></li>
</ul></li>
- <li><a name="toc-Using-Compendia" href="#Compendia">2.3.7 Using
Compendia</a></li>
- <li><a name="toc-Building-Sitemap" href="#Sitemap">2.3.8 Building
Sitemap</a></li>
- <li><a name="toc-Special-Handling-for-GNU-News" href="#GNU-News">2.3.9
Special Handling for GNU News</a></li>
+ <li><a name="toc-Useful-Hints-for-Editing-PO-Files" href="#PO-Tips">4.2
Useful Hints for Editing PO Files</a></li>
+ <li><a name="toc-Transforming-Existing-Translation-in-PO-Format"
href="#Migrating">4.3 Transforming Existing Translation in PO Format</a></li>
</ul></li>
- <li><a name="toc-Tips-and-Hints-for-Webmasters" href="#Webmaster-Tips">2.4
Tips and Hints for Webmasters</a>
+ <li><a name="toc-Tips-and-Hints-for-Webmasters" href="#Webmaster-Tips">5
Tips and Hints for Webmasters</a>
<ul class="no-bullet">
- <li><a name="toc-Validation-1" href="#Validation">2.4.1
Validation</a></li>
- <li><a name="toc-Comments-for-Translators-1"
href="#Comments-for-Translators">2.4.2 Comments for Translators</a></li>
- <li><a name="toc-Modifying-Boilerplates-1"
href="#Modifying-Boilerplates">2.4.3 Modifying Boilerplates</a></li>
- <li><a name="toc-Localized-URLs-1" href="#Localized-URLs">2.4.4
Localized URLs</a></li>
- <li><a name="toc-Splitting-Long-Passages-1"
href="#Splitting-Long-Passages">2.4.5 Splitting Long Passages</a></li>
- </ul></li>
+ <li><a name="toc-Validation-1" href="#Validation">5.1 Validation</a></li>
+ <li><a name="toc-Comments-for-Translators-1"
href="#Comments-for-Translators">5.2 Comments for Translators</a></li>
+ <li><a name="toc-Modifying-Boilerplates-1"
href="#Modifying-Boilerplates">5.3 Modifying Boilerplates</a></li>
+ <li><a name="toc-Localized-URLs-1" href="#Localized-URLs">5.4 Localized
URLs</a></li>
+ <li><a name="toc-Splitting-Long-Passages-1"
href="#Splitting-Long-Passages">5.5 Splitting Long Passages</a></li>
</ul></li>
- <li><a name="toc-Unexciting-Information-for-GNUN_0027s-Operation"
href="#Internals">3 Unexciting Information for GNUN’s Operation</a>
+ <li><a name="toc-Unexciting-Information-for-GNUN_0027s-Operation"
href="#Internals">6 Unexciting Information for GNUN’s Operation</a>
<ul class="no-bullet">
- <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>
+ <li><a name="toc-Files-and-Directories-1"
href="#Files-and-Directories">6.1 Files and Directories</a></li>
+ <li><a name="toc-GNUN-Scripts" href="#Scripts">6.2 GNUN Scripts</a>
<ul class="no-bullet">
- <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>
+ <li><a name="toc-The-gnun_002dadd_002dfuzzy_002ddiff-Script"
href="#gnun_002dadd_002dfuzzy_002ddiff">6.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">6.2.2 The <code>gnun-diff-po</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dinit_002dpo-Script"
href="#gnun_002dinit_002dpo">6.2.3 The <code>gnun-init-po</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dpreconvert-Script"
href="#gnun_002dpreconvert">6.2.4 The <code>gnun-preconvert</code>
Script</a></li>
+ <li><a name="toc-The-gnun_002dmerge_002dpreconverted-Script"
href="#gnun_002dmerge_002dpreconverted">6.2.5 The
<code>gnun-merge-preconverted</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dreport-Script"
href="#gnun_002dreport">6.2.6 The <code>gnun-report</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dvalidate_002dhtml-Script"
href="#gnun_002dvalidate_002dhtml">6.2.7 The <code>gnun-validate-html</code>
Script</a></li>
+ <li><a name="toc-The-mailfail-Script" href="#mailfail">6.2.8 The
<code>mailfail</code> Script</a></li>
+ <li><a name="toc-The-validate_002dhtml_002dnotify-Script"
href="#validate_002dhtml_002dnotify">6.2.9 The
<code>validate-html-notify</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dclear_002dprevious-Script"
href="#gnun_002dclear_002dprevious">6.2.10 The <code>gnun-clear-previous</code>
Script</a></li>
</ul></li>
</ul></li>
- <li><a name="toc-Reporting-Bugs" href="#Bugs">4 Reporting Bugs</a></li>
+ <li><a name="toc-Reporting-Bugs" href="#Bugs">7 Reporting Bugs</a></li>
<li><a name="toc-Index-1" href="#Index">Index</a></li>
<li><a name="toc-GNU-Free-Documentation-License"
href="#Copying-This-Manual">Appendix A GNU Free Documentation License</a></li>
</ul>
@@ -159,7 +157,7 @@
<a name="GNUnited-Nations"></a>
<h1 class="top">GNUnited Nations</h1>
-<p>This manual (updated 31 January 2013) is for GNUnited Nations (version
+<p>This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.<br>
</p><br>
@@ -181,13 +179,21 @@
</td></tr>
<tr><td align="left" valign="top">• <a href="#Usage"
accesskey="2">Usage</a>:</td><td> </td><td align="left"
valign="top">Basic usage, invocation and tips.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Internals"
accesskey="3">Internals</a>:</td><td> </td><td align="left"
valign="top">Dive into GNUN.
+<tr><td align="left" valign="top">• <a href="#Team_0027s-Repository"
accesskey="3">Team's Repository</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="#PO-Files" accesskey="4">PO
Files</a>:</td><td> </td><td align="left" valign="top">The gentle
art of editing PO files.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Webmaster-Tips"
accesskey="5">Webmaster Tips</a>:</td><td> </td><td align="left"
valign="top">The webmaster’s guide to GNUnited Nations’
+ galaxy.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Internals"
accesskey="6">Internals</a>:</td><td> </td><td align="left"
valign="top">Dive into GNUN.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Bugs"
accesskey="4">Bugs</a>:</td><td> </td><td align="left"
valign="top">How to report bugs.
+<tr><td align="left" valign="top">• <a href="#Bugs"
accesskey="7">Bugs</a>:</td><td> </td><td align="left"
valign="top">How to report bugs.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Index"
accesskey="5">Index</a>:</td><td> </td><td align="left" valign="top">
+<tr><td align="left" valign="top">• <a href="#Index"
accesskey="8">Index</a>:</td><td> </td><td align="left" valign="top">
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Copying-This-Manual"
accesskey="6">Copying This Manual</a>:</td><td> </td><td
align="left" valign="top">The GNU Free Documentation License.
+<tr><td align="left" valign="top">• <a href="#Copying-This-Manual"
accesskey="9">Copying This Manual</a>:</td><td> </td><td
align="left" valign="top">The GNU Free Documentation License.
</td></tr>
</table>
@@ -492,7 +498,7 @@
<a name="Usage"></a>
<div class="header">
<p>
-Next: <a href="#Internals" accesskey="n" rel="next">Internals</a>, Previous:
<a href="#Introduction" accesskey="p" rel="previous">Introduction</a>, Up: <a
href="#Top" accesskey="u" rel="up">Top</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="#Team_0027s-Repository" accesskey="n" rel="next">Team's
Repository</a>, Previous: <a href="#Introduction" accesskey="p"
rel="previous">Introduction</a>, Up: <a href="#Top" accesskey="u"
rel="up">Top</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="General-Usage"></a>
<h2 class="chapter">2 General Usage</h2>
@@ -524,12 +530,22 @@
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top">• <a href="#Invoking-GNUN"
accesskey="1">Invoking GNUN</a>:</td><td> </td><td align="left"
valign="top">How to trigger a (re)build.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Main-Variables"
accesskey="2">Main Variables</a>:</td><td> </td><td align="left"
valign="top">Specifying what to build.
+<tr><td align="left" valign="top">• <a href="#Runtime-Variables"
accesskey="2">Runtime Variables</a>:</td><td> </td><td align="left"
valign="top">Variables to control the build process.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#PO-Files" accesskey="3">PO
Files</a>:</td><td> </td><td align="left" valign="top">The gentle
art of editing PO files.
+<tr><td align="left" valign="top">• <a href="#Special-Targets"
accesskey="3">Special Targets</a>:</td><td> </td><td align="left"
valign="top">Targets that are not built by default.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Webmaster-Tips"
accesskey="4">Webmaster Tips</a>:</td><td> </td><td align="left"
valign="top">The webmaster’s guide to GNUnited Nations’
- galaxy.
+<tr><td align="left" valign="top">• <a href="#Main-Variables"
accesskey="4">Main Variables</a>:</td><td> </td><td align="left"
valign="top">Specifying what to build.
+</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
+ 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.
+</td></tr>
+<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="#Sitemap"
accesskey="8">Sitemap</a>:</td><td> </td><td align="left"
valign="top">Specifics of sitemap generation.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#GNU-News" accesskey="9">GNU
News</a>:</td><td> </td><td align="left" valign="top">Obsolete: How
to handle “whatsnew”.
</td></tr>
</table>
@@ -537,7 +553,7 @@
<a name="Invoking-GNUN"></a>
<div class="header">
<p>
-Next: <a href="#Main-Variables" accesskey="n" rel="next">Main Variables</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>
+Next: <a href="#Runtime-Variables" accesskey="n" rel="next">Runtime
Variables</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="Invoking-GNUN-1"></a>
<h3 class="section">2.1 Invoking GNUN</h3>
@@ -595,21 +611,14 @@
your hypothetical tree. (For gnu.org, that is not necessary since
a proper <samp>gnun.mk</samp> is maintained in ‘www’.)
</p>
-<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top">• <a href="#Runtime-Variables"
accesskey="1">Runtime Variables</a>:</td><td> </td><td align="left"
valign="top">Variables to control the build process.
-</td></tr>
-<tr><td align="left" valign="top">• <a href="#Special-Targets"
accesskey="2">Special Targets</a>:</td><td> </td><td align="left"
valign="top">Targets that are not built by default.
-</td></tr>
-</table>
-
<hr>
<a name="Runtime-Variables"></a>
<div class="header">
<p>
-Next: <a href="#Special-Targets" accesskey="n" rel="next">Special Targets</a>,
Up: <a href="#Invoking-GNUN" accesskey="u" rel="up">Invoking GNUN</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="#Special-Targets" accesskey="n" rel="next">Special Targets</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="Variables-to-Control-the-Build-Process"></a>
-<h4 class="subsection">2.1.1 Variables to Control the Build Process</h4>
+<h3 class="section">2.2 Variables to Control the Build Process</h3>
<a name="index-variables"></a>
<a name="index-variable_002c-behavior"></a>
@@ -800,10 +809,10 @@
<a name="Special-Targets"></a>
<div class="header">
<p>
-Previous: <a href="#Runtime-Variables" accesskey="p" rel="previous">Runtime
Variables</a>, Up: <a href="#Invoking-GNUN" accesskey="u" rel="up">Invoking
GNUN</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="#Main-Variables" accesskey="n" rel="next">Main Variables</a>,
Previous: <a href="#Runtime-Variables" accesskey="p" rel="previous">Runtime
Variables</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="Targets-Specified-on-the-Command-Line"></a>
-<h4 class="subsection">2.1.2 Targets Specified on the Command Line</h4>
+<h3 class="section">2.3 Targets Specified on the Command Line</h3>
<p>Some targets are not built by default, because they are only useful
under certain circumstances. Think of them like semi-automated
@@ -834,7 +843,7 @@
Next: <a href="#update_002dlocalized_002dURLs" accesskey="n"
rel="next">update-localized-URLs</a>, Up: <a href="#Special-Targets"
accesskey="u" rel="up">Special Targets</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-no_002dgrace_002ditems-Target"></a>
-<h4 class="subsubsection">2.1.2.1 The <code>no-grace-items</code> Target</h4>
+<h4 class="subsection">2.3.1 The <code>no-grace-items</code> Target</h4>
<p>The <code>no-grace-items</code> target regenerates a limited set of articles
that are not affected by the grace period, namely, the
@@ -851,7 +860,7 @@
Next: <a href="#sync" accesskey="n" rel="next">sync</a>, Previous: <a
href="#no_002dgrace_002ditems" accesskey="p" rel="previous">no-grace-items</a>,
Up: <a href="#Special-Targets" accesskey="u" rel="up">Special Targets</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-update_002dlocalized_002dURLs-Target"></a>
-<h4 class="subsubsection">2.1.2.2 The <code>update-localized-URLs</code>
Target</h4>
+<h4 class="subsection">2.3.2 The <code>update-localized-URLs</code> Target</h4>
<p>The <code>update-localized-URLs</code> target invokes a script that
generates the <samp>localized-urls.mk</samp> file. This file includes the
@@ -867,7 +876,7 @@
Next: <a href="#report" accesskey="n" rel="next">report</a>, Previous: <a
href="#update_002dlocalized_002dURLs" accesskey="p"
rel="previous">update-localized-URLs</a>, Up: <a href="#Special-Targets"
accesskey="u" rel="up">Special Targets</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-sync-Target"></a>
-<h4 class="subsubsection">2.1.2.3 The <code>sync</code> Target</h4>
+<h4 class="subsection">2.3.3 The <code>sync</code> Target</h4>
<a name="index-synchronization_002c-repository"></a>
<p>The <code>sync</code> target has a simple task: synchronize the
@@ -913,7 +922,7 @@
Next: <a href="#triggers" accesskey="n" rel="next">triggers</a>, Previous: <a
href="#sync" accesskey="p" rel="previous">sync</a>, Up: <a
href="#Special-Targets" accesskey="u" rel="up">Special Targets</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-report-Target"></a>
-<h4 class="subsubsection">2.1.2.4 The <code>report</code> Target</h4>
+<h4 class="subsection">2.3.4 The <code>report</code> Target</h4>
<a name="index-reporting"></a>
<a name="index-status_002c-translations"></a>
@@ -951,7 +960,7 @@
Next: <a href="#validate_002dall" accesskey="n" rel="next">validate-all</a>,
Previous: <a href="#report" accesskey="p" rel="previous">report</a>, Up: <a
href="#Special-Targets" accesskey="u" rel="up">Special Targets</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-triggers-Target"></a>
-<h4 class="subsubsection">2.1.2.5 The <code>triggers</code> Target</h4>
+<h4 class="subsection">2.3.5 The <code>triggers</code> Target</h4>
<p>This is a special target intended to be run by the automatic build after
the main build and <em>after</em> <code>cvs|svn|bzr commit</code>.
@@ -1011,7 +1020,7 @@
Previous: <a href="#triggers" accesskey="p" rel="previous">triggers</a>, Up:
<a href="#Special-Targets" accesskey="u" rel="up">Special Targets</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_002dall-Target"></a>
-<h4 class="subsubsection">2.1.2.6 The <code>validate-all</code> Target</h4>
+<h4 class="subsection">2.3.6 The <code>validate-all</code> Target</h4>
<a name="index-validation-2"></a>
<p>The <code>validate-all</code> target validates all HTML pages under
GNUN’s
@@ -1024,10 +1033,10 @@
<a name="Main-Variables"></a>
<div class="header">
<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>
+Next: <a href="#generic_002eLANG_002ehtml" accesskey="n"
rel="next">generic.LANG.html</a>, Previous: <a href="#Special-Targets"
accesskey="p" rel="previous">Special Targets</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>
+<h3 class="section">2.4 Defining Articles to Be Built</h3>
<a name="index-variables-1"></a>
<a name="index-gnun_002emk-1"></a>
@@ -1153,729 +1162,344 @@
</dl>
<hr>
-<a name="PO-Files"></a>
+<a name="generic_002eLANG_002ehtml"></a>
<div class="header">
<p>
-Next: <a href="#Webmaster-Tips" accesskey="n" rel="next">Webmaster Tips</a>,
Previous: <a href="#Main-Variables" accesskey="p" rel="previous">Main
Variables</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>
+Next: <a href="#languages_002etxt" accesskey="n" rel="next">languages.txt</a>,
Previous: <a href="#Main-Variables" accesskey="p" rel="previous">Main
Variables</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="Working-with-PO-Files"></a>
-<h3 class="section">2.3 Working with PO Files</h3>
+<a name="The-generic_002elang_002ehtml-File"></a>
+<h3 class="section">2.5 The <samp>generic.<var>lang</var>.html</samp> File</h3>
+<a name="index-team-information"></a>
+<a name="index-generic-notice_002c-translations"></a>
-<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>The files <samp>server/gnun/generic.<var>lang</var>.html</samp> are
special: if
+no such file exists for your language, an empty file will be created
+(and added to the repository if specified <code>VCS=yes</code>). This file
+is optional, and should contain a short message in your native
+language, ideally providing more information about the translation
+team or where to report bugs. For example:
</p>
-<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="#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="#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="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="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="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="7">Compendia</a>:</td><td> </td><td align="left"
valign="top">Using translation memory.
-</td></tr>
-<tr><td align="left" valign="top">• <a href="#Sitemap"
accesskey="8">Sitemap</a>:</td><td> </td><td align="left"
valign="top">Specifics of sitemap generation.
-</td></tr>
-<tr><td align="left" valign="top">• <a href="#GNU-News" accesskey="9">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>
+<div class="example">
+<pre class="example"><p>To join the Fooish translation team, see <a
+href="http://gnu.org/server/standards/translations/foo">the
+Foo team homepage</a>.</p>
+</pre></div>
+<p>The contents of <samp>generic.<var>lang</var>.html</samp> is injected right
after
+the translators’ credits, if any, and before the timestamp. It should
+be valid HTML markup.
+</p>
+<p>When you modify this file, for example, adding a message to the
+existing empty file or changing a URL, such modification will affect
+<em>all</em> articles of the language <var>lang</var> in
+<samp>generic.<var>lang</var>.html</samp>. The next time a build occurs, all
+translations of the language code <var>lang</var> (i.e. all
+<samp>.<var>lang</var>.html</samp>, including the homepage), will be modified
to
+include the contents of this special file.
+</p>
<hr>
-<a name="New-Translation"></a>
+<a name="languages_002etxt"></a>
<div class="header">
<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>
+Next: <a href="#Compendia" accesskey="n" rel="next">Compendia</a>, Previous:
<a href="#generic_002eLANG_002ehtml" accesskey="p"
rel="previous">generic.LANG.html</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="Starting-a-New-Translation"></a>
-<h4 class="subsection">2.3.1 Starting a New Translation</h4>
-<a name="index-translation_002c-new"></a>
-<a name="index-new-translation"></a>
+<a name="The-languages_002etxt-File"></a>
+<h3 class="section">2.6 The <samp>languages.txt</samp> File</h3>
-<p>To start a new translation, the most simple way is to copy the
-existing POT as <samp>article.<var>lang</var>.po</samp>, where <var>lang</var>
is your
-language code. For example, to prepare for a new translation of the
-essay <a
href="http://www.gnu.org/philosophy/free-sw.html";>http://www.gnu.org/philosophy/free-sw.html</a>,
you can
-simply do <code>cd philosophy/po; cp free-sw.pot
-free-sw.<var>lang</var>.po</code> and then edit the latter. If
-<samp>free-sw.pot</samp> does not exist it is because either the article is
-not yet “templated” (i.e. migrated to the new style), or the GNUN
-maintainers have not yet added it to the value of the appropriate
-variable in <samp>server/gnun/gnun.mk</samp>. In that case, just ask them
-to do the necessary in order the POT to be generated.
-</p>
-<p>You could also use the <code>msginit</code> utility that would populate
-the PO file header with the right information, provided your
-environment is set up correctly. See <a
href="http://www.gnu.org/software/gettext/manual/gettext.html#msginit-Invocation";>msginit
Invocation</a> in <cite>GNU gettext tools</cite>.
-</p>
-<p>GNUN also provides a customized script to automatically fill more
-header fields. See <a href="#gnun_002dinit_002dpo">gnun-init-po</a>.
+<p>The file <samp>server/gnun/languages.txt</samp> is used when generating
+lists of translations; those lists are subsequently included in all
+translations of the article. Every line in the file is either a
+comment (when it begins with “#”) or a definition for a language.
A
+language is defined by three <tt class="key">TAB</tt>-separated fields. The
first field
+defines the language suffix; it is used in file names and in texts of
+the links. The second field is the name of the language in English;
+it is used in HTML comments. The third field defines the name of the
+language in that language itself; it is used in texts of the links,
+and it should be in UTF-8. For example:
</p>
-<p>The PO file header as generated usually looks like this:
+<div class="example">
+<pre class="example">de German Deutsch
+</pre></div>
+
+<p>The generated list of translations may look like this:
</p>
<div class="example">
-<pre class="example"># SOME DESCRIPTIVE TITLE
-# Copyright (C) YEAR Free Software Foundation, Inc.
-# This file is distributed under the same license as the PACKAGE package.
-# FIRST AUTHOR <address@hidden>, YEAR.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2008-02-06 16:25-0500\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <address@hidden>\n"
-"Language-Team: LANGUAGE <address@hidden>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=CHARSET\n"
-"Content-Transfer-Encoding: ENCODING\n"
+<pre class="example"><!-- begin translinks file -->
+<div id="translations">
+<ul class="translations-list">
+<!-- German -->
+<li><a
href="/distros/screenshot.de.html">Deutsch</a>&nbsp;[de]</li>
+<!-- English -->
+<li><a
href="/distros/screenshot.html">English</a>&nbsp;[en]</li>
+<!-- Polish -->
+<li><a
href="/distros/screenshot.pl.html">polski</a>&nbsp;[pl]</li>
+</ul>
+</div> <!-- id="translations" -->
+<!-- end translinks file -->
</pre></div>
-<p>You have to edit the header to match the already established
-conventions, and the rules for gnu.org translations. For reference,
-here is a list with all fields explained:
+<hr>
+<a name="Compendia"></a>
+<div class="header">
+<p>
+Next: <a href="#Sitemap" accesskey="n" rel="next">Sitemap</a>, Previous: <a
href="#languages_002etxt" accesskey="p" rel="previous">languages.txt</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="Using-Compendia"></a>
+<h3 class="section">2.7 Using Compendia</h3>
+<a name="index-compendia"></a>
+<a name="index-translation-memory"></a>
+<a name="index-exclude_002epot"></a>
+<a name="index-compendium_002epot"></a>
+
+<p>Compendium is a PO file including translations for common strings; it is
+used to fill other PO files. See <a
href="http://www.gnu.org/software/gettext/manual/gettext.html#Compendium";>Using
+Translation Compendia</a> in <cite>GNU gettext tools</cite>. One example of
such
+common strings is the footer
+text about reporting bugs and sending inquiries: when a webmaster
+updates footer texts in an article, GNUN will use compendia to
+automatically fill the translations for the new version of the strings.
</p>
-<a name="index-PO-headers"></a>
-<dl compact="compact">
-<dt>‘<samp>Project-Id-Version</samp>’</dt>
-<dd><p>Add here the filename of the original article, without the
-sub-directory, like “body-include-1.html” or
“free-sw.html”.
+<p>GNUN uses compendia located in the <samp>server/gnun/compendia</samp>
+directory of the ‘www’ web repository. There are two kinds of
+compendia: <samp>master.<var>lang</var>.po</samp> and
+<samp>compendium.<var>lang</var>.po</samp>.
</p>
-</dd>
-<dt>‘<samp>POT-Creation-Date</samp>’</dt>
-<dd><p>Do not edit this field, it is already set when the POT is created.
+<p>The first kind, <samp>master.<var>lang</var>.po</samp>, can be used to
+simultaneously update all occurrences of the translations of a given
+string. Translations from this file will override the translations from
+<samp><var>article</var>.<var>lang</var>.po</samp>. When
<samp>master.<var>lang</var>.po</samp> is
+updated, the translations will be rebuilt. GNUN doesn’t modify this
+kind of compendia.
</p>
-</dd>
-<dt>‘<samp>PO-Revision-Date</samp>’</dt>
-<dd><p>Likewise, do not edit. This field is automatically filled in when you
-save the file with any decent PO editor.
+<p>The second kind, <samp>compendium.<var>lang</var>.po</samp>, is updated
+automatically. GNUN finds strings that repeat many times in POTs of
+articles and collects them in <samp>compendium.pot</samp>. Then it checks
+all available <samp><var>article</var>.<var>lang</var>.po</samp> files for
+translations of those strings and generates
+<samp>compendium.<var>lang</var>.po</samp>. This file is also used to fill
+missing translations, but it doesn’t override the translations from
+<samp><var>article</var>.<var>lang</var>.po</samp>, and the strings coming from
+<samp>compendium.<var>lang</var>.po</samp> are always marked as
“fuzzy” to
+prevent propagation of translations that may be wrong in a different
+context.
</p>
-</dd>
-<dt>‘<samp>Last-Translator</samp>’</dt>
-<dd><p>The name and email address of the last translator who has edited the
-translation. Pay attention that normally this is the name of a member
-of your team, it can be the translation team leader if he/she was the
-person who updated the translation. For example:
+<p>When updating <samp>compendium.pot</samp>, some strings should be excluded
+even though they repeat in the POT files many times—for instance,
+GNUN slots for translators’ notes. See <a href="#Notes-Slot">Notes
Slot</a>. They are not
+real translations, this is why they are likely to be different for
+different articles. In order to avoid including them in compendia,
+GNUN checks a specific file, <samp>exclude.pot</samp>, and when that file
+contains the string, it won’t be added to <samp>compendium.pot</samp>.
</p>
-<div class="example">
-<pre class="example">Elvis Parsley <address@hidden>
-</pre></div>
+<hr>
+<a name="Sitemap"></a>
+<div class="header">
+<p>
+Next: <a href="#GNU-News" accesskey="n" rel="next">GNU News</a>, Previous: <a
href="#Compendia" accesskey="p" rel="previous">Compendia</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="Building-Sitemap"></a>
+<h3 class="section">2.8 Building Sitemap</h3>
+<a name="index-sitemap-1"></a>
-</dd>
-<dt>‘<samp>Language-Team</samp>’</dt>
-<dd><p>This field should contain the mailing list on which the translation
-team can be reached—usually <a
href="mailto:www-LANG-…@gnu.org";>www-LANG-…@gnu.org</a>.
-Example:
+<p>Sitemaps differ from regular pages in two respects:
</p>
-<div class="example">
-<pre class="example">Czech <address@hidden>
-</pre></div>
+<ol>
+<li> They are typically regenerated automatically from the texts of the
+articles.
-</dd>
-<dt>‘<samp>MIME-Version</samp>’</dt>
-<dd><p>Leave it like it is.
+</li><li> They mostly consist of links, therefore significant part of their
text
+should come to translations without any changes.
+
+</li></ol>
+
+<p>Also, sitemaps contain many translatable messages, so it is desirable
+to eliminate manual work where possible.
</p>
-</dd>
-<dt>‘<samp>Content-Type</samp>’</dt>
-<dd><p>Usually this is <code>text/plain; charset=UTF-8</code>; change the
charset
-accordingly.
+<p>In order to take this into account, GNUN provides the <code>sitemap</code>
+variable in <samp>gnun.mk</samp>. All articles listed in <code>sitemap</code>
are
+rebuilt using an additional compendium (when present),
+<samp>server/gnun/compendia/sitemap-compendium.<var>lang</var>.po</samp>.
+</p>
+<p>Those additional compendia are supposed to be compiled outside of GNUN
+by the same tool that generates the sitemap. It is responsibility of
+that tool to provide the compendia with reasonable translations whose
+<code>msgid</code>s match those generated by PO4A when processing the
+English version of the sitemap.
</p>
-</dd>
-<dt>‘<samp>Content-Transfer-Encoding</samp>’</dt>
-<dd><p>Set this to <code>8bit</code>. Note that the PO file header ends with
this
-field, and it should contain a newline (‘<samp>\n</samp>’).
Unfortunately, some
-PO editors remove the newline, which causes an unnecessary revision when
-the file is automatically modified by GNUN’s rules.
-</p></dd>
-</dl>
-<p>Here is an example of a properly edited header:
+<hr>
+<a name="GNU-News"></a>
+<div class="header">
+<p>
+Previous: <a href="#Sitemap" accesskey="p" rel="previous">Sitemap</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="Special-Handling-for-GNU-News"></a>
+<h3 class="section">2.9 Special Handling for GNU News</h3>
+<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>
-<div class="example">
-<pre class="example"># Bulgarian translation of
http://www.gnu.org/philosophy/free-sw.html
-# Copyright (C) 2008 Free Software Foundation, Inc.
-# This file is distributed under the same license as the gnu.org article.
-# Yavor Doganov <address@hidden>, 2008.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: free-sw.html\n"
-"POT-Creation-Date: 2008-02-06 16:25-0500\n"
-"PO-Revision-Date: 2008-02-09 15:23+0200\n"
-"Last-Translator: Yavor Doganov <address@hidden>\n"
-"Language-Team: Bulgarian <address@hidden>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8-bit\n"
-</pre></div>
+<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="Team_0027s-Repository"></a>
+<div class="header">
+<p>
+Next: <a href="#PO-Files" accesskey="n" rel="next">PO Files</a>, Previous: <a
href="#Usage" accesskey="p" rel="previous">Usage</a>, Up: <a href="#Top"
accesskey="u" rel="up">Top</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>
+<h2 class="chapter">3 Maintaining Translations in Your Team’s
Repository</h2>
+<a name="index-project-repository"></a>
+<a name="index-repository_002c-translation-project"></a>
+<a name="index-team-maintenance"></a>
+<a name="index-GNUmakefile_002eteam"></a>
-<p>Notice the absence of the “fuzzy” marker; you should
“unfuzzy” the
-header after entering the necessary information (this is done by
-simply pressing <tt class="key">TAB</tt> in PO mode).
+<p>GNUN operates on the “official” Web repository of the Savannah
project
+‘www’, where normally only the coordinators of translation teams
have
+write access. However, all translation teams have their own projects,
+so it is possible to take advantage of Savannah as a hosting facility to
+make the team work more comfortable.
</p>
-<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="#publish">publish</a>).
+<p>The PO files provide an excellent and natural way to review each
other’s
+translations, because the translation appears right below the original
+message. Mutual reviews and proof-reading of translations is a crucial
+part of the process. Furthermore, team work is great for the community
+spirit; automating some of the operations also result in more time for
+all members to concentrate on the important tasks.
</p>
-<p>There are some special messages that appear in the POT and PO:
+<p>The file <samp>GNUmakefile.team</samp> in the
‘<samp>gnun</samp>’ package is a
+template, aimed for all translation teams who wish to use their own
+project’s repository as a place to keep their draft translations, until
+they ripe and are ready to be installed officially.
</p>
-<dl compact="compact">
-<dd><a name="index-notes_002c-translators"></a>
-<a name="index-translators_0027-notes"></a>
-<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:
+<a name="index-team-workflow"></a>
+<p>The following diagram illustrates a typical workflow—it is applicable
+for small, medium and large teams:
</p>
<div class="example">
-<pre class="example">msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
-msgstr " "
+<pre class="example">+----------+ +-------------------+
+| ``www'' | | ``www-LANG'' |
+| Web |------>---->-------|Sources repository |
+|repository| automatic merge +-------------------+
++----------+ | | |
+ | | | `-- Member A
+ +------------<----<-------------' |
+ Leader `---Member B
</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 if you do not want your name to appear there.
-See <a href="#Credits-Slot">Credits Slot</a>.
-</p></dd>
-</dl>
-
-<a name="index-wrapping-long-lines"></a>
-<a name="index-long-lines_002c-wrap"></a>
-<p>Most of the PO editors do not wrap long lines that inevitably appear in
-<code>msgstr</code>s. If that happens, long lines make reading subsequent
-diffs harder, and are generally annoying for most people. If this issue
-bothers you, you can “normalize” the already finished PO
translation
-by executing on the command line <code>msgcat -o <var>file</var>.po
-<var>file</var>.po</code>, before installing it in the repository. Either
way, the
-build system will treat it is a valid PO file.
+<p>All members and the team leader commit in their project’s
+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; 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>
-<p>For those lucky Emacs users, here is a code snippet that you can put
-in your <samp>.emacs</samp>; doing <kbd>M-x po-wrap</kbd> while in PO mode will
-wrap all long lines:
+<p>To take advantage of this semi-automation, rename this template
+<samp>GNUmakefile.team</samp> as <samp>GNUmakefile</samp> and install it in
the root
+of your project’s Sources repository. Then create directories and
+sub-directories exactly as they are in ‘www’. Do not create the
+<samp>/po</samp> sub-directories; they are redundant here. Instead, install
+the PO files in the normal locations where the corresponding
+<samp>.<var>lang</var>.html</samp> resides in ‘www’, for example:
</p>
-<div class="lisp">
-<pre class="lisp">(defun po-wrap ()
- "Filter current po-mode buffer through `msgcat' tool to wrap all
lines."
- (interactive)
- (if (eq major-mode 'po-mode)
- (let ((tmp-file (make-temp-file "po-wrap."))
- (tmp-buf (generate-new-buffer "*temp*")))
- (unwind-protect
- (progn
- (write-region (point-min) (point-max) tmp-file nil 1)
- (if (zerop
- (call-process
- "msgcat" nil tmp-buf t (shell-quote-argument
tmp-file)))
- (let ((saved (point))
- (inhibit-read-only t))
- (delete-region (point-min) (point-max))
- (insert-buffer tmp-buf)
- (goto-char (min saved (point-max))))
- (with-current-buffer tmp-buf
- (error (buffer-string)))))
- (kill-buffer tmp-buf)
- (delete-file tmp-file)))))
+<div class="example">
+<pre class="example">Root
+ |
+ |--GNUmakefile
+ |--home.<var>lang</var>.po
+ |--…
+ |--gnu
+ | |
+ | |
+ | +--linux-and-gnu.<var>lang</var>.po
+ | +--manifesto.<var>lang</var>.po
+ | +--…
+ |
+ |
+ +--philosophy
+ | |
+ | |
+ | +--free-sw.<var>lang</var>.po
+ | +--not-ipr.<var>lang</var>.po
+ | +--open-source-misses-the-point.<var>lang</var>.po
+ | +--…
+ |
+ +--…
</pre></div>
-<p>It is highly desirable that you check if the PO file you finished
-translating (or editing) is valid, before committing it. This is done
-by running <code>msgfmt -cv -o /dev/null <var>file</var></code> or by simply
-pressing <kbd>V</kbd> in PO mode. The build system automatically verifies
-each PO file when invoked with <code>VALIDATE=yes</code>, but you won’t
get a
-warm and fuzzy feeling if a stupid typo you made halts the whole update
-of all translations. Such things happen to everyone, so it is a good
-practice to check before you actually commit.
+<p>The next sections explain how to adopt the makefile for your team and
+how to invoke a “build”.
</p>
<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top">• <a href="#Notes-Slot"
accesskey="1">Notes Slot</a>:</td><td> </td><td align="left"
valign="top">How to handle translator’s notes.
+<tr><td align="left" valign="top">• <a
href="#GNUmakefile_002eteam-Variables" accesskey="1">GNUmakefile.team
Variables</a>:</td><td> </td><td align="left" valign="top">
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Credits-Slot"
accesskey="2">Credits Slot</a>:</td><td> </td><td align="left"
valign="top">Translator’s credits.
+<tr><td align="left" valign="top">• <a
href="#GNUmakefile_002eteam-Targets" accesskey="2">GNUmakefile.team
Targets</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#GNUmakefile_002eteam-and-Cron" accesskey="3">GNUmakefile.team and
Cron</a>:</td><td> </td><td align="left" valign="top">
</td></tr>
</table>
<hr>
-<a name="Notes-Slot"></a>
+<a name="GNUmakefile_002eteam-Variables"></a>
<div class="header">
<p>
-Next: <a href="#Credits-Slot" accesskey="n" rel="next">Credits Slot</a>, Up:
<a href="#New-Translation" accesskey="u" rel="up">New Translation</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="#GNUmakefile_002eteam-Targets" accesskey="n"
rel="next">GNUmakefile.team Targets</a>, Up: <a href="#Team_0027s-Repository"
accesskey="u" rel="up">Team's Repository</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-Special-Slot-for-Translator_0027s-Notes"></a>
-<h4 class="subsubsection">2.3.1.1 The Special Slot for Translator’s
Notes</h4>
-<a name="index-notes_002c-translators-1"></a>
-<a name="index-translators_0027-notes-1"></a>
+<a name="Adopting-GNUmakefile_002eteam-for-a-Specific-Team"></a>
+<h3 class="section">3.1 Adopting <samp>GNUmakefile.team</samp> for a Specific
Team</h3>
-<p>Sometimes it is necessary to complement the translation of an essay
-with translator’s notes. The special message <code>*GNUN-SLOT:
-TRANSLATOR'S NOTES*</code> is designed to serve this purpose. If your
-translation doesn’t have notes, you should “translate” the
-<code>msgstr</code> as a space (<tt class="key">SPC</tt>)—otherwise the
PO file will be
-considered incomplete, which is not what you want. Here is an example
-how to use translators’ notes in a PO file:
-</p>
-<div class="example">
-<pre class="example"># type: Content of: <p>
-msgid ""
-"To understand the concept, you should think of <q>free</q>
"
-"as in <q>free speech,</q> not as in <q>free
beer.</q>"
-msgstr ""
-"Translated message, where you want to clarify beer<sup><a "
-"href=\"#TransNote1\">1</a></sup>, presumably
because the "
-"expression in your language is different"
-…
-…
-# type: Content of: <div>
-#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
-msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
-msgstr ""
-"<h3>Translator's notes</h3>\n"
-"<ol>\n"
-"<li id=\"TransNote1\">Note clarifying the
text.</li>\n"
-"</ol>\n"
-</pre></div>
-
-<p>Certainly, everything in the <code>msgstr</code>s should be in your native
-language; we use English here in order the example to be understood by
-everyone. If you have more notes, each subsequent one should be with
-incremented number, i.e. ‘<samp>TransNote2</samp>’,
‘<samp>TransNote3</samp>’, etc. and
-you have to add them as more <code><li></code> elements accordingly.
-</p>
-<p>Do not worry about the <code>\n</code> character—it is inserted
-automatically when you press <tt class="key">RET</tt>. It is not compulsory
that
-notes start on a new line, this is the recommended way simply because
-it is easier to edit them.
-</p>
-<p>It is important to follow this specification, because notes will look
-consistently in all languages and will be clearly distinguishable from
-authors’ footnotes, if any. Furthermore, it would be easier to define
-a special CSS class for them, and also to convert the
-translations in other formats such as Texinfo—when these features
-are implemented.
-</p>
-<hr>
-<a name="Credits-Slot"></a>
-<div class="header">
-<p>
-Previous: <a href="#Notes-Slot" accesskey="p" rel="previous">Notes Slot</a>,
Up: <a href="#New-Translation" accesskey="u" rel="up">New Translation</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-Special-Slot-for-Translator_0027s-Credits"></a>
-<h4 class="subsubsection">2.3.1.2 The Special Slot for Translator’s
Credits</h4>
-<a name="index-credits_002c-translators-1"></a>
-<a name="index-translators_0027-credits-1"></a>
-
-<p>Most of the translators usually put their name under the translation,
-in the “footer” area. This is entirely acceptable, since some
-readers prefer to send buggestions directly to the translator. Also,
-giving credit where credit is due is a natural thing.
-</p>
-<p>Like the previous slot, you should “translate” it as a <tt
class="key">SPC</tt> if
-you don’t want your name to appear there.
-</p>
-<p>Here is an example of the recommended way to specify credits:
-</p>
-<div class="example">
-<pre class="example"><b>Traduction</b>: Benjamin Drieu
-<a
href="mailto:address@hidden">&lt;address@hidden&gt;</a>,
-2007, 2008.
-</pre></div>
-
-<p>It is highly desirable to use this form, but you may omit the email
-address or add a link to translator’s noncommercial personal home page,
-provided that the translation team leader ensures that it constantly
-meets the linking criteria for gnu.org. Please follow the FSF HTML
-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="#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.3 Transforming Existing Translation in PO
Format</h4>
-<a name="index-migration_002c-translations"></a>
-<a name="index-conversion-of-existing-translations"></a>
-
-<p>Migrating an existing translation to a PO file format is basically
-editing the header as described in the previous section, and
-populating each of the messages by copying the already translated text
-and/or markup from the existing translation in HTML format in the
-relevant message.
-</p>
-<p>Typically, you will visit <samp>po/foo.<var>lang</var>.po</samp> (in PO
mode) and
-<samp>foo.<var>lang</var>.html</samp> (in HTML mode) in another buffer. Then
you
-can copy a paragraph or an element from the latter and yank it in the
-relevant message in the former. Be extra careful, since this is the
-time to check <em>precisely</em> that the translation corresponds to the
-original. Further changes will be reflected, but if your “initial”
-PO file is not a 100% match, that would not necessarily mean that it
-is an improvement. Since it is very easy to do this kind of check,
-because the relevant <code>msgid</code> and <code>msgstr</code> appear one
above
-the other in the same buffer (or the similar concept in other PO
-editors), please <em>do</em> perform this initial sanity check even if
-you are confident that the translation you have been yanking strings
-from is a completely up-to-date translation.
-</p>
-<p>There is also a semi-automatic way to produce an initial PO file. You
-checkout the revision of the English page, <samp>foo.html</samp>, that
-corresponds to the latest revision of the translation,
-<samp>foo.<var>lang</var>.html</samp>. Then you run
<code>gnun-preconvert</code>
-which invokes <code>po4a-gettextize</code> (See <a
href="#gnun_002dpreconvert">gnun-preconvert</a>.):
-</p>
-<div class="example">
-<pre class="example">gnun-preconvert foo.lang.html foo.html
-</pre></div>
-
-<p>If some passages in <samp>foo.<var>lang</var>.html</samp> don’t match
the structure
-of <samp>foo.html</samp>, error messages will be displayed. Check them,
-adjust the files and try again. When you succeed, the result will be
-written to foo.lang.po. After that, run
-<code>gnun-merge-preconverted</code> (See <a
href="#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a>.):
-</p>
-<div class="example">
-<pre class="example">gnun-merge-preconverted -C compendium.lang.po foo.lang.po
foo.pot
-</pre></div>
-
-<p>If you have no compendium, just omit the “<code>-C
-compendium.lang.po</code>” part.
-</p>
-<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
-facilitate checking.
-</p>
-<p>There is no need to delete the existing HTML translation, GNUN will
-automatically overwrite it. The only thing a translator should do is to
-commit the PO file in the repository.
-</p>
-<p>When an essay has been translated by several people through the years,
-it is important that this information is recorded and reflected in the
-PO file. In the future, special targets may be added to enable the FSF
-to check who translated a particular article, and when.
-</p>
-<p>A recommended way to do this is as follows:
-</p>
-<div class="example">
-<pre class="example"># French translation of
http://www.gnu.org/philosophy/bsd.html
-# Copyright (C) 2006, 2007, 2008 Free Software Foundation, Inc.
-# This file is distributed under the same license as the gnu.org article.
-# Cédric Corazza <address@hidden>, 2006, 2008.
-# Jerôme Dominguez <address@hidden>, 2007.
-</pre></div>
-
-<p>In this example, it is clear that Cédric made the initial
-translation, Jerôme made some changes in 2007, and the original
-translator returned in 2008 and continued maintaining it.
-</p>
-<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="#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.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>
-
-<p>The files <samp>server/gnun/generic.<var>lang</var>.html</samp> are
special: if
-no such file exists for your language, an empty file will be created
-(and added to the repository if specified <code>VCS=yes</code>). This file
-is optional, and should contain a short message in your native
-language, ideally providing more information about the translation
-team or where to report bugs. For example:
-</p>
-<div class="example">
-<pre class="example"><p>To join the Fooish translation team, see <a
-href="http://gnu.org/server/standards/translations/foo">the
-Foo team homepage</a>.</p>
-</pre></div>
-
-<p>The contents of <samp>generic.<var>lang</var>.html</samp> is injected right
after
-the translators’ credits, if any, and before the timestamp. It should
-be valid HTML markup.
-</p>
-<p>When you modify this file, for example, adding a message to the
-existing empty file or changing a URL, such modification will affect
-<em>all</em> articles of the language <var>lang</var> in
-<samp>generic.<var>lang</var>.html</samp>. The next time a build occurs, all
-translations of the language code <var>lang</var> (i.e. all
-<samp>.<var>lang</var>.html</samp>, including the homepage), will be modified
to
-include the contents of this special file.
-</p>
-<hr>
-<a name="languages_002etxt"></a>
-<div class="header">
-<p>
-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.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
-translations of the article. Every line in the file is either a
-comment (when it begins with “#”) or a definition for a language.
A
-language is defined by three <tt class="key">TAB</tt>-separated fields. The
first field
-defines the language suffix; it is used in file names and in texts of
-the links. The second field is the name of the language in English;
-it is used in HTML comments. The third field defines the name of the
-language in that language itself; it is used in texts of the links,
-and it should be in UTF-8. For example:
-</p>
-<div class="example">
-<pre class="example">de German Deutsch
-</pre></div>
-
-<p>The generated list of translations may look like this:
-</p>
-<div class="example">
-<pre class="example"><!-- begin translinks file -->
-<div id="translations">
-<ul class="translations-list">
-<!-- German -->
-<li><a
href="/distros/screenshot.de.html">Deutsch</a>&nbsp;[de]</li>
-<!-- English -->
-<li><a
href="/distros/screenshot.html">English</a>&nbsp;[en]</li>
-<!-- Polish -->
-<li><a
href="/distros/screenshot.pl.html">polski</a>&nbsp;[pl]</li>
-</ul>
-</div> <!-- id="translations" -->
-<!-- end translinks file -->
-</pre></div>
-
-<hr>
-<a name="PO-Files-and-Team"></a>
-<div class="header">
-<p>
-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.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>
-<a name="index-GNUmakefile_002eteam"></a>
-
-<p>GNUN operates on the “official” Web repository of the Savannah
project
-‘www’, where normally only the coordinators of translation teams
have
-write access. However, all translation teams have their own projects,
-so it is possible to take advantage of Savannah as a hosting facility to
-make the team work more comfortable.
-</p>
-<p>The PO files provide an excellent and natural way to review each
other’s
-translations, because the translation appears right below the original
-message. Mutual reviews and proof-reading of translations is a crucial
-part of the process. Furthermore, team work is great for the community
-spirit; automating some of the operations also result in more time for
-all members to concentrate on the important tasks.
-</p>
-<p>The file <samp>GNUmakefile.team</samp> in the
‘<samp>gnun</samp>’ package is a
-template, aimed for all translation teams who wish to use their own
-project’s repository as a place to keep their draft translations, until
-they ripe and are ready to be installed officially.
-</p>
-<a name="index-team-workflow"></a>
-<p>The following diagram illustrates a typical workflow—it is applicable
-for small, medium and large teams:
-</p>
-<div class="example">
-<pre class="example">+----------+ +-------------------+
-| ``www'' | | ``www-LANG'' |
-| Web |------>---->-------|Sources repository |
-|repository| automatic merge +-------------------+
-+----------+ | | |
- | | | `-- Member A
- +------------<----<-------------' |
- Leader `---Member B
-</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 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; 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>
-<p>To take advantage of this semi-automation, rename this template
-<samp>GNUmakefile.team</samp> as <samp>GNUmakefile</samp> and install it in
the root
-of your project’s Sources repository. Then create directories and
-sub-directories exactly as they are in ‘www’. Do not create the
-<samp>/po</samp> sub-directories; they are redundant here. Instead, install
-the PO files in the normal locations where the corresponding
-<samp>.<var>lang</var>.html</samp> resides in ‘www’, for example:
-</p>
-<div class="example">
-<pre class="example">Root
- |
- |--GNUmakefile
- |--home.<var>lang</var>.po
- |--…
- |--gnu
- | |
- | |
- | +--linux-and-gnu.<var>lang</var>.po
- | +--manifesto.<var>lang</var>.po
- | +--…
- |
- |
- +--philosophy
- | |
- | |
- | +--free-sw.<var>lang</var>.po
- | +--not-ipr.<var>lang</var>.po
- | +--open-source-misses-the-point.<var>lang</var>.po
- | +--…
- |
- +--…
-</pre></div>
-
-<p>The next sections explain how to adopt the makefile for your team and
-how to invoke a “build”.
-</p>
-<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top">• <a
href="#GNUmakefile_002eteam-Variables" accesskey="1">GNUmakefile.team
Variables</a>:</td><td> </td><td align="left" valign="top">
-</td></tr>
-<tr><td align="left" valign="top">• <a
href="#GNUmakefile_002eteam-Targets" accesskey="2">GNUmakefile.team
Targets</a>:</td><td> </td><td align="left" valign="top">
-</td></tr>
-<tr><td align="left" valign="top">• <a
href="#GNUmakefile_002eteam-and-Cron" accesskey="3">GNUmakefile.team and
Cron</a>:</td><td> </td><td align="left" valign="top">
-</td></tr>
-</table>
-
-<hr>
-<a name="GNUmakefile_002eteam-Variables"></a>
-<div class="header">
-<p>
-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.6.1 Adopting <samp>GNUmakefile.team</samp> for a
Specific Team</h4>
-
-<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>
-<dd><p>The relative or absolute path to the working copy of the master
‘www’
-repository. So if you have checked out your project’s Sources
-repository at <samp>~/projects/www-<var>lang</var></samp> and the
‘www’ Web
-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>
-<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>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>
+<dd><p>The relative or absolute path to the working copy of the master
‘www’
+repository. So if you have checked out your project’s Sources
+repository at <samp>~/projects/www-<var>lang</var></samp> and the
‘www’ Web
+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>
+<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/
@@ -1944,10 +1568,10 @@
<a name="GNUmakefile_002eteam-Targets"></a>
<div class="header">
<p>
-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>
+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="#Team_0027s-Repository" accesskey="u" rel="up">Team's Repository</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.6.2 Targets in <samp>GNUmakefile.team</samp></h4>
+<h3 class="section">3.2 Targets in <samp>GNUmakefile.team</samp></h3>
<dl compact="compact">
<dt><code>update</code></dt>
@@ -2036,275 +1660,647 @@
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.
+<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>
+<dd><p>A convenience rule to re-wrap all files upto the standard length. Most
+PO editors leave the <code>msgstr</code> as a single long line after it has
+been edited, but GNUN will automatically re-wrap the file to the standard
+line length when it is processed. Wrapping long lines in PO files is a
+good practice as it avoids unnecessary revisions.
+</p>
+<p>This rule checks for all translations that have lines longer than 80,
+and runs <code>msgcat</code> accordingly to reformat them. For that
+reason, it is recommended that you wrap all long lines in the comment
+fields (e.g. the file header, including the copyright statement, and any
+other comments for specific messages), because <code>make format</code> will
+unnecessarily invoke <code>msgcat</code> for any file that has a longer
+line, wherever it may occur.
+</p>
+</dd>
+<dt><code>publish</code></dt>
+<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>.
+Usually, one would run <code>make publish</code> when one or a bunch of PO
+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 “fuzzy” messages and other
problems, if
+necessary.
+</p>
+<p>The <code>publish</code> rule does not depend on <code>sync</code>
explicitly,
+because that would be a nuisance for offline operations and basically
+unnecessary when the committer is fairly confident that there are no
+changes to (re-)merge. A hard dependency on <code>sync</code> would slow down
+the operation considerably.
+</p>
+<p>As usual, when committing to the official repository, it is always a
+good practice to examine the output of <code>cvs diff</code>.
+</p>
+<p>Invoking <code>make publish</code> prints warnings and does not actually
copy
+the affected file if the sub-directory in “www” is non-existent or
the
+corresponding <samp>.pot</samp> is missing.
+</p>
+<p>Typically, after an editing session (whether it involves actual editing
+or just merging contributions from team members), one would do:
+</p>
+<div class="example">
+<pre class="example">$ make sync VCS=yes
+$ make publish
+$ cd <var>wwwdir</var>
+$ cvs up
+(Add all new translations, if any.)
+ $ cvs add <var>file</var> …
+$ cvs diff
+$ cvs commit -m "Some descriptive message."
+</pre></div>
+
+</dd>
+<dt><code>clean</code></dt>
+<dd><p>Deletes all backup and auto-generated files.
+</p></dd>
+</dl>
+
+<p><code>make VCS=yes</code> is the recommended command to be run periodically.
+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. 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>
+<div class="header">
+<p>
+Previous: <a href="#GNUmakefile_002eteam-Targets" accesskey="p"
rel="previous">GNUmakefile.team Targets</a>, Up: <a
href="#Team_0027s-Repository" accesskey="u" rel="up">Team's Repository</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>
+<h3 class="section">3.3 Automatic Synchronization and Status Reports</h3>
+<a name="index-team-maintenance_002c-cron"></a>
+<a name="index-cron_002c-team-maintenance"></a>
+
+<p>It is convenient to invoke such synchronization automatically, for
+example once every day. If you have enabled commit notifications for
+the project’s repository, any new changes will be visible for
+subscribers. Here is an example crontab entry:
+</p>
+<div class="example">
+<pre class="example"># m h dom mon dow command
address@hidden cd $HOME/projects/www-<var>lang</var>; make VCS=yes
+</pre></div>
+
+<p>It is not necessary the job to be run on the team leader’s machine,
+since all team members have write access to their project repository.
+</p>
+<p>If desired, you could set up another job to report the status of the
+translations weekly or fortnightly, for example:
+</p>
+<div class="example">
+<pre class="example"># m h dom mon dow command
address@hidden cd $HOME/projects/www-<var>lang</var>; \
+ make report | mail -s "Weekly statistics" \
+ www-<var>lang</var>address@hidden
+</pre></div>
+
+<p><strong>Caution:</strong> Most cron implementations do not allow the
character
+‘\’ as a line continuation character—the example shown is
made that
+way for better readability.
+</p>
+<hr>
+<a name="PO-Files"></a>
+<div class="header">
+<p>
+Next: <a href="#Webmaster-Tips" accesskey="n" rel="next">Webmaster Tips</a>,
Previous: <a href="#Team_0027s-Repository" accesskey="p" rel="previous">Team's
Repository</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</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="Working-with-PO-Files"></a>
+<h2 class="chapter">4 Working with PO Files</h2>
+
+<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>
+<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="#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="#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><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+</pre></th></tr></table>
+
+<hr>
+<a name="New-Translation"></a>
+<div class="header">
+<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>
+<h3 class="section">4.1 Starting a New Translation</h3>
+<a name="index-translation_002c-new"></a>
+<a name="index-new-translation"></a>
+
+<p>To start a new translation, the most simple way is to copy the
+existing POT as <samp>article.<var>lang</var>.po</samp>, where <var>lang</var>
is your
+language code. For example, to prepare for a new translation of the
+essay <a
href="http://www.gnu.org/philosophy/free-sw.html";>http://www.gnu.org/philosophy/free-sw.html</a>,
you can
+simply do <code>cd philosophy/po; cp free-sw.pot
+free-sw.<var>lang</var>.po</code> and then edit the latter. If
+<samp>free-sw.pot</samp> does not exist it is because either the article is
+not yet “templated” (i.e. migrated to the new style), or the GNUN
+maintainers have not yet added it to the value of the appropriate
+variable in <samp>server/gnun/gnun.mk</samp>. In that case, just ask them
+to do the necessary in order the POT to be generated.
+</p>
+<p>You could also use the <code>msginit</code> utility that would populate
+the PO file header with the right information, provided your
+environment is set up correctly. See <a
href="http://www.gnu.org/software/gettext/manual/gettext.html#msginit-Invocation";>msginit
Invocation</a> in <cite>GNU gettext tools</cite>.
+</p>
+<p>GNUN also provides a customized script to automatically fill more
+header fields. See <a href="#gnun_002dinit_002dpo">gnun-init-po</a>.
+</p>
+<p>The PO file header as generated usually looks like this:
+</p>
+<div class="example">
+<pre class="example"># SOME DESCRIPTIVE TITLE
+# Copyright (C) YEAR Free Software Foundation, Inc.
+# This file is distributed under the same license as the PACKAGE package.
+# FIRST AUTHOR <address@hidden>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2008-02-06 16:25-0500\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <address@hidden>\n"
+"Language-Team: LANGUAGE <address@hidden>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=CHARSET\n"
+"Content-Transfer-Encoding: ENCODING\n"
+</pre></div>
+
+<p>You have to edit the header to match the already established
+conventions, and the rules for gnu.org translations. For reference,
+here is a list with all fields explained:
+</p>
+<a name="index-PO-headers"></a>
+<dl compact="compact">
+<dt>‘<samp>Project-Id-Version</samp>’</dt>
+<dd><p>Add here the filename of the original article, without the
+sub-directory, like “body-include-1.html” or
“free-sw.html”.
+</p>
+</dd>
+<dt>‘<samp>POT-Creation-Date</samp>’</dt>
+<dd><p>Do not edit this field, it is already set when the POT is created.
+</p>
+</dd>
+<dt>‘<samp>PO-Revision-Date</samp>’</dt>
+<dd><p>Likewise, do not edit. This field is automatically filled in when you
+save the file with any decent PO editor.
+</p>
+</dd>
+<dt>‘<samp>Last-Translator</samp>’</dt>
+<dd><p>The name and email address of the last translator who has edited the
+translation. Pay attention that normally this is the name of a member
+of your team, it can be the translation team leader if he/she was the
+person who updated the translation. For example:
+</p>
+<div class="example">
+<pre class="example">Elvis Parsley <address@hidden>
+</pre></div>
+
+</dd>
+<dt>‘<samp>Language-Team</samp>’</dt>
+<dd><p>This field should contain the mailing list on which the translation
+team can be reached—usually <a
href="mailto:www-LANG-…@gnu.org";>www-LANG-…@gnu.org</a>.
+Example:
+</p>
+<div class="example">
+<pre class="example">Czech <address@hidden>
+</pre></div>
+
+</dd>
+<dt>‘<samp>MIME-Version</samp>’</dt>
+<dd><p>Leave it like it is.
+</p>
+</dd>
+<dt>‘<samp>Content-Type</samp>’</dt>
+<dd><p>Usually this is <code>text/plain; charset=UTF-8</code>; change the
charset
+accordingly.
+</p>
+</dd>
+<dt>‘<samp>Content-Transfer-Encoding</samp>’</dt>
+<dd><p>Set this to <code>8bit</code>. Note that the PO file header ends with
this
+field, and it should contain a newline (‘<samp>\n</samp>’).
Unfortunately, some
+PO editors remove the newline, which causes an unnecessary revision when
+the file is automatically modified by GNUN’s rules.
</p></dd>
</dl>
-<p>This is an example of <samp>email-aliases</samp>:
+<p>Here is an example of a properly edited header:
</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 class="example"># Bulgarian translation of
http://www.gnu.org/philosophy/free-sw.html
+# Copyright (C) 2008 Free Software Foundation, Inc.
+# This file is distributed under the same license as the gnu.org article.
+# Yavor Doganov <address@hidden>, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: free-sw.html\n"
+"POT-Creation-Date: 2008-02-06 16:25-0500\n"
+"PO-Revision-Date: 2008-02-09 15:23+0200\n"
+"Last-Translator: Yavor Doganov <address@hidden>\n"
+"Language-Team: Bulgarian <address@hidden>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8-bit\n"
</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>
-<dd><p>A convenience rule to re-wrap all files upto the standard length. Most
-PO editors leave the <code>msgstr</code> as a single long line after it has
-been edited, but GNUN will automatically re-wrap the file to the standard
-line length when it is processed. Wrapping long lines in PO files is a
-good practice as it avoids unnecessary revisions.
-</p>
-<p>This rule checks for all translations that have lines longer than 80,
-and runs <code>msgcat</code> accordingly to reformat them. For that
-reason, it is recommended that you wrap all long lines in the comment
-fields (e.g. the file header, including the copyright statement, and any
-other comments for specific messages), because <code>make format</code> will
-unnecessarily invoke <code>msgcat</code> for any file that has a longer
-line, wherever it may occur.
-</p>
-</dd>
-<dt><code>publish</code></dt>
-<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>.
-Usually, one would run <code>make publish</code> when one or a bunch of PO
-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 “fuzzy” messages and other
problems, if
-necessary.
-</p>
-<p>The <code>publish</code> rule does not depend on <code>sync</code>
explicitly,
-because that would be a nuisance for offline operations and basically
-unnecessary when the committer is fairly confident that there are no
-changes to (re-)merge. A hard dependency on <code>sync</code> would slow down
-the operation considerably.
+<p>Notice the absence of the “fuzzy” marker; you should
“unfuzzy” the
+header after entering the necessary information (this is done by
+simply pressing <tt class="key">TAB</tt> in PO mode).
</p>
-<p>As usual, when committing to the official repository, it is always a
-good practice to examine the output of <code>cvs diff</code>.
+<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="#publish">publish</a>).
</p>
-<p>Invoking <code>make publish</code> prints warnings and does not actually
copy
-the affected file if the sub-directory in “www” is non-existent or
the
-corresponding <samp>.pot</samp> is missing.
+<p>There are some special messages that appear in the POT and PO:
</p>
-<p>Typically, after an editing session (whether it involves actual editing
-or just merging contributions from team members), one would do:
+<dl compact="compact">
+<dd><a name="index-notes_002c-translators"></a>
+<a name="index-translators_0027-notes"></a>
+<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:
</p>
<div class="example">
-<pre class="example">$ make sync VCS=yes
-$ make publish
-$ cd <var>wwwdir</var>
-$ cvs up
-(Add all new translations, if any.)
- $ cvs add <var>file</var> …
-$ cvs diff
-$ cvs commit -m "Some descriptive message."
+<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><code>clean</code></dt>
-<dd><p>Deletes all backup and auto-generated files.
+<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 if you do not want your name to appear there.
+See <a href="#Credits-Slot">Credits Slot</a>.
</p></dd>
</dl>
-<p><code>make VCS=yes</code> is the recommended command to be run periodically.
-To check the status of the translations, run <code>make report</code>.
+<a name="index-wrapping-long-lines"></a>
+<a name="index-long-lines_002c-wrap"></a>
+<p>Most of the PO editors do not wrap long lines that inevitably appear in
+<code>msgstr</code>s. If that happens, long lines make reading subsequent
+diffs harder, and are generally annoying for most people. If this issue
+bothers you, you can “normalize” the already finished PO
translation
+by executing on the command line <code>msgcat -o <var>file</var>.po
+<var>file</var>.po</code>, before installing it in the repository. Either
way, the
+build system will treat it is a valid PO file.
</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. 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>For those lucky Emacs users, here is a code snippet that you can put
+in your <samp>.emacs</samp>; doing <kbd>M-x po-wrap</kbd> while in PO mode will
+wrap all long lines:
+</p>
+<div class="lisp">
+<pre class="lisp">(defun po-wrap ()
+ "Filter current po-mode buffer through `msgcat' tool to wrap all
lines."
+ (interactive)
+ (if (eq major-mode 'po-mode)
+ (let ((tmp-file (make-temp-file "po-wrap."))
+ (tmp-buf (generate-new-buffer "*temp*")))
+ (unwind-protect
+ (progn
+ (write-region (point-min) (point-max) tmp-file nil 1)
+ (if (zerop
+ (call-process
+ "msgcat" nil tmp-buf t (shell-quote-argument
tmp-file)))
+ (let ((saved (point))
+ (inhibit-read-only t))
+ (delete-region (point-min) (point-max))
+ (insert-buffer tmp-buf)
+ (goto-char (min saved (point-max))))
+ (with-current-buffer tmp-buf
+ (error (buffer-string)))))
+ (kill-buffer tmp-buf)
+ (delete-file tmp-file)))))
+</pre></div>
+
+<p>It is highly desirable that you check if the PO file you finished
+translating (or editing) is valid, before committing it. This is done
+by running <code>msgfmt -cv -o /dev/null <var>file</var></code> or by simply
+pressing <kbd>V</kbd> in PO mode. The build system automatically verifies
+each PO file when invoked with <code>VALIDATE=yes</code>, but you won’t
get a
+warm and fuzzy feeling if a stupid typo you made halts the whole update
+of all translations. Such things happen to everyone, so it is a good
+practice to check before you actually commit.
</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#Notes-Slot"
accesskey="1">Notes Slot</a>:</td><td> </td><td align="left"
valign="top">How to handle translator’s notes.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Credits-Slot"
accesskey="2">Credits Slot</a>:</td><td> </td><td align="left"
valign="top">Translator’s credits.
+</td></tr>
+</table>
+
<hr>
-<a name="GNUmakefile_002eteam-and-Cron"></a>
+<a name="Notes-Slot"></a>
<div class="header">
<p>
-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>
+Next: <a href="#Credits-Slot" accesskey="n" rel="next">Credits Slot</a>, Up:
<a href="#New-Translation" accesskey="u" rel="up">New Translation</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.6.3 Automatic Synchronization and Status
Reports</h4>
-<a name="index-team-maintenance_002c-cron"></a>
-<a name="index-cron_002c-team-maintenance"></a>
+<a name="The-Special-Slot-for-Translator_0027s-Notes"></a>
+<h4 class="subsection">4.1.1 The Special Slot for Translator’s Notes</h4>
+<a name="index-notes_002c-translators-1"></a>
+<a name="index-translators_0027-notes-1"></a>
-<p>It is convenient to invoke such synchronization automatically, for
-example once every day. If you have enabled commit notifications for
-the project’s repository, any new changes will be visible for
-subscribers. Here is an example crontab entry:
+<p>Sometimes it is necessary to complement the translation of an essay
+with translator’s notes. The special message <code>*GNUN-SLOT:
+TRANSLATOR'S NOTES*</code> is designed to serve this purpose. If your
+translation doesn’t have notes, you should “translate” the
+<code>msgstr</code> as a space (<tt class="key">SPC</tt>)—otherwise the
PO file will be
+considered incomplete, which is not what you want. Here is an example
+how to use translators’ notes in a PO file:
</p>
<div class="example">
-<pre class="example"># m h dom mon dow command
address@hidden cd $HOME/projects/www-<var>lang</var>; make VCS=yes
+<pre class="example"># type: Content of: <p>
+msgid ""
+"To understand the concept, you should think of <q>free</q>
"
+"as in <q>free speech,</q> not as in <q>free
beer.</q>"
+msgstr ""
+"Translated message, where you want to clarify beer<sup><a "
+"href=\"#TransNote1\">1</a></sup>, presumably
because the "
+"expression in your language is different"
+…
+…
+# type: Content of: <div>
+#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
+msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
+msgstr ""
+"<h3>Translator's notes</h3>\n"
+"<ol>\n"
+"<li id=\"TransNote1\">Note clarifying the
text.</li>\n"
+"</ol>\n"
</pre></div>
-<p>It is not necessary the job to be run on the team leader’s machine,
-since all team members have write access to their project repository.
+<p>Certainly, everything in the <code>msgstr</code>s should be in your native
+language; we use English here in order the example to be understood by
+everyone. If you have more notes, each subsequent one should be with
+incremented number, i.e. ‘<samp>TransNote2</samp>’,
‘<samp>TransNote3</samp>’, etc. and
+you have to add them as more <code><li></code> elements accordingly.
</p>
-<p>If desired, you could set up another job to report the status of the
-translations weekly or fortnightly, for example:
+<p>Do not worry about the <code>\n</code> character—it is inserted
+automatically when you press <tt class="key">RET</tt>. It is not compulsory
that
+notes start on a new line, this is the recommended way simply because
+it is easier to edit them.
+</p>
+<p>It is important to follow this specification, because notes will look
+consistently in all languages and will be clearly distinguishable from
+authors’ footnotes, if any. Furthermore, it would be easier to define
+a special CSS class for them, and also to convert the
+translations in other formats such as Texinfo—when these features
+are implemented.
+</p>
+<hr>
+<a name="Credits-Slot"></a>
+<div class="header">
+<p>
+Previous: <a href="#Notes-Slot" accesskey="p" rel="previous">Notes Slot</a>,
Up: <a href="#New-Translation" accesskey="u" rel="up">New Translation</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-Special-Slot-for-Translator_0027s-Credits"></a>
+<h4 class="subsection">4.1.2 The Special Slot for Translator’s
Credits</h4>
+<a name="index-credits_002c-translators-1"></a>
+<a name="index-translators_0027-credits-1"></a>
+
+<p>Most of the translators usually put their name under the translation,
+in the “footer” area. This is entirely acceptable, since some
+readers prefer to send buggestions directly to the translator. Also,
+giving credit where credit is due is a natural thing.
+</p>
+<p>Like the previous slot, you should “translate” it as a <tt
class="key">SPC</tt> if
+you don’t want your name to appear there.
+</p>
+<p>Here is an example of the recommended way to specify credits:
</p>
<div class="example">
-<pre class="example"># m h dom mon dow command
address@hidden cd $HOME/projects/www-<var>lang</var>; \
- make report | mail -s "Weekly statistics" \
- www-<var>lang</var>address@hidden
+<pre class="example"><b>Traduction</b>: Benjamin Drieu
+<a
href="mailto:address@hidden">&lt;address@hidden&gt;</a>,
+2007, 2008.
</pre></div>
-<p><strong>Caution:</strong> Most cron implementations do not allow the
character
-‘\’ as a line continuation character—the example shown is
made that
-way for better readability.
+<p>It is highly desirable to use this form, but you may omit the email
+address or add a link to translator’s noncommercial personal home page,
+provided that the translation team leader ensures that it constantly
+meets the linking criteria for gnu.org. Please follow the FSF HTML
+Style Sheet when adding URIs or other information.
</p>
<hr>
-<a name="Compendia"></a>
+<a name="PO-Tips"></a>
<div class="header">
<p>
-Next: <a href="#Sitemap" accesskey="n" rel="next">Sitemap</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>
+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="Using-Compendia"></a>
-<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>
-<a name="index-compendium_002epot"></a>
+<a name="Useful-Hints-for-Editing-PO-Files"></a>
+<h3 class="section">4.2 Useful Hints for Editing PO Files</h3>
+<a name="index-tips_002c-translators"></a>
+<a name="index-recommendations_002c-PO-files"></a>
-<p>Compendium is a PO file including translations for common strings; it is
-used to fill other PO files. See <a
href="http://www.gnu.org/software/gettext/manual/gettext.html#Compendium";>Using
-Translation Compendia</a> in <cite>GNU gettext tools</cite>. One example of
such
-common strings is the footer
-text about reporting bugs and sending inquiries: when a webmaster
-updates footer texts in an article, GNUN will use compendia to
-automatically fill the translations for the new version of the strings.
-</p>
-<p>GNUN uses compendia located in the <samp>server/gnun/compendia</samp>
-directory of the ‘www’ web repository. There are two kinds of
-compendia: <samp>master.<var>lang</var>.po</samp> and
-<samp>compendium.<var>lang</var>.po</samp>.
-</p>
-<p>The first kind, <samp>master.<var>lang</var>.po</samp>, can be used to
-simultaneously update all occurrences of the translations of a given
-string. Translations from this file will override the translations from
-<samp><var>article</var>.<var>lang</var>.po</samp>. When
<samp>master.<var>lang</var>.po</samp> is
-updated, the translations will be rebuilt. GNUN doesn’t modify this
-kind of compendia.
-</p>
-<p>The second kind, <samp>compendium.<var>lang</var>.po</samp>, is updated
-automatically. GNUN finds strings that repeat many times in POTs of
-articles and collects them in <samp>compendium.pot</samp>. Then it checks
-all available <samp><var>article</var>.<var>lang</var>.po</samp> files for
-translations of those strings and generates
-<samp>compendium.<var>lang</var>.po</samp>. This file is also used to fill
-missing translations, but it doesn’t override the translations from
-<samp><var>article</var>.<var>lang</var>.po</samp>, and the strings coming from
-<samp>compendium.<var>lang</var>.po</samp> are always marked as
“fuzzy” to
-prevent propagation of translations that may be wrong in a different
-context.
+<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>
-<p>When updating <samp>compendium.pot</samp>, some strings should be excluded
-even though they repeat in the POT files many times—for instance,
-GNUN slots for translators’ notes. See <a href="#Notes-Slot">Notes
Slot</a>. They are not
-real translations, this is why they are likely to be different for
-different articles. In order to avoid including them in compendia,
-GNUN checks a specific file, <samp>exclude.pot</samp>, and when that file
-contains the string, it won’t be added to <samp>compendium.pot</samp>.
+<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="Sitemap"></a>
+<a name="Migrating"></a>
<div class="header">
<p>
-Next: <a href="#GNU-News" accesskey="n" rel="next">GNU News</a>, 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>
+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="Building-Sitemap"></a>
-<h4 class="subsection">2.3.8 Building Sitemap</h4>
-<a name="index-sitemap-1"></a>
+<a name="Transforming-Existing-Translation-in-PO-Format"></a>
+<h3 class="section">4.3 Transforming Existing Translation in PO Format</h3>
+<a name="index-migration_002c-translations"></a>
+<a name="index-conversion-of-existing-translations"></a>
-<p>Sitemaps differ from regular pages in two respects:
+<p>Migrating an existing translation to a PO file format is basically
+editing the header as described in the previous section, and
+populating each of the messages by copying the already translated text
+and/or markup from the existing translation in HTML format in the
+relevant message.
</p>
-<ol>
-<li> They are typically regenerated automatically from the texts of the
-articles.
-
-</li><li> They mostly consist of links, therefore significant part of their
text
-should come to translations without any changes.
-
-</li></ol>
-
-<p>Also, sitemaps contain many translatable messages, so it is desirable
-to eliminate manual work where possible.
+<p>Typically, you will visit <samp>po/foo.<var>lang</var>.po</samp> (in PO
mode) and
+<samp>foo.<var>lang</var>.html</samp> (in HTML mode) in another buffer. Then
you
+can copy a paragraph or an element from the latter and yank it in the
+relevant message in the former. Be extra careful, since this is the
+time to check <em>precisely</em> that the translation corresponds to the
+original. Further changes will be reflected, but if your “initial”
+PO file is not a 100% match, that would not necessarily mean that it
+is an improvement. Since it is very easy to do this kind of check,
+because the relevant <code>msgid</code> and <code>msgstr</code> appear one
above
+the other in the same buffer (or the similar concept in other PO
+editors), please <em>do</em> perform this initial sanity check even if
+you are confident that the translation you have been yanking strings
+from is a completely up-to-date translation.
</p>
-<p>In order to take this into account, GNUN provides the <code>sitemap</code>
-variable in <samp>gnun.mk</samp>. All articles listed in <code>sitemap</code>
are
-rebuilt using an additional compendium (when present),
-<samp>server/gnun/compendia/sitemap-compendium.<var>lang</var>.po</samp>.
+<p>There is also a semi-automatic way to produce an initial PO file. You
+checkout the revision of the English page, <samp>foo.html</samp>, that
+corresponds to the latest revision of the translation,
+<samp>foo.<var>lang</var>.html</samp>. Then you run
<code>gnun-preconvert</code>
+which invokes <code>po4a-gettextize</code> (See <a
href="#gnun_002dpreconvert">gnun-preconvert</a>.):
</p>
-<p>Those additional compendia are supposed to be compiled outside of GNUN
-by the same tool that generates the sitemap. It is responsibility of
-that tool to provide the compendia with reasonable translations whose
-<code>msgid</code>s match those generated by PO4A when processing the
-English version of the sitemap.
+<div class="example">
+<pre class="example">gnun-preconvert foo.lang.html foo.html
+</pre></div>
+
+<p>If some passages in <samp>foo.<var>lang</var>.html</samp> don’t match
the structure
+of <samp>foo.html</samp>, error messages will be displayed. Check them,
+adjust the files and try again. When you succeed, the result will be
+written to foo.lang.po. After that, run
+<code>gnun-merge-preconverted</code> (See <a
href="#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a>.):
</p>
-<hr>
-<a name="GNU-News"></a>
-<div class="header">
-<p>
-Previous: <a href="#Sitemap" accesskey="p" rel="previous">Sitemap</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.9 Special Handling for GNU News</h4>
-<a name="index-gnunews"></a>
-<a name="index-whatsnew"></a>
-<a name="index-gnusflashes"></a>
+<div class="example">
+<pre class="example">gnun-merge-preconverted -C compendium.lang.po foo.lang.po
foo.pot
+</pre></div>
-<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>If you have no compendium, just omit the “<code>-C
+compendium.lang.po</code>” part.
</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>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
+facilitate checking.
</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>There is no need to delete the existing HTML translation, GNUN will
+automatically overwrite it. The only thing a translator should do is to
+commit the PO file in the repository.
</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>When an essay has been translated by several people through the years,
+it is important that this information is recorded and reflected in the
+PO file. In the future, special targets may be added to enable the FSF
+to check who translated a particular article, and when.
+</p>
+<p>A recommended way to do this is as follows:
+</p>
+<div class="example">
+<pre class="example"># French translation of
http://www.gnu.org/philosophy/bsd.html
+# Copyright (C) 2006, 2007, 2008 Free Software Foundation, Inc.
+# This file is distributed under the same license as the gnu.org article.
+# Cédric Corazza <address@hidden>, 2006, 2008.
+# Jerôme Dominguez <address@hidden>, 2007.
+</pre></div>
+
+<p>In this example, it is clear that Cédric made the initial
+translation, Jerôme made some changes in 2007, and the original
+translator returned in 2008 and continued maintaining it.
</p>
<hr>
<a name="Webmaster-Tips"></a>
<div class="header">
<p>
-Previous: <a href="#PO-Files" accesskey="p" rel="previous">PO Files</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>
+Next: <a href="#Internals" accesskey="n" rel="next">Internals</a>, Previous:
<a href="#PO-Files" accesskey="p" rel="previous">PO Files</a>, Up: <a
href="#Top" accesskey="u" rel="up">Top</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="Tips-and-Hints-for-Webmasters"></a>
-<h3 class="section">2.4 Tips and Hints for Webmasters</h3>
+<h2 class="chapter">5 Tips and Hints for Webmasters</h2>
<a name="index-tips_002c-webmasters"></a>
<a name="index-webmaster-tips"></a>
@@ -2344,7 +2340,7 @@
Next: <a href="#Comments-for-Translators" accesskey="n" rel="next">Comments
for Translators</a>, Up: <a href="#Webmaster-Tips" accesskey="u"
rel="up">Webmaster Tips</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="Validation-1"></a>
-<h4 class="subsection">2.4.1 Validation</h4>
+<h3 class="section">5.1 Validation</h3>
<a name="index-validation-3"></a>
<p>The script <code>gnun-validate-html</code> is useful for webmasters who
@@ -2365,7 +2361,7 @@
Next: <a href="#Modifying-Boilerplates" accesskey="n" rel="next">Modifying
Boilerplates</a>, Previous: <a href="#Validation" accesskey="p"
rel="previous">Validation</a>, Up: <a href="#Webmaster-Tips" accesskey="u"
rel="up">Webmaster Tips</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="Comments-for-Translators-1"></a>
-<h4 class="subsection">2.4.2 Comments for Translators</h4>
+<h3 class="section">5.2 Comments for Translators</h3>
<a name="index-comments-for-translators"></a>
@@ -2400,7 +2396,7 @@
Next: <a href="#Localized-URLs" accesskey="n" rel="next">Localized URLs</a>,
Previous: <a href="#Comments-for-Translators" accesskey="p"
rel="previous">Comments for Translators</a>, Up: <a href="#Webmaster-Tips"
accesskey="u" rel="up">Webmaster Tips</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="Modifying-Boilerplates-1"></a>
-<h4 class="subsection">2.4.3 Modifying Boilerplates</h4>
+<h3 class="section">5.3 Modifying Boilerplates</h3>
<a name="index-boilerplates"></a>
<p><strong>Warning:</strong> Any significant structural diversion from
@@ -2418,7 +2414,7 @@
Next: <a href="#Splitting-Long-Passages" accesskey="n" rel="next">Splitting
Long Passages</a>, Previous: <a href="#Modifying-Boilerplates" accesskey="p"
rel="previous">Modifying Boilerplates</a>, Up: <a href="#Webmaster-Tips"
accesskey="u" rel="up">Webmaster Tips</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="Localized-URLs-1"></a>
-<h4 class="subsection">2.4.4 Localized URLs</h4>
+<h3 class="section">5.4 Localized URLs</h3>
<a name="index-localized-URLs"></a>
<p>Some articles may contain diagrams or other images with English text
@@ -2457,7 +2453,7 @@
Previous: <a href="#Localized-URLs" accesskey="p" rel="previous">Localized
URLs</a>, Up: <a href="#Webmaster-Tips" accesskey="u" rel="up">Webmaster
Tips</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="Splitting-Long-Passages-1"></a>
-<h4 class="subsection">2.4.5 Splitting Long Passages</h4>
+<h3 class="section">5.5 Splitting Long Passages</h3>
<a name="index-long-passages_002c-avoiding"></a>
<a name="index-conventional-separator-for-strings"></a>
@@ -2488,10 +2484,10 @@
<a name="Internals"></a>
<div class="header">
<p>
-Next: <a href="#Bugs" accesskey="n" rel="next">Bugs</a>, Previous: <a
href="#Usage" accesskey="p" rel="previous">Usage</a>, Up: <a href="#Top"
accesskey="u" rel="up">Top</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="#Bugs" accesskey="n" rel="next">Bugs</a>, Previous: <a
href="#Webmaster-Tips" accesskey="p" rel="previous">Webmaster Tips</a>, Up: <a
href="#Top" accesskey="u" rel="up">Top</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="Unexciting-Information-for-GNUN_0027s-Operation"></a>
-<h2 class="chapter">3 Unexciting Information for GNUN’s Operation</h2>
+<h2 class="chapter">6 Unexciting Information for GNUN’s Operation</h2>
<p>This chapter might be of interest probably only to people who would have
special interest in the software, plan to enhance it or develop a
@@ -2512,7 +2508,7 @@
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>
+<h3 class="section">6.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
@@ -2681,7 +2677,7 @@
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.2 GNUN Scripts</h3>
+<h3 class="section">6.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
@@ -2721,7 +2717,7 @@
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.2.1 The <code>gnun-add-fuzzy-diff</code> Script</h4>
+<h4 class="subsection">6.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
@@ -2756,7 +2752,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.2.2 The <code>gnun-diff-po</code> Script</h4>
+<h4 class="subsection">6.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
@@ -2807,7 +2803,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.2.3 The <code>gnun-init-po</code> Script</h4>
+<h4 class="subsection">6.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,
@@ -2867,7 +2863,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.2.4 The <code>gnun-preconvert</code> Script</h4>
+<h4 class="subsection">6.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>
@@ -2903,7 +2899,7 @@
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.2.5 The <code>gnun-merge-preconverted</code>
Script</h4>
+<h4 class="subsection">6.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>
@@ -2939,7 +2935,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.2.6 The <code>gnun-report</code> Script</h4>
+<h4 class="subsection">6.2.6 The <code>gnun-report</code> Script</h4>
<a name="index-reporting-1"></a>
<a name="index-status_002c-translations-1"></a>
@@ -3001,7 +2997,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.2.7 The <code>gnun-validate-html</code> Script</h4>
+<h4 class="subsection">6.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
@@ -3053,7 +3049,7 @@
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.2.8 The <code>mailfail</code> Script</h4>
+<h4 class="subsection">6.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
@@ -3115,7 +3111,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.2.9 The <code>validate-html-notify</code> Script</h4>
+<h4 class="subsection">6.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
@@ -3157,7 +3153,7 @@
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.2.10 The <code>gnun-clear-previous</code> Script</h4>
+<h4 class="subsection">6.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
@@ -3192,7 +3188,7 @@
Next: <a href="#Index" accesskey="n" rel="next">Index</a>, Previous: <a
href="#Internals" accesskey="p" rel="previous">Internals</a>, Up: <a
href="#Top" accesskey="u" rel="up">Top</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="Reporting-Bugs"></a>
-<h2 class="chapter">4 Reporting Bugs</h2>
+<h2 class="chapter">7 Reporting Bugs</h2>
<a name="index-bugs_002c-reporting"></a>
<a name="index-reporting-bugs"></a>
@@ -3301,7 +3297,7 @@
<tr><th><a name="Index_cp_letter-G">G</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a
href="#index-generic-notice_002c-translations">generic notice,
translations</a>:</td><td> </td><td valign="top"><a
href="#generic_002eLANG_002ehtml">generic.LANG.html</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-GNUmakefile">GNUmakefile</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-GNUmakefile_002eteam">GNUmakefile.team</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-GNUmakefile_002eteam">GNUmakefile.team</a>:</td><td> </td><td
valign="top"><a href="#Team_0027s-Repository">Team's Repository</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-gnun_002emk">gnun.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-gnun_002emk-1">gnun.mk</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-gnunews">gnunews</a>:</td><td> </td><td valign="top"><a
href="#GNU-News">GNU News</a></td></tr>
@@ -3354,7 +3350,7 @@
<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="#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></td><td valign="top"><a href="#index-project-repository">project
repository</a>:</td><td> </td><td valign="top"><a
href="#Team_0027s-Repository">Team's Repository</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>
@@ -3363,7 +3359,7 @@
<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>
-<tr><td></td><td valign="top"><a
href="#index-repository_002c-translation-project">repository, translation
project</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-repository_002c-translation-project">repository, translation
project</a>:</td><td> </td><td valign="top"><a
href="#Team_0027s-Repository">Team's Repository</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-ROOT">ROOT</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-S">S</a></th><td></td><td></td></tr>
@@ -3379,9 +3375,9 @@
<tr><th><a name="Index_cp_letter-T">T</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a
href="#index-TEAM">TEAM</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-team-information">team
information</a>:</td><td> </td><td valign="top"><a
href="#generic_002eLANG_002ehtml">generic.LANG.html</a></td></tr>
-<tr><td></td><td valign="top"><a href="#index-team-maintenance">team
maintenance</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-team-maintenance">team
maintenance</a>:</td><td> </td><td valign="top"><a
href="#Team_0027s-Repository">Team's Repository</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-team-maintenance_002c-cron">team
maintenance, cron</a>:</td><td> </td><td valign="top"><a
href="#GNUmakefile_002eteam-and-Cron">GNUmakefile.team and Cron</a></td></tr>
-<tr><td></td><td valign="top"><a href="#index-team-workflow">team
workflow</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-team-workflow">team
workflow</a>:</td><td> </td><td valign="top"><a
href="#Team_0027s-Repository">Team's Repository</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-templates_002c-additional">templates,
additional</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-templates_002c-defining">templates,
defining</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-templates_002c-optional">templates,
optional</a>:</td><td> </td><td valign="top"><a
href="#Main-Variables">Main Variables</a></td></tr>
Index: gnun/gnun.html.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.html.gz,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
Binary files /tmp/cvsbua9BL and /tmp/cvsLxsqIl 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.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
Binary files /tmp/cvsVlN3dM and /tmp/cvsqBNElm differ
Index: gnun/gnun.info.tar.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.info.tar.gz,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
Binary files /tmp/cvs6HS0wK and /tmp/cvsyigNFk differ
Index: gnun/gnun.pdf
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.pdf,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
Binary files /tmp/cvsipez6K and /tmp/cvsIIoRjl differ
Index: gnun/gnun.ps.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.ps.gz,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
Binary files /tmp/cvsZ0WaBQ and /tmp/cvsaNgXRq differ
Index: gnun/gnun.texi.tar.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.texi.tar.gz,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
Binary files /tmp/cvsJFZxjP and /tmp/cvs86o8Bp differ
Index: gnun/gnun.txt
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.txt,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- gnun/gnun.txt 31 Jan 2013 08:47:29 -0000 1.19
+++ gnun/gnun.txt 1 Feb 2013 06:06:07 -0000 1.20
@@ -6,56 +6,56 @@
1.4 Known Bugs and Limitations
2 General Usage
2.1 Invoking GNUN
- 2.1.1 Variables to Control the Build Process
- 2.1.2 Targets Specified on the Command Line
- 2.1.2.1 The 'no-grace-items' Target
- 2.1.2.2 The 'update-localized-URLs' Target
- 2.1.2.3 The 'sync' Target
- 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.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 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 Building Sitemap
- 2.3.9 Special Handling for GNU News
- 2.4 Tips and Hints for Webmasters
- 2.4.1 Validation
- 2.4.2 Comments for Translators
- 2.4.3 Modifying Boilerplates
- 2.4.4 Localized URLs
- 2.4.5 Splitting Long Passages
-3 Unexciting Information for GNUN's Operation
- 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
+ 2.2 Variables to Control the Build Process
+ 2.3 Targets Specified on the Command Line
+ 2.3.1 The 'no-grace-items' Target
+ 2.3.2 The 'update-localized-URLs' Target
+ 2.3.3 The 'sync' Target
+ 2.3.4 The 'report' Target
+ 2.3.5 The 'triggers' Target
+ 2.3.6 The 'validate-all' Target
+ 2.4 Defining Articles to Be Built
+ 2.5 The 'generic.LANG.html' File
+ 2.6 The 'languages.txt' File
+ 2.7 Using Compendia
+ 2.8 Building Sitemap
+ 2.9 Special Handling for GNU News
+3 Maintaining Translations in Your Team's Repository
+ 3.1 Adopting 'GNUmakefile.team' for a Specific Team
+ 3.2 Targets in 'GNUmakefile.team'
+ 3.3 Automatic Synchronization and Status Reports
+4 Working with PO Files
+ 4.1 Starting a New Translation
+ 4.1.1 The Special Slot for Translator's Notes
+ 4.1.2 The Special Slot for Translator's Credits
+ 4.2 Useful Hints for Editing PO Files
+ 4.3 Transforming Existing Translation in PO Format
+5 Tips and Hints for Webmasters
+ 5.1 Validation
+ 5.2 Comments for Translators
+ 5.3 Modifying Boilerplates
+ 5.4 Localized URLs
+ 5.5 Splitting Long Passages
+6 Unexciting Information for GNUN's Operation
+ 6.1 Files and Directories
+ 6.2 GNUN Scripts
+ 6.2.1 The 'gnun-add-fuzzy-diff' Script
+ 6.2.2 The 'gnun-diff-po' Script
+ 6.2.3 The 'gnun-init-po' Script
+ 6.2.4 The 'gnun-preconvert' Script
+ 6.2.5 The 'gnun-merge-preconverted' Script
+ 6.2.6 The 'gnun-report' Script
+ 6.2.7 The 'gnun-validate-html' Script
+ 6.2.8 The 'mailfail' Script
+ 6.2.9 The 'validate-html-notify' Script
+ 6.2.10 The 'gnun-clear-previous' Script
+7 Reporting Bugs
Index
Appendix A GNU Free Documentation License
GNUnited Nations
****************
-This manual (updated 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org essays and
other articles.
@@ -388,8 +388,8 @@
hypothetical tree. (For gnu.org, that is not necessary since a proper
'gnun.mk' is maintained in 'www'.)
-2.1.1 Variables to Control the Build Process
---------------------------------------------
+2.2 Variables to Control the Build Process
+==========================================
The build process has several modes of operation, and they all relate to
the handling of files that are to be added to the repository or
@@ -540,8 +540,8 @@
effectively adding them to the public repository. *Note triggers::, for
a short explanation.
-2.1.2 Targets Specified on the Command Line
--------------------------------------------
+2.3 Targets Specified on the Command Line
+=========================================
Some targets are not built by default, because they are only useful
under certain circumstances. Think of them like semi-automated commands
@@ -550,8 +550,8 @@
reads the makefiles--the filesets they affect are specific and already
defined, one way or another.
-2.1.2.1 The 'no-grace-items' Target
-...................................
+2.3.1 The 'no-grace-items' Target
+---------------------------------
The 'no-grace-items' target regenerates a limited set of articles that
are not affected by the grace period, namely, the server templates,
@@ -561,8 +561,8 @@
This target can be rebuilt more often than 'all'; however, currently
it is not used.
-2.1.2.2 The 'update-localized-URLs' Target
-..........................................
+2.3.2 The 'update-localized-URLs' Target
+----------------------------------------
The 'update-localized-URLs' target invokes a script that generates the
'localized-urls.mk' file. This file includes the list of URLs that
@@ -571,8 +571,8 @@
This target is meant to be rebuilt nightly.
-2.1.2.3 The 'sync' Target
-.........................
+2.3.3 The 'sync' Target
+-----------------------
The 'sync' target has a simple task: synchronize the _original English_
articles from a canonical repository, like 'www'. It is very important
@@ -606,8 +606,8 @@
'VCS=always' has no effect on this target, as well as 'VALIDATE'.
-2.1.2.4 The 'report' Target
-...........................
+2.3.4 The 'report' Target
+-------------------------
This target exists solely for convenience to translators, enabling them
to check which articles are not 100% translated and have to be updated.
@@ -633,8 +633,8 @@
which produces a more detailed report. *Note report in
GNUmakefile.team::.
-2.1.2.5 The 'triggers' Target
-.............................
+2.3.5 The 'triggers' Target
+---------------------------
This is a special target intended to be run by the automatic build after
the main build and _after_ 'cvs|svn|bzr commit'.
@@ -688,8 +688,8 @@
job in order to address some exceptional situations like concurrent
builds.
-2.1.2.6 The 'validate-all' Target
-.................................
+2.3.6 The 'validate-all' Target
+-------------------------------
The 'validate-all' target validates all HTML pages under GNUN's control.
It is needed because GNUN doesn't track dependencies on the included
@@ -697,7 +697,7 @@
This target is invoked once a day by the official GNUN cron job.
-2.2 Defining Articles to Be Built
+2.4 Defining Articles to Be Built
=================================
The file 'gnun.mk' contains variable definitions, based on which almost
@@ -790,452 +790,159 @@
Nations' internals. From a purely technical point of view, there is no
difference.
-2.3 Working with PO Files
-=========================
+2.5 The 'generic.LANG.html' File
+================================
-This section provides GNUN-specific information about woking with PO
-files. For general information, *note Working with PO Files:
-(web-trans)PO Files.
+The files 'server/gnun/generic.LANG.html' are special: if no such file
+exists for your language, an empty file will be created (and added to
+the repository if specified 'VCS=yes'). This file is optional, and
+should contain a short message in your native language, ideally
+providing more information about the translation team or where to report
+bugs. For example:
-2.3.1 Starting a New Translation
---------------------------------
+ <p>To join the Fooish translation team, see <a
+ href="http://gnu.org/server/standards/translations/foo";>the
+ Foo team homepage</a>.</p>
-To start a new translation, the most simple way is to copy the existing
-POT as 'article.LANG.po', where LANG is your language code. For
-example, to prepare for a new translation of the essay
-<http://www.gnu.org/philosophy/free-sw.html>, you can simply do 'cd
-philosophy/po; cp free-sw.pot free-sw.LANG.po' and then edit the latter.
-If 'free-sw.pot' does not exist it is because either the article is not
-yet "templated" (i.e. migrated to the new style), or the GNUN
-maintainers have not yet added it to the value of the appropriate
-variable in 'server/gnun/gnun.mk'. In that case, just ask them to do
-the necessary in order the POT to be generated.
+ The contents of 'generic.LANG.html' is injected right after the
+translators' credits, if any, and before the timestamp. It should be
+valid HTML markup.
- You could also use the 'msginit' utility that would populate the PO
-file header with the right information, provided your environment is set
-up correctly. *Note (gettext)msginit Invocation::.
+ When you modify this file, for example, adding a message to the
+existing empty file or changing a URL, such modification will affect
+_all_ articles of the language LANG in 'generic.LANG.html'. The next
+time a build occurs, all translations of the language code LANG (i.e.
+all '.LANG.html', including the homepage), will be modified to include
+the contents of this special file.
- GNUN also provides a customized script to automatically fill more
-header fields. *Note gnun-init-po::.
+2.6 The 'languages.txt' File
+============================
- The PO file header as generated usually looks like this:
+The file 'server/gnun/languages.txt' is used when generating lists of
+translations; those lists are subsequently included in all translations
+of the article. Every line in the file is either a comment (when it
+begins with "#") or a definition for a language. A language is defined
+by three <TAB>-separated fields. The first field defines the language
+suffix; it is used in file names and in texts of the links. The second
+field is the name of the language in English; it is used in HTML
+comments. The third field defines the name of the language in that
+language itself; it is used in texts of the links, and it should be in
+UTF-8. For example:
- # SOME DESCRIPTIVE TITLE
- # Copyright (C) YEAR Free Software Foundation, Inc.
- # This file is distributed under the same license as the PACKAGE package.
- # FIRST AUTHOR <address@hidden>, YEAR.
- #
- #, fuzzy
- msgid ""
- msgstr ""
- "Project-Id-Version: PACKAGE VERSION\n"
- "POT-Creation-Date: 2008-02-06 16:25-0500\n"
- "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
- "Last-Translator: FULL NAME <address@hidden>\n"
- "Language-Team: LANGUAGE <address@hidden>\n"
- "MIME-Version: 1.0\n"
- "Content-Type: text/plain; charset=CHARSET\n"
- "Content-Transfer-Encoding: ENCODING\n"
+ de German Deutsch
- You have to edit the header to match the already established
-conventions, and the rules for gnu.org translations. For reference,
-here is a list with all fields explained:
+ The generated list of translations may look like this:
-'Project-Id-Version'
- Add here the filename of the original article, without the
- sub-directory, like "body-include-1.html" or "free-sw.html".
+ <!-- begin translinks file -->
+ <div id="translations">
+ <ul class="translations-list">
+ <!-- German -->
+ <li><a href="/distros/screenshot.de.html">Deutsch</a> [de]</li>
+ <!-- English -->
+ <li><a href="/distros/screenshot.html">English</a> [en]</li>
+ <!-- Polish -->
+ <li><a href="/distros/screenshot.pl.html">polski</a> [pl]</li>
+ </ul>
+ </div> <!-- id="translations" -->
+ <!-- end translinks file -->
-'POT-Creation-Date'
- Do not edit this field, it is already set when the POT is created.
+2.7 Using Compendia
+===================
-'PO-Revision-Date'
- Likewise, do not edit. This field is automatically filled in when
- you save the file with any decent PO editor.
+Compendium is a PO file including translations for common strings; it is
+used to fill other PO files. *Note Compendium: (gettext)Compendium.
+One example of such common strings is the footer text about reporting
+bugs and sending inquiries: when a webmaster updates footer texts in an
+article, GNUN will use compendia to automatically fill the translations
+for the new version of the strings.
-'Last-Translator'
- The name and email address of the last translator who has edited
- the translation. Pay attention that normally this is the name of a
- member of your team, it can be the translation team leader if
- he/she was the person who updated the translation. For example:
+ GNUN uses compendia located in the 'server/gnun/compendia' directory
+of the 'www' web repository. There are two kinds of compendia:
+'master.LANG.po' and 'compendium.LANG.po'.
- Elvis Parsley <address@hidden>
+ The first kind, 'master.LANG.po', can be used to simultaneously
+update all occurrences of the translations of a given string.
+Translations from this file will override the translations from
+'ARTICLE.LANG.po'. When 'master.LANG.po' is updated, the translations
+will be rebuilt. GNUN doesn't modify this kind of compendia.
-'Language-Team'
- This field should contain the mailing list on which the translation
- team can be reached--usually <address@hidden>. Example:
+ The second kind, 'compendium.LANG.po', is updated automatically.
+GNUN finds strings that repeat many times in POTs of articles and
+collects them in 'compendium.pot'. Then it checks all available
+'ARTICLE.LANG.po' files for translations of those strings and generates
+'compendium.LANG.po'. This file is also used to fill missing
+translations, but it doesn't override the translations from
+'ARTICLE.LANG.po', and the strings coming from 'compendium.LANG.po' are
+always marked as "fuzzy" to prevent propagation of translations that may
+be wrong in a different context.
- Czech <address@hidden>
+ When updating 'compendium.pot', some strings should be excluded even
+though they repeat in the POT files many times--for instance, GNUN slots
+for translators' notes. *Note Notes Slot::. They are not real
+translations, this is why they are likely to be different for different
+articles. In order to avoid including them in compendia, GNUN checks a
+specific file, 'exclude.pot', and when that file contains the string, it
+won't be added to 'compendium.pot'.
-'MIME-Version'
- Leave it like it is.
+2.8 Building Sitemap
+====================
-'Content-Type'
- Usually this is 'text/plain; charset=UTF-8'; change the charset
- accordingly.
+Sitemaps differ from regular pages in two respects:
-'Content-Transfer-Encoding'
- Set this to '8bit'. Note that the PO file header ends with this
- field, and it should contain a newline ('\n'). Unfortunately, some
- PO editors remove the newline, which causes an unnecessary revision
- when the file is automatically modified by GNUN's rules.
+ 1. They are typically regenerated automatically from the texts of the
+ articles.
- Here is an example of a properly edited header:
+ 2. They mostly consist of links, therefore significant part of their
+ text should come to translations without any changes.
- # Bulgarian translation of http://www.gnu.org/philosophy/free-sw.html
- # Copyright (C) 2008 Free Software Foundation, Inc.
- # This file is distributed under the same license as the gnu.org article.
- # Yavor Doganov <address@hidden>, 2008.
- #
- msgid ""
- msgstr ""
- "Project-Id-Version: free-sw.html\n"
- "POT-Creation-Date: 2008-02-06 16:25-0500\n"
- "PO-Revision-Date: 2008-02-09 15:23+0200\n"
- "Last-Translator: Yavor Doganov <address@hidden>\n"
- "Language-Team: Bulgarian <address@hidden>\n"
- "MIME-Version: 1.0\n"
- "Content-Type: text/plain; charset=UTF-8\n"
- "Content-Transfer-Encoding: 8-bit\n"
+ Also, sitemaps contain many translatable messages, so it is desirable
+to eliminate manual work where possible.
- Notice the absence of the "fuzzy" marker; you should "unfuzzy" the
-header after entering the necessary information (this is done by simply
-pressing <TAB> in PO mode).
+ In order to take this into account, GNUN provides the 'sitemap'
+variable in 'gnun.mk'. All articles listed in 'sitemap' are rebuilt
+using an additional compendium (when present),
+'server/gnun/compendia/sitemap-compendium.LANG.po'.
- 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 publish::).
+ Those additional compendia are supposed to be compiled outside of
+GNUN by the same tool that generates the sitemap. It is responsibility
+of that tool to provide the compendia with reasonable translations whose
+'msgid's match those generated by PO4A when processing the English
+version of the sitemap.
- There are some special messages that appear in the POT and PO:
+2.9 Special Handling for GNU News
+=================================
-'*GNUN-SLOT: TRANSLATOR'S NOTES*'
- 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:
+*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.
- msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
- msgstr " "
+ 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-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 if you do not want your name to appear there. *Note
- Credits Slot::.
+ 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.
- 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
-harder, and are generally annoying for most people. If this issue
-bothers you, you can "normalize" the already finished PO translation by
-executing on the command line 'msgcat -o FILE.po FILE.po', before
-installing it in the repository. Either way, the build system will
-treat it is a valid PO file.
+ 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.
- For those lucky Emacs users, here is a code snippet that you can put
-in your '.emacs'; doing 'M-x po-wrap' while in PO mode will wrap all
-long lines:
+3 Maintaining Translations in Your Team's Repository
+****************************************************
- (defun po-wrap ()
- "Filter current po-mode buffer through `msgcat' tool to wrap all lines."
- (interactive)
- (if (eq major-mode 'po-mode)
- (let ((tmp-file (make-temp-file "po-wrap."))
- (tmp-buf (generate-new-buffer "*temp*")))
- (unwind-protect
- (progn
- (write-region (point-min) (point-max) tmp-file nil 1)
- (if (zerop
- (call-process
- "msgcat" nil tmp-buf t (shell-quote-argument tmp-file)))
- (let ((saved (point))
- (inhibit-read-only t))
- (delete-region (point-min) (point-max))
- (insert-buffer tmp-buf)
- (goto-char (min saved (point-max))))
- (with-current-buffer tmp-buf
- (error (buffer-string)))))
- (kill-buffer tmp-buf)
- (delete-file tmp-file)))))
-
- It is highly desirable that you check if the PO file you finished
-translating (or editing) is valid, before committing it. This is done
-by running 'msgfmt -cv -o /dev/null FILE' or by simply pressing 'V' in
-PO mode. The build system automatically verifies each PO file when
-invoked with 'VALIDATE=yes', but you won't get a warm and fuzzy feeling
-if a stupid typo you made halts the whole update of all translations.
-Such things happen to everyone, so it is a good practice to check before
-you actually commit.
-
-2.3.1.1 The Special Slot for Translator's Notes
-...............................................
-
-Sometimes it is necessary to complement the translation of an essay with
-translator's notes. The special message '*GNUN-SLOT: TRANSLATOR'S
-NOTES*' is designed to serve this purpose. If your translation doesn't
-have notes, you should "translate" the 'msgstr' as a space
-(<SPC>)--otherwise the PO file will be considered incomplete, which is
-not what you want. Here is an example how to use translators' notes in
-a PO file:
-
- # type: Content of: <p>
- msgid ""
- "To understand the concept, you should think of <q>free</q> "
- "as in <q>free speech,</q> not as in <q>free beer.</q>"
- msgstr ""
- "Translated message, where you want to clarify beer<sup><a "
- "href=\"#TransNote1\">1</a></sup>, presumably because the "
- "expression in your language is different"
- ...
- ...
- # type: Content of: <div>
- #. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
- msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
- msgstr ""
- "<h3>Translator's notes</h3>\n"
- "<ol>\n"
- "<li id=\"TransNote1\">Note clarifying the text.</li>\n"
- "</ol>\n"
-
- Certainly, everything in the 'msgstr's should be in your native
-language; we use English here in order the example to be understood by
-everyone. If you have more notes, each subsequent one should be with
-incremented number, i.e. 'TransNote2', 'TransNote3', etc. and you have
-to add them as more '<li>' elements accordingly.
-
- Do not worry about the '\n' character--it is inserted automatically
-when you press <RET>. It is not compulsory that notes start on a new
-line, this is the recommended way simply because it is easier to edit
-them.
-
- It is important to follow this specification, because notes will look
-consistently in all languages and will be clearly distinguishable from
-authors' footnotes, if any. Furthermore, it would be easier to define a
-special CSS class for them, and also to convert the translations in
-other formats such as Texinfo--when these features are implemented.
-
-2.3.1.2 The Special Slot for Translator's Credits
-.................................................
-
-Most of the translators usually put their name under the translation, in
-the "footer" area. This is entirely acceptable, since some readers
-prefer to send buggestions directly to the translator. Also, giving
-credit where credit is due is a natural thing.
-
- Like the previous slot, you should "translate" it as a <SPC> if you
-don't want your name to appear there.
-
- Here is an example of the recommended way to specify credits:
-
- <b>Traduction</b>: Benjamin Drieu
- <a href="mailto:address@hidden";><address@hidden></a>,
- 2007, 2008.
-
- It is highly desirable to use this form, but you may omit the email
-address or add a link to translator's noncommercial personal home page,
-provided that the translation team leader ensures that it constantly
-meets the linking criteria for gnu.org. Please follow the FSF HTML
-Style Sheet when adding URIs or other information.
-
-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
-editing the header as described in the previous section, and populating
-each of the messages by copying the already translated text and/or
-markup from the existing translation in HTML format in the relevant
-message.
-
- Typically, you will visit 'po/foo.LANG.po' (in PO mode) and
-'foo.LANG.html' (in HTML mode) in another buffer. Then you can copy a
-paragraph or an element from the latter and yank it in the relevant
-message in the former. Be extra careful, since this is the time to
-check _precisely_ that the translation corresponds to the original.
-Further changes will be reflected, but if your "initial" PO file is not
-a 100% match, that would not necessarily mean that it is an improvement.
-Since it is very easy to do this kind of check, because the relevant
-'msgid' and 'msgstr' appear one above the other in the same buffer (or
-the similar concept in other PO editors), please _do_ perform this
-initial sanity check even if you are confident that the translation you
-have been yanking strings from is a completely up-to-date translation.
-
- There is also a semi-automatic way to produce an initial PO file.
-You checkout the revision of the English page, 'foo.html', that
-corresponds to the latest revision of the translation, 'foo.LANG.html'.
-Then you run 'gnun-preconvert' which invokes 'po4a-gettextize' (*Note
-gnun-preconvert::.):
-
- gnun-preconvert foo.lang.html foo.html
-
- If some passages in 'foo.LANG.html' don't match the structure of
-'foo.html', error messages will be displayed. Check them, adjust the
-files and try again. When you succeed, the result will be written to
-foo.lang.po. After that, run 'gnun-merge-preconverted' (*Note
-gnun-merge-preconverted::.):
-
- gnun-merge-preconverted -C compendium.lang.po foo.lang.po foo.pot
-
- If you have no compendium, just omit the "'-C compendium.lang.po'"
-part.
-
- 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
-checking.
-
- There is no need to delete the existing HTML translation, GNUN will
-automatically overwrite it. The only thing a translator should do is to
-commit the PO file in the repository.
-
- When an essay has been translated by several people through the
-years, it is important that this information is recorded and reflected
-in the PO file. In the future, special targets may be added to enable
-the FSF to check who translated a particular article, and when.
-
- A recommended way to do this is as follows:
-
- # French translation of http://www.gnu.org/philosophy/bsd.html
- # Copyright (C) 2006, 2007, 2008 Free Software Foundation, Inc.
- # This file is distributed under the same license as the gnu.org article.
- # Ce'dric Corazza <address@hidden>, 2006, 2008.
- # Jero^me Dominguez <address@hidden>, 2007.
-
- In this example, it is clear that Ce'dric made the initial
-translation, Jero^me made some changes in 2007, and the original
-translator returned in 2008 and continued maintaining it.
-
-2.3.4 The 'generic.LANG.html' File
-----------------------------------
-
-The files 'server/gnun/generic.LANG.html' are special: if no such file
-exists for your language, an empty file will be created (and added to
-the repository if specified 'VCS=yes'). This file is optional, and
-should contain a short message in your native language, ideally
-providing more information about the translation team or where to report
-bugs. For example:
-
- <p>To join the Fooish translation team, see <a
- href="http://gnu.org/server/standards/translations/foo";>the
- Foo team homepage</a>.</p>
-
- The contents of 'generic.LANG.html' is injected right after the
-translators' credits, if any, and before the timestamp. It should be
-valid HTML markup.
-
- When you modify this file, for example, adding a message to the
-existing empty file or changing a URL, such modification will affect
-_all_ articles of the language LANG in 'generic.LANG.html'. The next
-time a build occurs, all translations of the language code LANG (i.e.
-all '.LANG.html', including the homepage), will be modified to include
-the contents of this special file.
-
-2.3.5 The 'languages.txt' File
-------------------------------
-
-The file 'server/gnun/languages.txt' is used when generating lists of
-translations; those lists are subsequently included in all translations
-of the article. Every line in the file is either a comment (when it
-begins with "#") or a definition for a language. A language is defined
-by three <TAB>-separated fields. The first field defines the language
-suffix; it is used in file names and in texts of the links. The second
-field is the name of the language in English; it is used in HTML
-comments. The third field defines the name of the language in that
-language itself; it is used in texts of the links, and it should be in
-UTF-8. For example:
-
- de German Deutsch
-
- The generated list of translations may look like this:
-
- <!-- begin translinks file -->
- <div id="translations">
- <ul class="translations-list">
- <!-- German -->
- <li><a href="/distros/screenshot.de.html">Deutsch</a> [de]</li>
- <!-- English -->
- <li><a href="/distros/screenshot.html">English</a> [en]</li>
- <!-- Polish -->
- <li><a href="/distros/screenshot.pl.html">polski</a> [pl]</li>
- </ul>
- </div> <!-- id="translations" -->
- <!-- end translinks file -->
-
-2.3.6 Maintaining Translations in Your Team's Repository
---------------------------------------------------------
-
-GNUN operates on the "official" Web repository of the Savannah project
-'www', where normally only the coordinators of translation teams have
-write access. However, all translation teams have their own projects,
-so it is possible to take advantage of Savannah as a hosting facility to
-make the team work more comfortable.
+GNUN operates on the "official" Web repository of the Savannah project
+'www', where normally only the coordinators of translation teams have
+write access. However, all translation teams have their own projects,
+so it is possible to take advantage of Savannah as a hosting facility to
+make the team work more comfortable.
The PO files provide an excellent and natural way to review each
other's translations, because the translation appears right below the
@@ -1312,8 +1019,8 @@
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
-.......................................................
+3.1 Adopting 'GNUmakefile.team' for a Specific Team
+===================================================
To adjust the makefile for your team, you need to edit the next
variables.
@@ -1362,306 +1069,599 @@
'NOTIFY=yes'
Make the 'notify' target actually send notifications.
-'NOTIFY=no'
- Do not send email notifications about errors. This is the default.
+'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
+ have the same effect.
+
+'VCS=yes'
+ Update both 'www' and 'www-LANG' repositories, then commit the
+ merged PO files in the latter repository. By default, there is no
+ VCS interaction. The VCS of the translation project repository is
+ determined automatically; currently only CVS, Subversion, GNU Bzr,
+ Git, Mercurial (Hg) and GNU Arch repositories are supported.
+
+ *Caution:* The makefile rule will commit all local changes, not
+ only those that resulted from running 'msgmerge'. Thus, it is
+ better to use a separate working copy dedicated solely for this
+ purpose.
+
+3.2 Targets in 'GNUmakefile.team'
+=================================
+
+'update'
+ Updates the repositories. Does nothing unless 'VCS=yes'.
+
+'sync'
+ Merges all available PO files from the corresponding POT in "www".
+ If a POT is missing in the master repository (usually, because it
+ was deleted when the original article was either split, renamed or
+ deleted), a warning is printed for the corresponding file and no
+ merging occurs for it.
+
+'report'
+ 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 "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 (unless the
+ 'force' option is used).
+
+ 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:
+
+ 'force'
+ Forces sending messages even when there are no files to work
+ on.
+
+ '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.
+ Most PO editors leave the 'msgstr' as a single long line after it
+ has been edited, but GNUN will automatically re-wrap the file to
+ the standard line length when it is processed. Wrapping long lines
+ in PO files is a good practice as it avoids unnecessary revisions.
+
+ This rule checks for all translations that have lines longer than
+ 80, and runs 'msgcat' accordingly to reformat them. For that
+ reason, it is recommended that you wrap all long lines in the
+ comment fields (e.g. the file header, including the copyright
+ statement, and any other comments for specific messages), because
+ 'make format' will unnecessarily invoke 'msgcat' for any file that
+ has a longer line, wherever it may occur.
+
+'publish'
+ The 'publish' rule's task is to copy all modified files to the
+ official "www" repository. It depends on the 'format' target to
+ ensure that all files are re-wrapped to the standard line length
+ limit, but deliberately does not depend on 'sync VCS=yes'.
+ Usually, one would run 'make publish' when one or a bunch of PO
+ files are in a satisfactory condition to be published, and this
+ rule is just a convenience to avoid multiple manual 'cp'
+ invocations. As a rule of thumb, before running this rule it is
+ sane to run 'sync' and correct any "fuzzy" messages and other
+ problems, if necessary.
+
+ The 'publish' rule does not depend on 'sync' explicitly, because
+ that would be a nuisance for offline operations and basically
+ unnecessary when the committer is fairly confident that there are
+ no changes to (re-)merge. A hard dependency on 'sync' would slow
+ down the operation considerably.
+
+ As usual, when committing to the official repository, it is always
+ a good practice to examine the output of 'cvs diff'.
+
+ Invoking 'make publish' prints warnings and does not actually copy
+ the affected file if the sub-directory in "www" is non-existent or
+ the corresponding '.pot' is missing.
+
+ Typically, after an editing session (whether it involves actual
+ editing or just merging contributions from team members), one would
+ do:
+
+ $ make sync VCS=yes
+ $ make publish
+ $ cd WWWDIR
+ $ cvs up
+ (Add all new translations, if any.)
+ $ cvs add FILE ...
+ $ cvs diff
+ $ cvs commit -m "Some descriptive message."
+
+'clean'
+ 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. 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.
+
+3.3 Automatic Synchronization and Status Reports
+================================================
+
+It is convenient to invoke such synchronization automatically, for
+example once every day. If you have enabled commit notifications for
+the project's repository, any new changes will be visible for
+subscribers. Here is an example crontab entry:
+
+ # m h dom mon dow command
+ @daily cd $HOME/projects/www-LANG; make VCS=yes
+
+ It is not necessary the job to be run on the team leader's machine,
+since all team members have write access to their project repository.
+
+ If desired, you could set up another job to report the status of the
+translations weekly or fortnightly, for example:
+
+ # m h dom mon dow command
+ @weekly cd $HOME/projects/www-LANG; \
+ make report | mail -s "Weekly statistics" \
+ address@hidden
+
+ *Caution:* Most cron implementations do not allow the character '\'
+as a line continuation character--the example shown is made that way for
+better readability.
+
+4 Working with PO Files
+***********************
+
+This section provides GNUN-specific information about woking with PO
+files. For general information, *note Working with PO Files:
+(web-trans)PO Files.
+
+4.1 Starting a New Translation
+==============================
+
+To start a new translation, the most simple way is to copy the existing
+POT as 'article.LANG.po', where LANG is your language code. For
+example, to prepare for a new translation of the essay
+<http://www.gnu.org/philosophy/free-sw.html>, you can simply do 'cd
+philosophy/po; cp free-sw.pot free-sw.LANG.po' and then edit the latter.
+If 'free-sw.pot' does not exist it is because either the article is not
+yet "templated" (i.e. migrated to the new style), or the GNUN
+maintainers have not yet added it to the value of the appropriate
+variable in 'server/gnun/gnun.mk'. In that case, just ask them to do
+the necessary in order the POT to be generated.
+
+ You could also use the 'msginit' utility that would populate the PO
+file header with the right information, provided your environment is set
+up correctly. *Note (gettext)msginit Invocation::.
+
+ GNUN also provides a customized script to automatically fill more
+header fields. *Note gnun-init-po::.
+
+ The PO file header as generated usually looks like this:
+
+ # SOME DESCRIPTIVE TITLE
+ # Copyright (C) YEAR Free Software Foundation, Inc.
+ # This file is distributed under the same license as the PACKAGE package.
+ # FIRST AUTHOR <address@hidden>, YEAR.
+ #
+ #, fuzzy
+ msgid ""
+ msgstr ""
+ "Project-Id-Version: PACKAGE VERSION\n"
+ "POT-Creation-Date: 2008-02-06 16:25-0500\n"
+ "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+ "Last-Translator: FULL NAME <address@hidden>\n"
+ "Language-Team: LANGUAGE <address@hidden>\n"
+ "MIME-Version: 1.0\n"
+ "Content-Type: text/plain; charset=CHARSET\n"
+ "Content-Transfer-Encoding: ENCODING\n"
-'VERBOSE=yes'
- Print more information from 'cvs', 'svn' and 'msgmerge'; off by
- default. Note that 'VERBOSE' can be defined to any string, it will
- have the same effect.
+ You have to edit the header to match the already established
+conventions, and the rules for gnu.org translations. For reference,
+here is a list with all fields explained:
-'VCS=yes'
- Update both 'www' and 'www-LANG' repositories, then commit the
- merged PO files in the latter repository. By default, there is no
- VCS interaction. The VCS of the translation project repository is
- determined automatically; currently only CVS, Subversion, GNU Bzr,
- Git, Mercurial (Hg) and GNU Arch repositories are supported.
+'Project-Id-Version'
+ Add here the filename of the original article, without the
+ sub-directory, like "body-include-1.html" or "free-sw.html".
- *Caution:* The makefile rule will commit all local changes, not
- only those that resulted from running 'msgmerge'. Thus, it is
- better to use a separate working copy dedicated solely for this
- purpose.
+'POT-Creation-Date'
+ Do not edit this field, it is already set when the POT is created.
-2.3.6.2 Targets in 'GNUmakefile.team'
-.....................................
+'PO-Revision-Date'
+ Likewise, do not edit. This field is automatically filled in when
+ you save the file with any decent PO editor.
-'update'
- Updates the repositories. Does nothing unless 'VCS=yes'.
+'Last-Translator'
+ The name and email address of the last translator who has edited
+ the translation. Pay attention that normally this is the name of a
+ member of your team, it can be the translation team leader if
+ he/she was the person who updated the translation. For example:
-'sync'
- Merges all available PO files from the corresponding POT in "www".
- If a POT is missing in the master repository (usually, because it
- was deleted when the original article was either split, renamed or
- deleted), a warning is printed for the corresponding file and no
- merging occurs for it.
+ Elvis Parsley <address@hidden>
-'report'
- 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 "www"
- repository.
+'Language-Team'
+ This field should contain the mailing list on which the translation
+ team can be reached--usually <address@hidden>. Example:
- More fine-grained notifications are implemented as the 'notify'
- target.
+ Czech <address@hidden>
-'notify'
- Invokes the 'report' target, filters its output for different
- translators and sends them notifications.
+'MIME-Version'
+ Leave it like it is.
- 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).
+'Content-Type'
+ Usually this is 'text/plain; charset=UTF-8'; change the charset
+ accordingly.
- 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 ':'.
+'Content-Transfer-Encoding'
+ Set this to '8bit'. Note that the PO file header ends with this
+ field, and it should contain a newline ('\n'). Unfortunately, some
+ PO editors remove the newline, which causes an unnecessary revision
+ when the file is automatically modified by GNUN's rules.
- 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.
+ Here is an example of a properly edited header:
- The second field is a space-separated list of single-word
- translators' identifiers for which the line applies. The file may
- look like this:
+ # Bulgarian translation of http://www.gnu.org/philosophy/free-sw.html
+ # Copyright (C) 2008 Free Software Foundation, Inc.
+ # This file is distributed under the same license as the gnu.org article.
+ # Yavor Doganov <address@hidden>, 2008.
+ #
+ msgid ""
+ msgstr ""
+ "Project-Id-Version: free-sw.html\n"
+ "POT-Creation-Date: 2008-02-06 16:25-0500\n"
+ "PO-Revision-Date: 2008-02-09 15:23+0200\n"
+ "Last-Translator: Yavor Doganov <address@hidden>\n"
+ "Language-Team: Bulgarian <address@hidden>\n"
+ "MIME-Version: 1.0\n"
+ "Content-Type: text/plain; charset=UTF-8\n"
+ "Content-Transfer-Encoding: 8-bit\n"
- ^gnu/gnu-history: alice bob carol
- ^distros/(common-distros|distros|screenshot): dan alice
- ^(licenses|philosophy)/: eve bob frank
- ^licenses/: dan
+ Notice the absence of the "fuzzy" marker; you should "unfuzzy" the
+header after entering the necessary information (this is done by simply
+pressing <TAB> in PO mode).
- 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.
+ 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 publish::).
- The first field is translators' identifier, the second is
- space-separated list of translators' email addresses. These two
- fields are mandatory.
+ There are some special messages that appear in the POT and PO:
- 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 (unless the
- 'force' option is used).
+'*GNUN-SLOT: TRANSLATOR'S NOTES*'
+ 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:
- The team-wide default period is defined in its GNUmakefile.team
- using the 'NOTIFICATION_PERIOD' variable.
+ msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
+ msgstr " "
- The fourth field provides comma-separated options for the report.
- Currently recognized options are:
+'*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 if you do not want your name to appear there. *Note
+ Credits Slot::.
- 'force'
- Forces sending messages even when there are no files to work
- on.
+ 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
+harder, and are generally annoying for most people. If this issue
+bothers you, you can "normalize" the already finished PO translation by
+executing on the command line 'msgcat -o FILE.po FILE.po', before
+installing it in the repository. Either way, the build system will
+treat it is a valid PO file.
- 'no-diffs'
- Disables sending "www" vs. "www-LANG" differences as
- attachments.
+ For those lucky Emacs users, here is a code snippet that you can put
+in your '.emacs'; doing 'M-x po-wrap' while in PO mode will wrap all
+long lines:
- '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.
+ (defun po-wrap ()
+ "Filter current po-mode buffer through `msgcat' tool to wrap all lines."
+ (interactive)
+ (if (eq major-mode 'po-mode)
+ (let ((tmp-file (make-temp-file "po-wrap."))
+ (tmp-buf (generate-new-buffer "*temp*")))
+ (unwind-protect
+ (progn
+ (write-region (point-min) (point-max) tmp-file nil 1)
+ (if (zerop
+ (call-process
+ "msgcat" nil tmp-buf t (shell-quote-argument tmp-file)))
+ (let ((saved (point))
+ (inhibit-read-only t))
+ (delete-region (point-min) (point-max))
+ (insert-buffer tmp-buf)
+ (goto-char (min saved (point-max))))
+ (with-current-buffer tmp-buf
+ (error (buffer-string)))))
+ (kill-buffer tmp-buf)
+ (delete-file tmp-file)))))
- This is an example of 'email-aliases':
+ It is highly desirable that you check if the PO file you finished
+translating (or editing) is valid, before committing it. This is done
+by running 'msgfmt -cv -o /dev/null FILE' or by simply pressing 'V' in
+PO mode. The build system automatically verifies each PO file when
+invoked with 'VALIDATE=yes', but you won't get a warm and fuzzy feeling
+if a stupid typo you made halts the whole update of all translations.
+Such things happen to everyone, so it is a good practice to check before
+you actually commit.
- 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
+4.1.1 The Special Slot for Translator's Notes
+---------------------------------------------
- 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.
+Sometimes it is necessary to complement the translation of an essay with
+translator's notes. The special message '*GNUN-SLOT: TRANSLATOR'S
+NOTES*' is designed to serve this purpose. If your translation doesn't
+have notes, you should "translate" the 'msgstr' as a space
+(<SPC>)--otherwise the PO file will be considered incomplete, which is
+not what you want. Here is an example how to use translators' notes in
+a PO file:
-'format'
- A convenience rule to re-wrap all files upto the standard length.
- Most PO editors leave the 'msgstr' as a single long line after it
- has been edited, but GNUN will automatically re-wrap the file to
- the standard line length when it is processed. Wrapping long lines
- in PO files is a good practice as it avoids unnecessary revisions.
+ # type: Content of: <p>
+ msgid ""
+ "To understand the concept, you should think of <q>free</q> "
+ "as in <q>free speech,</q> not as in <q>free beer.</q>"
+ msgstr ""
+ "Translated message, where you want to clarify beer<sup><a "
+ "href=\"#TransNote1\">1</a></sup>, presumably because the "
+ "expression in your language is different"
+ ...
+ ...
+ # type: Content of: <div>
+ #. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
+ msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
+ msgstr ""
+ "<h3>Translator's notes</h3>\n"
+ "<ol>\n"
+ "<li id=\"TransNote1\">Note clarifying the text.</li>\n"
+ "</ol>\n"
- This rule checks for all translations that have lines longer than
- 80, and runs 'msgcat' accordingly to reformat them. For that
- reason, it is recommended that you wrap all long lines in the
- comment fields (e.g. the file header, including the copyright
- statement, and any other comments for specific messages), because
- 'make format' will unnecessarily invoke 'msgcat' for any file that
- has a longer line, wherever it may occur.
+ Certainly, everything in the 'msgstr's should be in your native
+language; we use English here in order the example to be understood by
+everyone. If you have more notes, each subsequent one should be with
+incremented number, i.e. 'TransNote2', 'TransNote3', etc. and you have
+to add them as more '<li>' elements accordingly.
-'publish'
- The 'publish' rule's task is to copy all modified files to the
- official "www" repository. It depends on the 'format' target to
- ensure that all files are re-wrapped to the standard line length
- limit, but deliberately does not depend on 'sync VCS=yes'.
- Usually, one would run 'make publish' when one or a bunch of PO
- files are in a satisfactory condition to be published, and this
- rule is just a convenience to avoid multiple manual 'cp'
- invocations. As a rule of thumb, before running this rule it is
- sane to run 'sync' and correct any "fuzzy" messages and other
- problems, if necessary.
+ Do not worry about the '\n' character--it is inserted automatically
+when you press <RET>. It is not compulsory that notes start on a new
+line, this is the recommended way simply because it is easier to edit
+them.
- The 'publish' rule does not depend on 'sync' explicitly, because
- that would be a nuisance for offline operations and basically
- unnecessary when the committer is fairly confident that there are
- no changes to (re-)merge. A hard dependency on 'sync' would slow
- down the operation considerably.
+ It is important to follow this specification, because notes will look
+consistently in all languages and will be clearly distinguishable from
+authors' footnotes, if any. Furthermore, it would be easier to define a
+special CSS class for them, and also to convert the translations in
+other formats such as Texinfo--when these features are implemented.
- As usual, when committing to the official repository, it is always
- a good practice to examine the output of 'cvs diff'.
+4.1.2 The Special Slot for Translator's Credits
+-----------------------------------------------
- Invoking 'make publish' prints warnings and does not actually copy
- the affected file if the sub-directory in "www" is non-existent or
- the corresponding '.pot' is missing.
+Most of the translators usually put their name under the translation, in
+the "footer" area. This is entirely acceptable, since some readers
+prefer to send buggestions directly to the translator. Also, giving
+credit where credit is due is a natural thing.
- Typically, after an editing session (whether it involves actual
- editing or just merging contributions from team members), one would
- do:
+ Like the previous slot, you should "translate" it as a <SPC> if you
+don't want your name to appear there.
- $ make sync VCS=yes
- $ make publish
- $ cd WWWDIR
- $ cvs up
- (Add all new translations, if any.)
- $ cvs add FILE ...
- $ cvs diff
- $ cvs commit -m "Some descriptive message."
+ Here is an example of the recommended way to specify credits:
-'clean'
- Deletes all backup and auto-generated files.
+ <b>Traduction</b>: Benjamin Drieu
+ <a href="mailto:address@hidden";><address@hidden></a>,
+ 2007, 2008.
- 'make VCS=yes' is the recommended command to be run periodically. To
-check the status of the translations, run 'make report'.
+ It is highly desirable to use this form, but you may omit the email
+address or add a link to translator's noncommercial personal home page,
+provided that the translation team leader ensures that it constantly
+meets the linking criteria for gnu.org. Please follow the FSF HTML
+Style Sheet when adding URIs or other information.
- 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. 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.
+4.2 Useful Hints for Editing PO Files
+=====================================
-2.3.6.3 Automatic Synchronization and Status Reports
-....................................................
+This section contains additional explanations, some in the form of
+advices and recommendations; not all of them are strictly related to PO
+files editing.
-It is convenient to invoke such synchronization automatically, for
-example once every day. If you have enabled commit notifications for
-the project's repository, any new changes will be visible for
-subscribers. Here is an example crontab entry:
+ * 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.
- # m h dom mon dow command
- @daily cd $HOME/projects/www-LANG; make VCS=yes
+ 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.
- It is not necessary the job to be run on the team leader's machine,
-since all team members have write access to their project repository.
+ * 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.
- If desired, you could set up another job to report the status of the
-translations weekly or fortnightly, for example:
+ * 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.
- # m h dom mon dow command
- @weekly cd $HOME/projects/www-LANG; \
- make report | mail -s "Weekly statistics" \
- address@hidden
+ * 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.
- *Caution:* Most cron implementations do not allow the character '\'
-as a line continuation character--the example shown is made that way for
-better readability.
+ * 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.
-2.3.7 Using Compendia
----------------------
+ * 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:
-Compendium is a PO file including translations for common strings; it is
-used to fill other PO files. *Note Compendium: (gettext)Compendium.
-One example of such common strings is the footer text about reporting
-bugs and sending inquiries: when a webmaster updates footer texts in an
-article, GNUN will use compendia to automatically fill the translations
-for the new version of the strings.
+ # 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"
- GNUN uses compendia located in the 'server/gnun/compendia' directory
-of the 'www' web repository. There are two kinds of compendia:
-'master.LANG.po' and 'compendium.LANG.po'.
+ * 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.
- The first kind, 'master.LANG.po', can be used to simultaneously
-update all occurrences of the translations of a given string.
-Translations from this file will override the translations from
-'ARTICLE.LANG.po'. When 'master.LANG.po' is updated, the translations
-will be rebuilt. GNUN doesn't modify this kind of compendia.
+ * 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.
- The second kind, 'compendium.LANG.po', is updated automatically.
-GNUN finds strings that repeat many times in POTs of articles and
-collects them in 'compendium.pot'. Then it checks all available
-'ARTICLE.LANG.po' files for translations of those strings and generates
-'compendium.LANG.po'. This file is also used to fill missing
-translations, but it doesn't override the translations from
-'ARTICLE.LANG.po', and the strings coming from 'compendium.LANG.po' are
-always marked as "fuzzy" to prevent propagation of translations that may
-be wrong in a different context.
+4.3 Transforming Existing Translation in PO Format
+==================================================
- When updating 'compendium.pot', some strings should be excluded even
-though they repeat in the POT files many times--for instance, GNUN slots
-for translators' notes. *Note Notes Slot::. They are not real
-translations, this is why they are likely to be different for different
-articles. In order to avoid including them in compendia, GNUN checks a
-specific file, 'exclude.pot', and when that file contains the string, it
-won't be added to 'compendium.pot'.
+Migrating an existing translation to a PO file format is basically
+editing the header as described in the previous section, and populating
+each of the messages by copying the already translated text and/or
+markup from the existing translation in HTML format in the relevant
+message.
-2.3.8 Building Sitemap
-----------------------
+ Typically, you will visit 'po/foo.LANG.po' (in PO mode) and
+'foo.LANG.html' (in HTML mode) in another buffer. Then you can copy a
+paragraph or an element from the latter and yank it in the relevant
+message in the former. Be extra careful, since this is the time to
+check _precisely_ that the translation corresponds to the original.
+Further changes will be reflected, but if your "initial" PO file is not
+a 100% match, that would not necessarily mean that it is an improvement.
+Since it is very easy to do this kind of check, because the relevant
+'msgid' and 'msgstr' appear one above the other in the same buffer (or
+the similar concept in other PO editors), please _do_ perform this
+initial sanity check even if you are confident that the translation you
+have been yanking strings from is a completely up-to-date translation.
-Sitemaps differ from regular pages in two respects:
+ There is also a semi-automatic way to produce an initial PO file.
+You checkout the revision of the English page, 'foo.html', that
+corresponds to the latest revision of the translation, 'foo.LANG.html'.
+Then you run 'gnun-preconvert' which invokes 'po4a-gettextize' (*Note
+gnun-preconvert::.):
- 1. They are typically regenerated automatically from the texts of the
- articles.
+ gnun-preconvert foo.lang.html foo.html
- 2. They mostly consist of links, therefore significant part of their
- text should come to translations without any changes.
+ If some passages in 'foo.LANG.html' don't match the structure of
+'foo.html', error messages will be displayed. Check them, adjust the
+files and try again. When you succeed, the result will be written to
+foo.lang.po. After that, run 'gnun-merge-preconverted' (*Note
+gnun-merge-preconverted::.):
- Also, sitemaps contain many translatable messages, so it is desirable
-to eliminate manual work where possible.
+ gnun-merge-preconverted -C compendium.lang.po foo.lang.po foo.pot
- In order to take this into account, GNUN provides the 'sitemap'
-variable in 'gnun.mk'. All articles listed in 'sitemap' are rebuilt
-using an additional compendium (when present),
-'server/gnun/compendia/sitemap-compendium.LANG.po'.
+ If you have no compendium, just omit the "'-C compendium.lang.po'"
+part.
- Those additional compendia are supposed to be compiled outside of
-GNUN by the same tool that generates the sitemap. It is responsibility
-of that tool to provide the compendia with reasonable translations whose
-'msgid's match those generated by PO4A when processing the English
-version of the sitemap.
+ 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
+checking.
-2.3.9 Special Handling for GNU News
------------------------------------
+ There is no need to delete the existing HTML translation, GNUN will
+automatically overwrite it. The only thing a translator should do is to
+commit the PO file in the repository.
-*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.
+ When an essay has been translated by several people through the
+years, it is important that this information is recorded and reflected
+in the PO file. In the future, special targets may be added to enable
+the FSF to check who translated a particular article, and when.
- 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.
+ A recommended way to do this is as follows:
- 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.
+ # French translation of http://www.gnu.org/philosophy/bsd.html
+ # Copyright (C) 2006, 2007, 2008 Free Software Foundation, Inc.
+ # This file is distributed under the same license as the gnu.org article.
+ # Ce'dric Corazza <address@hidden>, 2006, 2008.
+ # Jero^me Dominguez <address@hidden>, 2007.
- 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.
+ In this example, it is clear that Ce'dric made the initial
+translation, Jero^me made some changes in 2007, and the original
+translator returned in 2008 and continued maintaining it.
-2.4 Tips and Hints for Webmasters
-=================================
+5 Tips and Hints for Webmasters
+*******************************
This section contains some tips and general recommendations for
webmasters in no particular order--it is not mandatory to follow them,
@@ -1677,8 +1677,8 @@
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
-----------------
+5.1 Validation
+==============
The script 'gnun-validate-html' is useful for webmasters who want to
verify if their (potentially intrusive) changes result in a valid
@@ -1689,8 +1689,8 @@
*Note gnun-validate-html::, for more information.
-2.4.2 Comments for Translators
-------------------------------
+5.2 Comments for Translators
+============================
If you want a comment to be visible for translators, place it _inside_
the element, for example:
@@ -1712,8 +1712,8 @@
the beginning of the HTML comment ('<!--'), since this will
unnecessarily indent the comment in the POT.
-2.4.3 Modifying Boilerplates
-----------------------------
+5.3 Modifying Boilerplates
+==========================
*Warning:* Any significant structural diversion from 'boilerplate.html'
in a specific article may result in errors from GNUN. Any untested
@@ -1723,8 +1723,8 @@
happen--only that they must be applied in our sandbox first, to ensure a
smooth transition.
-2.4.4 Localized URLs
---------------------
+5.4 Localized URLs
+==================
Some articles may contain diagrams or other images with English text
that can and should be translated. In order to make the translated
@@ -1753,8 +1753,8 @@
And please don't forget to commit the image in its source form
(typically, in SVG format).
-2.4.5 Splitting Long Passages
------------------------------
+5.5 Splitting Long Passages
+===========================
GNUN splits typical text by paragraphs, and translators write the
translations for the resulting parts of the text one by one. When a
@@ -1777,7 +1777,7 @@
parts of the sentence, and the translator has no control over the
sequence of the strings in the translation.
-3 Unexciting Information for GNUN's Operation
+6 Unexciting Information for GNUN's Operation
*********************************************
This chapter might be of interest probably only to people who would have
@@ -1785,7 +1785,7 @@
front-end, except the section about scripts that includes descriptions
of programs that may also be useful for the translators.
-3.1 Files and Directories
+6.1 Files and Directories
=========================
This is a brief diagram of "www" working copy; note that in this section
@@ -1924,7 +1924,7 @@
'server/gnun/compendia'
The directory for compendia. *Note Compendia::.
-3.2 GNUN Scripts
+6.2 GNUN Scripts
================
For the time being there are several helper scripts. Some of them are
@@ -1933,7 +1933,7 @@
mechanical actions, like initially filling the headers in the PO files.
They all can be invoked separately, as stand-alone programs.
-3.2.1 The 'gnun-add-fuzzy-diff' Script
+6.2.1 The 'gnun-add-fuzzy-diff' Script
--------------------------------------
This script adds comments with differences of current 'msgid's against
@@ -1954,7 +1954,7 @@
'--help'
Display usage information and exit.
-3.2.2 The 'gnun-diff-po' Script
+6.2.2 The 'gnun-diff-po' Script
-------------------------------
This script compares two versions of a PO file. It produces a HTML page
@@ -1989,7 +1989,7 @@
'--help'
Display usage information and exit.
-3.2.3 The 'gnun-init-po' Script
+6.2.3 The 'gnun-init-po' Script
-------------------------------
This script initializes a PO file using POT generated with GNUN, and
@@ -2032,7 +2032,7 @@
The PO file name is guessed from the name of POT and language suffix;
the file is created in the current working directory.
-3.2.4 The 'gnun-preconvert' Script
+6.2.4 The 'gnun-preconvert' Script
----------------------------------
This script uses 'po4a-gettextize' to convert a translation from HTML to
@@ -2053,7 +2053,7 @@
'--help'
Display usage information and exit.
-3.2.5 The 'gnun-merge-preconverted' Script
+6.2.5 The 'gnun-merge-preconverted' Script
------------------------------------------
This script takes 'po4a-gettextize' output, adds current 'msgid's as
@@ -2073,7 +2073,7 @@
'--help'
Display usage information and exit.
-3.2.6 The 'gnun-report' Script
+6.2.6 The 'gnun-report' Script
------------------------------
This script generates HTML reports about translations of a given team.
@@ -2115,7 +2115,7 @@
There is also a target in 'GNUmakefile' to generate text reports
intended for monthly messages sent to the teams. *Note report::.
-3.2.7 The 'gnun-validate-html' Script
+6.2.7 The 'gnun-validate-html' Script
-------------------------------------
This is a Bash script whose purpose is to "validate" both the original
@@ -2151,7 +2151,7 @@
'--help'
Display usage information and exit.
-3.2.8 The 'mailfail' Script
+6.2.8 The 'mailfail' Script
---------------------------
This is a helper script that runs a command, and mails the output of
@@ -2195,7 +2195,7 @@
argument is missing, the usage information is printed to the standard
output and the exit code is 1.
-3.2.9 The 'validate-html-notify' Script
+6.2.9 The 'validate-html-notify' Script
---------------------------------------
This script is a wrapper around 'gnun-validate-html' (*note
@@ -2223,7 +2223,7 @@
wrapper has a specific task and cannot be used to invoke an arbitrary
command--use 'mailfail' for that. *Note mailfail::.
-3.2.10 The 'gnun-clear-previous' Script
+6.2.10 The 'gnun-clear-previous' Script
---------------------------------------
This simple script is not used internally in GNUN. It is merely for
@@ -2245,7 +2245,7 @@
'--help'
Print usage information on stdout.
-4 Reporting Bugs
+7 Reporting Bugs
****************
GNUnited Nations, like any other software, is not bug free. There are
@@ -2273,19 +2273,19 @@
* comments for translators: Comments for Translators.
(line 1694)
* comparing, translations: gnun-diff-po. (line 1959)
-* compendia: Compendia. (line 1576)
-* compendium.pot: Compendia. (line 1576)
+* compendia: Compendia. (line 851)
+* compendium.pot: Compendia. (line 851)
* config.mk: Invoking GNUN. (line 365)
* conventional separator for strings: Splitting Long Passages.
(line 1758)
-* conversion of existing translations: Migrating. (line 1109)
+* conversion of existing translations: Migrating. (line 1597)
* conversion of existing translations <1>: gnun-preconvert. (line 2037)
* conversion of existing translations <2>: gnun-merge-preconverted.
(line 2058)
-* credits, translators: New Translation. (line 919)
-* credits, translators <1>: Credits Slot. (line 1018)
+* credits, translators: New Translation. (line 1407)
+* credits, translators <1>: Credits Slot. (line 1506)
* cron, team maintenance: GNUmakefile.team and Cron.
- (line 1550)
+ (line 1257)
* CVS: Runtime Variables. (line 400)
* deferred generation of articles: Runtime Variables. (line 482)
* defining articles in the root dir: Main Variables. (line 767)
@@ -2295,57 +2295,57 @@
* defining templates <2>: Main Variables. (line 741)
* directories, defining: Main Variables. (line 774)
* email-aliases: GNUmakefile.team Targets.
- (line 1432)
-* exclude.pot: Compendia. (line 1576)
+ (line 1139)
+* exclude.pot: Compendia. (line 851)
* extra-templates: Main Variables. (line 734)
* fuzzy strings: Runtime Variables. (line 482)
* FUZZY_DIFF_LINGUAS: Main Variables. (line 761)
-* generic notice, translations: generic.LANG.html. (line 1177)
+* generic notice, translations: generic.LANG.html. (line 795)
* GNUmakefile: Invoking GNUN. (line 350)
-* GNUmakefile.team: PO Files and Team. (line 1233)
+* GNUmakefile.team: Team's Repository. (line 940)
* gnun.mk: Invoking GNUN. (line 365)
* gnun.mk <1>: Main Variables. (line 702)
-* gnunews: GNU News. (line 1639)
-* gnusflashes: GNU News. (line 1639)
+* gnunews: GNU News. (line 914)
+* gnusflashes: GNU News. (line 914)
* GRACE: Runtime Variables. (line 482)
* grace period: Runtime Variables. (line 482)
* initializing, translations: gnun-init-po. (line 1994)
* invocation: Invoking GNUN. (line 350)
* invoking: Invoking GNUN. (line 350)
* localized URLs: Localized URLs. (line 1728)
-* long lines, wrap: New Translation. (line 925)
+* long lines, wrap: New Translation. (line 1413)
* long passages, avoiding: Splitting Long Passages.
(line 1758)
* mail, notifications: Runtime Variables. (line 449)
* mail, notifications <1>: GNUmakefile.team Variables.
- (line 1361)
+ (line 1068)
* mail, notifications <2>: mailfail. (line 2156)
-* migration, translations: Migrating. (line 1109)
+* migration, translations: Migrating. (line 1597)
* migration, translations <1>: gnun-preconvert. (line 2037)
* migration, translations <2>: gnun-merge-preconverted.
(line 2058)
-* new translation: New Translation. (line 802)
+* new translation: New Translation. (line 1290)
* new translations, notifications/announcements: Runtime Variables.
(line 462)
-* notes, translators: New Translation. (line 910)
-* notes, translators <1>: Notes Slot. (line 971)
+* notes, translators: New Translation. (line 1398)
+* notes, translators <1>: Notes Slot. (line 1459)
* notification period: GNUmakefile.team Targets.
- (line 1440)
+ (line 1147)
* notification period, default: GNUmakefile.team Variables.
- (line 1359)
+ (line 1066)
* NOTIFICATION_PERIOD: GNUmakefile.team Variables.
- (line 1359)
+ (line 1066)
* NOTIFY: Runtime Variables. (line 449)
* NOTIFY <1>: GNUmakefile.team Variables.
- (line 1361)
+ (line 1068)
* nottab: GNUmakefile.team Targets.
- (line 1415)
+ (line 1122)
* optional-templates: Main Variables. (line 741)
* outdated translations, notifications: GNUmakefile.team Targets.
- (line 1407)
+ (line 1114)
* OUTDATED-GRACE: Runtime Variables. (line 494)
* output, detailed: Runtime Variables. (line 475)
-* PO headers: New Translation. (line 843)
+* PO headers: New Translation. (line 1331)
* POT generation, articles: Main Variables. (line 778)
* previous, diff: Main Variables. (line 761)
* previous, diff <1>: gnun-add-fuzzy-diff.
@@ -2355,43 +2355,43 @@
* priorities.mk: Invoking GNUN. (line 365)
* priorities.mk <1>: report. (line 624)
* priorities.mk <2>: gnun-report. (line 2083)
-* project repository: PO Files and Team. (line 1233)
-* recommendations, PO files: PO Tips. (line 1041)
+* project repository: Team's Repository. (line 940)
+* recommendations, PO files: PO Tips. (line 1529)
* reminder period: GNUmakefile.team Targets.
- (line 1440)
+ (line 1147)
* reminder period, default: GNUmakefile.team Variables.
- (line 1359)
+ (line 1066)
* reporting: report. (line 611)
* reporting <1>: gnun-report. (line 2078)
* reporting bugs: Bugs. (line 2250)
-* repository, translation project: PO Files and Team. (line 1233)
+* repository, translation project: Team's Repository. (line 940)
* ROOT: Main Variables. (line 767)
* sanity checks: Runtime Variables. (line 427)
* sitemap: Main Variables. (line 756)
-* sitemap <1>: Sitemap. (line 1614)
+* sitemap <1>: Sitemap. (line 889)
* status, translations: report. (line 611)
* status, translations <1>: gnun-report. (line 2078)
* Subversion: Runtime Variables. (line 400)
* SVN: Runtime Variables. (line 400)
* synchronization, repository: sync. (line 576)
* TEAM: Runtime Variables. (line 503)
-* team information: generic.LANG.html. (line 1177)
-* team maintenance: PO Files and Team. (line 1233)
+* team information: generic.LANG.html. (line 795)
+* team maintenance: Team's Repository. (line 940)
* team maintenance, cron: GNUmakefile.team and Cron.
- (line 1550)
-* team workflow: PO Files and Team. (line 1251)
+ (line 1257)
+* team workflow: Team's Repository. (line 958)
* templates, additional: Main Variables. (line 734)
* templates, defining: Main Variables. (line 719)
* templates, optional: Main Variables. (line 741)
* TEMPLATE_LINGUAS: Main Variables. (line 719)
-* tips, translators: PO Tips. (line 1041)
+* tips, translators: PO Tips. (line 1529)
* tips, webmasters: Webmaster Tips. (line 1665)
-* translation memory: Compendia. (line 1576)
-* translation, new: New Translation. (line 802)
-* translators' credits: New Translation. (line 919)
-* translators' credits <1>: Credits Slot. (line 1018)
-* translators' notes: New Translation. (line 910)
-* translators' notes <1>: Notes Slot. (line 971)
+* translation memory: Compendia. (line 851)
+* translation, new: New Translation. (line 1290)
+* translators' credits: New Translation. (line 1407)
+* translators' credits <1>: Credits Slot. (line 1506)
+* translators' notes: New Translation. (line 1398)
+* translators' notes <1>: Notes Slot. (line 1459)
* triggering, build: Invoking GNUN. (line 350)
* VALIDATE: Runtime Variables. (line 427)
* validation: Runtime Variables. (line 427)
@@ -2406,8 +2406,8 @@
* VCS: Runtime Variables. (line 400)
* VERBOSE: Runtime Variables. (line 475)
* webmaster tips: Webmaster Tips. (line 1665)
-* whatsnew: GNU News. (line 1639)
-* wrapping long lines: New Translation. (line 925)
+* whatsnew: GNU News. (line 914)
+* wrapping long lines: New Translation. (line 1413)
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.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
Binary files /tmp/cvsJaiuAR and /tmp/cvsSyotXr differ
Index: gnun/index.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/index.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- gnun/index.html 31 Jan 2013 08:47:29 -0000 1.20
+++ gnun/index.html 1 Feb 2013 06:06:07 -0000 1.21
@@ -1,10 +1,10 @@
<!--#include virtual="/server/header.html" -->
-<title>GNU GNUN manual - GNU Project - Free Software Foundation (FSF)</title>
+<title>GNU GNUN Manual - GNU Project - Free Software Foundation (FSF)</title>
<!--#include virtual="/server/banner.html" -->
-<h2>GNU GNUN manual</h2>
+<h2>GNU GNUN Manual</h2>
<address>Free Software Foundation</address>
-<address>last updated January 31, 2013</address>
+<address>last updated February 01, 2013</address>
<p>This manual (gnun) is available in the following formats:</p>
Index: gnun/html_node/Advantages.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Advantages.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Advantages.html 31 Jan 2013 08:47:30 -0000 1.18
+++ gnun/html_node/Advantages.html 1 Feb 2013 06:06:08 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
Index: gnun/html_node/Bugs.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Bugs.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Bugs.html 31 Jan 2013 08:47:30 -0000 1.18
+++ gnun/html_node/Bugs.html 1 Feb 2013 06:06:08 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="Reporting-Bugs"></a>
-<h2 class="chapter">4 Reporting Bugs</h2>
+<h2 class="chapter">7 Reporting Bugs</h2>
<a name="index-bugs_002c-reporting"></a>
<a name="index-reporting-bugs"></a>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- gnun/html_node/Comments-for-Translators.html 31 Jan 2013 08:47:30
-0000 1.8
+++ gnun/html_node/Comments-for-Translators.html 1 Feb 2013 06:06:08
-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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="Comments-for-Translators-1"></a>
-<h4 class="subsection">2.4.2 Comments for Translators</h4>
+<h3 class="section">5.2 Comments for Translators</h3>
<a name="index-comments-for-translators"></a>
Index: gnun/html_node/Compendia.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Compendia.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- gnun/html_node/Compendia.html 31 Jan 2013 08:47:30 -0000 1.7
+++ gnun/html_node/Compendia.html 1 Feb 2013 06:06:08 -0000 1.8
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -28,9 +28,9 @@
<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="PO-Files.html#PO-Files" rel="up" title="PO Files">
+<link href="Usage.html#Usage" rel="up" title="Usage">
<link href="Sitemap.html#Sitemap" rel="next" title="Sitemap">
-<link href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron"
rel="previous" title="GNUmakefile.team and Cron">
+<link href="languages_002etxt.html#languages_002etxt" rel="previous"
title="languages.txt">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -67,11 +67,11 @@
<a name="Compendia"></a>
<div class="header">
<p>
-Next: <a href="Sitemap.html#Sitemap" accesskey="n" rel="next">Sitemap</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>
+Next: <a href="Sitemap.html#Sitemap" accesskey="n" rel="next">Sitemap</a>,
Previous: <a href="languages_002etxt.html#languages_002etxt" accesskey="p"
rel="previous">languages.txt</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="Using-Compendia"></a>
-<h4 class="subsection">2.3.7 Using Compendia</h4>
+<h3 class="section">2.7 Using Compendia</h3>
<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>
-Next: <a href="Sitemap.html#Sitemap" accesskey="n" rel="next">Sitemap</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>
+Next: <a href="Sitemap.html#Sitemap" accesskey="n" rel="next">Sitemap</a>,
Previous: <a href="languages_002etxt.html#languages_002etxt" accesskey="p"
rel="previous">languages.txt</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/Concepts.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Concepts.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Concepts.html 31 Jan 2013 08:47:30 -0000 1.18
+++ gnun/html_node/Concepts.html 1 Feb 2013 06:06:08 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Copying-This-Manual.html 31 Jan 2013 08:47:30 -0000
1.18
+++ gnun/html_node/Copying-This-Manual.html 1 Feb 2013 06:06:08 -0000
1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Credits-Slot.html 31 Jan 2013 08:47:30 -0000 1.18
+++ gnun/html_node/Credits-Slot.html 1 Feb 2013 06:06:08 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-Special-Slot-for-Translator_0027s-Credits"></a>
-<h4 class="subsubsection">2.3.1.2 The Special Slot for Translator’s
Credits</h4>
+<h4 class="subsection">4.1.2 The Special Slot for Translator’s
Credits</h4>
<a name="index-credits_002c-translators-1"></a>
<a name="index-translators_0027-credits-1"></a>
Index: gnun/html_node/Disadvantages.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/Disadvantages.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Disadvantages.html 31 Jan 2013 08:47:30 -0000 1.18
+++ gnun/html_node/Disadvantages.html 1 Feb 2013 06:06:09 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
Index: gnun/html_node/Files-and-Directories.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/Files-and-Directories.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- gnun/html_node/Files-and-Directories.html 31 Jan 2013 08:47:30 -0000
1.2
+++ gnun/html_node/Files-and-Directories.html 1 Feb 2013 06:06:09 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="Files-and-Directories-1"></a>
-<h3 class="section">3.1 Files and Directories</h3>
+<h3 class="section">6.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
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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/GNU-News.html 31 Jan 2013 08:47:30 -0000 1.18
+++ gnun/html_node/GNU-News.html 1 Feb 2013 06:06:09 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -28,8 +28,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="PO-Files.html#PO-Files" rel="up" title="PO Files">
-<link href="Webmaster-Tips.html#Webmaster-Tips" rel="next" title="Webmaster
Tips">
+<link href="Usage.html#Usage" rel="up" title="Usage">
+<link href="Team_0027s-Repository.html#Team_0027s-Repository" rel="next"
title="Team's Repository">
<link href="Sitemap.html#Sitemap" rel="previous" title="Sitemap">
<style type="text/css">
<!--
@@ -67,11 +67,11 @@
<a name="GNU-News"></a>
<div class="header">
<p>
-Previous: <a href="Sitemap.html#Sitemap" accesskey="p"
rel="previous">Sitemap</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="Sitemap.html#Sitemap" accesskey="p"
rel="previous">Sitemap</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="Special-Handling-for-GNU-News"></a>
-<h4 class="subsection">2.3.9 Special Handling for GNU News</h4>
+<h3 class="section">2.9 Special Handling for GNU News</h3>
<a name="index-gnunews"></a>
<a name="index-whatsnew"></a>
<a name="index-gnusflashes"></a>
Index: gnun/html_node/GNUN-Slots.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/GNUN-Slots.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- gnun/html_node/GNUN-Slots.html 31 Jan 2013 08:47:30 -0000 1.2
+++ gnun/html_node/GNUN-Slots.html 1 Feb 2013 06:06:09 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
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.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- gnun/html_node/GNUmakefile_002eteam-Targets.html 31 Jan 2013 08:47:31
-0000 1.3
+++ gnun/html_node/GNUmakefile_002eteam-Targets.html 1 Feb 2013 06:06:09
-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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -28,7 +28,7 @@
<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="PO-Files-and-Team.html#PO-Files-and-Team" rel="up" title="PO Files
and Team">
+<link href="Team_0027s-Repository.html#Team_0027s-Repository" rel="up"
title="Team's Repository">
<link href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron"
rel="next" title="GNUmakefile.team and Cron">
<link
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables"
rel="previous" title="GNUmakefile.team Variables">
<style type="text/css">
@@ -67,11 +67,11 @@
<a name="GNUmakefile_002eteam-Targets"></a>
<div class="header">
<p>
-Next: <a
href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron"
accesskey="n" rel="next">GNUmakefile.team and Cron</a>, Previous: <a
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables"
accesskey="p" rel="previous">GNUmakefile.team Variables</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>
+Next: <a
href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron"
accesskey="n" rel="next">GNUmakefile.team and Cron</a>, Previous: <a
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables"
accesskey="p" rel="previous">GNUmakefile.team Variables</a>, Up: <a
href="Team_0027s-Repository.html#Team_0027s-Repository" accesskey="u"
rel="up">Team's Repository</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="Targets-in-GNUmakefile_002eteam"></a>
-<h4 class="subsubsection">2.3.6.2 Targets in <samp>GNUmakefile.team</samp></h4>
+<h3 class="section">3.2 Targets in <samp>GNUmakefile.team</samp></h3>
<dl compact="compact">
<dt><code>update</code></dt>
@@ -260,7 +260,7 @@
<hr>
<div class="header">
<p>
-Next: <a
href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron"
accesskey="n" rel="next">GNUmakefile.team and Cron</a>, Previous: <a
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables"
accesskey="p" rel="previous">GNUmakefile.team Variables</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>
+Next: <a
href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron"
accesskey="n" rel="next">GNUmakefile.team and Cron</a>, Previous: <a
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables"
accesskey="p" rel="previous">GNUmakefile.team Variables</a>, Up: <a
href="Team_0027s-Repository.html#Team_0027s-Repository" accesskey="u"
rel="up">Team's Repository</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-Variables.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/GNUmakefile_002eteam-Variables.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/GNUmakefile_002eteam-Variables.html 31 Jan 2013 08:47:31
-0000 1.18
+++ gnun/html_node/GNUmakefile_002eteam-Variables.html 1 Feb 2013 06:06:09
-0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -28,9 +28,9 @@
<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="PO-Files-and-Team.html#PO-Files-and-Team" rel="up" title="PO Files
and Team">
+<link href="Team_0027s-Repository.html#Team_0027s-Repository" rel="up"
title="Team's Repository">
<link href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets"
rel="next" title="GNUmakefile.team Targets">
-<link href="PO-Files-and-Team.html#PO-Files-and-Team" rel="previous" title="PO
Files and Team">
+<link href="Team_0027s-Repository.html#Team_0027s-Repository" rel="previous"
title="Team's Repository">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -67,11 +67,11 @@
<a name="GNUmakefile_002eteam-Variables"></a>
<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>
+Next: <a href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets"
accesskey="n" rel="next">GNUmakefile.team Targets</a>, Up: <a
href="Team_0027s-Repository.html#Team_0027s-Repository" accesskey="u"
rel="up">Team's Repository</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="Adopting-GNUmakefile_002eteam-for-a-Specific-Team"></a>
-<h4 class="subsubsection">2.3.6.1 Adopting <samp>GNUmakefile.team</samp> for a
Specific Team</h4>
+<h3 class="section">3.1 Adopting <samp>GNUmakefile.team</samp> for a Specific
Team</h3>
<p>To adjust the makefile for your team, you need to edit the next
variables.
@@ -165,7 +165,7 @@
<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>
+Next: <a href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets"
accesskey="n" rel="next">GNUmakefile.team Targets</a>, Up: <a
href="Team_0027s-Repository.html#Team_0027s-Repository" accesskey="u"
rel="up">Team's Repository</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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/GNUmakefile_002eteam-and-Cron.html 31 Jan 2013 08:47:31
-0000 1.18
+++ gnun/html_node/GNUmakefile_002eteam-and-Cron.html 1 Feb 2013 06:06:09
-0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -28,8 +28,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="PO-Files-and-Team.html#PO-Files-and-Team" rel="up" title="PO Files
and Team">
-<link href="Compendia.html#Compendia" rel="next" title="Compendia">
+<link href="Team_0027s-Repository.html#Team_0027s-Repository" rel="up"
title="Team's Repository">
+<link href="PO-Files.html#PO-Files" rel="next" title="PO Files">
<link href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets"
rel="previous" title="GNUmakefile.team Targets">
<style type="text/css">
<!--
@@ -67,11 +67,11 @@
<a name="GNUmakefile_002eteam-and-Cron"></a>
<div class="header">
<p>
-Previous: <a
href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets"
accesskey="p" rel="previous">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>
+Previous: <a
href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets"
accesskey="p" rel="previous">GNUmakefile.team Targets</a>, Up: <a
href="Team_0027s-Repository.html#Team_0027s-Repository" accesskey="u"
rel="up">Team's Repository</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="Automatic-Synchronization-and-Status-Reports"></a>
-<h4 class="subsubsection">2.3.6.3 Automatic Synchronization and Status
Reports</h4>
+<h3 class="section">3.3 Automatic Synchronization and Status Reports</h3>
<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.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- gnun/html_node/GRACE.html 31 Jan 2013 08:47:31 -0000 1.4
+++ gnun/html_node/GRACE.html 1 Feb 2013 06:06:09 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
Index: gnun/html_node/Index.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Index.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Index.html 31 Jan 2013 08:47:31 -0000 1.18
+++ gnun/html_node/Index.html 1 Feb 2013 06:06:09 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -160,7 +160,7 @@
<tr><th><a name="Index_cp_letter-G">G</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a
href="generic_002eLANG_002ehtml.html#index-generic-notice_002c-translations">generic
notice, translations</a>:</td><td> </td><td valign="top"><a
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml">generic.LANG.html</a></td></tr>
<tr><td></td><td valign="top"><a
href="Invoking-GNUN.html#index-GNUmakefile">GNUmakefile</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="PO-Files-and-Team.html#index-GNUmakefile_002eteam">GNUmakefile.team</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="Team_0027s-Repository.html#index-GNUmakefile_002eteam">GNUmakefile.team</a>:</td><td> </td><td
valign="top"><a href="Team_0027s-Repository.html#Team_0027s-Repository">Team's
Repository</a></td></tr>
<tr><td></td><td valign="top"><a
href="Invoking-GNUN.html#index-gnun_002emk">gnun.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="Main-Variables.html#index-gnun_002emk-1">gnun.mk</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="GNU-News.html#index-gnunews">gnunews</a>:</td><td> </td><td
valign="top"><a href="GNU-News.html#GNU-News">GNU News</a></td></tr>
@@ -213,7 +213,7 @@
<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="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></td><td valign="top"><a
href="Team_0027s-Repository.html#index-project-repository">project
repository</a>:</td><td> </td><td valign="top"><a
href="Team_0027s-Repository.html#Team_0027s-Repository">Team's
Repository</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>
@@ -222,7 +222,7 @@
<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>
-<tr><td></td><td valign="top"><a
href="PO-Files-and-Team.html#index-repository_002c-translation-project">repository,
translation project</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="Team_0027s-Repository.html#index-repository_002c-translation-project">repository,
translation project</a>:</td><td> </td><td valign="top"><a
href="Team_0027s-Repository.html#Team_0027s-Repository">Team's
Repository</a></td></tr>
<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-ROOT">ROOT</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-S">S</a></th><td></td><td></td></tr>
@@ -238,9 +238,9 @@
<tr><th><a name="Index_cp_letter-T">T</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-TEAM">TEAM</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="generic_002eLANG_002ehtml.html#index-team-information">team
information</a>:</td><td> </td><td valign="top"><a
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml">generic.LANG.html</a></td></tr>
-<tr><td></td><td valign="top"><a
href="PO-Files-and-Team.html#index-team-maintenance">team
maintenance</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="Team_0027s-Repository.html#index-team-maintenance">team
maintenance</a>:</td><td> </td><td valign="top"><a
href="Team_0027s-Repository.html#Team_0027s-Repository">Team's
Repository</a></td></tr>
<tr><td></td><td valign="top"><a
href="GNUmakefile_002eteam-and-Cron.html#index-team-maintenance_002c-cron">team
maintenance, cron</a>:</td><td> </td><td valign="top"><a
href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron">GNUmakefile.team
and Cron</a></td></tr>
-<tr><td></td><td valign="top"><a
href="PO-Files-and-Team.html#index-team-workflow">team
workflow</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="Team_0027s-Repository.html#index-team-workflow">team
workflow</a>:</td><td> </td><td valign="top"><a
href="Team_0027s-Repository.html#Team_0027s-Repository">Team's
Repository</a></td></tr>
<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-templates_002c-additional">templates,
additional</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-templates_002c-defining">templates,
defining</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-templates_002c-optional">templates,
optional</a>:</td><td> </td><td valign="top"><a
href="Main-Variables.html#Main-Variables">Main Variables</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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Internals.html 31 Jan 2013 08:47:31 -0000 1.18
+++ gnun/html_node/Internals.html 1 Feb 2013 06:06:10 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -67,11 +67,11 @@
<a name="Internals"></a>
<div class="header">
<p>
-Next: <a href="Bugs.html#Bugs" accesskey="n" rel="next">Bugs</a>, Previous: <a
href="Usage.html#Usage" accesskey="p" rel="previous">Usage</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>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+Next: <a href="Bugs.html#Bugs" accesskey="n" rel="next">Bugs</a>, Previous: <a
href="Webmaster-Tips.html#Webmaster-Tips" accesskey="p"
rel="previous">Webmaster 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>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<hr>
<a name="Unexciting-Information-for-GNUN_0027s-Operation"></a>
-<h2 class="chapter">3 Unexciting Information for GNUN’s Operation</h2>
+<h2 class="chapter">6 Unexciting Information for GNUN’s Operation</h2>
<p>This chapter might be of interest probably only to people who would have
special interest in the software, plan to enhance it or develop a
Index: gnun/html_node/Introduction.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Introduction.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Introduction.html 31 Jan 2013 08:47:31 -0000 1.18
+++ gnun/html_node/Introduction.html 1 Feb 2013 06:06:10 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Invoking-GNUN.html 31 Jan 2013 08:47:31 -0000 1.18
+++ gnun/html_node/Invoking-GNUN.html 1 Feb 2013 06:06:10 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -67,7 +67,7 @@
<a name="Invoking-GNUN"></a>
<div class="header">
<p>
-Next: <a href="Main-Variables.html#Main-Variables" accesskey="n"
rel="next">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>
+Next: <a href="Runtime-Variables.html#Runtime-Variables" accesskey="n"
rel="next">Runtime 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>
<hr>
<a name="Invoking-GNUN-1"></a>
@@ -126,17 +126,10 @@
your hypothetical tree. (For gnu.org, that is not necessary since
a proper <samp>gnun.mk</samp> is maintained in ‘www’.)
</p>
-<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top">• <a
href="Runtime-Variables.html#Runtime-Variables" accesskey="1">Runtime
Variables</a>:</td><td> </td><td align="left" valign="top">Variables
to control the build process.
-</td></tr>
-<tr><td align="left" valign="top">• <a
href="Special-Targets.html#Special-Targets" accesskey="2">Special
Targets</a>:</td><td> </td><td align="left" valign="top">Targets
that are not built by default.
-</td></tr>
-</table>
-
<hr>
<div class="header">
<p>
-Next: <a href="Main-Variables.html#Main-Variables" accesskey="n"
rel="next">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>
+Next: <a href="Runtime-Variables.html#Runtime-Variables" accesskey="n"
rel="next">Runtime 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/Localized-URLs.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/Localized-URLs.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- gnun/html_node/Localized-URLs.html 31 Jan 2013 08:47:31 -0000 1.8
+++ gnun/html_node/Localized-URLs.html 1 Feb 2013 06:06:10 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="Localized-URLs-1"></a>
-<h4 class="subsection">2.4.4 Localized URLs</h4>
+<h3 class="section">5.4 Localized URLs</h3>
<a name="index-localized-URLs"></a>
<p>Some articles may contain diagrams or other images with English text
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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Main-Variables.html 31 Jan 2013 08:47:31 -0000 1.18
+++ gnun/html_node/Main-Variables.html 1 Feb 2013 06:06:10 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -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="Usage.html#Usage" rel="up" title="Usage">
-<link href="PO-Files.html#PO-Files" rel="next" title="PO Files">
+<link href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
rel="next" title="generic.LANG.html">
<link href="validate_002dall.html#validate_002dall" rel="previous"
title="validate-all">
<style type="text/css">
<!--
@@ -67,11 +67,11 @@
<a name="Main-Variables"></a>
<div class="header">
<p>
-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>
+Next: <a href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
accesskey="n" rel="next">generic.LANG.html</a>, Previous: <a
href="Special-Targets.html#Special-Targets" accesskey="p"
rel="previous">Special Targets</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>
+<h3 class="section">2.4 Defining Articles to Be Built</h3>
<a name="index-variables-1"></a>
<a name="index-gnun_002emk-1"></a>
@@ -208,7 +208,7 @@
<hr>
<div class="header">
<p>
-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>
+Next: <a href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
accesskey="n" rel="next">generic.LANG.html</a>, Previous: <a
href="Special-Targets.html#Special-Targets" accesskey="p"
rel="previous">Special Targets</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/Migrating.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Migrating.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- gnun/html_node/Migrating.html 31 Jan 2013 08:47:31 -0000 1.19
+++ gnun/html_node/Migrating.html 1 Feb 2013 06:06:10 -0000 1.20
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -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="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
rel="next" title="generic.LANG.html">
+<link href="Webmaster-Tips.html#Webmaster-Tips" rel="next" title="Webmaster
Tips">
<link href="PO-Tips.html#PO-Tips" rel="previous" title="PO Tips">
<style type="text/css">
<!--
@@ -67,11 +67,11 @@
<a name="Migrating"></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="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>
+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.3 Transforming Existing Translation in PO
Format</h4>
+<h3 class="section">4.3 Transforming Existing Translation in PO Format</h3>
<a name="index-migration_002c-translations"></a>
<a name="index-conversion-of-existing-translations"></a>
@@ -150,7 +150,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="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>
+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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- gnun/html_node/Modifying-Boilerplates.html 31 Jan 2013 08:47:31 -0000
1.8
+++ gnun/html_node/Modifying-Boilerplates.html 1 Feb 2013 06:06:10 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="Modifying-Boilerplates-1"></a>
-<h4 class="subsection">2.4.3 Modifying Boilerplates</h4>
+<h3 class="section">5.3 Modifying Boilerplates</h3>
<a name="index-boilerplates"></a>
<p><strong>Warning:</strong> Any significant structural diversion from
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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/New-Translation.html 31 Jan 2013 08:47:31 -0000 1.18
+++ gnun/html_node/New-Translation.html 1 Feb 2013 06:06:10 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="Starting-a-New-Translation"></a>
-<h4 class="subsection">2.3.1 Starting a New Translation</h4>
+<h3 class="section">4.1 Starting a New Translation</h3>
<a name="index-translation_002c-new"></a>
<a name="index-new-translation"></a>
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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Notes-Slot.html 31 Jan 2013 08:47:31 -0000 1.18
+++ gnun/html_node/Notes-Slot.html 1 Feb 2013 06:06:10 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-Special-Slot-for-Translator_0027s-Notes"></a>
-<h4 class="subsubsection">2.3.1.1 The Special Slot for Translator’s
Notes</h4>
+<h4 class="subsection">4.1.1 The Special Slot for Translator’s Notes</h4>
<a name="index-notes_002c-translators-1"></a>
<a name="index-translators_0027-notes-1"></a>
Index: gnun/html_node/Overview.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Overview.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Overview.html 31 Jan 2013 08:47:31 -0000 1.18
+++ gnun/html_node/Overview.html 1 Feb 2013 06:06:10 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/PO-Files.html 31 Jan 2013 08:47:32 -0000 1.18
+++ gnun/html_node/PO-Files.html 1 Feb 2013 06:06:10 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -28,9 +28,9 @@
<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="Usage.html#Usage" rel="up" title="Usage">
+<link href="index.html#Top" rel="up" title="Top">
<link href="New-Translation.html#New-Translation" rel="next" title="New
Translation">
-<link href="Main-Variables.html#Main-Variables" rel="previous" title="Main
Variables">
+<link href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron"
rel="previous" title="GNUmakefile.team and Cron">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -67,11 +67,11 @@
<a name="PO-Files"></a>
<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>
+Next: <a href="Webmaster-Tips.html#Webmaster-Tips" accesskey="n"
rel="next">Webmaster Tips</a>, Previous: <a
href="Team_0027s-Repository.html#Team_0027s-Repository" accesskey="p"
rel="previous">Team's Repository</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>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="Working-with-PO-Files"></a>
-<h3 class="section">2.3 Working with PO Files</h3>
+<h2 class="chapter">4 Working with PO Files</h2>
<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>.
@@ -84,20 +84,6 @@
<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="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="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="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="7">Compendia</a>:</td><td> </td><td align="left"
valign="top">Using translation memory.
-</td></tr>
-<tr><td align="left" valign="top">• <a href="Sitemap.html#Sitemap"
accesskey="8">Sitemap</a>:</td><td> </td><td align="left"
valign="top">Specifics of sitemap generation.
-</td></tr>
-<tr><td align="left" valign="top">• <a href="GNU-News.html#GNU-News"
accesskey="9">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>
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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/PO-Tips.html 31 Jan 2013 08:47:32 -0000 1.18
+++ gnun/html_node/PO-Tips.html 1 Feb 2013 06:06:11 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="Useful-Hints-for-Editing-PO-Files"></a>
-<h4 class="subsection">2.3.2 Useful Hints for Editing PO Files</h4>
+<h3 class="section">4.2 Useful Hints for Editing PO Files</h3>
<a name="index-tips_002c-translators"></a>
<a name="index-recommendations_002c-PO-files"></a>
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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Runtime-Variables.html 31 Jan 2013 08:47:32 -0000
1.18
+++ gnun/html_node/Runtime-Variables.html 1 Feb 2013 06:06:11 -0000
1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -28,7 +28,7 @@
<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="Invoking-GNUN.html#Invoking-GNUN" rel="up" title="Invoking GNUN">
+<link href="Usage.html#Usage" rel="up" title="Usage">
<link href="Special-Targets.html#Special-Targets" rel="next" title="Special
Targets">
<link href="Invoking-GNUN.html#Invoking-GNUN" rel="previous" title="Invoking
GNUN">
<style type="text/css">
@@ -67,11 +67,11 @@
<a name="Runtime-Variables"></a>
<div class="header">
<p>
-Next: <a href="Special-Targets.html#Special-Targets" accesskey="n"
rel="next">Special Targets</a>, Up: <a href="Invoking-GNUN.html#Invoking-GNUN"
accesskey="u" rel="up">Invoking GNUN</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="Special-Targets.html#Special-Targets" accesskey="n"
rel="next">Special Targets</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="Variables-to-Control-the-Build-Process"></a>
-<h4 class="subsection">2.1.1 Variables to Control the Build Process</h4>
+<h3 class="section">2.2 Variables to Control the Build Process</h3>
<a name="index-variables"></a>
<a name="index-variable_002c-behavior"></a>
@@ -271,7 +271,7 @@
<hr>
<div class="header">
<p>
-Next: <a href="Special-Targets.html#Special-Targets" accesskey="n"
rel="next">Special Targets</a>, Up: <a href="Invoking-GNUN.html#Invoking-GNUN"
accesskey="u" rel="up">Invoking GNUN</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="Special-Targets.html#Special-Targets" accesskey="n"
rel="next">Special Targets</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>
Index: gnun/html_node/Scripts.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Scripts.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Scripts.html 31 Jan 2013 08:47:32 -0000 1.18
+++ gnun/html_node/Scripts.html 1 Feb 2013 06:06:11 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="GNUN-Scripts"></a>
-<h3 class="section">3.2 GNUN Scripts</h3>
+<h3 class="section">6.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
Index: gnun/html_node/Sitemap.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Sitemap.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- gnun/html_node/Sitemap.html 31 Jan 2013 08:51:08 -0000 1.1
+++ gnun/html_node/Sitemap.html 1 Feb 2013 06:06:11 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -28,7 +28,7 @@
<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="PO-Files.html#PO-Files" rel="up" title="PO Files">
+<link href="Usage.html#Usage" rel="up" title="Usage">
<link href="GNU-News.html#GNU-News" rel="next" title="GNU News">
<link href="Compendia.html#Compendia" rel="previous" title="Compendia">
<style type="text/css">
@@ -67,11 +67,11 @@
<a name="Sitemap"></a>
<div class="header">
<p>
-Next: <a href="GNU-News.html#GNU-News" accesskey="n" rel="next">GNU News</a>,
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>
+Next: <a href="GNU-News.html#GNU-News" accesskey="n" rel="next">GNU News</a>,
Previous: <a href="Compendia.html#Compendia" accesskey="p"
rel="previous">Compendia</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="Building-Sitemap"></a>
-<h4 class="subsection">2.3.8 Building Sitemap</h4>
+<h3 class="section">2.8 Building Sitemap</h3>
<a name="index-sitemap-1"></a>
<p>Sitemaps differ from regular pages in two respects:
@@ -102,5 +102,6 @@
+
</body>
</html>
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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Special-Targets.html 31 Jan 2013 08:47:32 -0000 1.18
+++ gnun/html_node/Special-Targets.html 1 Feb 2013 06:06:11 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -28,7 +28,7 @@
<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="Invoking-GNUN.html#Invoking-GNUN" rel="up" title="Invoking GNUN">
+<link href="Usage.html#Usage" rel="up" title="Usage">
<link href="no_002dgrace_002ditems.html#no_002dgrace_002ditems" rel="next"
title="no-grace-items">
<link href="Runtime-Variables.html#Runtime-Variables" rel="previous"
title="Runtime Variables">
<style type="text/css">
@@ -67,11 +67,11 @@
<a name="Special-Targets"></a>
<div class="header">
<p>
-Previous: <a href="Runtime-Variables.html#Runtime-Variables" accesskey="p"
rel="previous">Runtime Variables</a>, Up: <a
href="Invoking-GNUN.html#Invoking-GNUN" accesskey="u" rel="up">Invoking
GNUN</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="Main-Variables.html#Main-Variables" accesskey="n"
rel="next">Main Variables</a>, Previous: <a
href="Runtime-Variables.html#Runtime-Variables" accesskey="p"
rel="previous">Runtime 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>
<hr>
<a name="Targets-Specified-on-the-Command-Line"></a>
-<h4 class="subsection">2.1.2 Targets Specified on the Command Line</h4>
+<h3 class="section">2.3 Targets Specified on the Command Line</h3>
<p>Some targets are not built by default, because they are only useful
under certain circumstances. Think of them like semi-automated
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.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- gnun/html_node/Splitting-Long-Passages.html 31 Jan 2013 08:47:32 -0000
1.4
+++ gnun/html_node/Splitting-Long-Passages.html 1 Feb 2013 06:06:11 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="Splitting-Long-Passages-1"></a>
-<h4 class="subsection">2.4.5 Splitting Long Passages</h4>
+<h3 class="section">5.5 Splitting Long Passages</h3>
<a name="index-long-passages_002c-avoiding"></a>
<a name="index-conventional-separator-for-strings"></a>
Index: gnun/html_node/Usage.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Usage.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Usage.html 31 Jan 2013 08:47:32 -0000 1.18
+++ gnun/html_node/Usage.html 1 Feb 2013 06:06:11 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -67,7 +67,7 @@
<a name="Usage"></a>
<div class="header">
<p>
-Next: <a href="Internals.html#Internals" accesskey="n"
rel="next">Internals</a>, Previous: <a href="Introduction.html#Introduction"
accesskey="p" rel="previous">Introduction</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>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="Team_0027s-Repository.html#Team_0027s-Repository" accesskey="n"
rel="next">Team's Repository</a>, Previous: <a
href="Introduction.html#Introduction" accesskey="p"
rel="previous">Introduction</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>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
<hr>
<a name="General-Usage"></a>
@@ -100,15 +100,30 @@
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top">• <a
href="Invoking-GNUN.html#Invoking-GNUN" accesskey="1">Invoking
GNUN</a>:</td><td> </td><td align="left" valign="top">How to trigger
a (re)build.
</td></tr>
-<tr><td align="left" valign="top">• <a
href="Main-Variables.html#Main-Variables" accesskey="2">Main
Variables</a>:</td><td> </td><td align="left"
valign="top">Specifying what to build.
+<tr><td align="left" valign="top">• <a
href="Runtime-Variables.html#Runtime-Variables" accesskey="2">Runtime
Variables</a>:</td><td> </td><td align="left" valign="top">Variables
to control the build process.
</td></tr>
-<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">The gentle art of editing PO files.
+<tr><td align="left" valign="top">• <a
href="Special-Targets.html#Special-Targets" accesskey="3">Special
Targets</a>:</td><td> </td><td align="left" valign="top">Targets
that are not built by default.
</td></tr>
-<tr><td align="left" valign="top">• <a
href="Webmaster-Tips.html#Webmaster-Tips" accesskey="4">Webmaster
Tips</a>:</td><td> </td><td align="left" valign="top">The
webmaster’s guide to GNUnited Nations’
- galaxy.
+<tr><td align="left" valign="top">• <a
href="Main-Variables.html#Main-Variables" accesskey="4">Main
Variables</a>:</td><td> </td><td align="left"
valign="top">Specifying what to build.
+</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
+ 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.
+</td></tr>
+<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="Sitemap.html#Sitemap"
accesskey="8">Sitemap</a>:</td><td> </td><td align="left"
valign="top">Specifics of sitemap generation.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="GNU-News.html#GNU-News"
accesskey="9">GNU News</a>:</td><td> </td><td align="left"
valign="top">Obsolete: How to handle “whatsnew”.
</td></tr>
</table>
+<hr>
+<div class="header">
+<p>
+Next: <a href="Team_0027s-Repository.html#Team_0027s-Repository" accesskey="n"
rel="next">Team's Repository</a>, Previous: <a
href="Introduction.html#Introduction" accesskey="p"
rel="previous">Introduction</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>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
Index: gnun/html_node/Validation.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Validation.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- gnun/html_node/Validation.html 31 Jan 2013 08:47:32 -0000 1.8
+++ gnun/html_node/Validation.html 1 Feb 2013 06:06:11 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="Validation-1"></a>
-<h4 class="subsection">2.4.1 Validation</h4>
+<h3 class="section">5.1 Validation</h3>
<a name="index-validation-3"></a>
<p>The script <code>gnun-validate-html</code> is useful for webmasters who
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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/Webmaster-Tips.html 31 Jan 2013 08:47:32 -0000 1.18
+++ gnun/html_node/Webmaster-Tips.html 1 Feb 2013 06:06:11 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -28,9 +28,9 @@
<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="Usage.html#Usage" rel="up" title="Usage">
+<link href="index.html#Top" rel="up" title="Top">
<link href="Validation.html#Validation" rel="next" title="Validation">
-<link href="GNU-News.html#GNU-News" rel="previous" title="GNU News">
+<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="Webmaster-Tips"></a>
<div class="header">
<p>
-Previous: <a href="PO-Files.html#PO-Files" accesskey="p" rel="previous">PO
Files</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>
+Next: <a href="Internals.html#Internals" accesskey="n"
rel="next">Internals</a>, Previous: <a href="PO-Files.html#PO-Files"
accesskey="p" rel="previous">PO Files</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>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="Tips-and-Hints-for-Webmasters"></a>
-<h3 class="section">2.4 Tips and Hints for Webmasters</h3>
+<h2 class="chapter">5 Tips and Hints for Webmasters</h2>
<a name="index-tips_002c-webmasters"></a>
<a name="index-webmaster-tips"></a>
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.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- gnun/html_node/extra_002dtemplates.html 31 Jan 2013 08:47:32 -0000
1.4
+++ gnun/html_node/extra_002dtemplates.html 1 Feb 2013 06:06:12 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/generic_002eLANG_002ehtml.html 31 Jan 2013 08:47:32
-0000 1.18
+++ gnun/html_node/generic_002eLANG_002ehtml.html 1 Feb 2013 06:06:12
-0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -28,9 +28,9 @@
<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="PO-Files.html#PO-Files" rel="up" title="PO Files">
+<link href="Usage.html#Usage" rel="up" title="Usage">
<link href="languages_002etxt.html#languages_002etxt" rel="next"
title="languages.txt">
-<link href="Migrating.html#Migrating" rel="previous" title="Migrating">
+<link href="Main-Variables.html#Main-Variables" rel="previous" title="Main
Variables">
<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="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>
+Next: <a href="languages_002etxt.html#languages_002etxt" accesskey="n"
rel="next">languages.txt</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>
<hr>
<a name="The-generic_002elang_002ehtml-File"></a>
-<h4 class="subsection">2.3.4 The <samp>generic.<var>lang</var>.html</samp>
File</h4>
+<h3 class="section">2.5 The <samp>generic.<var>lang</var>.html</samp> File</h3>
<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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- gnun/html_node/gnun_002dadd_002dfuzzy_002ddiff.html 31 Jan 2013 08:47:32
-0000 1.8
+++ gnun/html_node/gnun_002dadd_002dfuzzy_002ddiff.html 1 Feb 2013 06:06:12
-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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-gnun_002dadd_002dfuzzy_002ddiff-Script"></a>
-<h4 class="subsection">3.2.1 The <code>gnun-add-fuzzy-diff</code> Script</h4>
+<h4 class="subsection">6.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
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.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- gnun/html_node/gnun_002dclear_002dprevious.html 31 Jan 2013 08:47:32
-0000 1.10
+++ gnun/html_node/gnun_002dclear_002dprevious.html 1 Feb 2013 06:06:12
-0000 1.11
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-gnun_002dclear_002dprevious-Script"></a>
-<h4 class="subsection">3.2.10 The <code>gnun-clear-previous</code> Script</h4>
+<h4 class="subsection">6.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
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.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- gnun/html_node/gnun_002ddiff_002dpo.html 31 Jan 2013 08:47:32 -0000
1.3
+++ gnun/html_node/gnun_002ddiff_002dpo.html 1 Feb 2013 06:06:12 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-gnun_002ddiff_002dpo-Script"></a>
-<h4 class="subsection">3.2.2 The <code>gnun-diff-po</code> Script</h4>
+<h4 class="subsection">6.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.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- gnun/html_node/gnun_002dinit_002dpo.html 31 Jan 2013 08:47:32 -0000
1.5
+++ gnun/html_node/gnun_002dinit_002dpo.html 1 Feb 2013 06:06:12 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-gnun_002dinit_002dpo-Script"></a>
-<h4 class="subsection">3.2.3 The <code>gnun-init-po</code> Script</h4>
+<h4 class="subsection">6.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,
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.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- gnun/html_node/gnun_002dmerge_002dpreconverted.html 31 Jan 2013 08:47:32
-0000 1.6
+++ gnun/html_node/gnun_002dmerge_002dpreconverted.html 1 Feb 2013 06:06:12
-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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-gnun_002dmerge_002dpreconverted-Script"></a>
-<h4 class="subsection">3.2.5 The <code>gnun-merge-preconverted</code>
Script</h4>
+<h4 class="subsection">6.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>
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.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- gnun/html_node/gnun_002dpreconvert.html 31 Jan 2013 08:47:33 -0000
1.6
+++ gnun/html_node/gnun_002dpreconvert.html 1 Feb 2013 06:06:12 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-gnun_002dpreconvert-Script"></a>
-<h4 class="subsection">3.2.4 The <code>gnun-preconvert</code> Script</h4>
+<h4 class="subsection">6.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.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- gnun/html_node/gnun_002dreport.html 31 Jan 2013 08:47:33 -0000 1.3
+++ gnun/html_node/gnun_002dreport.html 1 Feb 2013 06:06:12 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-gnun_002dreport-Script"></a>
-<h4 class="subsection">3.2.6 The <code>gnun-report</code> Script</h4>
+<h4 class="subsection">6.2.6 The <code>gnun-report</code> Script</h4>
<a name="index-reporting-1"></a>
<a name="index-status_002c-translations-1"></a>
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.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- gnun/html_node/gnun_002dvalidate_002dhtml.html 31 Jan 2013 08:47:33
-0000 1.14
+++ gnun/html_node/gnun_002dvalidate_002dhtml.html 1 Feb 2013 06:06:12
-0000 1.15
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-gnun_002dvalidate_002dhtml-Script"></a>
-<h4 class="subsection">3.2.7 The <code>gnun-validate-html</code> Script</h4>
+<h4 class="subsection">6.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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/index.html 31 Jan 2013 08:47:33 -0000 1.18
+++ gnun/html_node/index.html 1 Feb 2013 06:06:12 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -83,68 +83,66 @@
</ul></li>
<li><a name="toc-General-Usage" href="Usage.html#Usage">2 General Usage</a>
<ul class="no-bullet">
- <li><a name="toc-Invoking-GNUN-1"
href="Invoking-GNUN.html#Invoking-GNUN">2.1 Invoking GNUN</a>
- <ul class="no-bullet">
- <li><a name="toc-Variables-to-Control-the-Build-Process"
href="Runtime-Variables.html#Runtime-Variables">2.1.1 Variables to Control the
Build Process</a></li>
- <li><a name="toc-Targets-Specified-on-the-Command-Line"
href="Special-Targets.html#Special-Targets">2.1.2 Targets Specified on the
Command Line</a>
- <ul class="no-bullet">
- <li><a name="toc-The-no_002dgrace_002ditems-Target"
href="no_002dgrace_002ditems.html#no_002dgrace_002ditems">2.1.2.1 The
<code>no-grace-items</code> Target</a></li>
- <li><a name="toc-The-update_002dlocalized_002dURLs-Target"
href="update_002dlocalized_002dURLs.html#update_002dlocalized_002dURLs">2.1.2.2
The <code>update-localized-URLs</code> Target</a></li>
- <li><a name="toc-The-sync-Target" href="sync.html#sync">2.1.2.3 The
<code>sync</code> Target</a></li>
- <li><a name="toc-The-report-Target" href="report.html#report">2.1.2.4
The <code>report</code> Target</a></li>
- <li><a name="toc-The-triggers-Target"
href="triggers.html#triggers">2.1.2.5 The <code>triggers</code> Target</a></li>
- <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-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>
- <ul class="no-bullet">
- <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-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.7
Using Compendia</a></li>
- <li><a name="toc-Building-Sitemap" href="Sitemap.html#Sitemap">2.3.8
Building Sitemap</a></li>
- <li><a name="toc-Special-Handling-for-GNU-News"
href="GNU-News.html#GNU-News">2.3.9 Special Handling for GNU News</a></li>
+ <li><a name="toc-Invoking-GNUN-1"
href="Invoking-GNUN.html#Invoking-GNUN">2.1 Invoking GNUN</a></li>
+ <li><a name="toc-Variables-to-Control-the-Build-Process"
href="Runtime-Variables.html#Runtime-Variables">2.2 Variables to Control the
Build Process</a></li>
+ <li><a name="toc-Targets-Specified-on-the-Command-Line"
href="Special-Targets.html#Special-Targets">2.3 Targets Specified on the
Command Line</a>
+ <ul class="no-bullet">
+ <li><a name="toc-The-no_002dgrace_002ditems-Target"
href="no_002dgrace_002ditems.html#no_002dgrace_002ditems">2.3.1 The
<code>no-grace-items</code> Target</a></li>
+ <li><a name="toc-The-update_002dlocalized_002dURLs-Target"
href="update_002dlocalized_002dURLs.html#update_002dlocalized_002dURLs">2.3.2
The <code>update-localized-URLs</code> Target</a></li>
+ <li><a name="toc-The-sync-Target" href="sync.html#sync">2.3.3 The
<code>sync</code> Target</a></li>
+ <li><a name="toc-The-report-Target" href="report.html#report">2.3.4 The
<code>report</code> Target</a></li>
+ <li><a name="toc-The-triggers-Target"
href="triggers.html#triggers">2.3.5 The <code>triggers</code> Target</a></li>
+ <li><a name="toc-The-validate_002dall-Target"
href="validate_002dall.html#validate_002dall">2.3.6 The
<code>validate-all</code> Target</a></li>
+ </ul></li>
+ <li><a name="toc-Defining-Articles-to-Be-Built"
href="Main-Variables.html#Main-Variables">2.4 Defining Articles to Be
Built</a></li>
+ <li><a name="toc-The-generic_002elang_002ehtml-File"
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml">2.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.6 The
<samp>languages.txt</samp> File</a></li>
+ <li><a name="toc-Using-Compendia" href="Compendia.html#Compendia">2.7
Using Compendia</a></li>
+ <li><a name="toc-Building-Sitemap" href="Sitemap.html#Sitemap">2.8
Building Sitemap</a></li>
+ <li><a name="toc-Special-Handling-for-GNU-News"
href="GNU-News.html#GNU-News">2.9 Special Handling for GNU News</a></li>
+ </ul></li>
+ <li><a name="toc-Maintaining-Translations-in-Your-Team_0027s-Repository"
href="Team_0027s-Repository.html#Team_0027s-Repository">3 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">3.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">3.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">3.3
Automatic Synchronization and Status Reports</a></li>
+ </ul></li>
+ <li><a name="toc-Working-with-PO-Files" href="PO-Files.html#PO-Files">4
Working with PO Files</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Starting-a-New-Translation"
href="New-Translation.html#New-Translation">4.1 Starting a New Translation</a>
+ <ul class="no-bullet">
+ <li><a name="toc-The-Special-Slot-for-Translator_0027s-Notes"
href="Notes-Slot.html#Notes-Slot">4.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">4.1.2 The Special Slot for
Translator’s Credits</a></li>
+ </ul></li>
+ <li><a name="toc-Useful-Hints-for-Editing-PO-Files"
href="PO-Tips.html#PO-Tips">4.2 Useful Hints for Editing PO Files</a></li>
+ <li><a name="toc-Transforming-Existing-Translation-in-PO-Format"
href="Migrating.html#Migrating">4.3 Transforming Existing Translation in PO
Format</a></li>
+ </ul></li>
+ <li><a name="toc-Tips-and-Hints-for-Webmasters"
href="Webmaster-Tips.html#Webmaster-Tips">5 Tips and Hints for Webmasters</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Validation-1" href="Validation.html#Validation">5.1
Validation</a></li>
+ <li><a name="toc-Comments-for-Translators-1"
href="Comments-for-Translators.html#Comments-for-Translators">5.2 Comments for
Translators</a></li>
+ <li><a name="toc-Modifying-Boilerplates-1"
href="Modifying-Boilerplates.html#Modifying-Boilerplates">5.3 Modifying
Boilerplates</a></li>
+ <li><a name="toc-Localized-URLs-1"
href="Localized-URLs.html#Localized-URLs">5.4 Localized URLs</a></li>
+ <li><a name="toc-Splitting-Long-Passages-1"
href="Splitting-Long-Passages.html#Splitting-Long-Passages">5.5 Splitting Long
Passages</a></li>
+ </ul></li>
+ <li><a name="toc-Unexciting-Information-for-GNUN_0027s-Operation"
href="Internals.html#Internals">6 Unexciting Information for GNUN’s
Operation</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Files-and-Directories-1"
href="Files-and-Directories.html#Files-and-Directories">6.1 Files and
Directories</a></li>
+ <li><a name="toc-GNUN-Scripts" href="Scripts.html#Scripts">6.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">6.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">6.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">6.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">6.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">6.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">6.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">6.2.7 The
<code>gnun-validate-html</code> Script</a></li>
+ <li><a name="toc-The-mailfail-Script"
href="mailfail.html#mailfail">6.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">6.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">6.2.10 The
<code>gnun-clear-previous</code> Script</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">
- <li><a name="toc-Validation-1" href="Validation.html#Validation">2.4.1
Validation</a></li>
- <li><a name="toc-Comments-for-Translators-1"
href="Comments-for-Translators.html#Comments-for-Translators">2.4.2 Comments
for Translators</a></li>
- <li><a name="toc-Modifying-Boilerplates-1"
href="Modifying-Boilerplates.html#Modifying-Boilerplates">2.4.3 Modifying
Boilerplates</a></li>
- <li><a name="toc-Localized-URLs-1"
href="Localized-URLs.html#Localized-URLs">2.4.4 Localized URLs</a></li>
- <li><a name="toc-Splitting-Long-Passages-1"
href="Splitting-Long-Passages.html#Splitting-Long-Passages">2.4.5 Splitting
Long Passages</a></li>
- </ul></li>
- </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-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.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>
- </ul></li>
- <li><a name="toc-Reporting-Bugs" href="Bugs.html#Bugs">4 Reporting
Bugs</a></li>
+ <li><a name="toc-Reporting-Bugs" href="Bugs.html#Bugs">7 Reporting
Bugs</a></li>
<li><a name="toc-Index-1" href="Index.html#Index">Index</a></li>
<li><a name="toc-GNU-Free-Documentation-License"
href="Copying-This-Manual.html#Copying-This-Manual">Appendix A GNU Free
Documentation License</a></li>
</ul>
@@ -161,7 +159,7 @@
<a name="GNUnited-Nations"></a>
<h1 class="top">GNUnited Nations</h1>
-<p>This manual (updated 31 January 2013) is for GNUnited Nations (version
+<p>This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.<br>
</p><br>
@@ -183,13 +181,21 @@
</td></tr>
<tr><td align="left" valign="top">• <a href="Usage.html#Usage"
accesskey="2">Usage</a>:</td><td> </td><td align="left"
valign="top">Basic usage, invocation and tips.
</td></tr>
-<tr><td align="left" valign="top">• <a href="Internals.html#Internals"
accesskey="3">Internals</a>:</td><td> </td><td align="left"
valign="top">Dive into GNUN.
+<tr><td align="left" valign="top">• <a
href="Team_0027s-Repository.html#Team_0027s-Repository" accesskey="3">Team's
Repository</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="PO-Files.html#PO-Files"
accesskey="4">PO Files</a>:</td><td> </td><td align="left"
valign="top">The gentle art of editing PO files.
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Webmaster-Tips.html#Webmaster-Tips" accesskey="5">Webmaster
Tips</a>:</td><td> </td><td align="left" valign="top">The
webmaster’s guide to GNUnited Nations’
+ galaxy.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="Internals.html#Internals"
accesskey="6">Internals</a>:</td><td> </td><td align="left"
valign="top">Dive into GNUN.
</td></tr>
-<tr><td align="left" valign="top">• <a href="Bugs.html#Bugs"
accesskey="4">Bugs</a>:</td><td> </td><td align="left"
valign="top">How to report bugs.
+<tr><td align="left" valign="top">• <a href="Bugs.html#Bugs"
accesskey="7">Bugs</a>:</td><td> </td><td align="left"
valign="top">How to report bugs.
</td></tr>
-<tr><td align="left" valign="top">• <a href="Index.html#Index"
accesskey="5">Index</a>:</td><td> </td><td align="left" valign="top">
+<tr><td align="left" valign="top">• <a href="Index.html#Index"
accesskey="8">Index</a>:</td><td> </td><td align="left" valign="top">
</td></tr>
-<tr><td align="left" valign="top">• <a
href="Copying-This-Manual.html#Copying-This-Manual" accesskey="6">Copying This
Manual</a>:</td><td> </td><td align="left" valign="top">The GNU Free
Documentation License.
+<tr><td align="left" valign="top">• <a
href="Copying-This-Manual.html#Copying-This-Manual" accesskey="9">Copying This
Manual</a>:</td><td> </td><td align="left" valign="top">The GNU Free
Documentation License.
</td></tr>
</table>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- gnun/html_node/languages_002etxt.html 31 Jan 2013 08:47:33 -0000
1.8
+++ gnun/html_node/languages_002etxt.html 1 Feb 2013 06:06:13 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -28,8 +28,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="PO-Files.html#PO-Files" rel="up" title="PO Files">
-<link href="PO-Files-and-Team.html#PO-Files-and-Team" rel="next" title="PO
Files and Team">
+<link href="Usage.html#Usage" rel="up" title="Usage">
+<link href="Compendia.html#Compendia" rel="next" title="Compendia">
<link href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
rel="previous" title="generic.LANG.html">
<style type="text/css">
<!--
@@ -67,11 +67,11 @@
<a name="languages_002etxt"></a>
<div class="header">
<p>
-Next: <a href="PO-Files-and-Team.html#PO-Files-and-Team" accesskey="n"
rel="next">PO Files and Team</a>, Previous: <a
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml" accesskey="p"
rel="previous">generic.LANG.html</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="Compendia.html#Compendia" accesskey="n"
rel="next">Compendia</a>, Previous: <a
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml" accesskey="p"
rel="previous">generic.LANG.html</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="The-languages_002etxt-File"></a>
-<h4 class="subsection">2.3.5 The <samp>languages.txt</samp> File</h4>
+<h3 class="section">2.6 The <samp>languages.txt</samp> File</h3>
<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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/mailfail.html 31 Jan 2013 08:47:33 -0000 1.18
+++ gnun/html_node/mailfail.html 1 Feb 2013 06:06:13 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-mailfail-Script"></a>
-<h4 class="subsection">3.2.8 The <code>mailfail</code> Script</h4>
+<h4 class="subsection">6.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
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- gnun/html_node/no_002dgrace_002ditems.html 31 Jan 2013 08:47:33 -0000
1.8
+++ gnun/html_node/no_002dgrace_002ditems.html 1 Feb 2013 06:06:13 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-no_002dgrace_002ditems-Target"></a>
-<h4 class="subsubsection">2.1.2.1 The <code>no-grace-items</code> Target</h4>
+<h4 class="subsection">2.3.1 The <code>no-grace-items</code> Target</h4>
<p>The <code>no-grace-items</code> target regenerates a limited set of articles
that are not affected by the grace period, namely, the
Index: gnun/html_node/notify-in-GNUmakefile_002eteam.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/notify-in-GNUmakefile_002eteam.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- gnun/html_node/notify-in-GNUmakefile_002eteam.html 31 Jan 2013 08:51:08
-0000 1.1
+++ gnun/html_node/notify-in-GNUmakefile_002eteam.html 1 Feb 2013 06:06:13
-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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
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.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- gnun/html_node/optional_002dtemplates.html 31 Jan 2013 08:47:33 -0000
1.4
+++ gnun/html_node/optional_002dtemplates.html 1 Feb 2013 06:06:13 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
Index: gnun/html_node/publish.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/publish.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- gnun/html_node/publish.html 31 Jan 2013 08:47:33 -0000 1.2
+++ gnun/html_node/publish.html 1 Feb 2013 06:06:13 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
Index: gnun/html_node/report-in-GNUmakefile_002eteam.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/report-in-GNUmakefile_002eteam.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- gnun/html_node/report-in-GNUmakefile_002eteam.html 31 Jan 2013 08:47:33
-0000 1.2
+++ gnun/html_node/report-in-GNUmakefile_002eteam.html 1 Feb 2013 06:06:13
-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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
Index: gnun/html_node/report.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/report.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/report.html 31 Jan 2013 08:47:33 -0000 1.18
+++ gnun/html_node/report.html 1 Feb 2013 06:06:13 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-report-Target"></a>
-<h4 class="subsubsection">2.1.2.4 The <code>report</code> Target</h4>
+<h4 class="subsection">2.3.4 The <code>report</code> Target</h4>
<a name="index-reporting"></a>
<a name="index-status_002c-translations"></a>
Index: gnun/html_node/sync.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/sync.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/sync.html 31 Jan 2013 08:47:33 -0000 1.18
+++ gnun/html_node/sync.html 1 Feb 2013 06:06:14 -0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-sync-Target"></a>
-<h4 class="subsubsection">2.1.2.3 The <code>sync</code> Target</h4>
+<h4 class="subsection">2.3.3 The <code>sync</code> Target</h4>
<a name="index-synchronization_002c-repository"></a>
<p>The <code>sync</code> target has a simple task: synchronize the
Index: gnun/html_node/triggers.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/triggers.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- gnun/html_node/triggers.html 31 Jan 2013 08:47:33 -0000 1.17
+++ gnun/html_node/triggers.html 1 Feb 2013 06:06:14 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-triggers-Target"></a>
-<h4 class="subsubsection">2.1.2.5 The <code>triggers</code> Target</h4>
+<h4 class="subsection">2.3.5 The <code>triggers</code> Target</h4>
<p>This is a special target intended to be run by the automatic build after
the main build and <em>after</em> <code>cvs|svn|bzr commit</code>.
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- gnun/html_node/update_002dlocalized_002dURLs.html 31 Jan 2013 08:47:34
-0000 1.8
+++ gnun/html_node/update_002dlocalized_002dURLs.html 1 Feb 2013 06:06:14
-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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-update_002dlocalized_002dURLs-Target"></a>
-<h4 class="subsubsection">2.1.2.2 The <code>update-localized-URLs</code>
Target</h4>
+<h4 class="subsection">2.3.2 The <code>update-localized-URLs</code> Target</h4>
<p>The <code>update-localized-URLs</code> target invokes a script that
generates the <samp>localized-urls.mk</samp> file. This file includes the
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.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- gnun/html_node/validate_002dall.html 31 Jan 2013 08:47:34 -0000
1.5
+++ gnun/html_node/validate_002dall.html 1 Feb 2013 06:06:14 -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-validate_002dall-Target"></a>
-<h4 class="subsubsection">2.1.2.6 The <code>validate-all</code> Target</h4>
+<h4 class="subsection">2.3.6 The <code>validate-all</code> Target</h4>
<a name="index-validation-2"></a>
<p>The <code>validate-all</code> target validates all HTML pages under
GNUN’s
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.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnun/html_node/validate_002dhtml_002dnotify.html 31 Jan 2013 08:47:34
-0000 1.18
+++ gnun/html_node/validate_002dhtml_002dnotify.html 1 Feb 2013 06:06:14
-0000 1.19
@@ -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 31 January 2013) is for GNUnited Nations (version
+This manual (updated 1 February 2013) is for GNUnited Nations (version
0.7), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -71,7 +71,7 @@
</div>
<hr>
<a name="The-validate_002dhtml_002dnotify-Script"></a>
-<h4 class="subsection">3.2.9 The <code>validate-html-notify</code> Script</h4>
+<h4 class="subsection">6.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.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- web-trans/index.html 31 Jan 2013 08:47:34 -0000 1.13
+++ web-trans/index.html 1 Feb 2013 06:06:14 -0000 1.14
@@ -4,20 +4,20 @@
<h2>GNU Web Translators Manual</h2>
<address>Free Software Foundation</address>
-<address>last updated January 31, 2013</address>
+<address>last updated February 01, 2013</address>
<p>This manual (web-trans) is available in the following formats:</p>
<ul>
<li><a href="web-trans.html">HTML
- (144K bytes)</a> - entirely on one web page.</li>
+ (140K 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="web-trans.html.gz">HTML compressed
(40K gzipped characters)</a> - entirely on
one web page.</li>
<li><a href="web-trans.html_node.tar.gz">HTML compressed
- (52K gzipped tar file)</a> -
+ (48K gzipped tar file)</a> -
with one web page per node.</li>
<li><a href="web-trans.info.tar.gz">Info document
(36K bytes gzipped tar file)</a>.</li>
@@ -30,7 +30,7 @@
<li><a href="web-trans.ps.gz">PostScript file
(276K bytes gzipped)</a>.</li>
<li><a href="web-trans.pdf">PDF file
- (368K bytes)</a>.</li>
+ (364K bytes)</a>.</li>
<li><a href="web-trans.texi.tar.gz">Texinfo source
(72K 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.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
Binary files /tmp/cvsWOuzum and /tmp/cvsnwkANX differ
Index: web-trans/web-trans.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- web-trans/web-trans.html 31 Jan 2013 08:47:34 -0000 1.13
+++ web-trans/web-trans.html 1 Feb 2013 06:06:14 -0000 1.14
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -91,45 +91,41 @@
<li><a name="toc-How-to-Proceed-with-Unreviewed-Translations"
href="#Unreviewed-Translations">3.3.2 How to Proceed with Unreviewed
Translations</a></li>
</ul></li>
<li><a name="toc-CVS-Commits-and-Best-Practices" href="#Commits">3.4 CVS
Commits and Best Practices</a></li>
- <li><a name="toc-Working-with-PO-Files" href="#PO-Files">3.5 Working with
PO Files</a>
+ <li><a name="toc-Taking-Advantage-of-Savannah" href="#Savannah">3.5 Taking
Advantage of Savannah</a>
<ul class="no-bullet">
- <li><a name="toc-Web_002dbased-Systems"
href="#Web_002dbased-Systems">3.5.1 Web-based Systems</a></li>
+ <li><a name="toc-Managing-Members" href="#Savannah-Members">3.5.1
Managing Members</a></li>
+ <li><a name="toc-Homepage-of-the-Team" href="#Savannah-Homepage">3.5.2
Homepage of the Team</a></li>
+ <li><a name="toc-Support-Tracker" href="#Savannah-Support">3.5.3 Support
Tracker</a></li>
+ <li><a name="toc-Tasks-Tracker" href="#Savannah-Tasks">3.5.4 Tasks
Tracker</a></li>
+ <li><a name="toc-Bugs-Tracker" href="#Savannah-Bugs">3.5.5 Bugs
Tracker</a></li>
+ <li><a name="toc-News-Tracker" href="#Savannah-News">3.5.6 News
Tracker</a></li>
+ <li><a name="toc-Managing-Mailing-Lists"
href="#Savannah-Mailing-Lists">3.5.7 Managing Mailing Lists</a></li>
+ <li><a name="toc-Version-Control-Systems" href="#Savannah-VCS">3.5.8
Version Control Systems</a></li>
</ul></li>
- <li><a name="toc-Taking-Advantage-of-Savannah" href="#Savannah">3.6 Taking
Advantage of Savannah</a>
- <ul class="no-bullet">
- <li><a name="toc-Managing-Members" href="#Savannah-Members">3.6.1
Managing Members</a></li>
- <li><a name="toc-Homepage-of-the-Team" href="#Savannah-Homepage">3.6.2
Homepage of the Team</a></li>
- <li><a name="toc-Support-Tracker" href="#Savannah-Support">3.6.3 Support
Tracker</a></li>
- <li><a name="toc-Tasks-Tracker" href="#Savannah-Tasks">3.6.4 Tasks
Tracker</a></li>
- <li><a name="toc-Bugs-Tracker" href="#Savannah-Bugs">3.6.5 Bugs
Tracker</a></li>
- <li><a name="toc-News-Tracker" href="#Savannah-News">3.6.6 News
Tracker</a></li>
- <li><a name="toc-Managing-Mailing-Lists"
href="#Savannah-Mailing-Lists">3.6.7 Managing Mailing Lists</a></li>
- <li><a name="toc-Version-Control-Systems" href="#Savannah-VCS">3.6.8
Version Control Systems</a></li>
- </ul></li>
- <li><a name="toc-Promoting-Members-as-Co_002dleaders"
href="#Co_002dleaders">3.7 Promoting Members as Co-leaders</a></li>
- <li><a name="toc-Reporting-Team-Status" href="#Reports">3.8 Reporting Team
Status</a></li>
- <li><a name="toc-How-to-Retire-Painlessly" href="#Stepping-Down">3.9 How
to Retire Painlessly</a></li>
+ <li><a name="toc-Promoting-Members-as-Co_002dleaders"
href="#Co_002dleaders">3.6 Promoting Members as Co-leaders</a></li>
+ <li><a name="toc-Reporting-Team-Status" href="#Reports">3.7 Reporting Team
Status</a></li>
+ <li><a name="toc-How-to-Retire-Painlessly" href="#Stepping-Down">3.8 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-Translation-Process-1" href="#Translation-Process">4
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-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-What-to-Translate" href="#Priorities">4.1 What to
Translate</a></li>
+ <li><a name="toc-Keeping-Translations-Current" href="#Updating">4.2
Keeping Translations Current</a></li>
+ <li><a name="toc-When-to-CAPITALIZE" href="#Capitalization">4.3 When to
CAPITALIZE</a></li>
+ <li><a name="toc-Distribution-Terms-1" href="#Distribution-Terms">4.4
Distribution Terms</a></li>
+ <li><a name="toc-Language_002dspecific-Terminology"
href="#Terminology">4.5 Language-specific Terminology</a></li>
+ <li><a name="toc-Related-Mailing-Lists" href="#Mailing-Lists">4.6 Related
Mailing Lists</a></li>
+ <li><a name="toc-Savannah-Projects-Membership"
href="#Savannah-Projects">4.7 Savannah Projects Membership</a></li>
+ <li><a name="toc-Working-with-PO-Files" href="#PO-Files">4.8 Working with
PO Files</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-Specific-Issues-Related-to-RTL" href="#RTL">5.3.2
Specific Issues Related to RTL</a></li>
+ <li><a name="toc-Web_002dbased-Systems"
href="#Web_002dbased-Systems">4.8.1 Web-based Systems</a></li>
</ul></li>
- <li><a name="toc-What-to-Translate" href="#Priorities">5.4 What to
Translate</a></li>
- <li><a name="toc-Keeping-Translations-Current" href="#Updating">5.5
Keeping Translations Current</a></li>
- <li><a name="toc-When-to-CAPITALIZE" href="#Capitalization">5.6 When to
CAPITALIZE</a></li>
- <li><a name="toc-Distribution-Terms-1" href="#Distribution-Terms">5.7
Distribution Terms</a></li>
- <li><a name="toc-Language_002dspecific-Terminology"
href="#Terminology">5.8 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-Migration-to-the-New-Style" href="#Migrating">4.9
Migration to the New Style</a></li>
+ <li><a name="toc-Summary-of-SSI-_0023includes" href="#SSI">4.10 Summary of
SSI <code>#include</code>s</a></li>
+ <li><a name="toc-How-to-Use-Custom-CSS" href="#CSS">4.11 How to Use Custom
CSS</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>
+ <li><a name="toc-Localizing-the-topbanner-Image"
href="#topbanner">4.11.1 Localizing the <samp>topbanner</samp> Image</a></li>
+ <li><a name="toc-Specific-Issues-Related-to-RTL" href="#RTL">4.11.2
Specific Issues Related to RTL</a></li>
+ </ul></li>
</ul></li>
<li><a name="toc-GNU-Free-Documentation-License"
href="#Copying-This-Manual">Appendix A GNU Free Documentation License</a></li>
</ul>
@@ -146,7 +142,7 @@
<h1 class="top">GNU Web Translators Manual</h1>
<p>This manual is a guide for the GNU Web Translators.<br> Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
</p><br>
<p>Copyright © 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -168,14 +164,9 @@
</td></tr>
<tr><td align="left" valign="top">• <a href="#Leaders"
accesskey="3">Leaders</a>:</td><td> </td><td align="left"
valign="top">Guidelines and procedures for team leaders.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Translation-Managers"
accesskey="4">Translation Managers</a>:</td><td> </td><td
align="left" valign="top">Responsibilities of the GNU Web Translation
- co-ordinators.
+<tr><td align="left" valign="top">• <a href="#Translation-Process"
accesskey="4">Translation Process</a>:</td><td> </td><td
align="left" valign="top">General guidelines and tips.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Translation-Tips"
accesskey="5">Translation Tips</a>:</td><td> </td><td align="left"
valign="top">Explanation of some non-obvious things.
-</td></tr>
-<tr><td align="left" valign="top">• <a href="#Summary"
accesskey="6">Summary</a>:</td><td> </td><td align="left"
valign="top">Overview.
-</td></tr>
-<tr><td align="left" valign="top">• <a href="#Copying-This-Manual"
accesskey="7">Copying This Manual</a>:</td><td> </td><td
align="left" valign="top">The GNU Free Documentation License.
+<tr><td align="left" valign="top">• <a href="#Copying-This-Manual"
accesskey="5">Copying This Manual</a>:</td><td> </td><td
align="left" valign="top">The GNU Free Documentation License.
</td></tr>
</table>
@@ -221,19 +212,18 @@
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
+language teams. Each team has one or more co-ordinators, who are
+responsible for the respective team; they are also referred to as
+leaders or (when multiple in a single team) co-leaders. The
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
+Managers (also known as Translation Managers or web-translators).
+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,
-see <a href="#Leaders">Leaders</a>. The chapter about the
‘<samp>trans-coord</samp>’
-administrators (a.k.a. <em>GNU Translation Managers</em>) describes all the
-responsibilities and procedures involved in performing this duty.
-See <a href="#Translation-Managers">Translation Managers</a>.
+see <a href="#Leaders">Leaders</a>.
</p>
<hr>
<a name="Members"></a>
@@ -318,7 +308,7 @@
two weeks), please write to <a href="mailto:address@hidden";>address@hidden</a>.
</p>
<p>For general information about the translation process,
-see <a href="#Translation-Tips">Translation Tips</a>.
+see <a href="#Translation-Process">Translation Process</a>.
</p>
<hr>
<a name="Submitting"></a>
@@ -517,7 +507,7 @@
<a name="Leaders"></a>
<div class="header">
<p>
-Next: <a href="#Translation-Managers" accesskey="n" rel="next">Translation
Managers</a>, Previous: <a href="#Members" accesskey="p"
rel="previous">Members</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
+Next: <a href="#Translation-Process" accesskey="n" rel="next">Translation
Process</a>, Previous: <a href="#Members" accesskey="p"
rel="previous">Members</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="Team-Co_002dordinators"></a>
<h2 class="chapter">3 Team Co-ordinators</h2>
@@ -546,15 +536,13 @@
</td></tr>
<tr><td align="left" valign="top">• <a href="#Commits"
accesskey="4">Commits</a>:</td><td> </td><td align="left"
valign="top">CVS commits and best practices.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#PO-Files" accesskey="5">PO
Files</a>:</td><td> </td><td align="left" valign="top">Working with
PO files.
+<tr><td align="left" valign="top">• <a href="#Savannah"
accesskey="5">Savannah</a>:</td><td> </td><td align="left"
valign="top">Taking advantage of Savannah.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Savannah"
accesskey="6">Savannah</a>:</td><td> </td><td align="left"
valign="top">Taking advantage of Savannah.
+<tr><td align="left" valign="top">• <a href="#Co_002dleaders"
accesskey="6">Co-leaders</a>:</td><td> </td><td align="left"
valign="top">Promoting members as co-leaders.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Co_002dleaders"
accesskey="7">Co-leaders</a>:</td><td> </td><td align="left"
valign="top">Promoting members as co-leaders.
+<tr><td align="left" valign="top">• <a href="#Reports"
accesskey="7">Reports</a>:</td><td> </td><td align="left"
valign="top">Reporting team status and activity.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Reports"
accesskey="8">Reports</a>:</td><td> </td><td align="left"
valign="top">Reporting team status and activity.
-</td></tr>
-<tr><td align="left" valign="top">• <a href="#Stepping-Down"
accesskey="9">Stepping Down</a>:</td><td> </td><td align="left"
valign="top">Orphaning the team and finding a replacement.
+<tr><td align="left" valign="top">• <a href="#Stepping-Down"
accesskey="8">Stepping Down</a>:</td><td> </td><td align="left"
valign="top">Orphaning the team and finding a replacement.
</td></tr>
</table>
@@ -714,6 +702,14 @@
</li><li>- www-discuss
</li></ul>
+</li><li> When you are appointed the admin of the new project, please edit its
+configuration; in particular, write its description, create a mailing
+list (don’t forget to subscribe yourself!), optionally add a home
+page using Web CVS repository.
+
+<p>If you are taking over an orphaned team, Translation Managers will
+make you the owner of its mailing lists (if any).
+</p>
</li></ol>
<p>The whole process should not take more than two weeks or maximum a
@@ -935,7 +931,7 @@
<a name="Commits"></a>
<div class="header">
<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="#Leaders"
accesskey="u" rel="up">Leaders</a> [<a href="#SEC_Contents" title="Table
of contents" rel="contents">Contents</a>]</p>
+Next: <a href="#Savannah" accesskey="n" rel="next">Savannah</a>, Previous: <a
href="#Review" accesskey="p" rel="previous">Review</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="CVS-Commits-and-Best-Practices"></a>
<h3 class="section">3.4 CVS Commits and Best Practices</h3>
@@ -1022,102 +1018,13 @@
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="#Leaders" accesskey="u" rel="up">Leaders</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
-</div>
-<a name="Working-with-PO-Files"></a>
-<h3 class="section">3.5 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<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="subsection">3.5.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="#PO-Files" accesskey="p" rel="previous">PO Files</a>, Up: <a
href="#Leaders" accesskey="u" rel="up">Leaders</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="#Commits" accesskey="p" rel="previous">Commits</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="Taking-Advantage-of-Savannah"></a>
-<h3 class="section">3.6 Taking Advantage of Savannah</h3>
+<h3 class="section">3.5 Taking Advantage of Savannah</h3>
<p>Every translation team should have a project in Savannah. There are
some teams that use their own resources outside Savannah; although
@@ -1187,7 +1094,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="subsection">3.6.1 Managing Members</h4>
+<h4 class="subsection">3.5.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
@@ -1214,7 +1121,7 @@
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="subsection">3.6.2 Homepage of the Team</h4>
+<h4 class="subsection">3.5.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
@@ -1244,7 +1151,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="subsection">3.6.3 Support Tracker</h4>
+<h4 class="subsection">3.5.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
@@ -1259,7 +1166,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="subsection">3.6.4 Tasks Tracker</h4>
+<h4 class="subsection">3.5.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
@@ -1279,7 +1186,7 @@
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="subsection">3.6.5 Bugs Tracker</h4>
+<h4 class="subsection">3.5.5 Bugs Tracker</h4>
<p>The ‘<samp>Bugs</samp>’ tracker is designed for tracking bugs.
You can use for
several purposes:
@@ -1302,7 +1209,7 @@
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="subsection">3.6.6 News Tracker</h4>
+<h4 class="subsection">3.5.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
@@ -1323,12 +1230,14 @@
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="subsection">3.6.7 Managing Mailing Lists</h4>
+<h4 class="subsection">3.5.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
list. The list owner should be the co-ordinator of the team. The
-name of the list should begin with
‘<samp>www-<var>lang</var>-</samp>’.
+name of the list should begin with
‘<samp>www-<var>lang</var>-</samp>’. The team
+co-ordinator is in the position to decide about the settings like
+being public or private.
</p>
<p>The list will make it possible for the GNU project to contact the team
when the co-ordinator disappears; its archive will also give access to
@@ -1348,7 +1257,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="subsection">3.6.8 Version Control Systems</h4>
+<h4 class="subsection">3.5.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
@@ -1357,7 +1266,7 @@
ready. It is also convenient to update the translation (merge any
changes from the original) while it is still under review.
</p>
-<p>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>, for
+<p>See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#Team_0027s-Repository";>Team's
Repository</a> in <cite>The GNUnited Nations Manual</cite>, for
more information.
</p>
<p><strong>Remember:</strong> A choice of a particular VCS is a sensitive
@@ -1373,7 +1282,7 @@
Next: <a href="#Reports" accesskey="n" rel="next">Reports</a>, Previous: <a
href="#Savannah" accesskey="p" rel="previous">Savannah</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="Promoting-Members-as-Co_002dleaders"></a>
-<h3 class="section">3.7 Promoting Members as Co-leaders</h3>
+<h3 class="section">3.6 Promoting Members as Co-leaders</h3>
<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
@@ -1402,7 +1311,7 @@
Next: <a href="#Stepping-Down" accesskey="n" rel="next">Stepping Down</a>,
Previous: <a href="#Co_002dleaders" accesskey="p"
rel="previous">Co-leaders</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="Reporting-Team-Status"></a>
-<h3 class="section">3.8 Reporting Team Status</h3>
+<h3 class="section">3.7 Reporting Team Status</h3>
<p>Team leaders must send an annual report about the status of the team. A
good report should include:
@@ -1451,7 +1360,7 @@
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.9 How to Retire Painlessly</h3>
+<h3 class="section">3.8 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
@@ -1466,741 +1375,805 @@
to proceed without your further help and advice.
</p>
<hr>
-<a name="Translation-Managers"></a>
-<div class="header">
-<p>
-Next: <a href="#Translation-Tips" accesskey="n" rel="next">Translation
Tips</a>, Previous: <a href="#Leaders" accesskey="p"
rel="previous">Leaders</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="trans_002dcoord-Admins"></a>
-<h2 class="chapter">4 ‘<samp>trans-coord</samp>’ Admins</h2>
-
-<p>This chapter is not yet written. The current admins know what to do,
-hopefully.
-</p>
-<hr>
-<a name="Translation-Tips"></a>
+<a name="Translation-Process"></a>
<div class="header">
<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>
+Next: <a href="#Copying-This-Manual" accesskey="n" rel="next">Copying This
Manual</a>, Previous: <a href="#Leaders" accesskey="p"
rel="previous">Leaders</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="Translation-Process-1"></a>
+<h2 class="chapter">4 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
-become well known as time goes by; however, practice shows that it is
-difficult to figure them out at once.
+<p>In general, it is expected that all participants in the translation
+process apply common sense for all of the decisions (important or not)
+they are going to take in their capacity as a manager, team leader, or
+contributing member. Certainly, many decisions are not easy, and
+require some thought.
</p>
-<p>Some limitations and oddities are just historical remnants from old
-habits and previous incarnations of old (inefficient) translation and
-webmastering processes. Others are outright deficiencies
-(i.e. “bugs”), but no one has stepped in to correct them so far.
+<p>This manual is a work in progress—it is not set in stone, and it
+will never be finished—the ultimate goal is to constantly improve
+the translation process, and as a consequence, the documentation.
+Every participant in the process should be free to suggest
+modifications to the current procedures and suggestions how to improve
+the current state of affairs. Ideally, they should be accompanied
+with patches to the Texinfo source, but that’s not mandatory. In any
+event, please write to <a
href="mailto:address@hidden";>address@hidden</a>—the goal
+of this list is precisely to discuss improvements of the translation
+process.
</p>
<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top">• <a href="#Migrating"
accesskey="1">Migrating</a>:</td><td> </td><td align="left"
valign="top">How to migrate to the new style.
+<tr><td align="left" valign="top">• <a href="#Priorities"
accesskey="1">Priorities</a>:</td><td> </td><td align="left"
valign="top">What to translate as a priority.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Updating"
accesskey="2">Updating</a>:</td><td> </td><td align="left"
valign="top">Keeping translations current is a priority.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#SSI"
accesskey="2">SSI</a>:</td><td> </td><td align="left"
valign="top">Overview of SSI #include directives.
+<tr><td align="left" valign="top">• <a href="#Capitalization"
accesskey="3">Capitalization</a>:</td><td> </td><td align="left"
valign="top">To CAPITALIZE or not?
</td></tr>
-<tr><td align="left" valign="top">• <a href="#CSS"
accesskey="3">CSS</a>:</td><td> </td><td align="left"
valign="top">General advice how to use CSS.
+<tr><td align="left" valign="top">• <a href="#Distribution-Terms"
accesskey="4">Distribution Terms</a>:</td><td> </td><td align="left"
valign="top">Translating distribution terms.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Priorities"
accesskey="4">Priorities</a>:</td><td> </td><td align="left"
valign="top">What to translate as a priority.
+<tr><td align="left" valign="top">• <a href="#Terminology"
accesskey="5">Terminology</a>:</td><td> </td><td align="left"
valign="top">Dealing with terminology issues.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Updating"
accesskey="5">Updating</a>:</td><td> </td><td align="left"
valign="top">Keeping translations current is a priority.
+<tr><td align="left" valign="top">• <a href="#Mailing-Lists"
accesskey="6">Mailing Lists</a>:</td><td> </td><td align="left"
valign="top">Summary of mailing lists.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Capitalization"
accesskey="6">Capitalization</a>:</td><td> </td><td align="left"
valign="top">To CAPITALIZE or not?
+<tr><td align="left" valign="top">• <a href="#Savannah-Projects"
accesskey="7">Savannah Projects</a>:</td><td> </td><td align="left"
valign="top">Projects membership.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Distribution-Terms"
accesskey="7">Distribution Terms</a>:</td><td> </td><td align="left"
valign="top">Translating distribution terms.
+<tr><td align="left" valign="top">• <a href="#PO-Files" accesskey="8">PO
Files</a>:</td><td> </td><td align="left" valign="top">Working with
PO files.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Terminology"
accesskey="8">Terminology</a>:</td><td> </td><td align="left"
valign="top">Dealing with terminology issues.
+<tr><td align="left" valign="top">• <a href="#Migrating"
accesskey="9">Migrating</a>:</td><td> </td><td align="left"
valign="top">How to migrate to the new style.
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#SSI">SSI</a>:</td><td> </td><td align="left"
valign="top">Overview of SSI #include directives.
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#CSS">CSS</a>:</td><td> </td><td align="left"
valign="top">General advice how to use CSS.
</td></tr>
</table>
<hr>
-<a name="Migrating"></a>
+<a name="Priorities"></a>
<div class="header">
<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>
+Next: <a href="#Updating" accesskey="n" rel="next">Updating</a>, Up: <a
href="#Translation-Process" accesskey="u" rel="up">Translation Process</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="What-to-Translate"></a>
+<h3 class="section">4.1 What to Translate</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
-translations, see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#Migrating";>Migrating</a>
in <cite>The GNUnited Nations Manual</cite>.
-If the old translation is HTML 2.0 (or 3.2), you still have to take care
-about the inner markup. Overall, it is substantially easier than doing
-all of it manually.
+<p>The page
+<a
href="http://www.gnu.org/server/standards/translations/priorities.html";>http://www.gnu.org/server/standards/translations/priorities.html</a>
+lists the most important essays to translate. In general, articles in
+the directories <samp>philosophy</samp>, <samp>gnu</samp>,
+<samp>education</samp>, <samp>distros</samp>,
+<samp>copyleft</samp> and <samp>licenses</samp> are important. The others may
be
+deferred for a time when a team completes most of the important
+translations, or they can be translated as a “rest”—in
translators’
+parlance this means doing something in between which is typically easier
+to handle.
</p>
-<p>Subsequent migrations to newer HTML standards and newer look and feel
-of the website are supposed to happen semi-automatically, although
-this manual will be updated as needed.
+<p>You can find links automatic reports about current status of
+translations of all active teams sorted by their priority 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
+<a href="mailto:address@hidden";>address@hidden</a> to add it to the cron job.
</p>
-<hr>
-<a name="SSI"></a>
-<div class="header">
-<p>
-Next: <a href="#CSS" accesskey="n" rel="next">CSS</a>, Previous: <a
href="#Migrating" accesskey="p" rel="previous">Migrating</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="Summary-of-SSI-_0023includes"></a>
-<h3 class="section">5.2 Summary of SSI <code>#include</code>s</h3>
-
-<p>The GNU Project’s website uses SSI (Server Side Includes) to manage
some
-common parts that are the same in many of the articles. With the help
-of GNUN their handling should be behind the scenes, but for some of them
-manual intervention is needed. Here is a (possibly incomplete) list of
-the <code>#include</code>’s used:
+<p><em>Do not</em> translate articles under these directories:
</p>
<dl compact="compact">
-<dt><samp>server/banner.html</samp></dt>
-<dd><p>This file contains only <code>#include</code> directives, so the
-“translation” should be identical, with filenames modified to have
the
-<var>lang</var> extension.
-</p>
-</dd>
-<dt><samp>server/body-include-1.html</samp></dt>
-<dd><p>Contains the top menu with useful “skip to” links.
+<dt><samp>software/<var>pkg</var>/</samp></dt>
+<dd><p>These pages are maintained by the respective <var>pkg</var> maintainers.
+GNUN does not support them for the time being, as they reside in
+separate repositories. The procedures for contributing translations of
+such articles are not yet settled.
</p>
</dd>
-<dt><samp>server/body-include-2.html</samp></dt>
-<dd><p>This is the file containing the menus, the FSF widget, and any visible
-announcements made from time to time. If a string gets “fuzzy” or
-“new” here, it will appear in English in all translations, until
-<samp>server/po/body-include-2.<var>lang</var>.po</samp> is updated. Note that
-some validation errors originate from an error in
-<samp>server/body-include-2.<var>lang</var>.html</samp> or some other template
-file.
+<dt><samp>brave-gnu-world</samp></dt>
+<dd><p>The Brave GNU World initiative has been abandoned long time ago, and
+it’s in a separate repository—thus not supported by the automatic
GNUN
+build job.
</p>
</dd>
-<dt><samp>server/bottom-notes.html</samp></dt>
-<dd><p>A link to the FSF page explaining how to report possible copyright
-infringements.
+<dt><samp>home.html</samp></dt>
+<dd><p>There is no problem to translate this page, but don’t make the
mistake
+to pick it up as your first translation. It is modified often,
+sometimes intensively, and only active team members should take that
+road.
</p>
</dd>
-<dt><samp>server/footer-text.html</samp></dt>
-<dd><p>This is a very short file currently containing the “back to
top” link.
-Also translatable via GNUN.
+<dt><samp>server/whatsnew.html</samp></dt>
+<dd><p>This is “What’s New”, also known as
“GNU’s Flashes”, also known as
+“GNU News”. It is deprecated since quite some time and translating
+it is discouraged.
+</p></dd>
+</dl>
+
+<hr>
+<a name="Updating"></a>
+<div class="header">
+<p>
+Next: <a href="#Capitalization" accesskey="n" rel="next">Capitalization</a>,
Previous: <a href="#Priorities" accesskey="p" rel="previous">Priorities</a>,
Up: <a href="#Translation-Process" accesskey="u" rel="up">Translation
Process</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
+</div>
+<a name="Keeping-Translations-Current"></a>
+<h3 class="section">4.2 Keeping Translations Current</h3>
+
+<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. We developped different means to automate
+the process of tracking outdated translations.
</p>
-</dd>
-<dt><samp>server/header.html</samp></dt>
-<dd><p>The declaration that is included in literally every file. It is
-maintained manually, as it does not make much sense to put it under
-GNUN’s control (there are no translatable strings). Remember to specify
-the proper <code>xml:lang</code> and <code>lang</code> attributes, and for RTL
-languages, the <code>dir</code> attribute. For example, the file
-<samp>header.ar.html</samp> should contain this line:
+<ul>
+<li> 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 cron job which sends the output of this
+rule 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>.
+
+</li><li> The <code>gnun-report</code> script produces a HTML page listing
detailed
+status of translations; see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#gnun_002dreport";>gnun-report</a>
in <cite>The GNUnited
+Nations Manual</cite>. A cron job commits updated reports for all active
+teams to GNUN project web repository, typically twice an hour. The
+links to those reports are provided on
+<a
href="http://gnu.org/software/gnun/reports/";>http://gnu.org/software/gnun/reports/</a>.
+
+</li><li> GNUmakefile.team provides a more detailed <code>report</code>
target: unlike
+the output of the previous tools, it analyzes the status of files in
+team’s repository as well as of those in ‘<samp>www</samp>’
repository;
+see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#report-in-GNUmakefile_002eteam";>report
in GNUmakefile.team</a> in <cite>The GNUnited
+Nations Manual</cite>.
+
+</li><li> GNUmakefile.team also has a means to send a further detalized reports
+to specific translators; see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#notify-in-GNUmakefile_002eteam";>notify
in GNUmakefile.team</a> in <cite>The GNUnited Nations Manual</cite>. The
notification facility takes the
+output of the <code>report</code> target, adds the URLs of relevant files,
+and the results are sent with attached HTML files of
+team’s-against-‘<samp>www</samp>’ differences to the
translators who requested
+tracking particular files.
+
+<p>The feature is supposed to be invoked via a cron job; such jobs
+already run for some teams on our server. If you’d like GNU Web
+Translation Managers to setup a job for your team, please write to
+<a href="mailto:address@hidden";>address@hidden</a>.
</p>
-<div class="example">
-<pre class="example"><html xmlns="http://www.w3.org/1999/xhtml"
xml:lang="ar" lang="ar"
- dir="rtl">
-</pre></div>
+</li></ul>
-</dd>
-<dt><samp>server/head-include-1.html</samp></dt>
-<dd><p>This file (included from <samp>server/header.html</samp>) is very
important:
-the encoding is defined here. Note that it is applicable for all
-translations, so it is not possible to have different articles in
-different encodings. Even if a specific PO file is deliberately encoded
-in another encoding, the generated HTML will contain the encoding
-declared in the <code><meta></code> element at
-<samp>server/head-include-1.<var>lang</var>.html</samp>, so browsers will obey
it.
-</p>
-<p>The encoding should be UTF-8. This is required because the English text
-in the articles serves as a replacement of the translation when the latter
-is not complete, and because all translated pages share automatically
-generated lists of translations.
-</p>
-</dd>
-<dt><samp>server/html5-header.html</samp></dt>
-<dd><p>This file is included in newer pages using some entities introduced
-in HTML5 draft. We have to distinguish those pages since some features
-of HTML4 were rejected in HTML5, and our old pages don’t validate
-as HTML5.
-</p>
-</dd>
-<dt><samp>server/html5-head-include-1.html</samp></dt>
-<dd><p>Likewise, this file replaces head-include-1.html for HTML5 pages.
-</p>
-</dd>
-<dt><samp>server/head-include-2.html</samp></dt>
-<dd><p>Imports the standard CSS, which can be overridden. See <a
href="#CSS">CSS</a>.
-</p>
-</dd>
-<dt><samp>server/footer.html</samp></dt>
-<dd><p>This is a very short and simple file (at least at the time of writing),
-containing another <code>#include</code> directive. It is maintained
-manually, so just add <var>lang</var> to the filename, in order the localized
-<samp>footer-text.<var>lang</var>.html</samp> to be included.
-</p>
-</dd>
-<dt><samp>server/outdated.html</samp></dt>
-<dd><p>This file is automatically included in outdated translations. It
-contains respective message with links to the English file and
-to a generated difference of the current revision of the English
-file against the most recent revision that has a complete translation.
-It is only included in articles affected by “grace period” because
-in those cases the outdated passages are replaced with English text,
-and it is evident without any notices that there is no complete
-and up to date translation.
-</p>
-</dd>
-<dt><samp>server/skip-translations.html</samp></dt>
-<dd><p>The text for a link to the end of the autogenerated list of
-translations.
-</p>
-</dd>
-<dt><samp>server/top-addendum.html</samp></dt>
-<dd><p>The text saying that the page is a translation.
-</p>
-</dd>
-<dt><samp>translations.include</samp></dt>
-<dd><p>The list of translations for the homepage (and only the homepage). It
-is maintained manually; in order the link to a translation to appear on
-all of the homepages, it has to be present here.
-</p>
-</dd>
-<dt><samp>licenses/gpl-3.0-body.html</samp></dt>
-<dt><samp>licenses/fdl-1.3-body.html</samp></dt>
-<dt><samp>…</samp></dt>
-<dd><p>Some of the licenses have the text of the license itself separated in
-another file. This serves two purposes: 1) to provide a
“standalone”
-HTML version of the license without the gnu.org style; 2) to prevent
-strings sneaking in the <samp>.pot</samp> files, as licenses have only
-unofficial translations, hosted elsewhere. Nothing special should be
-done about these SSI directives; the files generated by GNUN include
-them verbatim as they should not be translated.
-</p>
-</dd>
-<dt><samp>server/sidebar*.html</samp></dt>
-<dd><p>These files are deprecated—they are remnants from an older design
that
-lived shortly in the middle between the old classic design and the
-current one. If all translations are successfully migrated and none of
-them includes such files, you should delete them. You can use
-<code>grep</code> to check this.
-</p></dd>
-</dl>
+<hr>
+<a name="Capitalization"></a>
+<div class="header">
+<p>
+Next: <a href="#Distribution-Terms" accesskey="n" rel="next">Distribution
Terms</a>, Previous: <a href="#Updating" accesskey="p"
rel="previous">Updating</a>, Up: <a href="#Translation-Process" accesskey="u"
rel="up">Translation Process</a> [<a href="#SEC_Contents" title="Table
of contents" rel="contents">Contents</a>]</p>
+</div>
+<a name="When-to-CAPITALIZE"></a>
+<h3 class="section">4.3 When to CAPITALIZE</h3>
-<p>The files
+<p>The English language has some rules for capitalization of titles,
+chapters, acronym expansions and the like. These rules are neither
+strict nor uniform, although the gnu.org website strives to apply them
+consistently. They do not make sense for many other languages, but
+unfortunately, many translators <em>erroneously duplicate</em> the
+capitalization in their translation.
</p>
-<ul class="no-bullet">
-<li>- <samp>header.html</samp>
-</li><li>- <samp>head-include-1.html</samp>
-</li><li>- <samp>html5-header.html</samp>
-</li><li>- <samp>html5-head-include-1.html</samp>
-</li><li>- <samp>head-include-2.html</samp>
-</li><li>- <samp>banner.html</samp>
-</li><li>- <samp>body-include-1.html</samp>
-</li><li>- <samp>body-include-2.html</samp>
-</li><li>- <samp>bottom-notes.html</samp>
-</li><li>- <samp>footer.html</samp>
-</li><li>- <samp>footer-text.html</samp>
-</li><li>- <samp>skip-translations.html</samp>
-</li></ul>
-
-<p>in the <samp>server</samp> sub-directory are what webmasters call “the
-server templates”. These files are included in almost every article,
-translated or not. They are somewhat important, as an error made in
-translating them propagates everywhere. The server templates, the
-homepages, and whatsnew (a.k.a. “GNU News”) are being rebuilt by
-GNUN whenever there is a change in the original English files; the
-<code>GRACE</code> variable has no effect for them. See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#Runtime-Variables";>Runtime
-Variables</a> in <cite>The GNUnited Nations Manual</cite>.
+<p>Examples for common (and correct) English capitalization is the title of
+the article “Why Software Should Be Free” or “Free Software
+Foundation” (FSF). However, in languages that do not have such grammar
+rules it is wrong to write “Dlaczego Oprogramowanie Powinno Być
+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 list of translations when
+languages are written beginning with a small letter according to your
+own rules<a name="DOCF6" href="#FOOT6"><sup>6</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="CSS"></a>
+<a name="Distribution-Terms"></a>
<div class="header">
<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>
+Next: <a href="#Terminology" accesskey="n" rel="next">Terminology</a>,
Previous: <a href="#Capitalization" accesskey="p"
rel="previous">Capitalization</a>, Up: <a href="#Translation-Process"
accesskey="u" rel="up">Translation Process</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="Distribution-Terms-1"></a>
+<h3 class="section">4.4 Distribution Terms</h3>
-<p>The CSS file <samp>layout.css</samp> gets included (with three other CSS
files)
-in almost all the English articles through
-<samp>server/head-include-2.<var>lang</var>.html</samp>. However, sometimes
this
-style isn’t quite right for translations—many languages have much
-longer expressions, and that is natural. To include your own CSS,
-create a file <samp>style.<var>lang</var>.css</samp> and add it <em>after</em>
the
-directive to include <samp>server/head-include-2.<var>lang</var>.html</samp>
and
-<em>before</em> the closing <code></head></code> tag in
-<samp>server/banner.<var>lang</var>.html</samp>, i.e.
+<p>Most www.gnu.org articles are released under the terms of
+the Creative Commons Attribution-NoDerivs 3.0 United States license.
+The exact HTML for English pages to use is:
</p>
<div class="example">
-<pre class="example"><!-- start of banner.bg.html -->
-<!--#include virtual="/server/head-include-2.bg.html" -->
-<link rel="stylesheet" href="/style.bg.css"
media="screen" />
-</head>
+<pre class="example">This page is licensed under a <a
rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.
</pre></div>
-<p>Override only what is necessary and looks broken in your language; do
-not invent your own style. This is important for the consistency of the
-gnu.org website. A typical language-specific
-<samp>style.<var>lang</var>.css</samp> file looks like this:
+<p>Pages in other languages should translate this notice, and should link
+to a translated version of the Creative Commons license “deed” if
it’s
+available. Creative Commons provides standard text for this in all the
+languages they support, and we should use that wording whenever
+possible. To do that, follow these steps:
</p>
-<div class="example">
-<pre class="example">.inner { max-width: 65em; }
+<ul>
+<li> Check at the bottom of the English deed page to see the list of
+languages they support. Follow the link the language that you want a
+translation for, if available.
-#logo{background:url(/graphics/topbanner.bg.png) no-repeat;}
-#fssbox {font-size: 50%;}
+</li><li> Follow the “Use this license for your own work” link
near the bottom
+of the translated deed page—it’s in distinct yellow text.
+
+</li><li> The textarea on that page provides standard HTML. Note that
we’re not
+using the graphic, just the text.
+
+</li></ul>
+
+<p>For example, here’s the text they provide for Dutch:
+</p>
+<div class="example">
+<pre class="example">Dit werk is gelicenseerd onder een <a
rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.nl">
+Creative Commons Naamsvermelding-GeenAfgeleideWerken 3.0 Verenigde
+Staten licentie</a>
</pre></div>
-<p>This widens the menu and the area where the articles are displayed
-(because the menu entries are <em>much</em> longer than the English
-equivalents when translated), includes a localized logo, and makes the
-font size for the FSF widget twice smaller (because in this language,
-the translations are almost twice longer and displayed truncated, which
-is undesirable).
+<p>Note that the link in this text is changed to point directly to the
+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>When creating your own <samp>style.<var>lang</var>.css</samp>, don’t
forget to
-include the license notice from the <samp>layout.css</samp>, with a short
-comment.
+<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>If using the default CSS style for translations does not give the
-expected good results, or there are other problems (significant or not)
-that obstruct reading and/or worsen the look from aesthetic point of
-view, please write to <a href="mailto:address@hidden";>address@hidden</a> with
a description of
-the issue. If there are several unrelated problems, send separate
-messages with appropriate explanation (which may include a demonstration
-of the bug, such as a screenshot).
+<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
+States</em> license, and <em>not</em> a different port like CC BY-ND 3.0
+Japan. This is because there are substantive differences between the way
+different ports handle moral rights issues, and we prefer the specific
+terms that are in the United States license.
</p>
-<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top">• <a href="#topbanner"
accesskey="1">topbanner</a>:</td><td> </td><td align="left"
valign="top">How to localize the topbanner image.
-</td></tr>
-<tr><td align="left" valign="top">• <a href="#RTL"
accesskey="2">RTL</a>:</td><td> </td><td align="left"
valign="top">Special notes about RTL languages.
-</td></tr>
-</table>
-
<hr>
-<a name="topbanner"></a>
+<a name="Terminology"></a>
<div class="header">
<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>
+Next: <a href="#Mailing-Lists" accesskey="n" rel="next">Mailing Lists</a>,
Previous: <a href="#Distribution-Terms" accesskey="p"
rel="previous">Distribution Terms</a>, Up: <a href="#Translation-Process"
accesskey="u" rel="up">Translation Process</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="Language_002dspecific-Terminology"></a>
+<h3 class="section">4.5 Language-specific Terminology</h3>
-<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:
+<p>This is a very important topic, not yet covered by this manual.
</p>
-<ol>
-<li> Copy <samp>graphics/topbanner.svg</samp> as
-<samp>graphics/topbanner.<var>lang</var>.svg</samp> where <var>lang</var> is
the
-language code, as usual. Edit the file with Inkscape or with a plain
-text editor such as GNU Emacs, translating “GNU Operating System”.
-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="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,
-namely:
-
-<div class="example">
-<pre
class="example">#logo{background:url(/graphics/topbanner.<var>lang</var>.png)
no-repeat;}
-</pre></div>
-
-</li><li> If not done already for other reasons, update
-<samp>banner.<var>lang</var>.html</samp> to include the language specific
-<samp>style.<var>lang</var>.css</samp>. See <a href="#CSS">CSS</a>.
-</li></ol>
-
-<p>If you feel uncomfortable manipulating images—don’t despair!
Send a
-plea for help to <a href="mailto:address@hidden";>address@hidden</a>, some
people would
-be happy to help you. Failing that, write to
-<a href="mailto:address@hidden";>address@hidden</a>.
+<p>Some tips are given on
+<a
href="http://www.gnu.org/server/standards/README.translations.en.html";>http://www.gnu.org/server/standards/README.translations.en.html</a>.
</p>
<hr>
-<a name="RTL"></a>
+<a name="Mailing-Lists"></a>
<div class="header">
<p>
-Previous: <a href="#topbanner" accesskey="p" rel="previous">topbanner</a>, Up:
<a href="#CSS" accesskey="u" rel="up">CSS</a> [<a href="#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
+Next: <a href="#Savannah-Projects" accesskey="n" rel="next">Savannah
Projects</a>, Previous: <a href="#Terminology" accesskey="p"
rel="previous">Terminology</a>, Up: <a href="#Translation-Process"
accesskey="u" rel="up">Translation Process</a> [<a href="#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-<a name="Specific-Issues-Related-to-RTL"></a>
-<h4 class="subsection">5.3.2 Specific Issues Related to RTL</h4>
+<a name="Related-Mailing-Lists"></a>
+<h3 class="section">4.6 Related Mailing Lists</h3>
-<p>Unfortunately, the <a href="http://gnu.org";>http://gnu.org</a> website does
not have excellent
-support for RTL (right-to-left) languages, although best efforts are
-made. If your language is in this category, make sure to:
+<p>Here is a short summary of the mailing lists relevant to the translation
+process, and a brief description about how they relate to the various
+participants in the process.
</p>
-<ul>
-<li> Set the attribute <code>dir="rtl"</code> in the
<code>html</code> element at
-<samp>server/header.<var>lang</var>.html</samp>.
-
-</li><li> You <em>must</em> have a custom CSS to override some of the
pre-defined
-values. See <samp>style.ar.css</samp> and <samp>style.fa.css</samp> to
understand
-how these two languages solve some of the problems. See <a
href="#CSS">CSS</a>.
-</li></ul>
+<dl compact="compact">
+<dt><a href="mailto:address@hidden";>address@hidden</a></dt>
+<dd><p>The basic discussion list of the GNU Webmasters. All team leaders are
+required to subscribe.
+</p>
+<p>This is a private mailing list.
+</p>
+</dd>
+<dt><a href="mailto:address@hidden";>address@hidden</a></dt>
+<dd><p>Commits to the ‘<samp>www</samp>’ 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 delivery can
+be disabled personally.
+</p>
+<p>This is a public mailing list, so everyone can subscribe and review the
+archives. The ‘<samp>www</samp>’ CVS repository is also public.
+</p>
+</dd>
+<dt><a href="mailto:address@hidden";>address@hidden</a></dt>
+<dd><p>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 in general
+policies for translations are also announced and discussed here.
+</p>
+<p>This is a private mailing list.
+</p>
+</dd>
+<dt><a href="mailto:address@hidden";>address@hidden</a></dt>
+<dd><p>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 announcements,
+subscribe to the ‘<samp>gnun</samp>’ topic via Mailman’s
user interface.
+Likewise, if you want to receive only <em>What’s New</em> updates,
+subscribe to the ‘<samp>whatsnew</samp>’ topic.
+</p>
+<p>Automatic announcements for new gnu.org translations (provided they’re
+handled by GNUN) are also delivered here. There are separate
+‘<samp><var>lang</var>-ann</samp>’ topics for every GNUN-aware
language, so it is a
+good idea to advertise this capability widely among your local
+community. For example, if a reader wants to be informed only about new
+Spanish translations, she can just subscribe to the
‘<samp>es-ann</samp>’
+mailing list topic.
+</p>
+<p>This is a public mailing list.
+</p>
+</dd>
+<dt><a href="mailto:address@hidden";>address@hidden</a></dt>
+<dd><p>All development of GNUN happens here. Commits to the
‘<samp>trans-coord</samp>’
+repository are also sent to this list.
+</p>
+<p>This is a public list, and <a
href="mailto:address@hidden";>address@hidden</a> is an alias.
+</p></dd>
+</dl>
-<p><strong>Important:</strong> Some articles contain their own
<code><style></code>
-redefinitions, or style attributes in the form <code><p
-style="…"></code>. In such situations, it is quite
possible that the
-general language-specific CSS does not help, and the translation of this
-specific article does not look correct. Please write to
-<a href="mailto:address@hidden";>address@hidden</a>; if you have a working
solution that works
-for both cases—so much the better. For general issues that affect
-your language and require a general solution, write to
-<a href="mailto:address@hidden";>address@hidden</a> as well, precisely
describing the problem.
+<p>Every team should also use at least one mailing list on Savannah,
+see <a href="#Savannah-Mailing-Lists">Savannah Mailing Lists</a>.
</p>
<hr>
-<a name="Priorities"></a>
+<a name="Savannah-Projects"></a>
<div class="header">
<p>
-Next: <a href="#Updating" accesskey="n" rel="next">Updating</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>
+Next: <a href="#PO-Files" accesskey="n" rel="next">PO Files</a>, Previous: <a
href="#Mailing-Lists" accesskey="p" rel="previous">Mailing Lists</a>, Up: <a
href="#Translation-Process" accesskey="u" rel="up">Translation Process</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="Savannah-Projects-Membership"></a>
+<h3 class="section">4.7 Savannah Projects Membership</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>
-lists the most important essays to translate. In general, articles in
-the directories <samp>philosophy</samp>, <samp>gnu</samp>,
-<samp>education</samp>, <samp>distros</samp>,
-<samp>copyleft</samp> and <samp>licenses</samp> are important. The others may
be
-deferred for a time when a team completes most of the important
-translations, or they can be translated as a “rest”—in
translators’
-parlance this means doing something in between which is typically easier
-to handle.
-</p>
-<p>You can find links automatic reports about current status of
-translations of all active teams sorted by their priority 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
-<a href="mailto:address@hidden";>address@hidden</a> to add it to the cron job.
-</p>
-<p><em>Do not</em> translate articles under these directories:
+<p>Participants in the www.gnu.org translations process normally have to be
+members of the following Savannah projects, depending on the case:
</p>
<dl compact="compact">
-<dt><samp>software/<var>pkg</var>/</samp></dt>
-<dd><p>These pages are maintained by the respective <var>pkg</var> maintainers.
-GNUN does not support them for the time being, as they reside in
-separate repositories. The procedures for contributing translations of
-such articles are not yet settled.
+<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 leaders’ applications). All
+team leaders (and co-leaders) should be members of this project.
</p>
-</dd>
-<dt><samp>brave-gnu-world</samp></dt>
-<dd><p>The Brave GNU World initiative has been abandoned long time ago, and
-it’s in a separate repository—thus not supported by the automatic
GNUN
-build job.
+<p>Note that this project has no direct relationship with translators,
+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>home.html</samp></dt>
-<dd><p>There is no problem to translate this page, but don’t make the
mistake
-to pick it up as your first translation. It is modified often,
-sometimes intensively, and only active team members should take that
-road.
+<dt>‘<samp>trans-coord</samp>’</dt>
+<dd><p>An organizational project especially created for co-ordination and
+improvement of the translation process. All team leaders are required
+to be members, as bugs reported to <a
href="mailto:address@hidden";>address@hidden</a> are
+often redirected to the ‘<samp>trans-coord</samp>’
‘<samp>Bugs</samp>’ tracker.
+</p>
+<p>The admins of this project are the GNU Web Translation Managers.
</p>
</dd>
-<dt><samp>server/whatsnew.html</samp></dt>
-<dd><p>This is “What’s New”, also known as
“GNU’s Flashes”, also known as
-“GNU News”. It is deprecated since quite some time and translating
-it is discouraged.
+<dt>‘<samp>www-<var>lang</var></samp>’</dt>
+<dd><p>All translation team leaders of the language <var>lang</var> should be
+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>
<hr>
-<a name="Updating"></a>
+<a name="PO-Files"></a>
<div class="header">
<p>
-Next: <a href="#Capitalization" accesskey="n" rel="next">Capitalization</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>
+Next: <a href="#Migrating" accesskey="n" rel="next">Migrating</a>, Previous:
<a href="#Savannah-Projects" accesskey="p" rel="previous">Savannah
Projects</a>, Up: <a href="#Translation-Process" accesskey="u"
rel="up">Translation Process</a> [<a href="#SEC_Contents" title="Table
of contents" rel="contents">Contents</a>]</p>
</div>
-<a name="Keeping-Translations-Current"></a>
-<h3 class="section">5.5 Keeping Translations Current</h3>
+<a name="Working-with-PO-Files"></a>
+<h3 class="section">4.8 Working with PO Files</h3>
+<a name="index-PO_002c-editing"></a>
-<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. We developped different means to automate
-the process of tracking outdated translations.
+<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="DOCF7" href="#FOOT7"><sup>7</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="subsection">4.8.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> 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 cron job which sends the output of this
-rule 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>.
+<li> Pootle—<a
href="http://translate.sourceforge.net/wiki/pootle";>http://translate.sourceforge.net/wiki/pootle</a>
-</li><li> The <code>gnun-report</code> script produces a HTML page listing
detailed
-status of translations; see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#gnun_002dreport";>gnun-report</a>
in <cite>The GNUnited
-Nations Manual</cite>. A cron job commits updated reports for all active
-teams to GNUN project web repository, typically twice an hour. The
-links to those reports are provided on
-<a
href="http://gnu.org/software/gnun/reports/";>http://gnu.org/software/gnun/reports/</a>.
+</li><li> Vertaal—<a
href="http://code.google.com/p/vertaal";>http://code.google.com/p/vertaal</a>
-</li><li> GNUmakefile.team provides a more detailed <code>report</code>
target: unlike
-the output of the previous tools, it analyzes the status of files in
-team’s repository as well as of those in ‘<samp>www</samp>’
repository;
-see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#report-in-GNUmakefile_002eteam";>report
in GNUmakefile.team</a> in <cite>The GNUnited
-Nations Manual</cite>.
+</li><li> Narro—<a
href="http://code.google.com/p/narro";>http://code.google.com/p/narro</a>
-</li><li> GNUmakefile.team also has a means to send a further detalized reports
-to specific translators; see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#notify-in-GNUmakefile_002eteam";>notify
in GNUmakefile.team</a> in <cite>The GNUnited Nations Manual</cite>. The
notification facility takes the
-output of the <code>report</code> target, adds the URLs of relevant files,
-and the results are sent with attached HTML files of
-team’s-against-‘<samp>www</samp>’ differences to the
translators who requested
-tracking particular files.
+</li><li> Launchpad—<a
href="https://dev.launchpad.net";>https://dev.launchpad.net</a>
-<p>The feature is supposed to be invoked via a cron job; such jobs
-already run for some teams on our server. If you’d like GNU Web
-Translation Managers to setup a job for your team, please write to
-<a href="mailto:address@hidden";>address@hidden</a>.
-</p>
</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="Capitalization"></a>
+<a name="Migrating"></a>
<div class="header">
<p>
-Next: <a href="#Distribution-Terms" accesskey="n" rel="next">Distribution
Terms</a>, Previous: <a href="#Updating" accesskey="p"
rel="previous">Updating</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>
+Next: <a href="#SSI" accesskey="n" rel="next">SSI</a>, Previous: <a
href="#PO-Files" accesskey="p" rel="previous">PO Files</a>, Up: <a
href="#Translation-Process" accesskey="u" rel="up">Translation Process</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.6 When to CAPITALIZE</h3>
+<a name="Migration-to-the-New-Style"></a>
+<h3 class="section">4.9 Migration to the New Style</h3>
-<p>The English language has some rules for capitalization of titles,
-chapters, acronym expansions and the like. These rules are neither
-strict nor uniform, although the gnu.org website strives to apply them
-consistently. They do not make sense for many other languages, but
-unfortunately, many translators <em>erroneously duplicate</em> the
-capitalization in their translation.
-</p>
-<p>Examples for common (and correct) English capitalization is the title of
-the article “Why Software Should Be Free” or “Free Software
-Foundation” (FSF). However, in languages that do not have such grammar
-rules it is wrong to write “Dlaczego Oprogramowanie Powinno Być
-Wolne” (Polish) or “Fondation Pour Le Logiciel Libre”
(French).
+<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
+translations, see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#Migrating";>Migrating</a>
in <cite>The GNUnited Nations Manual</cite>.
+If the old translation is HTML 2.0 (or 3.2), you still have to take care
+about the inner markup. Overall, it is substantially easier than doing
+all of it manually.
</p>
-<p>Another prominent and widely spread mistake is to write your own
-language with a capital letter in the list of translations when
-languages are written beginning with a small letter according to your
-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>Subsequent migrations to newer HTML standards and newer look and feel
+of the website are supposed to happen semi-automatically, although
+this manual will be updated as needed.
</p>
<hr>
-<a name="Distribution-Terms"></a>
+<a name="SSI"></a>
<div class="header">
<p>
-Next: <a href="#Terminology" accesskey="n" rel="next">Terminology</a>,
Previous: <a href="#Capitalization" accesskey="p"
rel="previous">Capitalization</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>
+Next: <a href="#CSS" accesskey="n" rel="next">CSS</a>, Previous: <a
href="#Migrating" accesskey="p" rel="previous">Migrating</a>, Up: <a
href="#Translation-Process" accesskey="u" rel="up">Translation Process</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-<a name="Distribution-Terms-1"></a>
-<h3 class="section">5.7 Distribution Terms</h3>
+<a name="Summary-of-SSI-_0023includes"></a>
+<h3 class="section">4.10 Summary of SSI <code>#include</code>s</h3>
-<p>Most www.gnu.org articles are released under the terms of
-the Creative Commons Attribution-NoDerivs 3.0 United States license.
-The exact HTML for English pages to use is:
+<p>The GNU Project’s website uses SSI (Server Side Includes) to manage
some
+common parts that are the same in many of the articles. With the help
+of GNUN their handling should be behind the scenes, but for some of them
+manual intervention is needed. Here is a (possibly incomplete) list of
+the <code>#include</code>’s used:
</p>
-<div class="example">
-<pre class="example">This page is licensed under a <a
rel="license"
-href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
-Commons Attribution-NoDerivs 3.0 United States License</a>.
-</pre></div>
-
-<p>Pages in other languages should translate this notice, and should link
-to a translated version of the Creative Commons license “deed” if
it’s
-available. Creative Commons provides standard text for this in all the
-languages they support, and we should use that wording whenever
-possible. To do that, follow these steps:
+<dl compact="compact">
+<dt><samp>server/banner.html</samp></dt>
+<dd><p>This file contains only <code>#include</code> directives, so the
+“translation” should be identical, with filenames modified to have
the
+<var>lang</var> extension.
</p>
-<ul>
-<li> Check at the bottom of the English deed page to see the list of
-languages they support. Follow the link the language that you want a
-translation for, if available.
-
-</li><li> Follow the “Use this license for your own work” link
near the bottom
-of the translated deed page—it’s in distinct yellow text.
-
-</li><li> The textarea on that page provides standard HTML. Note that
we’re not
-using the graphic, just the text.
-
-</li></ul>
-
-<p>For example, here’s the text they provide for Dutch:
+</dd>
+<dt><samp>server/body-include-1.html</samp></dt>
+<dd><p>Contains the top menu with useful “skip to” links.
+</p>
+</dd>
+<dt><samp>server/body-include-2.html</samp></dt>
+<dd><p>This is the file containing the menus, the FSF widget, and any visible
+announcements made from time to time. If a string gets “fuzzy” or
+“new” here, it will appear in English in all translations, until
+<samp>server/po/body-include-2.<var>lang</var>.po</samp> is updated. Note that
+some validation errors originate from an error in
+<samp>server/body-include-2.<var>lang</var>.html</samp> or some other template
+file.
+</p>
+</dd>
+<dt><samp>server/bottom-notes.html</samp></dt>
+<dd><p>A link to the FSF page explaining how to report possible copyright
+infringements.
+</p>
+</dd>
+<dt><samp>server/footer-text.html</samp></dt>
+<dd><p>This is a very short file currently containing the “back to
top” link.
+Also translatable via GNUN.
+</p>
+</dd>
+<dt><samp>server/header.html</samp></dt>
+<dd><p>The declaration that is included in literally every file. It is
+maintained manually, as it does not make much sense to put it under
+GNUN’s control (there are no translatable strings). Remember to specify
+the proper <code>xml:lang</code> and <code>lang</code> attributes, and for RTL
+languages, the <code>dir</code> attribute. For example, the file
+<samp>header.ar.html</samp> should contain this line:
</p>
<div class="example">
-<pre class="example">Dit werk is gelicenseerd onder een <a
rel="license"
-href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.nl">
-Creative Commons Naamsvermelding-GeenAfgeleideWerken 3.0 Verenigde
-Staten licentie</a>
+<pre class="example"><html xmlns="http://www.w3.org/1999/xhtml"
xml:lang="ar" lang="ar"
+ dir="rtl">
</pre></div>
-<p>Note that the link in this text is changed to point directly to the
-Dutch language deed. We should always link to a copy of the license
-deed that’s in the same language as the page itself.
+</dd>
+<dt><samp>server/head-include-1.html</samp></dt>
+<dd><p>This file (included from <samp>server/header.html</samp>) is very
important:
+the encoding is defined here. Note that it is applicable for all
+translations, so it is not possible to have different articles in
+different encodings. Even if a specific PO file is deliberately encoded
+in another encoding, the generated HTML will contain the encoding
+declared in the <code><meta></code> element at
+<samp>server/head-include-1.<var>lang</var>.html</samp>, so browsers will obey
it.
</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>The encoding should be UTF-8. This is required because the English text
+in the articles serves as a replacement of the translation when the latter
+is not complete, and because all translated pages share automatically
+generated lists of translations.
+</p>
+</dd>
+<dt><samp>server/html5-header.html</samp></dt>
+<dd><p>This file is included in newer pages using some entities introduced
+in HTML5 draft. We have to distinguish those pages since some features
+of HTML4 were rejected in HTML5, and our old pages don’t validate
+as HTML5.
+</p>
+</dd>
+<dt><samp>server/html5-head-include-1.html</samp></dt>
+<dd><p>Likewise, this file replaces head-include-1.html for HTML5 pages.
+</p>
+</dd>
+<dt><samp>server/head-include-2.html</samp></dt>
+<dd><p>Imports the standard CSS, which can be overridden. See <a
href="#CSS">CSS</a>.
+</p>
+</dd>
+<dt><samp>server/footer.html</samp></dt>
+<dd><p>This is a very short and simple file (at least at the time of writing),
+containing another <code>#include</code> directive. It is maintained
+manually, so just add <var>lang</var> to the filename, in order the localized
+<samp>footer-text.<var>lang</var>.html</samp> to be included.
+</p>
+</dd>
+<dt><samp>server/outdated.html</samp></dt>
+<dd><p>This file is automatically included in outdated translations. It
+contains respective message with links to the English file and
+to a generated difference of the current revision of the English
+file against the most recent revision that has a complete translation.
+It is only included in articles affected by “grace period” because
+in those cases the outdated passages are replaced with English text,
+and it is evident without any notices that there is no complete
+and up to date translation.
+</p>
+</dd>
+<dt><samp>server/skip-translations.html</samp></dt>
+<dd><p>The text for a link to the end of the autogenerated list of
+translations.
+</p>
+</dd>
+<dt><samp>server/top-addendum.html</samp></dt>
+<dd><p>The text saying that the page is a translation.
+</p>
+</dd>
+<dt><samp>translations.include</samp></dt>
+<dd><p>The list of translations for the homepage (and only the homepage). It
+is maintained manually; in order the link to a translation to appear on
+all of the homepages, it has to be present here.
+</p>
+</dd>
+<dt><samp>licenses/gpl-3.0-body.html</samp></dt>
+<dt><samp>licenses/fdl-1.3-body.html</samp></dt>
+<dt><samp>…</samp></dt>
+<dd><p>Some of the licenses have the text of the license itself separated in
+another file. This serves two purposes: 1) to provide a
“standalone”
+HTML version of the license without the gnu.org style; 2) to prevent
+strings sneaking in the <samp>.pot</samp> files, as licenses have only
+unofficial translations, hosted elsewhere. Nothing special should be
+done about these SSI directives; the files generated by GNUN include
+them verbatim as they should not be translated.
+</p>
+</dd>
+<dt><samp>server/sidebar*.html</samp></dt>
+<dd><p>These files are deprecated—they are remnants from an older design
that
+lived shortly in the middle between the old classic design and the
+current one. If all translations are successfully migrated and none of
+them includes such files, you should delete them. You can use
+<code>grep</code> to check this.
+</p></dd>
+</dl>
+
+<p>The files
</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
-States</em> license, and <em>not</em> a different port like CC BY-ND 3.0
-Japan. This is because there are substantive differences between the way
-different ports handle moral rights issues, and we prefer the specific
-terms that are in the United States license.
+<ul class="no-bullet">
+<li>- <samp>header.html</samp>
+</li><li>- <samp>head-include-1.html</samp>
+</li><li>- <samp>html5-header.html</samp>
+</li><li>- <samp>html5-head-include-1.html</samp>
+</li><li>- <samp>head-include-2.html</samp>
+</li><li>- <samp>banner.html</samp>
+</li><li>- <samp>body-include-1.html</samp>
+</li><li>- <samp>body-include-2.html</samp>
+</li><li>- <samp>bottom-notes.html</samp>
+</li><li>- <samp>footer.html</samp>
+</li><li>- <samp>footer-text.html</samp>
+</li><li>- <samp>skip-translations.html</samp>
+</li></ul>
+
+<p>in the <samp>server</samp> sub-directory are what webmasters call “the
+server templates”. These files are included in almost every article,
+translated or not. They are somewhat important, as an error made in
+translating them propagates everywhere. The server templates, the
+homepages, and whatsnew (a.k.a. “GNU News”) are being rebuilt by
+GNUN whenever there is a change in the original English files; the
+<code>GRACE</code> variable has no effect for them. See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#Runtime-Variables";>Runtime
+Variables</a> in <cite>The GNUnited Nations Manual</cite>.
</p>
<hr>
-<a name="Terminology"></a>
+<a name="CSS"></a>
<div class="header">
<p>
-Previous: <a href="#Distribution-Terms" accesskey="p"
rel="previous">Distribution Terms</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>
+Previous: <a href="#SSI" accesskey="p" rel="previous">SSI</a>, Up: <a
href="#Translation-Process" accesskey="u" rel="up">Translation Process</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-<a name="Language_002dspecific-Terminology"></a>
-<h3 class="section">5.8 Language-specific Terminology</h3>
+<a name="How-to-Use-Custom-CSS"></a>
+<h3 class="section">4.11 How to Use Custom CSS</h3>
-<p>This is a very important topic, not yet covered by this manual.
+<p>The CSS file <samp>layout.css</samp> gets included (with three other CSS
files)
+in almost all the English articles through
+<samp>server/head-include-2.<var>lang</var>.html</samp>. However, sometimes
this
+style isn’t quite right for translations—many languages have much
+longer expressions, and that is natural. To include your own CSS,
+create a file <samp>style.<var>lang</var>.css</samp> and add it <em>after</em>
the
+directive to include <samp>server/head-include-2.<var>lang</var>.html</samp>
and
+<em>before</em> the closing <code></head></code> tag in
+<samp>server/banner.<var>lang</var>.html</samp>, i.e.
</p>
-<hr>
-<a name="Summary"></a>
-<div class="header">
-<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>
+<div class="example">
+<pre class="example"><!-- start of banner.bg.html -->
+<!--#include virtual="/server/head-include-2.bg.html" -->
+<link rel="stylesheet" href="/style.bg.css"
media="screen" />
+</head>
+</pre></div>
-<p>In general, it is expected that all participants in the translation
-process apply common sense for all of the decisions (important or not)
-they are going to take in their capacity as a manager, team leader, or
-contributing member. Certainly, many decisions are not easy, and
-require some thought.
+<p>Override only what is necessary and looks broken in your language; do
+not invent your own style. This is important for the consistency of the
+gnu.org website. A typical language-specific
+<samp>style.<var>lang</var>.css</samp> file looks like this:
</p>
-<p>This manual is a work in progress—it is not set in stone, and it
-will never be finished—the ultimate goal is to constantly improve
-the translation process, and as a consequence, the documentation.
-Every participant in the process should be free to suggest
-modifications to the current procedures and suggestions how to improve
-the current state of affairs. Ideally, they should be accompanied
-with patches to the Texinfo source, but that’s not mandatory. In any
-event, please write to <a
href="mailto:address@hidden";>address@hidden</a>—the goal
-of this list is precisely to discuss improvements of the translation
-process.
+<div class="example">
+<pre class="example">.inner { max-width: 65em; }
+
+#logo{background:url(/graphics/topbanner.bg.png) no-repeat;}
+#fssbox {font-size: 50%;}
+</pre></div>
+
+<p>This widens the menu and the area where the articles are displayed
+(because the menu entries are <em>much</em> longer than the English
+equivalents when translated), includes a localized logo, and makes the
+font size for the FSF widget twice smaller (because in this language,
+the translations are almost twice longer and displayed truncated, which
+is undesirable).
+</p>
+<p>When creating your own <samp>style.<var>lang</var>.css</samp>, don’t
forget to
+include the license notice from the <samp>layout.css</samp>, with a short
+comment.
+</p>
+<p>If using the default CSS style for translations does not give the
+expected good results, or there are other problems (significant or not)
+that obstruct reading and/or worsen the look from aesthetic point of
+view, please write to <a href="mailto:address@hidden";>address@hidden</a> with
a description of
+the issue. If there are several unrelated problems, send separate
+messages with appropriate explanation (which may include a demonstration
+of the bug, such as a screenshot).
</p>
<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top">• <a href="#Mailing-Lists"
accesskey="1">Mailing Lists</a>:</td><td> </td><td align="left"
valign="top">Summary of mailing lists.
+<tr><td align="left" valign="top">• <a href="#topbanner"
accesskey="1">topbanner</a>:</td><td> </td><td align="left"
valign="top">How to localize the topbanner image.
</td></tr>
-<tr><td align="left" valign="top">• <a href="#Savannah-Projects"
accesskey="2">Savannah Projects</a>:</td><td> </td><td align="left"
valign="top">Projects’ membership.
+<tr><td align="left" valign="top">• <a href="#RTL"
accesskey="2">RTL</a>:</td><td> </td><td align="left"
valign="top">Special notes about RTL languages.
</td></tr>
</table>
<hr>
-<a name="Mailing-Lists"></a>
+<a name="topbanner"></a>
<div class="header">
<p>
-Next: <a href="#Savannah-Projects" accesskey="n" rel="next">Savannah
Projects</a>, Up: <a href="#Summary" accesskey="u" rel="up">Summary</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</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="Related-Mailing-Lists"></a>
-<h3 class="section">6.1 Related Mailing Lists</h3>
+<a name="Localizing-the-topbanner-Image"></a>
+<h4 class="subsection">4.11.1 Localizing the <samp>topbanner</samp> Image</h4>
-<p>Here is a short summary of the mailing lists relevant to the translation
-process, and a brief description about how they relate to the various
-participants in the process.
-</p>
-<dl compact="compact">
-<dt><a href="mailto:address@hidden";>address@hidden</a></dt>
-<dd><p>The basic discussion list of the GNU Webmasters. All team leaders are
-required to subscribe.
-</p>
-<p>This is a private mailing list.
-</p>
-</dd>
-<dt><a href="mailto:address@hidden";>address@hidden</a></dt>
-<dd><p>Commits to the ‘<samp>www</samp>’ 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 delivery can
-be disabled personally.
-</p>
-<p>This is a public mailing list, so everyone can subscribe and review the
-archives. The ‘<samp>www</samp>’ CVS repository is also public.
-</p>
-</dd>
-<dt><a href="mailto:address@hidden";>address@hidden</a></dt>
-<dd><p>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 in general
-policies for translations are also announced and discussed here.
-</p>
-<p>This is a private mailing list.
-</p>
-</dd>
-<dt><a href="mailto:address@hidden";>address@hidden</a></dt>
-<dd><p>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 announcements,
-subscribe to the ‘<samp>gnun</samp>’ topic via Mailman’s
user interface.
-Likewise, if you want to receive only <em>What’s New</em> updates,
-subscribe to the ‘<samp>whatsnew</samp>’ topic.
-</p>
-<p>Automatic announcements for new gnu.org translations (provided they’re
-handled by GNUN) are also delivered here. There are separate
-‘<samp><var>lang</var>-ann</samp>’ topics for every GNUN-aware
language, so it is a
-good idea to advertise this capability widely among your local
-community. For example, if a reader wants to be informed only about new
-Spanish translations, she can just subscribe to the
‘<samp>es-ann</samp>’
-mailing list topic.
-</p>
-<p>This is a public mailing list.
-</p>
-</dd>
-<dt><a href="mailto:address@hidden";>address@hidden</a></dt>
-<dd><p>All development of GNUN happens here. Commits to the
‘<samp>trans-coord</samp>’
-repository are also sent to this list.
+<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:
</p>
-<p>This is a public list, and <a
href="mailto:address@hidden";>address@hidden</a> is an alias.
-</p></dd>
-</dl>
+<ol>
+<li> Copy <samp>graphics/topbanner.svg</samp> as
+<samp>graphics/topbanner.<var>lang</var>.svg</samp> where <var>lang</var> is
the
+language code, as usual. Edit the file with Inkscape or with a plain
+text editor such as GNU Emacs, translating “GNU Operating System”.
+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="DOCF8" href="#FOOT8"><sup>8</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,
+namely:
+
+<div class="example">
+<pre
class="example">#logo{background:url(/graphics/topbanner.<var>lang</var>.png)
no-repeat;}
+</pre></div>
+
+</li><li> If not done already for other reasons, update
+<samp>banner.<var>lang</var>.html</samp> to include the language specific
+<samp>style.<var>lang</var>.css</samp>. See <a href="#CSS">CSS</a>.
+</li></ol>
+<p>If you feel uncomfortable manipulating images—don’t despair!
Send a
+plea for help to <a href="mailto:address@hidden";>address@hidden</a>, some
people would
+be happy to help you. Failing that, write to
+<a href="mailto:address@hidden";>address@hidden</a>.
+</p>
<hr>
-<a name="Savannah-Projects"></a>
+<a name="RTL"></a>
<div class="header">
<p>
-Previous: <a href="#Mailing-Lists" accesskey="p" rel="previous">Mailing
Lists</a>, Up: <a href="#Summary" accesskey="u" rel="up">Summary</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
+Previous: <a href="#topbanner" accesskey="p" rel="previous">topbanner</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="Savannah-Projects-Membership"></a>
-<h3 class="section">6.2 Savannah Projects Membership</h3>
+<a name="Specific-Issues-Related-to-RTL"></a>
+<h4 class="subsection">4.11.2 Specific Issues Related to RTL</h4>
-<p>Participants in the www.gnu.org translations process normally have to be
-members of the following Savannah projects, depending on the case:
-</p>
-<dl compact="compact">
-<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 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 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>
-<dd><p>An organizational project especially created for co-ordination and
-improvement of the translation process. All team leaders are required
-to be members, as bugs reported to <a
href="mailto:address@hidden";>address@hidden</a> are
-often redirected to the ‘<samp>trans-coord</samp>’
‘<samp>Bugs</samp>’ tracker.
+<p>Unfortunately, the <a href="http://gnu.org";>http://gnu.org</a> website does
not have excellent
+support for RTL (right-to-left) languages, although best efforts are
+made. If your language is in this category, make sure to:
</p>
-<p>The admins of this project are the GNU Web Translation Managers.
+<ul>
+<li> Set the attribute <code>dir="rtl"</code> in the
<code>html</code> element at
+<samp>server/header.<var>lang</var>.html</samp>.
+
+</li><li> You <em>must</em> have a custom CSS to override some of the
pre-defined
+values. See <samp>style.ar.css</samp> and <samp>style.fa.css</samp> to
understand
+how these two languages solve some of the problems. See <a
href="#CSS">CSS</a>.
+</li></ul>
+
+<p><strong>Important:</strong> Some articles contain their own
<code><style></code>
+redefinitions, or style attributes in the form <code><p
+style="…"></code>. In such situations, it is quite
possible that the
+general language-specific CSS does not help, and the translation of this
+specific article does not look correct. Please write to
+<a href="mailto:address@hidden";>address@hidden</a>; if you have a working
solution that works
+for both cases—so much the better. For general issues that affect
+your language and require a general solution, write to
+<a href="mailto:address@hidden";>address@hidden</a> as well, precisely
describing the problem.
</p>
-</dd>
-<dt>‘<samp>www-<var>lang</var></samp>’</dt>
-<dd><p>All translation team leaders of the language <var>lang</var> should be
-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>
<hr>
<a name="Copying-This-Manual"></a>
<div class="header">
<p>
-Previous: <a href="#Summary" accesskey="p" rel="previous">Summary</a>, Up: <a
href="#Top" accesskey="u" rel="up">Top</a> [<a href="#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
+Previous: <a href="#Translation-Process" accesskey="p"
rel="previous">Translation Process</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="GNU-Free-Documentation-License"></a>
<h2 class="appendix">Appendix A GNU Free Documentation License</h2>
@@ -2701,16 +2674,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>
+<h3><a name="FOOT7" href="#DOCF7">(7)</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="FOOT8" href="#DOCF8">(8)</a></h3>
+<p>This
+advice applies to all new files, of course.</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.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
Binary files /tmp/cvs0tc5So and /tmp/cvsFeBPg0 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.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
Binary files /tmp/cvshFXb9m and /tmp/cvsIicdyY 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.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
Binary files /tmp/cvs1r7VMn and /tmp/cvsamAadZ differ
Index: web-trans/web-trans.pdf
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.pdf,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
Binary files /tmp/cvsdSLgIq and /tmp/cvsV56jc2 differ
Index: web-trans/web-trans.ps.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.ps.gz,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
Binary files /tmp/cvskdijxt and /tmp/cvsAbVL44 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.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
Binary files /tmp/cvsygTacs and /tmp/cvsc8RtL3 differ
Index: web-trans/web-trans.txt
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.txt,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- web-trans/web-trans.txt 31 Jan 2013 08:47:35 -0000 1.13
+++ web-trans/web-trans.txt 1 Feb 2013 06:06:16 -0000 1.14
@@ -13,41 +13,39 @@
3.3.1 How to Track Tasks and Bugs Using Savannah
3.3.2 How to Proceed with Unreviewed Translations
3.4 CVS Commits and Best Practices
- 3.5 Working with PO Files
- 3.5.1 Web-based Systems
- 3.6 Taking Advantage of Savannah
- 3.6.1 Managing Members
- 3.6.2 Homepage of the Team
- 3.6.3 Support Tracker
- 3.6.4 Tasks Tracker
- 3.6.5 Bugs Tracker
- 3.6.6 News Tracker
- 3.6.7 Managing Mailing Lists
- 3.6.8 Version Control Systems
- 3.7 Promoting Members as Co-leaders
- 3.8 Reporting Team Status
- 3.9 How to Retire Painlessly
-4 'trans-coord' Admins
-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.2 Specific Issues Related to RTL
- 5.4 What to Translate
- 5.5 Keeping Translations Current
- 5.6 When to CAPITALIZE
- 5.7 Distribution Terms
- 5.8 Language-specific Terminology
-6 Overview of the Translation Process
- 6.1 Related Mailing Lists
- 6.2 Savannah Projects Membership
+ 3.5 Taking Advantage of Savannah
+ 3.5.1 Managing Members
+ 3.5.2 Homepage of the Team
+ 3.5.3 Support Tracker
+ 3.5.4 Tasks Tracker
+ 3.5.5 Bugs Tracker
+ 3.5.6 News Tracker
+ 3.5.7 Managing Mailing Lists
+ 3.5.8 Version Control Systems
+ 3.6 Promoting Members as Co-leaders
+ 3.7 Reporting Team Status
+ 3.8 How to Retire Painlessly
+4 Translation Process
+ 4.1 What to Translate
+ 4.2 Keeping Translations Current
+ 4.3 When to CAPITALIZE
+ 4.4 Distribution Terms
+ 4.5 Language-specific Terminology
+ 4.6 Related Mailing Lists
+ 4.7 Savannah Projects Membership
+ 4.8 Working with PO Files
+ 4.8.1 Web-based Systems
+ 4.9 Migration to the New Style
+ 4.10 Summary of SSI '#include's
+ 4.11 How to Use Custom CSS
+ 4.11.1 Localizing the 'topbanner' Image
+ 4.11.2 Specific Issues Related to RTL
Appendix A GNU Free Documentation License
GNU Web Translators Manual
**************************
This manual is a guide for the GNU Web Translators.
-Last updated on 17.01.2013, for GNUnited Nations version 0.7.
+Last updated on 1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software Foundation,
Inc.
@@ -95,19 +93,17 @@
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, who are responsible for
+the respective team; they are also referred to as leaders or (when
+multiple in a single team) co-leaders. The co-ordinators participate in
+the Savannah 'trans-coord' organizational project, which is managed by
+the GNU Web Translation Managers (also known as Translation Managers or
+web-translators). 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,
-*note Leaders::. The chapter about the 'trans-coord' administrators
-(a.k.a. "GNU Translation Managers") describes all the responsibilities
-and procedures involved in performing this duty. *Note Translation
-Managers::.
+*note Leaders::.
2 Team Members
**************
@@ -167,7 +163,7 @@
two weeks), please write to <address@hidden>.
For general information about the translation process, *note
-Translation Tips::.
+Translation Process::.
2.2 How to Submit a Translation
===============================
@@ -481,6 +477,14 @@
- www-discuss
+ 10. When you are appointed the admin of the new project, please edit
+ its configuration; in particular, write its description, create a
+ mailing list (don't forget to subscribe yourself!), optionally add
+ a home page using Web CVS repository.
+
+ If you are taking over an orphaned team, Translation Managers will
+ make you the owner of its mailing lists (if any).
+
The whole process should not take more than two weeks or maximum a
month--if this period turns out to be longer, it is an indication that
you do not have the required time and resources for this job, or
@@ -753,86 +757,7 @@
systems--we don't dictate what OS people use, but we can at least
prevent this technical kind of damage.
-3.5 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.5.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.6 Taking Advantage of Savannah
+3.5 Taking Advantage of Savannah
================================
Every translation team should have a project in Savannah. There are
@@ -877,7 +802,7 @@
facilities provided by Savannah. It is not mandatory to follow them,
they are just suggestions.
-3.6.1 Managing Members
+3.5.1 Managing Members
----------------------
You should add active translators as members of the translation team,
@@ -898,7 +823,7 @@
the total number of members, and they appear separately on 'View
Members'.
-3.6.2 Homepage of the Team
+3.5.2 Homepage of the Team
--------------------------
Every Savannah project has a Web repository, which is, for technical and
@@ -922,7 +847,7 @@
These locations are deprecated, and the contents will be removed without
warning.
-3.6.3 Support Tracker
+3.5.3 Support Tracker
---------------------
This tracker is supposed to be related to things about the _project
@@ -931,7 +856,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.6.4 Tasks Tracker
+3.5.4 Tasks Tracker
-------------------
This is a way to manage all sorts of tasks. They appear in the personal
@@ -945,7 +870,7 @@
Feel free to organize the 'Tasks' management as you see fit.
-3.6.5 Bugs Tracker
+3.5.5 Bugs Tracker
------------------
The 'Bugs' tracker is designed for tracking bugs. You can use for
@@ -960,7 +885,7 @@
(who is supposed to be a 'www-LANG' project member), if you have
such policy.
-3.6.6 News Tracker
+3.5.6 News Tracker
------------------
That is a way to inform newcomers and interested people (who visit the
@@ -975,13 +900,14 @@
perfectly OK to announce it here. Some teams use it to announce new
translations, which is also fine.
-3.6.7 Managing Mailing Lists
+3.5.7 Managing Mailing Lists
----------------------------
Every team should have a mailing list on lists.gnu.org and use it for
internal communications. All active translators should be on the list.
The list owner should be the co-ordinator of the team. The name of the
-list should begin with 'www-LANG-'.
+list should begin with 'www-LANG-'. The team co-ordinator is in the
+position to decide about the settings like being public or private.
The list will make it possible for the GNU project to contact the
team when the co-ordinator disappears; its archive will also give access
@@ -994,7 +920,7 @@
You can redirect all messages generated by the trackers to any list.
-3.6.8 Version Control Systems
+3.5.8 Version Control Systems
-----------------------------
An easy way to keep up with changes in the original articles and to
@@ -1004,7 +930,7 @@
It is also convenient to update the translation (merge any changes from
the original) while it is still under review.
- *Note (gnun)PO Files and Team::, for more information.
+ *Note (gnun)Team's Repository::, for more information.
*Remember:* A choice of a particular VCS is a sensitive matter--some
modern ones provide compelling features, but they also bump the barrier
@@ -1012,7 +938,7 @@
maintenance--if it eases only you, project members just won't use it so
that won't be a net win.
-3.7 Promoting Members as Co-leaders
+3.6 Promoting Members as Co-leaders
===================================
When the team grows large and it becomes hard for a single person to
@@ -1035,7 +961,7 @@
'README.translations.html' yourself; this is a final formality step to
be performed by the Translation Managers.
-3.8 Reporting Team Status
+3.7 Reporting Team Status
=========================
Team leaders must send an annual report about the status of the team. A
@@ -1074,7 +1000,7 @@
If you do not wish to share some information that is in the report,
please send it to <address@hidden>.
-3.9 How to Retire Painlessly
+3.8 How to Retire Painlessly
============================
When you feel you don't have the energy to manage the team successfully,
@@ -1089,387 +1015,136 @@
Co-leaders::) and retire completely when she is absolutely ready to
proceed without your further help and advice.
-4 'trans-coord' Admins
-**********************
+4 Translation Process
+*********************
-This chapter is not yet written. The current admins know what to do,
-hopefully.
+In general, it is expected that all participants in the translation
+process apply common sense for all of the decisions (important or not)
+they are going to take in their capacity as a manager, team leader, or
+contributing member. Certainly, many decisions are not easy, and
+require some thought.
-5 Details about the Translation Process
-***************************************
+ This manual is a work in progress--it is not set in stone, and it
+will never be finished--the ultimate goal is to constantly improve the
+translation process, and as a consequence, the documentation. Every
+participant in the process should be free to suggest modifications to
+the current procedures and suggestions how to improve the current state
+of affairs. Ideally, they should be accompanied with patches to the
+Texinfo source, but that's not mandatory. In any event, please write to
+<address@hidden>--the goal of this list is precisely to
+discuss improvements of the translation process.
-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
-become well known as time goes by; however, practice shows that it is
-difficult to figure them out at once.
-
- Some limitations and oddities are just historical remnants from old
-habits and previous incarnations of old (inefficient) translation and
-webmastering processes. Others are outright deficiencies (i.e.
-"bugs"), but no one has stepped in to correct them so far.
+4.1 What to Translate
+=====================
-5.1 Migration to the New Style
-==============================
+The page
+<http://www.gnu.org/server/standards/translations/priorities.html> lists
+the most important essays to translate. In general, articles in the
+directories 'philosophy', 'gnu', 'education', 'distros', 'copyleft' and
+'licenses' are important. The others may be deferred for a time when a
+team completes most of the important translations, or they can be
+translated as a "rest"--in translators' parlance this means doing
+something in between which is typically easier to handle.
-Migration to the new style should be straightforward, and this is one of
-the problems GNUN set out to solve. If you have to migrate old-style
-translations, *note (gnun)Migrating::. If the old translation is HTML
-2.0 (or 3.2), you still have to take care about the inner markup.
-Overall, it is substantially easier than doing all of it manually.
+ You can find links automatic reports about current status of
+translations of all active teams sorted by their priority in
+<http://www.gnu.org/software/gnun/reports/>. If the page for your team
+is missing there, please ask <address@hidden> to add it to the
+cron job.
- Subsequent migrations to newer HTML standards and newer look and feel
-of the website are supposed to happen semi-automatically, although this
-manual will be updated as needed.
+ _Do not_ translate articles under these directories:
-5.2 Summary of SSI '#include's
-==============================
+'software/PKG/'
+ These pages are maintained by the respective PKG maintainers. GNUN
+ does not support them for the time being, as they reside in
+ separate repositories. The procedures for contributing
+ translations of such articles are not yet settled.
-The GNU Project's website uses SSI (Server Side Includes) to manage some
-common parts that are the same in many of the articles. With the help
-of GNUN their handling should be behind the scenes, but for some of them
-manual intervention is needed. Here is a (possibly incomplete) list of
-the '#include''s used:
+'brave-gnu-world'
+ The Brave GNU World initiative has been abandoned long time ago,
+ and it's in a separate repository--thus not supported by the
+ automatic GNUN build job.
-'server/banner.html'
- This file contains only '#include' directives, so the "translation"
- should be identical, with filenames modified to have the LANG
- extension.
+'home.html'
+ There is no problem to translate this page, but don't make the
+ mistake to pick it up as your first translation. It is modified
+ often, sometimes intensively, and only active team members should
+ take that road.
-'server/body-include-1.html'
- Contains the top menu with useful "skip to" links.
+'server/whatsnew.html'
+ This is "What's New", also known as "GNU's Flashes", also known as
+ "GNU News". It is deprecated since quite some time and translating
+ it is discouraged.
-'server/body-include-2.html'
- This is the file containing the menus, the FSF widget, and any
- visible announcements made from time to time. If a string gets
- "fuzzy" or "new" here, it will appear in English in all
- translations, until 'server/po/body-include-2.LANG.po' is updated.
- Note that some validation errors originate from an error in
- 'server/body-include-2.LANG.html' or some other template file.
+4.2 Keeping Translations Current
+================================
-'server/bottom-notes.html'
- A link to the FSF page explaining how to report possible copyright
- infringements.
+It is very important to keep existing translations up-to-date with the
+respective English originals. This task should be higher priority than
+translating new articles. We developped different means to automate the
+process of tracking outdated translations.
-'server/footer-text.html'
- This is a very short file currently containing the "back to top"
- link. Also translatable via GNUN.
+ * GNUN's 'report' rule can help you to identify precisely which
+ articles need updating; *note (gnun)report::. There is a monthly
+ cron job which sends the output of this rule to each team as
+ requested by their leaders. If you want the addresses changed,
+ please write to <address@hidden>.
-'server/header.html'
- The declaration that is included in literally every file. It is
- maintained manually, as it does not make much sense to put it under
- GNUN's control (there are no translatable strings). Remember to
- specify the proper 'xml:lang' and 'lang' attributes, and for RTL
- languages, the 'dir' attribute. For example, the file
- 'header.ar.html' should contain this line:
+ * The 'gnun-report' script produces a HTML page listing detailed
+ status of translations; *note (gnun)gnun-report::. A cron job
+ commits updated reports for all active teams to GNUN project web
+ repository, typically twice an hour. The links to those reports
+ are provided on <http://gnu.org/software/gnun/reports/>.
- <html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="ar" lang="ar"
- dir="rtl">
+ * GNUmakefile.team provides a more detailed 'report' target: unlike
+ the output of the previous tools, it analyzes the status of files
+ in team's repository as well as of those in 'www' repository; *note
+ (gnun)report in GNUmakefile.team::.
-'server/head-include-1.html'
- This file (included from 'server/header.html') is very important:
- the encoding is defined here. Note that it is applicable for all
- translations, so it is not possible to have different articles in
- different encodings. Even if a specific PO file is deliberately
- encoded in another encoding, the generated HTML will contain the
- encoding declared in the '<meta>' element at
- 'server/head-include-1.LANG.html', so browsers will obey it.
+ * GNUmakefile.team also has a means to send a further detalized
+ reports to specific translators; *note (gnun)notify in
+ GNUmakefile.team::. The notification facility takes the output of
+ the 'report' target, adds the URLs of relevant files, and the
+ results are sent with attached HTML files of team's-against-'www'
+ differences to the translators who requested tracking particular
+ files.
- The encoding should be UTF-8. This is required because the English
- text in the articles serves as a replacement of the translation
- when the latter is not complete, and because all translated pages
- share automatically generated lists of translations.
+ The feature is supposed to be invoked via a cron job; such jobs
+ already run for some teams on our server. If you'd like GNU Web
+ Translation Managers to setup a job for your team, please write to
+ <address@hidden>.
-'server/html5-header.html'
- This file is included in newer pages using some entities introduced
- in HTML5 draft. We have to distinguish those pages since some
- features of HTML4 were rejected in HTML5, and our old pages don't
- validate as HTML5.
+4.3 When to CAPITALIZE
+======================
-'server/html5-head-include-1.html'
- Likewise, this file replaces head-include-1.html for HTML5 pages.
+The English language has some rules for capitalization of titles,
+chapters, acronym expansions and the like. These rules are neither
+strict nor uniform, although the gnu.org website strives to apply them
+consistently. They do not make sense for many other languages, but
+unfortunately, many translators _erroneously duplicate_ the
+capitalization in their translation.
-'server/head-include-2.html'
- Imports the standard CSS, which can be overridden. *Note CSS::.
+ Examples for common (and correct) English capitalization is the title
+of the article "Why Software Should Be Free" or "Free Software
+Foundation" (FSF). However, in languages that do not have such grammar
+rules it is wrong to write "Dlaczego Oprogramowanie Powinno Byc' Wolne"
+(Polish) or "Fondation Pour Le Logiciel Libre" (French).
-'server/footer.html'
- This is a very short and simple file (at least at the time of
- writing), containing another '#include' directive. It is
- maintained manually, so just add LANG to the filename, in order the
- localized 'footer-text.LANG.html' to be included.
+ Another prominent and widely spread mistake is to write your own
+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.
-'server/outdated.html'
- This file is automatically included in outdated translations. It
- contains respective message with links to the English file and to a
- generated difference of the current revision of the English file
- against the most recent revision that has a complete translation.
- It is only included in articles affected by "grace period" because
- in those cases the outdated passages are replaced with English
- text, and it is evident without any notices that there is no
- complete and up to date translation.
-
-'server/skip-translations.html'
- The text for a link to the end of the autogenerated list of
- translations.
-
-'server/top-addendum.html'
- The text saying that the page is a translation.
-
-'translations.include'
- The list of translations for the homepage (and only the homepage).
- It is maintained manually; in order the link to a translation to
- appear on all of the homepages, it has to be present here.
-
-'licenses/gpl-3.0-body.html'
-'licenses/fdl-1.3-body.html'
-'...'
- Some of the licenses have the text of the license itself separated
- in another file. This serves two purposes: 1) to provide a
- "standalone" HTML version of the license without the gnu.org style;
- 2) to prevent strings sneaking in the '.pot' files, as licenses
- have only unofficial translations, hosted elsewhere. Nothing
- special should be done about these SSI directives; the files
- generated by GNUN include them verbatim as they should not be
- translated.
-
-'server/sidebar*.html'
- These files are deprecated--they are remnants from an older design
- that lived shortly in the middle between the old classic design and
- the current one. If all translations are successfully migrated and
- none of them includes such files, you should delete them. You can
- use 'grep' to check this.
-
- The files
-
- - 'header.html'
- - 'head-include-1.html'
- - 'html5-header.html'
- - 'html5-head-include-1.html'
- - 'head-include-2.html'
- - 'banner.html'
- - 'body-include-1.html'
- - 'body-include-2.html'
- - 'bottom-notes.html'
- - 'footer.html'
- - 'footer-text.html'
- - 'skip-translations.html'
-
- in the 'server' sub-directory are what webmasters call "the server
-templates". These files are included in almost every article,
-translated or not. They are somewhat important, as an error made in
-translating them propagates everywhere. The server templates, the
-homepages, and whatsnew (a.k.a. "GNU News") are being rebuilt by GNUN
-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
-=========================
-
-The CSS file 'layout.css' gets included (with three other CSS files) in
-almost all the English articles through
-'server/head-include-2.LANG.html'. However, sometimes this style isn't
-quite right for translations--many languages have much longer
-expressions, and that is natural. To include your own CSS, create a
-file 'style.LANG.css' and add it _after_ the directive to include
-'server/head-include-2.LANG.html' and _before_ the closing '</head>' tag
-in 'server/banner.LANG.html', i.e.
-
- <!-- start of banner.bg.html -->
- <!--#include virtual="/server/head-include-2.bg.html" -->
- <link rel="stylesheet" href="/style.bg.css" media="screen" />
- </head>
-
- Override only what is necessary and looks broken in your language; do
-not invent your own style. This is important for the consistency of the
-gnu.org website. A typical language-specific 'style.LANG.css' file
-looks like this:
-
- .inner { max-width: 65em; }
-
- #logo{background:url(/graphics/topbanner.bg.png) no-repeat;}
- #fssbox {font-size: 50%;}
-
- This widens the menu and the area where the articles are displayed
-(because the menu entries are _much_ longer than the English equivalents
-when translated), includes a localized logo, and makes the font size for
-the FSF widget twice smaller (because in this language, the translations
-are almost twice longer and displayed truncated, which is undesirable).
-
- When creating your own 'style.LANG.css', don't forget to include the
-license notice from the 'layout.css', with a short comment.
-
- If using the default CSS style for translations does not give the
-expected good results, or there are other problems (significant or not)
-that obstruct reading and/or worsen the look from aesthetic point of
-view, please write to <address@hidden> with a description of the
-issue. If there are several unrelated problems, send separate messages
-with appropriate explanation (which may include a demonstration of the
-bug, such as a screenshot).
-
-5.3.1 Localizing the 'topbanner' Image
---------------------------------------
-
-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:
-
- 1. Copy 'graphics/topbanner.svg' as 'graphics/topbanner.LANG.svg'
- where LANG is the language code, as usual. Edit the file with
- Inkscape or with a plain text editor such as GNU Emacs, translating
- "GNU Operating System". Then with Inkscape, save the file as
- 'graphics/topbanner.LANG.png' (File -> Export Bitmap...). Then
- open the PNG image with the GIMP and flatten it (Image -> Flatten
- Image). Don't forget to save and 'cvs add' the files(1).
-
- 2. Create a 'style.LANG.css' at the toplevel directory, if it doesn't
- exist already. Normally, you would need only one line in it,
- namely:
-
- #logo{background:url(/graphics/topbanner.LANG.png) no-repeat;}
-
- 3. If not done already for other reasons, update 'banner.LANG.html' to
- include the language specific 'style.LANG.css'. *Note CSS::.
-
- If you feel uncomfortable manipulating images--don't despair! Send a
-plea for help to <address@hidden>, some people would be
-happy to help you. Failing that, write to <address@hidden>.
-
- ---------- Footnotes ----------
-
- (1) This advice applies to all new files, of course.
-
-5.3.2 Specific Issues Related to RTL
-------------------------------------
-
-Unfortunately, the <http://gnu.org> website does not have excellent
-support for RTL (right-to-left) languages, although best efforts are
-made. If your language is in this category, make sure to:
-
- * Set the attribute 'dir="rtl"' in the 'html' element at
- 'server/header.LANG.html'.
-
- * You _must_ have a custom CSS to override some of the pre-defined
- values. See 'style.ar.css' and 'style.fa.css' to understand how
- these two languages solve some of the problems. *Note CSS::.
-
- *Important:* Some articles contain their own '<style>' redefinitions,
-or style attributes in the form '<p style="...">'. In such situations,
-it is quite possible that the general language-specific CSS does not
-help, and the translation of this specific article does not look
-correct. Please write to <address@hidden>; if you have a working
-solution that works for both cases--so much the better. For general
-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
-=====================
-
-The article
-<http://www.gnu.org/server/standards/translations/priorities.html> lists
-the most important essays to translate. In general, articles in the
-directories 'philosophy', 'gnu', 'education', 'distros', 'copyleft' and
-'licenses' are important. The others may be deferred for a time when a
-team completes most of the important translations, or they can be
-translated as a "rest"--in translators' parlance this means doing
-something in between which is typically easier to handle.
-
- You can find links automatic reports about current status of
-translations of all active teams sorted by their priority in
-<http://www.gnu.org/software/gnun/reports/>. If the page for your team
-is missing there, please ask <address@hidden> to add it to the
-cron job.
-
- _Do not_ translate articles under these directories:
-
-'software/PKG/'
- These pages are maintained by the respective PKG maintainers. GNUN
- does not support them for the time being, as they reside in
- separate repositories. The procedures for contributing
- translations of such articles are not yet settled.
-
-'brave-gnu-world'
- The Brave GNU World initiative has been abandoned long time ago,
- and it's in a separate repository--thus not supported by the
- automatic GNUN build job.
-
-'home.html'
- There is no problem to translate this page, but don't make the
- mistake to pick it up as your first translation. It is modified
- often, sometimes intensively, and only active team members should
- take that road.
-
-'server/whatsnew.html'
- This is "What's New", also known as "GNU's Flashes", also known as
- "GNU News". It is deprecated since quite some time and translating
- it is discouraged.
-
-5.5 Keeping Translations Current
-================================
-
-It is very important to keep existing translations up-to-date with the
-respective English originals. This task should be higher priority than
-translating new articles. We developped different means to automate the
-process of tracking outdated translations.
-
- * GNUN's 'report' rule can help you to identify precisely which
- articles need updating; *note (gnun)report::. There is a monthly
- cron job which sends the output of this rule to each team as
- requested by their leaders. If you want the addresses changed,
- please write to <address@hidden>.
-
- * The 'gnun-report' script produces a HTML page listing detailed
- status of translations; *note (gnun)gnun-report::. A cron job
- commits updated reports for all active teams to GNUN project web
- repository, typically twice an hour. The links to those reports
- are provided on <http://gnu.org/software/gnun/reports/>.
-
- * GNUmakefile.team provides a more detailed 'report' target: unlike
- the output of the previous tools, it analyzes the status of files
- in team's repository as well as of those in 'www' repository; *note
- (gnun)report in GNUmakefile.team::.
-
- * GNUmakefile.team also has a means to send a further detalized
- reports to specific translators; *note (gnun)notify in
- GNUmakefile.team::. The notification facility takes the output of
- the 'report' target, adds the URLs of relevant files, and the
- results are sent with attached HTML files of team's-against-'www'
- differences to the translators who requested tracking particular
- files.
-
- The feature is supposed to be invoked via a cron job; such jobs
- already run for some teams on our server. If you'd like GNU Web
- Translation Managers to setup a job for your team, please write to
- <address@hidden>.
-
-5.6 When to CAPITALIZE
-======================
-
-The English language has some rules for capitalization of titles,
-chapters, acronym expansions and the like. These rules are neither
-strict nor uniform, although the gnu.org website strives to apply them
-consistently. They do not make sense for many other languages, but
-unfortunately, many translators _erroneously duplicate_ the
-capitalization in their translation.
-
- Examples for common (and correct) English capitalization is the title
-of the article "Why Software Should Be Free" or "Free Software
-Foundation" (FSF). However, in languages that do not have such grammar
-rules it is wrong to write "Dlaczego Oprogramowanie Powinno Byc' Wolne"
-(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 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 ----------
+ ---------- 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.7 Distribution Terms
+4.4 Distribution Terms
======================
Most www.gnu.org articles are released under the terms of the Creative
@@ -1522,32 +1197,16 @@
ports handle moral rights issues, and we prefer the specific terms that
are in the United States license.
-5.8 Language-specific Terminology
+4.5 Language-specific Terminology
=================================
This is a very important topic, not yet covered by this manual.
-6 Overview of the Translation Process
-*************************************
+ Some tips are given on
+<http://www.gnu.org/server/standards/README.translations.en.html>.
-In general, it is expected that all participants in the translation
-process apply common sense for all of the decisions (important or not)
-they are going to take in their capacity as a manager, team leader, or
-contributing member. Certainly, many decisions are not easy, and
-require some thought.
-
- This manual is a work in progress--it is not set in stone, and it
-will never be finished--the ultimate goal is to constantly improve the
-translation process, and as a consequence, the documentation. Every
-participant in the process should be free to suggest modifications to
-the current procedures and suggestions how to improve the current state
-of affairs. Ideally, they should be accompanied with patches to the
-Texinfo source, but that's not mandatory. In any event, please write to
-<address@hidden>--the goal of this list is precisely to
-discuss improvements of the translation process.
-
-6.1 Related Mailing Lists
-=========================
+4.6 Related Mailing Lists
+=========================
Here is a short summary of the mailing lists relevant to the translation
process, and a brief description about how they relate to the various
@@ -1601,7 +1260,10 @@
This is a public list, and <address@hidden> is an alias.
-6.2 Savannah Projects Membership
+ Every team should also use at least one mailing list on Savannah,
+*note Savannah Mailing Lists::.
+
+4.7 Savannah Projects Membership
================================
Participants in the www.gnu.org translations process normally have to be
@@ -1633,6 +1295,336 @@
of the project 'www-LANG'. The leaders may also appoint some other
members as 'www-LANG' admins for team's internal reasons.
+4.8 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.
+
+4.8.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.
+
+4.9 Migration to the New Style
+==============================
+
+Migration to the new style should be straightforward, and this is one of
+the problems GNUN set out to solve. If you have to migrate old-style
+translations, *note (gnun)Migrating::. If the old translation is HTML
+2.0 (or 3.2), you still have to take care about the inner markup.
+Overall, it is substantially easier than doing all of it manually.
+
+ Subsequent migrations to newer HTML standards and newer look and feel
+of the website are supposed to happen semi-automatically, although this
+manual will be updated as needed.
+
+4.10 Summary of SSI '#include's
+===============================
+
+The GNU Project's website uses SSI (Server Side Includes) to manage some
+common parts that are the same in many of the articles. With the help
+of GNUN their handling should be behind the scenes, but for some of them
+manual intervention is needed. Here is a (possibly incomplete) list of
+the '#include''s used:
+
+'server/banner.html'
+ This file contains only '#include' directives, so the "translation"
+ should be identical, with filenames modified to have the LANG
+ extension.
+
+'server/body-include-1.html'
+ Contains the top menu with useful "skip to" links.
+
+'server/body-include-2.html'
+ This is the file containing the menus, the FSF widget, and any
+ visible announcements made from time to time. If a string gets
+ "fuzzy" or "new" here, it will appear in English in all
+ translations, until 'server/po/body-include-2.LANG.po' is updated.
+ Note that some validation errors originate from an error in
+ 'server/body-include-2.LANG.html' or some other template file.
+
+'server/bottom-notes.html'
+ A link to the FSF page explaining how to report possible copyright
+ infringements.
+
+'server/footer-text.html'
+ This is a very short file currently containing the "back to top"
+ link. Also translatable via GNUN.
+
+'server/header.html'
+ The declaration that is included in literally every file. It is
+ maintained manually, as it does not make much sense to put it under
+ GNUN's control (there are no translatable strings). Remember to
+ specify the proper 'xml:lang' and 'lang' attributes, and for RTL
+ languages, the 'dir' attribute. For example, the file
+ 'header.ar.html' should contain this line:
+
+ <html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="ar" lang="ar"
+ dir="rtl">
+
+'server/head-include-1.html'
+ This file (included from 'server/header.html') is very important:
+ the encoding is defined here. Note that it is applicable for all
+ translations, so it is not possible to have different articles in
+ different encodings. Even if a specific PO file is deliberately
+ encoded in another encoding, the generated HTML will contain the
+ encoding declared in the '<meta>' element at
+ 'server/head-include-1.LANG.html', so browsers will obey it.
+
+ The encoding should be UTF-8. This is required because the English
+ text in the articles serves as a replacement of the translation
+ when the latter is not complete, and because all translated pages
+ share automatically generated lists of translations.
+
+'server/html5-header.html'
+ This file is included in newer pages using some entities introduced
+ in HTML5 draft. We have to distinguish those pages since some
+ features of HTML4 were rejected in HTML5, and our old pages don't
+ validate as HTML5.
+
+'server/html5-head-include-1.html'
+ Likewise, this file replaces head-include-1.html for HTML5 pages.
+
+'server/head-include-2.html'
+ Imports the standard CSS, which can be overridden. *Note CSS::.
+
+'server/footer.html'
+ This is a very short and simple file (at least at the time of
+ writing), containing another '#include' directive. It is
+ maintained manually, so just add LANG to the filename, in order the
+ localized 'footer-text.LANG.html' to be included.
+
+'server/outdated.html'
+ This file is automatically included in outdated translations. It
+ contains respective message with links to the English file and to a
+ generated difference of the current revision of the English file
+ against the most recent revision that has a complete translation.
+ It is only included in articles affected by "grace period" because
+ in those cases the outdated passages are replaced with English
+ text, and it is evident without any notices that there is no
+ complete and up to date translation.
+
+'server/skip-translations.html'
+ The text for a link to the end of the autogenerated list of
+ translations.
+
+'server/top-addendum.html'
+ The text saying that the page is a translation.
+
+'translations.include'
+ The list of translations for the homepage (and only the homepage).
+ It is maintained manually; in order the link to a translation to
+ appear on all of the homepages, it has to be present here.
+
+'licenses/gpl-3.0-body.html'
+'licenses/fdl-1.3-body.html'
+'...'
+ Some of the licenses have the text of the license itself separated
+ in another file. This serves two purposes: 1) to provide a
+ "standalone" HTML version of the license without the gnu.org style;
+ 2) to prevent strings sneaking in the '.pot' files, as licenses
+ have only unofficial translations, hosted elsewhere. Nothing
+ special should be done about these SSI directives; the files
+ generated by GNUN include them verbatim as they should not be
+ translated.
+
+'server/sidebar*.html'
+ These files are deprecated--they are remnants from an older design
+ that lived shortly in the middle between the old classic design and
+ the current one. If all translations are successfully migrated and
+ none of them includes such files, you should delete them. You can
+ use 'grep' to check this.
+
+ The files
+
+ - 'header.html'
+ - 'head-include-1.html'
+ - 'html5-header.html'
+ - 'html5-head-include-1.html'
+ - 'head-include-2.html'
+ - 'banner.html'
+ - 'body-include-1.html'
+ - 'body-include-2.html'
+ - 'bottom-notes.html'
+ - 'footer.html'
+ - 'footer-text.html'
+ - 'skip-translations.html'
+
+ in the 'server' sub-directory are what webmasters call "the server
+templates". These files are included in almost every article,
+translated or not. They are somewhat important, as an error made in
+translating them propagates everywhere. The server templates, the
+homepages, and whatsnew (a.k.a. "GNU News") are being rebuilt by GNUN
+whenever there is a change in the original English files; the 'GRACE'
+variable has no effect for them. *Note (gnun)Runtime Variables::.
+
+4.11 How to Use Custom CSS
+==========================
+
+The CSS file 'layout.css' gets included (with three other CSS files) in
+almost all the English articles through
+'server/head-include-2.LANG.html'. However, sometimes this style isn't
+quite right for translations--many languages have much longer
+expressions, and that is natural. To include your own CSS, create a
+file 'style.LANG.css' and add it _after_ the directive to include
+'server/head-include-2.LANG.html' and _before_ the closing '</head>' tag
+in 'server/banner.LANG.html', i.e.
+
+ <!-- start of banner.bg.html -->
+ <!--#include virtual="/server/head-include-2.bg.html" -->
+ <link rel="stylesheet" href="/style.bg.css" media="screen" />
+ </head>
+
+ Override only what is necessary and looks broken in your language; do
+not invent your own style. This is important for the consistency of the
+gnu.org website. A typical language-specific 'style.LANG.css' file
+looks like this:
+
+ .inner { max-width: 65em; }
+
+ #logo{background:url(/graphics/topbanner.bg.png) no-repeat;}
+ #fssbox {font-size: 50%;}
+
+ This widens the menu and the area where the articles are displayed
+(because the menu entries are _much_ longer than the English equivalents
+when translated), includes a localized logo, and makes the font size for
+the FSF widget twice smaller (because in this language, the translations
+are almost twice longer and displayed truncated, which is undesirable).
+
+ When creating your own 'style.LANG.css', don't forget to include the
+license notice from the 'layout.css', with a short comment.
+
+ If using the default CSS style for translations does not give the
+expected good results, or there are other problems (significant or not)
+that obstruct reading and/or worsen the look from aesthetic point of
+view, please write to <address@hidden> with a description of the
+issue. If there are several unrelated problems, send separate messages
+with appropriate explanation (which may include a demonstration of the
+bug, such as a screenshot).
+
+4.11.1 Localizing the 'topbanner' Image
+---------------------------------------
+
+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:
+
+ 1. Copy 'graphics/topbanner.svg' as 'graphics/topbanner.LANG.svg'
+ where LANG is the language code, as usual. Edit the file with
+ Inkscape or with a plain text editor such as GNU Emacs, translating
+ "GNU Operating System". Then with Inkscape, save the file as
+ 'graphics/topbanner.LANG.png' (File -> Export Bitmap...). Then
+ open the PNG image with the GIMP and flatten it (Image -> Flatten
+ Image). Don't forget to save and 'cvs add' the files(1).
+
+ 2. Create a 'style.LANG.css' at the toplevel directory, if it doesn't
+ exist already. Normally, you would need only one line in it,
+ namely:
+
+ #logo{background:url(/graphics/topbanner.LANG.png) no-repeat;}
+
+ 3. If not done already for other reasons, update 'banner.LANG.html' to
+ include the language specific 'style.LANG.css'. *Note CSS::.
+
+ If you feel uncomfortable manipulating images--don't despair! Send a
+plea for help to <address@hidden>, some people would be
+happy to help you. Failing that, write to <address@hidden>.
+
+ ---------- Footnotes ----------
+
+ (1) This advice applies to all new files, of course.
+
+4.11.2 Specific Issues Related to RTL
+-------------------------------------
+
+Unfortunately, the <http://gnu.org> website does not have excellent
+support for RTL (right-to-left) languages, although best efforts are
+made. If your language is in this category, make sure to:
+
+ * Set the attribute 'dir="rtl"' in the 'html' element at
+ 'server/header.LANG.html'.
+
+ * You _must_ have a custom CSS to override some of the pre-defined
+ values. See 'style.ar.css' and 'style.fa.css' to understand how
+ these two languages solve some of the problems. *Note CSS::.
+
+ *Important:* Some articles contain their own '<style>' redefinitions,
+or style attributes in the form '<p style="...">'. In such situations,
+it is quite possible that the general language-specific CSS does not
+help, and the translation of this specific article does not look
+correct. Please write to <address@hidden>; if you have a working
+solution that works for both cases--so much the better. For general
+issues that affect your language and require a general solution, write
+to <address@hidden> as well, precisely describing the problem.
+
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.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
Binary files /tmp/cvsa1dOGu and /tmp/cvssoIIj6 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.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- web-trans/html_node/CSS.html 31 Jan 2013 08:47:35 -0000 1.12
+++ web-trans/html_node/CSS.html 1 Feb 2013 06:06:17 -0000 1.13
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -26,7 +26,7 @@
<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="Translation-Tips.html#Translation-Tips" rel="up"
title="Translation Tips">
+<link href="Translation-Process.html#Translation-Process" rel="up"
title="Translation Process">
<link href="topbanner.html#topbanner" rel="next" title="topbanner">
<link href="SSI.html#SSI" rel="previous" title="SSI">
<style type="text/css">
@@ -65,11 +65,11 @@
<a name="CSS"></a>
<div class="header">
<p>
-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>
+Previous: <a href="SSI.html#SSI" accesskey="p" rel="previous">SSI</a>, Up: <a
href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</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>
+<h3 class="section">4.11 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
@@ -129,7 +129,7 @@
<hr>
<div class="header">
<p>
-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>
+Previous: <a href="SSI.html#SSI" accesskey="p" rel="previous">SSI</a>, Up: <a
href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Capitalization.html 31 Jan 2013 08:47:35 -0000
1.11
+++ web-trans/html_node/Capitalization.html 1 Feb 2013 06:06:17 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -26,7 +26,7 @@
<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="Translation-Tips.html#Translation-Tips" rel="up"
title="Translation Tips">
+<link href="Translation-Process.html#Translation-Process" rel="up"
title="Translation Process">
<link href="Distribution-Terms.html#Distribution-Terms" rel="next"
title="Distribution Terms">
<link href="Updating.html#Updating" rel="previous" title="Updating">
<style type="text/css">
@@ -65,11 +65,11 @@
<a name="Capitalization"></a>
<div class="header">
<p>
-Next: <a href="Distribution-Terms.html#Distribution-Terms" accesskey="n"
rel="next">Distribution Terms</a>, Previous: <a href="Updating.html#Updating"
accesskey="p" rel="previous">Updating</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>
+Next: <a href="Distribution-Terms.html#Distribution-Terms" accesskey="n"
rel="next">Distribution Terms</a>, Previous: <a href="Updating.html#Updating"
accesskey="p" rel="previous">Updating</a>, Up: <a
href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</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.6 When to CAPITALIZE</h3>
+<h3 class="section">4.3 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
@@ -87,7 +87,7 @@
<p>Another prominent and widely spread mistake is to write your own
language with a capital letter in the list of translations when
languages are written beginning with a small letter according to your
-own rules<a name="DOCF8" href="#FOOT8"><sup>8</sup></a>. In other words, it
is right to write
+own rules<a name="DOCF6" href="#FOOT6"><sup>6</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
@@ -97,7 +97,7 @@
<hr>
<h4 class="footnotes-heading">Footnotes</h4>
-<h3><a name="FOOT8" href="#DOCF8">(8)</a></h3>
+<h3><a name="FOOT6" href="#DOCF6">(6)</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
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Co_002dleaders.html 31 Jan 2013 08:47:35 -0000
1.11
+++ web-trans/html_node/Co_002dleaders.html 1 Feb 2013 06:06:17 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="Promoting-Members-as-Co_002dleaders"></a>
-<h3 class="section">3.7 Promoting Members as Co-leaders</h3>
+<h3 class="section">3.6 Promoting Members as Co-leaders</h3>
<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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Commits.html 31 Jan 2013 08:47:35 -0000 1.11
+++ web-trans/html_node/Commits.html 1 Feb 2013 06:06:17 -0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -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="Leaders.html#Leaders" rel="up" title="Leaders">
-<link href="PO-Files.html#PO-Files" rel="next" title="PO Files">
+<link href="Savannah.html#Savannah" rel="next" title="Savannah">
<link href="Unreviewed-Translations.html#Unreviewed-Translations"
rel="previous" title="Unreviewed Translations">
<style type="text/css">
<!--
@@ -65,7 +65,7 @@
<a name="Commits"></a>
<div class="header">
<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="Leaders.html#Leaders" accesskey="u" rel="up">Leaders</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</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="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="CVS-Commits-and-Best-Practices"></a>
@@ -169,7 +169,7 @@
<hr>
<div class="header">
<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="Leaders.html#Leaders" accesskey="u" rel="up">Leaders</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</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="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>
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Copying-This-Manual.html 31 Jan 2013 08:47:35
-0000 1.11
+++ web-trans/html_node/Copying-This-Manual.html 1 Feb 2013 06:06:17
-0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -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="index.html#Top" rel="up" title="Top">
-<link href="Savannah-Projects.html#Savannah-Projects" rel="previous"
title="Savannah Projects">
+<link href="RTL.html#RTL" rel="previous" title="RTL">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -64,7 +64,7 @@
<a name="Copying-This-Manual"></a>
<div class="header">
<p>
-Previous: <a href="Summary.html#Summary" accesskey="p"
rel="previous">Summary</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>
+Previous: <a href="Translation-Process.html#Translation-Process" accesskey="p"
rel="previous">Translation Process</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="GNU-Free-Documentation-License"></a>
@@ -544,7 +544,7 @@
<hr>
<div class="header">
<p>
-Previous: <a href="Summary.html#Summary" accesskey="p"
rel="previous">Summary</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>
+Previous: <a href="Translation-Process.html#Translation-Process" accesskey="p"
rel="previous">Translation Process</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>
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.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- web-trans/html_node/Distribution-Terms.html 31 Jan 2013 08:47:35 -0000
1.7
+++ web-trans/html_node/Distribution-Terms.html 1 Feb 2013 06:06:18 -0000
1.8
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -26,7 +26,7 @@
<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="Translation-Tips.html#Translation-Tips" rel="up"
title="Translation Tips">
+<link href="Translation-Process.html#Translation-Process" rel="up"
title="Translation Process">
<link href="Terminology.html#Terminology" rel="next" title="Terminology">
<link href="Capitalization.html#Capitalization" rel="previous"
title="Capitalization">
<style type="text/css">
@@ -65,11 +65,11 @@
<a name="Distribution-Terms"></a>
<div class="header">
<p>
-Next: <a href="Terminology.html#Terminology" accesskey="n"
rel="next">Terminology</a>, Previous: <a
href="Capitalization.html#Capitalization" accesskey="p"
rel="previous">Capitalization</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>
+Next: <a href="Terminology.html#Terminology" accesskey="n"
rel="next">Terminology</a>, Previous: <a
href="Capitalization.html#Capitalization" accesskey="p"
rel="previous">Capitalization</a>, Up: <a
href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<hr>
<a name="Distribution-Terms-1"></a>
-<h3 class="section">5.7 Distribution Terms</h3>
+<h3 class="section">4.4 Distribution Terms</h3>
<p>Most www.gnu.org articles are released under the terms of
the Creative Commons Attribution-NoDerivs 3.0 United States license.
@@ -132,7 +132,7 @@
<hr>
<div class="header">
<p>
-Next: <a href="Terminology.html#Terminology" accesskey="n"
rel="next">Terminology</a>, Previous: <a
href="Capitalization.html#Capitalization" accesskey="p"
rel="previous">Capitalization</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>
+Next: <a href="Terminology.html#Terminology" accesskey="n"
rel="next">Terminology</a>, Previous: <a
href="Capitalization.html#Capitalization" accesskey="p"
rel="previous">Capitalization</a>, Up: <a
href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Introduction.html 31 Jan 2013 08:47:35 -0000
1.11
+++ web-trans/html_node/Introduction.html 1 Feb 2013 06:06:18 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -104,19 +104,18 @@
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
+language teams. Each team has one or more co-ordinators, who are
+responsible for the respective team; they are also referred to as
+leaders or (when multiple in a single team) co-leaders. The
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
+Managers (also known as Translation Managers or web-translators).
+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,
-see <a href="Leaders.html#Leaders">Leaders</a>. The chapter about the
‘<samp>trans-coord</samp>’
-administrators (a.k.a. <em>GNU Translation Managers</em>) describes all the
-responsibilities and procedures involved in performing this duty.
-See <a href="Translation-Managers.html#Translation-Managers">Translation
Managers</a>.
+see <a href="Leaders.html#Leaders">Leaders</a>.
</p>
<hr>
<div class="header">
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Joining.html 31 Jan 2013 08:47:35 -0000 1.11
+++ web-trans/html_node/Joining.html 1 Feb 2013 06:06:18 -0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -121,7 +121,7 @@
two weeks), please write to <a href="mailto:address@hidden";>address@hidden</a>.
</p>
<p>For general information about the translation process,
-see <a href="Translation-Tips.html#Translation-Tips">Translation Tips</a>.
+see <a href="Translation-Process.html#Translation-Process">Translation
Process</a>.
</p>
<hr>
<div class="header">
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Leaders.html 31 Jan 2013 08:47:36 -0000 1.11
+++ web-trans/html_node/Leaders.html 1 Feb 2013 06:06:18 -0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -65,7 +65,7 @@
<a name="Leaders"></a>
<div class="header">
<p>
-Next: <a href="Translation-Managers.html#Translation-Managers" accesskey="n"
rel="next">Translation Managers</a>, Previous: <a href="Members.html#Members"
accesskey="p" rel="previous">Members</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>
+Next: <a href="Translation-Process.html#Translation-Process" accesskey="n"
rel="next">Translation Process</a>, Previous: <a href="Members.html#Members"
accesskey="p" rel="previous">Members</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="Team-Co_002dordinators"></a>
@@ -95,15 +95,13 @@
</td></tr>
<tr><td align="left" valign="top">• <a href="Commits.html#Commits"
accesskey="4">Commits</a>:</td><td> </td><td align="left"
valign="top">CVS commits and best practices.
</td></tr>
-<tr><td align="left" valign="top">• <a href="PO-Files.html#PO-Files"
accesskey="5">PO Files</a>:</td><td> </td><td align="left"
valign="top">Working with PO files.
+<tr><td align="left" valign="top">• <a href="Savannah.html#Savannah"
accesskey="5">Savannah</a>:</td><td> </td><td align="left"
valign="top">Taking advantage of Savannah.
</td></tr>
-<tr><td align="left" valign="top">• <a href="Savannah.html#Savannah"
accesskey="6">Savannah</a>:</td><td> </td><td align="left"
valign="top">Taking advantage of Savannah.
+<tr><td align="left" valign="top">• <a
href="Co_002dleaders.html#Co_002dleaders"
accesskey="6">Co-leaders</a>:</td><td> </td><td align="left"
valign="top">Promoting members as co-leaders.
</td></tr>
-<tr><td align="left" valign="top">• <a
href="Co_002dleaders.html#Co_002dleaders"
accesskey="7">Co-leaders</a>:</td><td> </td><td align="left"
valign="top">Promoting members as co-leaders.
+<tr><td align="left" valign="top">• <a href="Reports.html#Reports"
accesskey="7">Reports</a>:</td><td> </td><td align="left"
valign="top">Reporting team status and activity.
</td></tr>
-<tr><td align="left" valign="top">• <a href="Reports.html#Reports"
accesskey="8">Reports</a>:</td><td> </td><td align="left"
valign="top">Reporting team status and activity.
-</td></tr>
-<tr><td align="left" valign="top">• <a
href="Stepping-Down.html#Stepping-Down" accesskey="9">Stepping
Down</a>:</td><td> </td><td align="left" valign="top">Orphaning the
team and finding a replacement.
+<tr><td align="left" valign="top">• <a
href="Stepping-Down.html#Stepping-Down" accesskey="8">Stepping
Down</a>:</td><td> </td><td align="left" valign="top">Orphaning the
team and finding a replacement.
</td></tr>
</table>
Index: web-trans/html_node/Leaving-a-Team.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Leaving-a-Team.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- web-trans/html_node/Leaving-a-Team.html 31 Jan 2013 08:47:36 -0000
1.2
+++ web-trans/html_node/Leaving-a-Team.html 1 Feb 2013 06:06:18 -0000
1.3
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Mailing-Lists.html 31 Jan 2013 08:47:36 -0000
1.11
+++ web-trans/html_node/Mailing-Lists.html 1 Feb 2013 06:06:18 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -26,9 +26,9 @@
<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="Summary.html#Summary" rel="up" title="Summary">
+<link href="Translation-Process.html#Translation-Process" rel="up"
title="Translation Process">
<link href="Savannah-Projects.html#Savannah-Projects" rel="next"
title="Savannah Projects">
-<link href="Summary.html#Summary" rel="previous" title="Summary">
+<link href="Terminology.html#Terminology" rel="previous" title="Terminology">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -65,11 +65,11 @@
<a name="Mailing-Lists"></a>
<div class="header">
<p>
-Next: <a href="Savannah-Projects.html#Savannah-Projects" accesskey="n"
rel="next">Savannah Projects</a>, Up: <a href="Summary.html#Summary"
accesskey="u" rel="up">Summary</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
+Next: <a href="Savannah-Projects.html#Savannah-Projects" accesskey="n"
rel="next">Savannah Projects</a>, Previous: <a
href="Terminology.html#Terminology" accesskey="p"
rel="previous">Terminology</a>, Up: <a
href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<hr>
<a name="Related-Mailing-Lists"></a>
-<h3 class="section">6.1 Related Mailing Lists</h3>
+<h3 class="section">4.6 Related Mailing Lists</h3>
<p>Here is a short summary of the mailing lists relevant to the translation
process, and a brief description about how they relate to the various
@@ -129,10 +129,13 @@
</p></dd>
</dl>
+<p>Every team should also use at least one mailing list on Savannah,
+see <a href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists">Savannah
Mailing Lists</a>.
+</p>
<hr>
<div class="header">
<p>
-Next: <a href="Savannah-Projects.html#Savannah-Projects" accesskey="n"
rel="next">Savannah Projects</a>, Up: <a href="Summary.html#Summary"
accesskey="u" rel="up">Summary</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
+Next: <a href="Savannah-Projects.html#Savannah-Projects" accesskey="n"
rel="next">Savannah Projects</a>, Previous: <a
href="Terminology.html#Terminology" accesskey="p"
rel="previous">Terminology</a>, Up: <a
href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Managing.html 31 Jan 2013 08:47:36 -0000 1.11
+++ web-trans/html_node/Managing.html 1 Feb 2013 06:06:18 -0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Members.html 31 Jan 2013 08:47:36 -0000 1.11
+++ web-trans/html_node/Members.html 1 Feb 2013 06:06:18 -0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Migrating.html 31 Jan 2013 08:47:36 -0000 1.11
+++ web-trans/html_node/Migrating.html 1 Feb 2013 06:06:20 -0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -26,9 +26,9 @@
<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="Translation-Tips.html#Translation-Tips" rel="up"
title="Translation Tips">
+<link href="Translation-Process.html#Translation-Process" rel="up"
title="Translation Process">
<link href="SSI.html#SSI" rel="next" title="SSI">
-<link href="Translation-Tips.html#Translation-Tips" rel="previous"
title="Translation Tips">
+<link href="PO-Files.html#PO-Files" rel="previous" title="PO Files">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -65,11 +65,11 @@
<a name="Migrating"></a>
<div class="header">
<p>
-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>
+Next: <a href="SSI.html#SSI" accesskey="n" rel="next">SSI</a>, Previous: <a
href="PO-Files.html#PO-Files" accesskey="p" rel="previous">PO Files</a>, Up: <a
href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</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>
+<h3 class="section">4.9 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.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- web-trans/html_node/New-Team.html 31 Jan 2013 08:47:36 -0000 1.12
+++ web-trans/html_node/New-Team.html 1 Feb 2013 06:06:20 -0000 1.13
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -218,6 +218,14 @@
</li><li>- www-discuss
</li></ul>
+</li><li> When you are appointed the admin of the new project, please edit its
+configuration; in particular, write its description, create a mailing
+list (don’t forget to subscribe yourself!), optionally add a home
+page using Web CVS repository.
+
+<p>If you are taking over an orphaned team, Translation Managers will
+make you the owner of its mailing lists (if any).
+</p>
</li></ol>
<p>The whole process should not take more than two weeks or maximum a
Index: web-trans/html_node/PO-Files.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/PO-Files.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- web-trans/html_node/PO-Files.html 31 Jan 2013 08:47:36 -0000 1.2
+++ web-trans/html_node/PO-Files.html 1 Feb 2013 06:06:20 -0000 1.3
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -26,9 +26,9 @@
<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="Leaders.html#Leaders" rel="up" title="Leaders">
-<link href="Savannah.html#Savannah" rel="next" title="Savannah">
-<link href="Commits.html#Commits" rel="previous" title="Commits">
+<link href="Translation-Process.html#Translation-Process" rel="up"
title="Translation Process">
+<link href="Migrating.html#Migrating" rel="next" title="Migrating">
+<link href="Savannah-Projects.html#Savannah-Projects" rel="previous"
title="Savannah Projects">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -65,16 +65,16 @@
<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="Leaders.html#Leaders" accesskey="u"
rel="up">Leaders</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
+Next: <a href="Migrating.html#Migrating" accesskey="n"
rel="next">Migrating</a>, Previous: <a
href="Savannah-Projects.html#Savannah-Projects" accesskey="p"
rel="previous">Savannah Projects</a>, Up: <a
href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</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>
-<h3 class="section">3.5 Working with PO Files</h3>
+<h3 class="section">4.8 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<a name="DOCF6" href="#FOOT6"><sup>6</sup></a>.
+before<a name="DOCF7" href="#FOOT7"><sup>7</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.
@@ -120,7 +120,7 @@
</li></ul>
<a name="Web_002dbased-Systems"></a>
-<h4 class="subsection">3.5.1 Web-based Systems</h4>
+<h4 class="subsection">4.8.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
@@ -155,14 +155,14 @@
<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>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="Leaders.html#Leaders" accesskey="u"
rel="up">Leaders</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
+Next: <a href="Migrating.html#Migrating" accesskey="n"
rel="next">Migrating</a>, Previous: <a
href="Savannah-Projects.html#Savannah-Projects" accesskey="p"
rel="previous">Savannah Projects</a>, Up: <a
href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Priorities.html 31 Jan 2013 08:47:36 -0000 1.11
+++ web-trans/html_node/Priorities.html 1 Feb 2013 06:06:20 -0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -26,9 +26,9 @@
<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="Translation-Tips.html#Translation-Tips" rel="up"
title="Translation Tips">
+<link href="Translation-Process.html#Translation-Process" rel="up"
title="Translation Process">
<link href="Updating.html#Updating" rel="next" title="Updating">
-<link href="RTL.html#RTL" rel="previous" title="RTL">
+<link href="Translation-Process.html#Translation-Process" rel="previous"
title="Translation Process">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -65,13 +65,13 @@
<a name="Priorities"></a>
<div class="header">
<p>
-Next: <a href="Updating.html#Updating" accesskey="n" rel="next">Updating</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>
+Next: <a href="Updating.html#Updating" accesskey="n" rel="next">Updating</a>,
Up: <a href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</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>
+<h3 class="section">4.1 What to Translate</h3>
-<p>The article
+<p>The page
<a
href="http://www.gnu.org/server/standards/translations/priorities.html";>http://www.gnu.org/server/standards/translations/priorities.html</a>
lists the most important essays to translate. In general, articles in
the directories <samp>philosophy</samp>, <samp>gnu</samp>,
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/RTL.html 31 Jan 2013 08:47:36 -0000 1.11
+++ web-trans/html_node/RTL.html 1 Feb 2013 06:06:21 -0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -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="CSS.html#CSS" rel="up" title="CSS">
-<link href="Priorities.html#Priorities" rel="next" title="Priorities">
+<link href="Copying-This-Manual.html#Copying-This-Manual" rel="next"
title="Copying This Manual">
<link href="topbanner.html#topbanner" rel="previous" title="topbanner">
<style type="text/css">
<!--
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="Specific-Issues-Related-to-RTL"></a>
-<h4 class="subsection">5.3.2 Specific Issues Related to RTL</h4>
+<h4 class="subsection">4.11.2 Specific Issues Related to RTL</h4>
<p>Unfortunately, the <a href="http://gnu.org";>http://gnu.org</a> website does
not have excellent
support for RTL (right-to-left) languages, although best efforts are
@@ -97,5 +97,6 @@
+
</body>
</html>
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Reports.html 31 Jan 2013 08:47:36 -0000 1.11
+++ web-trans/html_node/Reports.html 1 Feb 2013 06:06:21 -0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="Reporting-Team-Status"></a>
-<h3 class="section">3.8 Reporting Team Status</h3>
+<h3 class="section">3.7 Reporting Team Status</h3>
<p>Team leaders must send an annual report about the status of the team. A
good report should include:
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Review.html 31 Jan 2013 08:47:36 -0000 1.11
+++ web-trans/html_node/Review.html 1 Feb 2013 06:06:21 -0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/SSI.html 31 Jan 2013 08:47:36 -0000 1.11
+++ web-trans/html_node/SSI.html 1 Feb 2013 06:06:21 -0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -26,7 +26,7 @@
<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="Translation-Tips.html#Translation-Tips" rel="up"
title="Translation Tips">
+<link href="Translation-Process.html#Translation-Process" rel="up"
title="Translation Process">
<link href="CSS.html#CSS" rel="next" title="CSS">
<link href="Migrating.html#Migrating" rel="previous" title="Migrating">
<style type="text/css">
@@ -65,11 +65,11 @@
<a name="SSI"></a>
<div class="header">
<p>
-Next: <a href="CSS.html#CSS" accesskey="n" rel="next">CSS</a>, Previous: <a
href="Migrating.html#Migrating" accesskey="p" rel="previous">Migrating</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>
+Next: <a href="CSS.html#CSS" accesskey="n" rel="next">CSS</a>, Previous: <a
href="Migrating.html#Migrating" accesskey="p" rel="previous">Migrating</a>, Up:
<a href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<hr>
<a name="Summary-of-SSI-_0023includes"></a>
-<h3 class="section">5.2 Summary of SSI <code>#include</code>s</h3>
+<h3 class="section">4.10 Summary of SSI <code>#include</code>s</h3>
<p>The GNU Project’s website uses SSI (Server Side Includes) to manage
some
common parts that are the same in many of the articles. With the help
@@ -235,7 +235,7 @@
<hr>
<div class="header">
<p>
-Next: <a href="CSS.html#CSS" accesskey="n" rel="next">CSS</a>, Previous: <a
href="Migrating.html#Migrating" accesskey="p" rel="previous">Migrating</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>
+Next: <a href="CSS.html#CSS" accesskey="n" rel="next">CSS</a>, Previous: <a
href="Migrating.html#Migrating" accesskey="p" rel="previous">Migrating</a>, Up:
<a href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Savannah-Bugs.html 31 Jan 2013 08:47:36 -0000
1.11
+++ web-trans/html_node/Savannah-Bugs.html 1 Feb 2013 06:06:22 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="Bugs-Tracker"></a>
-<h4 class="subsection">3.6.5 Bugs Tracker</h4>
+<h4 class="subsection">3.5.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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Savannah-Homepage.html 31 Jan 2013 08:47:36 -0000
1.11
+++ web-trans/html_node/Savannah-Homepage.html 1 Feb 2013 06:06:22 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="Homepage-of-the-Team"></a>
-<h4 class="subsection">3.6.2 Homepage of the Team</h4>
+<h4 class="subsection">3.5.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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Savannah-Mailing-Lists.html 31 Jan 2013 08:47:36
-0000 1.11
+++ web-trans/html_node/Savannah-Mailing-Lists.html 1 Feb 2013 06:06:22
-0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -69,12 +69,14 @@
</div>
<hr>
<a name="Managing-Mailing-Lists"></a>
-<h4 class="subsection">3.6.7 Managing Mailing Lists</h4>
+<h4 class="subsection">3.5.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
list. The list owner should be the co-ordinator of the team. The
-name of the list should begin with
‘<samp>www-<var>lang</var>-</samp>’.
+name of the list should begin with
‘<samp>www-<var>lang</var>-</samp>’. The team
+co-ordinator is in the position to decide about the settings like
+being public or private.
</p>
<p>The list will make it possible for the GNU project to contact the team
when the co-ordinator disappears; its archive will also give access to
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Savannah-Members.html 31 Jan 2013 08:47:36 -0000
1.11
+++ web-trans/html_node/Savannah-Members.html 1 Feb 2013 06:06:22 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="Managing-Members"></a>
-<h4 class="subsection">3.6.1 Managing Members</h4>
+<h4 class="subsection">3.5.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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Savannah-News.html 31 Jan 2013 08:47:36 -0000
1.11
+++ web-trans/html_node/Savannah-News.html 1 Feb 2013 06:06:22 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="News-Tracker"></a>
-<h4 class="subsection">3.6.6 News Tracker</h4>
+<h4 class="subsection">3.5.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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Savannah-Projects.html 31 Jan 2013 08:47:36 -0000
1.11
+++ web-trans/html_node/Savannah-Projects.html 1 Feb 2013 06:06:23 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -26,8 +26,8 @@
<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="Summary.html#Summary" rel="up" title="Summary">
-<link href="Copying-This-Manual.html#Copying-This-Manual" rel="next"
title="Copying This Manual">
+<link href="Translation-Process.html#Translation-Process" rel="up"
title="Translation Process">
+<link href="PO-Files.html#PO-Files" rel="next" title="PO Files">
<link href="Mailing-Lists.html#Mailing-Lists" rel="previous" title="Mailing
Lists">
<style type="text/css">
<!--
@@ -65,11 +65,11 @@
<a name="Savannah-Projects"></a>
<div class="header">
<p>
-Previous: <a href="Mailing-Lists.html#Mailing-Lists" accesskey="p"
rel="previous">Mailing Lists</a>, Up: <a href="Summary.html#Summary"
accesskey="u" rel="up">Summary</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="Mailing-Lists.html#Mailing-Lists" accesskey="p"
rel="previous">Mailing Lists</a>, Up: <a
href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<hr>
<a name="Savannah-Projects-Membership"></a>
-<h3 class="section">6.2 Savannah Projects Membership</h3>
+<h3 class="section">4.7 Savannah Projects Membership</h3>
<p>Participants in the www.gnu.org translations process normally have to be
members of the following Savannah projects, depending on the case:
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Savannah-Support.html 31 Jan 2013 08:47:37 -0000
1.11
+++ web-trans/html_node/Savannah-Support.html 1 Feb 2013 06:06:23 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="Support-Tracker"></a>
-<h4 class="subsection">3.6.3 Support Tracker</h4>
+<h4 class="subsection">3.5.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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Savannah-Tasks.html 31 Jan 2013 08:47:37 -0000
1.11
+++ web-trans/html_node/Savannah-Tasks.html 1 Feb 2013 06:06:23 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="Tasks-Tracker"></a>
-<h4 class="subsection">3.6.4 Tasks Tracker</h4>
+<h4 class="subsection">3.5.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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Savannah-VCS.html 31 Jan 2013 08:47:37 -0000
1.11
+++ web-trans/html_node/Savannah-VCS.html 1 Feb 2013 06:06:23 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="Version-Control-Systems"></a>
-<h4 class="subsection">3.6.8 Version Control Systems</h4>
+<h4 class="subsection">3.5.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
@@ -78,7 +78,7 @@
ready. It is also convenient to update the translation (merge any
changes from the original) while it is still under review.
</p>
-<p>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>, for
+<p>See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/Team_0027s-Repository.html#Team_0027s-Repository";>Team's
Repository</a> in <cite>The GNUnited Nations Manual</cite>, for
more information.
</p>
<p><strong>Remember:</strong> A choice of a particular VCS is a sensitive
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Savannah.html 31 Jan 2013 08:47:37 -0000 1.11
+++ web-trans/html_node/Savannah.html 1 Feb 2013 06:06:23 -0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -28,7 +28,7 @@
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Leaders.html#Leaders" rel="up" title="Leaders">
<link href="Savannah-Members.html#Savannah-Members" rel="next" title="Savannah
Members">
-<link href="PO-Files.html#PO-Files" rel="previous" title="PO Files">
+<link href="Commits.html#Commits" rel="previous" title="Commits">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -65,11 +65,11 @@
<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="PO-Files.html#PO-Files"
accesskey="p" rel="previous">PO Files</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>
+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="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="Taking-Advantage-of-Savannah"></a>
-<h3 class="section">3.6 Taking Advantage of Savannah</h3>
+<h3 class="section">3.5 Taking Advantage of Savannah</h3>
<p>Every translation team should have a project in Savannah. There are
some teams that use their own resources outside Savannah; although
@@ -135,7 +135,7 @@
<hr>
<div class="header">
<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="Leaders.html#Leaders"
accesskey="u" rel="up">Leaders</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="Commits.html#Commits"
accesskey="p" rel="previous">Commits</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>
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Stepping-Down.html 31 Jan 2013 08:47:37 -0000
1.11
+++ web-trans/html_node/Stepping-Down.html 1 Feb 2013 06:06:24 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -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="Leaders.html#Leaders" rel="up" title="Leaders">
-<link href="Translation-Managers.html#Translation-Managers" rel="next"
title="Translation Managers">
+<link href="Translation-Process.html#Translation-Process" rel="next"
title="Translation Process">
<link href="Reports.html#Reports" rel="previous" title="Reports">
<style type="text/css">
<!--
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="How-to-Retire-Painlessly"></a>
-<h3 class="section">3.9 How to Retire Painlessly</h3>
+<h3 class="section">3.8 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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Submitting-as-PO.html 31 Jan 2013 08:47:37 -0000
1.11
+++ web-trans/html_node/Submitting-as-PO.html 1 Feb 2013 06:06:24 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Submitting-as-Plain-Text.html 31 Jan 2013 08:47:37
-0000 1.11
+++ web-trans/html_node/Submitting-as-Plain-Text.html 1 Feb 2013 06:06:24
-0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Submitting.html 31 Jan 2013 08:47:37 -0000 1.11
+++ web-trans/html_node/Submitting.html 1 Feb 2013 06:06:24 -0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Terminology.html 31 Jan 2013 08:47:37 -0000
1.11
+++ web-trans/html_node/Terminology.html 1 Feb 2013 06:06:24 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -26,8 +26,8 @@
<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="Translation-Tips.html#Translation-Tips" rel="up"
title="Translation Tips">
-<link href="Summary.html#Summary" rel="next" title="Summary">
+<link href="Translation-Process.html#Translation-Process" rel="up"
title="Translation Process">
+<link href="Mailing-Lists.html#Mailing-Lists" rel="next" title="Mailing Lists">
<link href="Distribution-Terms.html#Distribution-Terms" rel="previous"
title="Distribution Terms">
<style type="text/css">
<!--
@@ -65,14 +65,17 @@
<a name="Terminology"></a>
<div class="header">
<p>
-Previous: <a href="Distribution-Terms.html#Distribution-Terms" accesskey="p"
rel="previous">Distribution Terms</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>
+Next: <a href="Mailing-Lists.html#Mailing-Lists" accesskey="n"
rel="next">Mailing Lists</a>, Previous: <a
href="Distribution-Terms.html#Distribution-Terms" accesskey="p"
rel="previous">Distribution Terms</a>, Up: <a
href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<hr>
<a name="Language_002dspecific-Terminology"></a>
-<h3 class="section">5.8 Language-specific Terminology</h3>
+<h3 class="section">4.5 Language-specific Terminology</h3>
<p>This is a very important topic, not yet covered by this manual.
</p>
+<p>Some tips are given on
+<a
href="http://www.gnu.org/server/standards/README.translations.en.html";>http://www.gnu.org/server/standards/README.translations.en.html</a>.
+</p>
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Tracking-Tasks.html 31 Jan 2013 08:47:37 -0000
1.11
+++ web-trans/html_node/Tracking-Tasks.html 1 Feb 2013 06:06:24 -0000
1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/Unreviewed-Translations.html 31 Jan 2013 08:47:37
-0000 1.11
+++ web-trans/html_node/Unreviewed-Translations.html 1 Feb 2013 06:06:24
-0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
Index: web-trans/html_node/Updating.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Updating.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- web-trans/html_node/Updating.html 31 Jan 2013 08:51:08 -0000 1.1
+++ web-trans/html_node/Updating.html 1 Feb 2013 06:06:24 -0000 1.2
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -26,7 +26,7 @@
<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="Translation-Tips.html#Translation-Tips" rel="up"
title="Translation Tips">
+<link href="Translation-Process.html#Translation-Process" rel="up"
title="Translation Process">
<link href="Capitalization.html#Capitalization" rel="next"
title="Capitalization">
<link href="Priorities.html#Priorities" rel="previous" title="Priorities">
<style type="text/css">
@@ -65,11 +65,11 @@
<a name="Updating"></a>
<div class="header">
<p>
-Next: <a href="Capitalization.html#Capitalization" accesskey="n"
rel="next">Capitalization</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>
+Next: <a href="Capitalization.html#Capitalization" accesskey="n"
rel="next">Capitalization</a>, Previous: <a href="Priorities.html#Priorities"
accesskey="p" rel="previous">Priorities</a>, Up: <a
href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<hr>
<a name="Keeping-Translations-Current"></a>
-<h3 class="section">5.5 Keeping Translations Current</h3>
+<h3 class="section">4.2 Keeping Translations Current</h3>
<p>It is very important to keep existing translations up-to-date with the
respective English originals. This task should be higher priority than
@@ -113,7 +113,7 @@
<hr>
<div class="header">
<p>
-Next: <a href="Capitalization.html#Capitalization" accesskey="n"
rel="next">Capitalization</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>
+Next: <a href="Capitalization.html#Capitalization" accesskey="n"
rel="next">Capitalization</a>, Previous: <a href="Priorities.html#Priorities"
accesskey="p" rel="previous">Priorities</a>, Up: <a
href="Translation-Process.html#Translation-Process" accesskey="u"
rel="up">Translation Process</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- web-trans/html_node/index.html 31 Jan 2013 08:47:37 -0000 1.11
+++ web-trans/html_node/index.html 1 Feb 2013 06:06:24 -0000 1.12
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -92,45 +92,41 @@
<li><a name="toc-How-to-Proceed-with-Unreviewed-Translations"
href="Unreviewed-Translations.html#Unreviewed-Translations">3.3.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.4 CVS Commits and Best Practices</a></li>
- <li><a name="toc-Working-with-PO-Files" href="PO-Files.html#PO-Files">3.5
Working with PO Files</a>
+ <li><a name="toc-Taking-Advantage-of-Savannah"
href="Savannah.html#Savannah">3.5 Taking Advantage of Savannah</a>
<ul class="no-bullet">
- <li><a name="toc-Web_002dbased-Systems"
href="PO-Files.html#Web_002dbased-Systems">3.5.1 Web-based Systems</a></li>
- </ul></li>
- <li><a name="toc-Taking-Advantage-of-Savannah"
href="Savannah.html#Savannah">3.6 Taking Advantage of Savannah</a>
- <ul class="no-bullet">
- <li><a name="toc-Managing-Members"
href="Savannah-Members.html#Savannah-Members">3.6.1 Managing Members</a></li>
- <li><a name="toc-Homepage-of-the-Team"
href="Savannah-Homepage.html#Savannah-Homepage">3.6.2 Homepage of the
Team</a></li>
- <li><a name="toc-Support-Tracker"
href="Savannah-Support.html#Savannah-Support">3.6.3 Support Tracker</a></li>
- <li><a name="toc-Tasks-Tracker"
href="Savannah-Tasks.html#Savannah-Tasks">3.6.4 Tasks Tracker</a></li>
- <li><a name="toc-Bugs-Tracker"
href="Savannah-Bugs.html#Savannah-Bugs">3.6.5 Bugs Tracker</a></li>
- <li><a name="toc-News-Tracker"
href="Savannah-News.html#Savannah-News">3.6.6 News Tracker</a></li>
- <li><a name="toc-Managing-Mailing-Lists"
href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists">3.6.7 Managing
Mailing Lists</a></li>
- <li><a name="toc-Version-Control-Systems"
href="Savannah-VCS.html#Savannah-VCS">3.6.8 Version Control Systems</a></li>
- </ul></li>
- <li><a name="toc-Promoting-Members-as-Co_002dleaders"
href="Co_002dleaders.html#Co_002dleaders">3.7 Promoting Members as
Co-leaders</a></li>
- <li><a name="toc-Reporting-Team-Status" href="Reports.html#Reports">3.8
Reporting Team Status</a></li>
- <li><a name="toc-How-to-Retire-Painlessly"
href="Stepping-Down.html#Stepping-Down">3.9 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>
- <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-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-Managing-Members"
href="Savannah-Members.html#Savannah-Members">3.5.1 Managing Members</a></li>
+ <li><a name="toc-Homepage-of-the-Team"
href="Savannah-Homepage.html#Savannah-Homepage">3.5.2 Homepage of the
Team</a></li>
+ <li><a name="toc-Support-Tracker"
href="Savannah-Support.html#Savannah-Support">3.5.3 Support Tracker</a></li>
+ <li><a name="toc-Tasks-Tracker"
href="Savannah-Tasks.html#Savannah-Tasks">3.5.4 Tasks Tracker</a></li>
+ <li><a name="toc-Bugs-Tracker"
href="Savannah-Bugs.html#Savannah-Bugs">3.5.5 Bugs Tracker</a></li>
+ <li><a name="toc-News-Tracker"
href="Savannah-News.html#Savannah-News">3.5.6 News Tracker</a></li>
+ <li><a name="toc-Managing-Mailing-Lists"
href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists">3.5.7 Managing
Mailing Lists</a></li>
+ <li><a name="toc-Version-Control-Systems"
href="Savannah-VCS.html#Savannah-VCS">3.5.8 Version Control Systems</a></li>
+ </ul></li>
+ <li><a name="toc-Promoting-Members-as-Co_002dleaders"
href="Co_002dleaders.html#Co_002dleaders">3.6 Promoting Members as
Co-leaders</a></li>
+ <li><a name="toc-Reporting-Team-Status" href="Reports.html#Reports">3.7
Reporting Team Status</a></li>
+ <li><a name="toc-How-to-Retire-Painlessly"
href="Stepping-Down.html#Stepping-Down">3.8 How to Retire Painlessly</a></li>
+ </ul></li>
+ <li><a name="toc-Translation-Process-1"
href="Translation-Process.html#Translation-Process">4 Translation Process</a>
+ <ul class="no-bullet">
+ <li><a name="toc-What-to-Translate" href="Priorities.html#Priorities">4.1
What to Translate</a></li>
+ <li><a name="toc-Keeping-Translations-Current"
href="Updating.html#Updating">4.2 Keeping Translations Current</a></li>
+ <li><a name="toc-When-to-CAPITALIZE"
href="Capitalization.html#Capitalization">4.3 When to CAPITALIZE</a></li>
+ <li><a name="toc-Distribution-Terms-1"
href="Distribution-Terms.html#Distribution-Terms">4.4 Distribution
Terms</a></li>
+ <li><a name="toc-Language_002dspecific-Terminology"
href="Terminology.html#Terminology">4.5 Language-specific Terminology</a></li>
+ <li><a name="toc-Related-Mailing-Lists"
href="Mailing-Lists.html#Mailing-Lists">4.6 Related Mailing Lists</a></li>
+ <li><a name="toc-Savannah-Projects-Membership"
href="Savannah-Projects.html#Savannah-Projects">4.7 Savannah Projects
Membership</a></li>
+ <li><a name="toc-Working-with-PO-Files" href="PO-Files.html#PO-Files">4.8
Working with PO Files</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Web_002dbased-Systems"
href="PO-Files.html#Web_002dbased-Systems">4.8.1 Web-based Systems</a></li>
+ </ul></li>
+ <li><a name="toc-Migration-to-the-New-Style"
href="Migrating.html#Migrating">4.9 Migration to the New Style</a></li>
+ <li><a name="toc-Summary-of-SSI-_0023includes" href="SSI.html#SSI">4.10
Summary of SSI <code>#include</code>s</a></li>
+ <li><a name="toc-How-to-Use-Custom-CSS" href="CSS.html#CSS">4.11 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-Specific-Issues-Related-to-RTL"
href="RTL.html#RTL">5.3.2 Specific Issues Related to RTL</a></li>
+ <li><a name="toc-Localizing-the-topbanner-Image"
href="topbanner.html#topbanner">4.11.1 Localizing the <samp>topbanner</samp>
Image</a></li>
+ <li><a name="toc-Specific-Issues-Related-to-RTL"
href="RTL.html#RTL">4.11.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-Keeping-Translations-Current"
href="Updating.html#Updating">5.5 Keeping Translations Current</a></li>
- <li><a name="toc-When-to-CAPITALIZE"
href="Capitalization.html#Capitalization">5.6 When to CAPITALIZE</a></li>
- <li><a name="toc-Distribution-Terms-1"
href="Distribution-Terms.html#Distribution-Terms">5.7 Distribution
Terms</a></li>
- <li><a name="toc-Language_002dspecific-Terminology"
href="Terminology.html#Terminology">5.8 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>
- <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>
</ul></li>
<li><a name="toc-GNU-Free-Documentation-License"
href="Copying-This-Manual.html#Copying-This-Manual">Appendix A GNU Free
Documentation License</a></li>
</ul>
@@ -148,7 +144,7 @@
<h1 class="top">GNU Web Translators Manual</h1>
<p>This manual is a guide for the GNU Web Translators.<br> Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
</p><br>
<p>Copyright © 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -170,14 +166,9 @@
</td></tr>
<tr><td align="left" valign="top">• <a href="Leaders.html#Leaders"
accesskey="3">Leaders</a>:</td><td> </td><td align="left"
valign="top">Guidelines and procedures for team leaders.
</td></tr>
-<tr><td align="left" valign="top">• <a
href="Translation-Managers.html#Translation-Managers" accesskey="4">Translation
Managers</a>:</td><td> </td><td align="left"
valign="top">Responsibilities of the GNU Web Translation
- co-ordinators.
-</td></tr>
-<tr><td align="left" valign="top">• <a
href="Translation-Tips.html#Translation-Tips" accesskey="5">Translation
Tips</a>:</td><td> </td><td align="left" valign="top">Explanation of
some non-obvious things.
-</td></tr>
-<tr><td align="left" valign="top">• <a href="Summary.html#Summary"
accesskey="6">Summary</a>:</td><td> </td><td align="left"
valign="top">Overview.
+<tr><td align="left" valign="top">• <a
href="Translation-Process.html#Translation-Process" accesskey="4">Translation
Process</a>:</td><td> </td><td align="left" valign="top">General
guidelines and tips.
</td></tr>
-<tr><td align="left" valign="top">• <a
href="Copying-This-Manual.html#Copying-This-Manual" accesskey="7">Copying This
Manual</a>:</td><td> </td><td align="left" valign="top">The GNU Free
Documentation License.
+<tr><td align="left" valign="top">• <a
href="Copying-This-Manual.html#Copying-This-Manual" accesskey="5">Copying This
Manual</a>:</td><td> </td><td align="left" valign="top">The GNU Free
Documentation License.
</td></tr>
</table>
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.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- web-trans/html_node/topbanner.html 31 Jan 2013 08:47:37 -0000 1.12
+++ web-trans/html_node/topbanner.html 1 Feb 2013 06:06:24 -0000 1.13
@@ -3,7 +3,7 @@
<!--
This manual is a guide for the GNU Web Translators.
Last updated on
-17.01.2013, for GNUnited Nations version 0.7.
+1 February 2013, for GNUnited Nations version 0.7.
Copyright (C) 2009, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc.
@@ -69,7 +69,7 @@
</div>
<hr>
<a name="Localizing-the-topbanner-Image"></a>
-<h4 class="subsection">5.3.1 Localizing the <samp>topbanner</samp> Image</h4>
+<h4 class="subsection">4.11.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="DOCF7" href="#FOOT7"><sup>7</sup></a>.
+Image). Don’t forget to save and <code>cvs add</code> the files<a
name="DOCF8" href="#FOOT8"><sup>8</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="FOOT7" href="#DOCF7">(7)</a></h3>
+<h3><a name="FOOT8" href="#DOCF8">(8)</a></h3>
<p>This
advice applies to all new files, of course.</p>
</div>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- trans-coord/manual gnun/gnun.dvi.gz gnun/gnun.h...,
Pavel Kharitonov <=