[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
trans-coord/manual gnun/gnun.dvi.gz gnun/gnun.h...
|
From: |
Pavel Kharitonov |
|
Subject: |
trans-coord/manual gnun/gnun.dvi.gz gnun/gnun.h... |
|
Date: |
Tue, 04 Dec 2012 16:24:30 +0000 |
CVSROOT: /web/trans-coord
Module name: trans-coord
Changes by: Pavel Kharitonov <ineiev> 12/12/04 16:24:29
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
GNU-News.html
GNUmakefile_002eteam-Variables.html
GNUmakefile_002eteam-and-Cron.html
GRACE.html Index.html Internals.html
Introduction.html Invoking-GNUN.html
Localized-URLs.html Main-Variables.html
Migrating.html
Modifying-Boilerplates.html
New-Translation.html Notes-Slot.html
Overview.html PO-Files-and-Team.html
PO-Files.html PO-Tips.html Rules.html
Runtime-Variables.html Scripts.html
Special-Targets.html
Splitting-Long-Passages.html Usage.html
Validation.html Webmaster-Tips.html
extra_002dtemplates.html
generic_002eLANG_002ehtml.html
gnun_002dadd_002dfuzzy_002ddiff.html
gnun_002dclear_002dprevious.html
gnun_002dinit_002dpo.html
gnun_002dmerge_002dpreconverted.html
gnun_002dpreconvert.html
gnun_002dvalidate_002dhtml.html
index.html languages_002etxt.html
mailfail.html no_002dgrace_002ditems.html
optional_002dtemplates.html report.html
sync.html triggers.html
update_002dlocalized_002dURLs.html
validate_002dall.html
validate_002dhtml_002dnotify.html
manual/web-trans: index.html web-trans.dvi.gz web-trans.html
web-trans.html.gz web-trans.html_node.tar.gz
web-trans.info.tar.gz web-trans.pdf
web-trans.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 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-Patch.html
Savannah-Projects.html
Savannah-Support.html
Savannah-Tasks.html
Savannah-VCS.html Savannah.html
Stepping-Down.html
Submitting-as-PO.html
Submitting-as-Plain-Text.html
Submitting.html Summary.html
Terminology.html Tracking-Tasks.html
Translation-Managers.html
Translation-Tips.html
Unreviewed-Translations.html
index.html topbanner.html
Log message:
Regenerate.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.dvi.gz?cvsroot=trans-coord&rev=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.html.gz?cvsroot=trans-coord&rev=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.html_node.tar.gz?cvsroot=trans-coord&rev=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.info.tar.gz?cvsroot=trans-coord&rev=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.pdf?cvsroot=trans-coord&rev=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.ps.gz?cvsroot=trans-coord&rev=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.texi.tar.gz?cvsroot=trans-coord&rev=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.txt?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/gnun.txt.gz?cvsroot=trans-coord&rev=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/index.html?cvsroot=trans-coord&r1=1.17&r2=1.18
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Advantages.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Bugs.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Comments-for-Translators.html?cvsroot=trans-coord&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Compendia.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Concepts.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Copying-This-Manual.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Credits-Slot.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Disadvantages.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GNU-News.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GNUmakefile_002eteam-Variables.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GNUmakefile_002eteam-and-Cron.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/GRACE.html?cvsroot=trans-coord&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Index.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Internals.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Introduction.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Invoking-GNUN.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Localized-URLs.html?cvsroot=trans-coord&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Main-Variables.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Migrating.html?cvsroot=trans-coord&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Modifying-Boilerplates.html?cvsroot=trans-coord&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/New-Translation.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Notes-Slot.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Overview.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/PO-Files-and-Team.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/PO-Files.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/PO-Tips.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Rules.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Runtime-Variables.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Scripts.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Special-Targets.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Splitting-Long-Passages.html?cvsroot=trans-coord&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Usage.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Validation.html?cvsroot=trans-coord&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/Webmaster-Tips.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/extra_002dtemplates.html?cvsroot=trans-coord&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/generic_002eLANG_002ehtml.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dadd_002dfuzzy_002ddiff.html?cvsroot=trans-coord&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dclear_002dprevious.html?cvsroot=trans-coord&r1=1.7&r2=1.8
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dinit_002dpo.html?cvsroot=trans-coord&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dmerge_002dpreconverted.html?cvsroot=trans-coord&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/gnun_002dpreconvert.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.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/index.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/languages_002etxt.html?cvsroot=trans-coord&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/mailfail.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/no_002dgrace_002ditems.html?cvsroot=trans-coord&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/optional_002dtemplates.html?cvsroot=trans-coord&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/report.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/sync.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/triggers.html?cvsroot=trans-coord&r1=1.14&r2=1.15
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/update_002dlocalized_002dURLs.html?cvsroot=trans-coord&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/validate_002dall.html?cvsroot=trans-coord&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/gnun/html_node/validate_002dhtml_002dnotify.html?cvsroot=trans-coord&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/index.html?cvsroot=trans-coord&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.dvi.gz?cvsroot=trans-coord&rev=1.11
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.html?cvsroot=trans-coord&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.html.gz?cvsroot=trans-coord&rev=1.11
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.html_node.tar.gz?cvsroot=trans-coord&rev=1.11
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.info.tar.gz?cvsroot=trans-coord&rev=1.11
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.pdf?cvsroot=trans-coord&rev=1.11
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.ps.gz?cvsroot=trans-coord&rev=1.11
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.texi.tar.gz?cvsroot=trans-coord&rev=1.11
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.txt?cvsroot=trans-coord&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.txt.gz?cvsroot=trans-coord&rev=1.11
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/CSS.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Capitalization.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Co_002dleaders.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Commits.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Copying-This-Manual.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Distribution-Terms.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Introduction.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Joining.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Leaders.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Leaving-A-Team.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Mailing-Lists.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Managing.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Members.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Migrating.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/New-Team.html?cvsroot=trans-coord&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Priorities.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/RTL.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Reports.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Review.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/SSI.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Bugs.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Homepage.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Mailing-Lists.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Members.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-News.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Patch.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Projects.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Support.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Tasks.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-VCS.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Stepping-Down.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Submitting-as-PO.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Submitting-as-Plain-Text.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Submitting.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Summary.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Terminology.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Tracking-Tasks.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Translation-Managers.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Translation-Tips.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Unreviewed-Translations.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/index.html?cvsroot=trans-coord&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/topbanner.html?cvsroot=trans-coord&r1=1.9&r2=1.10
Patches:
Index: gnun/gnun.dvi.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.dvi.gz,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
Binary files /tmp/cvsuVw3qk and /tmp/cvsIW8KJk differ
Index: gnun/gnun.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/gnun.html 26 Sep 2012 14:49:37 -0000 1.16
+++ gnun/gnun.html 4 Dec 2012 16:24:18 -0000 1.17
@@ -1,13 +1,7 @@
-<html lang="en">
-<head>
-<title>GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,235 +9,276 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled "GNU Free Documentation License."
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations</title>
+
+<meta name="description" content="GNUnited Nations">
+<meta name="keywords" content="GNUnited Nations">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="#Top" rel="start" title="Top">
+<link href="#Index" rel="index" title="Index">
+<link href="#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="dir.html#Top" rel="up" title="(dir)">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<h1 class="settitle">GNUnited Nations</h1>
- <div class="contents">
-<h2>Table of Contents</h2>
-<ul>
-<li><a name="toc_Top" href="#Top">GNUnited Nations</a>
-<li><a name="toc_Introduction" href="#Introduction">1 Introduction to GNUnited
Nations</a>
-<ul>
-<li><a href="#Overview">1.1 Why GNUN is Being Developed</a>
-<li><a href="#Concepts">1.2 What GNUnited Nations is and Should be</a>
-<li><a href="#Advantages">1.3 Major Advantages of GNUN</a>
-<li><a href="#Disadvantages">1.4 Known Bugs and Limitations</a>
-</li></ul>
-<li><a name="toc_Usage" href="#Usage">2 General Usage</a>
-<ul>
-<li><a href="#Invoking-GNUN">2.1 Invoking GNUN</a>
-<ul>
-<li><a href="#Runtime-Variables">2.1.1 Variables to Control the Build
Process</a>
-<li><a href="#Special-Targets">2.1.2 Targets Specified on the Command Line</a>
-<ul>
-<li><a href="#no_002dgrace_002ditems">2.1.2.1 The <code>no-grace-items</code>
Target</a>
-<li><a href="#update_002dlocalized_002dURLs">2.1.2.2 The
<code>update-localized-URLs</code> Target</a>
-<li><a href="#sync">2.1.2.3 The <code>sync</code> Target</a>
-<li><a href="#report">2.1.2.4 The <code>report</code> Target</a>
-<li><a href="#triggers">2.1.2.5 The <code>triggers</code> Target</a>
-<li><a href="#validate_002dall">2.1.2.6 The <code>validate-all</code>
Target</a>
-</li></ul>
-</li></ul>
-<li><a href="#Main-Variables">2.2 Defining Articles to be Built</a>
-<li><a href="#PO-Files">2.3 Working with PO Files</a>
-<ul>
-<li><a href="#New-Translation">2.3.1 Starting a New Translation</a>
-<ul>
-<li><a href="#Notes-Slot">2.3.1.1 The Special Slot for Translator's Notes</a>
-<li><a href="#Credits-Slot">2.3.1.2 The Special Slot for Translator's
Credits</a>
-</li></ul>
-<li><a href="#Migrating">2.3.2 Transforming Existing Translation in PO
Format</a>
-<li><a href="#GNU-News">2.3.3 Special Handling for GNU News</a>
-<li><a href="#PO-Tips">2.3.4 Useful Hints for Editing PO Files</a>
-<li><a href="#generic_002eLANG_002ehtml">2.3.5 The <samp><span
class="file">generic.</span><var>lang</var><span
class="file">.html</span></samp> File</a>
-<li><a href="#languages_002etxt">2.3.6 The <samp><span
class="file">languages.txt</span></samp> File</a>
-<li><a href="#PO-Files-and-Team">2.3.7 Maintaining Translations in Your Team's
Repository</a>
-<ul>
-<li><a href="#GNUmakefile_002eteam-Variables">2.3.7.1 Adopting <samp><span
class="file">GNUmakefile.team</span></samp> for a Specific Team</a>
-<li><a href="#GNUmakefile_002eteam-Variables">Targets in <samp><span
class="file">GNUmakefile.team</span></samp></a>
-<li><a href="#GNUmakefile_002eteam-and-Cron">2.3.7.2 Automatic Synchronization
and Status Reports</a>
-</li></ul>
-<li><a href="#Compendia">2.3.8 Using Compendia</a>
-</li></ul>
-<li><a href="#Webmaster-Tips">2.4 Tips and Hints for Webmasters</a>
-<ul>
-<li><a href="#Validation">2.4.1 Validation</a>
-<li><a href="#Comments-for-Translators">2.4.2 Comments for Translators</a>
-<li><a href="#Modifying-Boilerplates">2.4.3 Modifying Boilerplates</a>
-<li><a href="#Localized-URLs">2.4.4 Localized URLs</a>
-<li><a href="#Splitting-Long-Passages">2.4.5 Splitting Long Passages</a>
-</li></ul>
-</li></ul>
-<li><a name="toc_Internals" href="#Internals">3 Unexciting Information for
GNUN's Operation</a>
-<ul>
-<li><a href="#Scripts">3.1 GNUN Scripts</a>
-<ul>
-<li><a href="#make_002dprototype">3.1.1 The <samp><span
class="command">make-prototype</span></samp> Script</a>
-<li><a href="#gnun_002dadd_002dfuzzy_002ddiff">3.1.2 The <samp><span
class="command">gnun-add-fuzzy-diff</span></samp> Script</a>
-<li><a href="#gnun_002dinit_002dpo">3.1.3 The <samp><span
class="command">gnun-init-po</span></samp> Script</a>
-<li><a href="#gnun_002dpreconvert">3.1.4 The <samp><span
class="command">gnun-preconvert</span></samp> Script</a>
-<li><a href="#gnun_002dmerge_002dpreconverted">3.1.5 The <samp><span
class="command">gnun-merge-preconverted</span></samp> Script</a>
-<li><a href="#gnun_002dvalidate_002dhtml">3.1.6 The <samp><span
class="command">gnun-validate-html</span></samp> Script</a>
-<li><a href="#mailfail">3.1.7 The <samp><span
class="command">mailfail</span></samp> Script</a>
-<li><a href="#validate_002dhtml_002dnotify">3.1.8 The <samp><span
class="command">validate-html-notify</span></samp> Script</a>
-<li><a href="#gnun_002dclear_002dprevious">3.1.9 The <samp><span
class="command">gnun-clear-previous</span></samp> Script</a>
-</li></ul>
-<li><a href="#Rules">3.2 How The Recipes Work</a>
-</li></ul>
-<li><a name="toc_Bugs" href="#Bugs">4 Reporting Bugs</a>
-<li><a name="toc_Copying-This-Manual" href="#Copying-This-Manual">Appendix A
GNU Free Documentation License</a>
-<li><a name="toc_Index" href="#Index">Index</a>
-</li></ul>
-</div>
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+<h1 class="settitle" align="center">GNUnited Nations</h1>
-<div class="node">
-<a name="Top"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Introduction">Introduction</a>,
-Up: <a rel="up" accesskey="u" href="#dir">(dir)</a>
+
+<a name="SEC_Contents"></a>
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="no-bullet">
+ <li><a name="toc-Introduction-to-GNUnited-Nations" href="#Introduction">1
Introduction to GNUnited Nations</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Why-GNUN-is-Being-Developed" href="#Overview">1.1 Why
GNUN is Being Developed</a></li>
+ <li><a name="toc-What-GNUnited-Nations-is-and-Should-be"
href="#Concepts">1.2 What GNUnited Nations is and Should be</a></li>
+ <li><a name="toc-Major-Advantages-of-GNUN" href="#Advantages">1.3 Major
Advantages of GNUN</a></li>
+ <li><a name="toc-Known-Bugs-and-Limitations" href="#Disadvantages">1.4
Known Bugs and Limitations</a></li>
+ </ul></li>
+ <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>
+ <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>
+ </ul></li>
+ </ul></li>
+ <li><a name="toc-Defining-Articles-to-be-Built" href="#Main-Variables">2.2
Defining Articles to be Built</a></li>
+ <li><a name="toc-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>
+ <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>
+ </ul></li>
+ <li><a name="toc-Transforming-Existing-Translation-in-PO-Format"
href="#Migrating">2.3.2 Transforming Existing Translation in PO Format</a></li>
+ <li><a name="toc-Special-Handling-for-GNU-News" href="#GNU-News">2.3.3
Special Handling for GNU News</a></li>
+ <li><a name="toc-Useful-Hints-for-Editing-PO-Files"
href="#PO-Tips">2.3.4 Useful Hints for Editing PO Files</a></li>
+ <li><a name="toc-The-generic_002elang_002ehtml-File"
href="#generic_002eLANG_002ehtml">2.3.5 The
<samp>generic.<var>lang</var>.html</samp> File</a></li>
+ <li><a name="toc-The-languages_002etxt-File"
href="#languages_002etxt">2.3.6 The <samp>languages.txt</samp> File</a></li>
+ <li><a name="toc-Maintaining-Translations-in-Your-Team_0027s-Repository"
href="#PO-Files-and-Team">2.3.7 Maintaining Translations in Your Team’s
Repository</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Adopting-GNUmakefile_002eteam-for-a-Specific-Team"
href="#GNUmakefile_002eteam-Variables">2.3.7.1 Adopting
<samp>GNUmakefile.team</samp> for a Specific Team</a></li>
+ <li><a name="toc-Targets-in-GNUmakefile_002eteam"
href="#GNUmakefile_002eteam-Targets">2.3.7.2 Targets in
<samp>GNUmakefile.team</samp></a></li>
+ <li><a name="toc-Automatic-Synchronization-and-Status-Reports"
href="#GNUmakefile_002eteam-and-Cron">2.3.7.3 Automatic Synchronization and
Status Reports</a></li>
+ </ul></li>
+ <li><a name="toc-Using-Compendia" href="#Compendia">2.3.8 Using
Compendia</a></li>
+ </ul></li>
+ <li><a name="toc-Tips-and-Hints-for-Webmasters" href="#Webmaster-Tips">2.4
Tips and Hints for Webmasters</a>
+ <ul class="no-bullet">
+ <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>
+ </ul></li>
+ <li><a name="toc-Unexciting-Information-for-GNUN_0027s-Operation"
href="#Internals">3 Unexciting Information for GNUN’s Operation</a>
+ <ul class="no-bullet">
+ <li><a name="toc-GNUN-Scripts" href="#Scripts">3.1 GNUN Scripts</a>
+ <ul class="no-bullet">
+ <li><a name="toc-The-gnun_002dadd_002dfuzzy_002ddiff-Script"
href="#gnun_002dadd_002dfuzzy_002ddiff">3.1.1 The
<code>gnun-add-fuzzy-diff</code> Script</a></li>
+ <li><a name="toc-The-gnun_002ddiff_002dpo-Script"
href="#gnun_002ddiff_002dpo">3.1.2 The <code>gnun-diff-po</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dinit_002dpo-Script"
href="#gnun_002dinit_002dpo">3.1.3 The <code>gnun-init-po</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dpreconvert-Script"
href="#gnun_002dpreconvert">3.1.4 The <code>gnun-preconvert</code>
Script</a></li>
+ <li><a name="toc-The-gnun_002dmerge_002dpreconverted-Script"
href="#gnun_002dmerge_002dpreconverted">3.1.5 The
<code>gnun-merge-preconverted</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dreport-Script"
href="#gnun_002dreport">3.1.6 The <code>gnun-report</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dvalidate_002dhtml-Script"
href="#gnun_002dvalidate_002dhtml">3.1.7 The <code>gnun-validate-html</code>
Script</a></li>
+ <li><a name="toc-The-mailfail-Script" href="#mailfail">3.1.8 The
<code>mailfail</code> Script</a></li>
+ <li><a name="toc-The-validate_002dhtml_002dnotify-Script"
href="#validate_002dhtml_002dnotify">3.1.9 The
<code>validate-html-notify</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dclear_002dprevious-Script"
href="#gnun_002dclear_002dprevious">3.1.10 The <code>gnun-clear-previous</code>
Script</a></li>
+ </ul></li>
+ <li><a name="toc-How-The-Recipes-Work" href="#Rules">3.2 How The Recipes
Work</a></li>
+ </ul></li>
+ <li><a name="toc-Reporting-Bugs" href="#Bugs">4 Reporting Bugs</a></li>
+ <li><a name="toc-Index-1" href="#Index">Index</a></li>
+ <li><a name="toc-GNU-Free-Documentation-License"
href="#Copying-This-Manual">Appendix A GNU Free Documentation License</a></li>
+</ul>
</div>
-<h2 class="unnumbered">GNUnited Nations</h2>
-<p>This manual (updated 26 September 2012) is for GNUnited Nations (version
+
+<a name="Top"></a>
+<div class="header">
+<p>
+Next: <a href="#Introduction" accesskey="n" rel="next">Introduction</a>, Up:
<a href="dir.html#Top" accesskey="u" rel="up">(dir)</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="GNUnited-Nations"></a>
+<h1 class="top">GNUnited Nations</h1>
+
+<p>This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.<br>
- <pre class="sp">
-
-</pre>
-Copyright © 2008, 2009, 2010, 2011, 2012 Free Software
+</p><br>
+<p>Copyright © 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
-
- <blockquote>
-Permission is granted to copy, distribute and/or modify this document
+</p>
+<blockquote>
+<p>Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled “GNU Free
Documentation License.”
-</blockquote>
+</p></blockquote>
-<ul class="menu">
-<li><a accesskey="1" href="#Introduction">Introduction</a>: Overview
of GNUnited Nations.
-<li><a accesskey="2" href="#Usage">Usage</a>: Basic usage,
invocation and tips.
-<li><a accesskey="3" href="#Internals">Internals</a>: Dive into
GNUN.
-<li><a accesskey="4" href="#Bugs">Bugs</a>: How to report
bugs.
-<li><a accesskey="5" href="#Index">Index</a>
-<li><a accesskey="6" href="#Copying-This-Manual">Copying This Manual</a>: The
GNU Free Documentation License.
-</ul>
-<div class="node">
-<a name="Introduction"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Usage">Usage</a>,
-Previous: <a rel="previous" accesskey="p" href="#Top">Top</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#Introduction"
accesskey="1">Introduction</a>:</td><td> </td><td align="left"
valign="top">Overview of GNUnited Nations.
+</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.
+</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.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Index"
accesskey="5">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.
+</td></tr>
+</table>
+<hr>
+<a name="Introduction"></a>
+<div class="header">
+<p>
+Next: <a href="#Usage" accesskey="n" rel="next">Usage</a>, Previous: <a
href="#Top" accesskey="p" rel="previous">Top</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="Introduction-to-GNUnited-Nations"></a>
<h2 class="chapter">1 Introduction to GNUnited Nations</h2>
<p>GNUnited Nations (abbreviated GNUN) is a collection of makefiles and
scripts that are supposed to make the life of <a
href="http://gnu.org";>http://gnu.org</a>
translators easier. Although it is specifically developed for the GNU
-Project's website, it could be customized, at least in theory, to fit
+Project’s website, it could be customized, at least in theory, to fit
the needs of other internationalized sites. GNUN is in early stage of
development, but if it proves useful, and if there is sufficient
interest (and time), it is possible to develop a robust configuration
interface that would be appropriate for general usage.
-
- <p>It is vitally important to understand that GNUN is <em>not</em> a silver
+</p>
+<p>It is vitally important to understand that GNUN is <em>not</em> a silver
bullet that solves all problems. If we have to be honest, deploying
GNUN in fact even does create some (see <a
href="#Disadvantages">Disadvantages</a>).
-
- <p>GNUnited Nations is free software, available under the GNU General
+</p>
+<p>GNUnited Nations is free software, available under the GNU General
Public License.
-
- <p>This manual is organized in way that is suitable both for translators
+</p>
+<p>This manual is organized in way that is suitable both for translators
and GNU Web Translation managers (plus eventually interested GNU
Webmasters, if any). It may also serve as an introductory material and
reference for new GNUN developers and contributors. Hopefully, it might
be useful to people who customize and adopt the software for a third
party site or for their own needs. Feel free to skip sections or entire
chapters if they are irrelevant for your intended usage.
-
- <p>This manual is free documentation, and you can modify and redistribute
+</p>
+<p>This manual is free documentation, and you can modify and redistribute
it under the terms of the GNU Free Documentation License. See <a
href="#Copying-This-Manual">GNU Free Documentation License</a>.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#Overview"
accesskey="1">Overview</a>:</td><td> </td><td align="left"
valign="top">What is GNUN and why is necessary?
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Concepts"
accesskey="2">Concepts</a>:</td><td> </td><td align="left"
valign="top">Basic concepts and goals.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Advantages"
accesskey="3">Advantages</a>:</td><td> </td><td align="left"
valign="top">The goodness GNUN brings.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Disadvantages"
accesskey="4">Disadvantages</a>:</td><td> </td><td align="left"
valign="top">Staying on firm ground.
+</td></tr>
+</table>
-<ul class="menu">
-<li><a accesskey="1" href="#Overview">Overview</a>: What is GNUN
and why is necessary?
-<li><a accesskey="2" href="#Concepts">Concepts</a>: Basic concepts
and goals.
-<li><a accesskey="3" href="#Advantages">Advantages</a>: The goodness
GNUN brings.
-<li><a accesskey="4" href="#Disadvantages">Disadvantages</a>: Staying
on firm ground.
-</ul>
-
-<div class="node">
+<hr>
<a name="Overview"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Concepts">Concepts</a>,
-Up: <a rel="up" accesskey="u" href="#Introduction">Introduction</a>
-
+<div class="header">
+<p>
+Next: <a href="#Concepts" accesskey="n" rel="next">Concepts</a>, Up: <a
href="#Introduction" accesskey="u" rel="up">Introduction</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
-
+<a name="Why-GNUN-is-Being-Developed"></a>
<h3 class="section">1.1 Why GNUN is Being Developed</h3>
-<p>The GNU Project's website, <a
href="http://www.gnu.org";>http://www.gnu.org</a>, has become
+<p>The GNU Project’s website, <a
href="http://www.gnu.org";>http://www.gnu.org</a>, has become
considerably large over the years. Maintaining it requires significant
effort, and sometimes a new web standard is developed faster than the
time required to migrate all articles to the next widely adopted one.
-
- <p>When it comes to internationalization, the problems are so many that
+</p>
+<p>When it comes to internationalization, the problems are so many that
it is hard to enumerate them. It has become apparent that maintaining
translations up-to-date is a major undertaking, involving tedious
skimming through commit logs, reviewing diffs and other medieval
techniques to catch up. Some translation teams have developed their
own sets of scripts, but so far there has been no universal solution.
-
- <p>This unpleasant situation, combined with rapid and incompatible design
+</p>
+<p>This unpleasant situation, combined with rapid and incompatible design
changes, have lead some teams to neglect the important work of keeping
their translation in line with the changing original articles. As a
consequence, the GNU Project is facing the problem of maintaining them
in suboptimal ways, in order to keep the information updated.
-
- <p>The reasons for developing GNUnited Nations are very similar to those
+</p>
+<p>The reasons for developing GNUnited Nations are very similar to those
that lead to the inception of GNU gettext, or GNOME Documentation
Utilities (<code>gnome-doc-utils</code>) some years later.
-
-<div class="node">
+</p>
+<hr>
<a name="Concepts"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Advantages">Advantages</a>,
-Previous: <a rel="previous" accesskey="p" href="#Overview">Overview</a>,
-Up: <a rel="up" accesskey="u" href="#Introduction">Introduction</a>
-
+<div class="header">
+<p>
+Next: <a href="#Advantages" accesskey="n" rel="next">Advantages</a>, Previous:
<a href="#Overview" accesskey="p" rel="previous">Overview</a>, Up: <a
href="#Introduction" accesskey="u" rel="up">Introduction</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
-
+<a name="What-GNUnited-Nations-is-and-Should-be"></a>
<h3 class="section">1.2 What GNUnited Nations is and Should be</h3>
<p>The basic concept behind GNUN is that localization of HTML articles is
-similar to localization of computer programs<a rel="footnote" href="#fn-1"
name="fnd-1"><sup>1</sup></a>. In articles, like in programs, not every string
is considered
+similar to localization of computer programs<a name="DOCF1"
href="#FOOT1"><sup>1</sup></a>. In articles, like in programs, not every
string is considered
translatable, so translatable strings must be identified first, and then
collected in a file (called “PO template”) for translation.
Articles,
like programs, tend to change in time, but not every change in the
@@ -251,147 +286,139 @@
affect the translatable strings, but sometimes it does. So, translators
must have means to identify those changes and apply the appropriate
updates to the translation.
-
- <p>The GNU <code>gettext</code> package already provides the needed
-infrastructure for maintaining translations using PO files. See <a
href="gettext.html#Top">Introduction</a>, for a basic overview.
+</p>
+<p>The GNU <code>gettext</code> package already provides the needed
+infrastructure for maintaining translations using PO files. See <a
href="http://www.gnu.org/software/gettext/manual/gettext.html#Top";>Introduction</a>
in <cite>GNU gettext tools</cite>, for a basic overview.
GNUnited Nations fills the gaps to apply this infrastructure to articles
-in <a href="http://gnu.org";>http://gnu.org</a> web site.<a rel="footnote"
href="#fn-2" name="fnd-2"><sup>2</sup></a>
-
- <p>The following diagram summarizes the relation between the files handled
+in <a href="http://gnu.org";>http://gnu.org</a> web site.<a name="DOCF2"
href="#FOOT2"><sup>2</sup></a>
+</p>
+<p>The following diagram summarizes the relation between the files handled
by GNUN. It is followed by somewhat detailed explanations, which you
should read while keeping an eye on the diagram. Having a clear
understanding of these interrelations will surely help translators and
web maintainers.
-
-<pre class="example"> .---<--- * Original ARTICLE.html
- |
- | .---> ARTICLE.pot ---> * ARTICLE.LANG.po --->---.
- `---+ |
+</p>
+<div class="example">
+<pre class="example">.---<--- * Original ARTICLE.html
+|
+| .---> ARTICLE.pot ---> * ARTICLE.LANG.po --->---.
+`---+ |
`--->---. .------<----------------------------'
| |
| `---.
| +---> Translated ARTICLE.LANG.html
`-------'
-</pre>
- <p>The indication ‘<samp><span class="samp">*</span></samp>’
appears in two places in this picture, and means
+</pre></div>
+
+<p>The indication ‘<samp>*</samp>’ appears in two places in this
picture, and means
that the corresponding file is intended to be edited by humans. The
-author or web maintainer edits the original <samp><var>article</var><span
class="file">.html</span></samp>,
-and translators edit <samp><var>article</var><span
class="file">.</span><var>lang</var><span class="file">.po</span></samp>. All
other
+author or web maintainer edits the original
<samp><var>article</var>.html</samp>,
+and translators edit <samp><var>article</var>.<var>lang</var>.po</samp>. All
other
files are regenerated by GNUN and any manual changes on them will be
lost on the next run.
-
- <p>Arrows denote dependency relation between files, where a change in one
+</p>
+<p>Arrows denote dependency relation between files, where a change in one
file will affect the other. Those automatic changes will be applied by
-running ‘<samp><span class="samp">make -C
server/gnun</span></samp>’. This is the primary way to invoke
+running ‘<samp>make -C server/gnun</samp>’. This is the primary
way to invoke
GNUN, since it is implemented as a set of recipes for GNU <code>make</code>.
-
- <p>First, GNUN extracts all translatable strings from the original English
-article <samp><var>article</var><span class="file">.html</span></samp> into
<samp><var>article</var><span class="file">.pot</span></samp>. The
+</p>
+<p>First, GNUN extracts all translatable strings from the original English
+article <samp><var>article</var>.html</samp> into
<samp><var>article</var>.pot</samp>. The
resulted file is suitable for manipulation with the various GNU
-‘<samp><span class="samp">gettext</span></samp>’ utilities. It
contains all original article strings and
-all translations are set to empty. The letter <code>t</code> in <samp><span
class="file">.pot</span></samp>
+‘<samp>gettext</samp>’ utilities. It contains all original
article strings and
+all translations are set to empty. The letter <code>t</code> in
<samp>.pot</samp>
marks this as a Template PO file, not yet oriented towards any
particular language.
-
- <p>The first time though, there is no <samp><var>article</var><span
class="file">.</span><var>lang</var><span class="file">.po</span></samp>
-yet, so a translator must manually copy <samp><var>article</var><span
class="file">.pot</span></samp> to
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>, where <var>lang</var> represents the
+</p>
+<p>The first time though, there is no
<samp><var>article</var>.<var>lang</var>.po</samp>
+yet, so a translator must manually copy <samp><var>article</var>.pot</samp> to
+<samp><var>article</var>.<var>lang</var>.po</samp>, where <var>lang</var>
represents the
target language. See <a href="#New-Translation">New Translation</a>, for
details.
-
- <p>Then comes the initial translation of messages in
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>. Translation in itself is a whole
+</p>
+<p>Then comes the initial translation of messages in
+<samp><var>article</var>.<var>lang</var>.po</samp>. Translation in itself is
a whole
matter, whose complexity far overwhelms the level of this manual.
Nevertheless, a few hints are given in some other chapter of this
manual.
-
- <p>It is possible to make GNUN get translations for common strings from
+</p>
+<p>It is possible to make GNUN get translations for common strings from
dedicated PO files, so called compendia. See <a
href="#Compendia">Compendia</a>, for more
information.
+</p>
- <p>You may use any compatible PO editor to add translated messages into
-the PO file. See <a href="gettext.html#Editing">Editing</a>,
+<p>You may use any compatible PO editor to add translated messages into
+the PO file. See <a
href="http://www.gnu.org/software/gettext/manual/gettext.html#Editing";>Editing</a>
in <cite>GNU gettext tools</cite>,
for more information.
-
- <p>When the PO file actually exists (hopefully populated with initial
-translations), GNUN generates <samp><var>article</var><span
class="file">.</span><var>lang</var><span class="file">.html</span></samp>
file.
-It takes its structure from the original <samp><var>article</var><span
class="file">.html</span></samp>, but
+</p>
+<p>When the PO file actually exists (hopefully populated with initial
+translations), GNUN generates
<samp><var>article</var>.<var>lang</var>.html</samp> file.
+It takes its structure from the original <samp><var>article</var>.html</samp>,
but
all translatable strings are replaced with their translations specified
-in <samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>.
-
- <p>Original articles sometimes change. A new paragraph is being added or a
+in <samp><var>article</var>.<var>lang</var>.po</samp>.
+</p>
+<p>Original articles sometimes change. A new paragraph is being added or a
tiny change in the wording is introduced. Also, some articles are
dynamic in nature, like ones containing news entries or a list of other
articles. If the original article changes, GNUN will automatically
-rebuild <samp><var>article</var><span class="file">.pot</span></samp>, and
will merge the changes to
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>. Any outdated translations will be
+rebuild <samp><var>article</var>.pot</samp>, and will merge the changes to
+<samp><var>article</var>.<var>lang</var>.po</samp>. Any outdated translations
will be
marked as fuzzy, any new strings will be added with empty translations,
waiting to be translated. In the same run
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.html</span></samp> will be rebuilt so the relevant
+<samp><var>article</var>.<var>lang</var>.html</samp> will be rebuilt so the
relevant
strings in the translation will be substituted with the original English
text, until the translation teams update them in
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>.
-
- <p>Those changes in the original article that do not affect the
+<samp><var>article</var>.<var>lang</var>.po</samp>.
+</p>
+<p>Those changes in the original article that do not affect the
translatable strings will not lead to changes in
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>. Thus, no actions from translators
-will be needed. <samp><var>article</var><span
class="file">.</span><var>lang</var><span class="file">.html</span></samp> will
be
+<samp><var>article</var>.<var>lang</var>.po</samp>. Thus, no actions from
translators
+will be needed. <samp><var>article</var>.<var>lang</var>.html</samp> will be
automatically regenerated to reflect the changes.
+</p>
-<!-- FIXME: The following paragraphs should go to a separate section -->
-<!-- that explains those details like exact paths in www, diagram with -->
-<!-- the basic directory layout, additional files like .translinks, etc. -->
- <p>The POT for every article under GNUN's control is kept in the `www'
-repository under a special directory <samp><span
class="file">po/</span></samp>, which is a
-sub-directory of the relevant directory in the `www' tree. So, for
-<<code>http://www.gnu.org/philosophy/free-sw.html</code>> that is
-<samp><span class="file">philosophy/po/</span></samp>. Except <samp><span
class="file">free-sw.pot</span></samp>, this directory holds
-the canonical source of every translation, like <samp><span
class="file">free-sw.bg.po</span></samp>,
-<samp><span class="file">free-sw.ca.po</span></samp>, etc.
-
- <p>Several additional features are implemented, like automatic update of
+<p>The POT for every article under GNUN’s control is kept in the
‘www’
+repository under a special directory <samp>po/</samp>, which is a
+sub-directory of the relevant directory in the ‘www’ tree. So, for
+‘<code>http://www.gnu.org/philosophy/free-sw.html</code>’ that is
+<samp>philosophy/po/</samp>. Except <samp>free-sw.pot</samp>, this directory
holds
+the canonical source of every translation, like <samp>free-sw.bg.po</samp>,
+<samp>free-sw.ca.po</samp>, etc.
+</p>
+<p>Several additional features are implemented, like automatic update of
the list of the available translations. For example, if a new
-<samp><span class="file">free-sw.ja.po</span></samp> translation is added, the
list of translations
-included in <samp><span class="file">free-sw.html</span></samp> and all
translated
-<samp><span class="file">free-sw.</span><var>lang</var><span
class="file">.html</span></samp> is updated. This saves a lot of
+<samp>free-sw.ja.po</samp> translation is added, the list of translations
+included in <samp>free-sw.html</samp> and all translated
+<samp>free-sw.<var>lang</var>.html</samp> is updated. This saves a lot of
tedious, repetitive work and eliminates a source of mistakes. There
is a basic infrastructure to “inject” general information about a
translation team—like a note how to contact the team, or how to
-report a bug/suggestion for improvement. Translators' credits are
-also handled, as well as translators' notes, if any.
+report a bug/suggestion for improvement. Translators’ credits are
+also handled, as well as translators’ notes, if any.
+</p>
-<!-- ineiev: This passage carries no practically useful information -->
-<!-- for GNUN users; extensibility is a feature of any program, the plans -->
-<!-- seem too long-term. -->
-<!-- GNUN can be extended, and new features will certainly be added. The -->
-<!-- @file{TODO} file currently lists some of them, but new ideas pop up -->
-<!-- quite often. The plan is to make a solid foundation and develop -->
-<!-- front-ends-a web front-end, possibly based on Pootle, a statistics -->
-<!-- facility, probably a wiki compiler, and more. -->
-<div class="node">
+<hr>
<a name="Advantages"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Disadvantages">Disadvantages</a>,
-Previous: <a rel="previous" accesskey="p" href="#Concepts">Concepts</a>,
-Up: <a rel="up" accesskey="u" href="#Introduction">Introduction</a>
-
+<div class="header">
+<p>
+Next: <a href="#Disadvantages" accesskey="n" rel="next">Disadvantages</a>,
Previous: <a href="#Concepts" accesskey="p" rel="previous">Concepts</a>, Up: <a
href="#Introduction" accesskey="u" rel="up">Introduction</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
-
+<a name="Major-Advantages-of-GNUN"></a>
<h3 class="section">1.3 Major Advantages of GNUN</h3>
<p>Here is a simple list of situations where we hope this suite would
prove to be useful.
-
- <ul>
-<li>Automatic rebuild of all translations when the original article
+</p>
+<ul>
+<li> Automatic rebuild of all translations when the original article
changes. This is the most important feature, as it prevents
accumulation of seriously outdated translations.
- <li>Global update of the whole site. Apply the previous point to the web
-server templates (under <samp><span class="file">server/</span></samp> in the
`www' repository). A
+</li><li> Global update of the whole site. Apply the previous point to the web
+server templates (under <samp>server/</samp> in the ‘www’
repository). A
single change to such a file will affect literally <em>all</em>
articles, translated or not.
- <li>Urgent notices. Sometimes an “urgent” notice is added by
the
+</li><li> Urgent notices. Sometimes an “urgent” notice is added
by the
webmasters, which should appear on all pages. Typically this is about
an event where urgent action is needed, although often it is only
relevant to a single country or even a particular city. Such a notice
@@ -403,878 +430,974 @@
notice will appear in all translated pages and people who usually read
gnu.org pages in their native language will see it, so they can take
action as necessary. When the notice is removed, often in a week or
-two, it will disappear without translators' intervention, whether they
+two, it will disappear without translators’ intervention, whether they
translated it or not.
- <li>HTML validation. As a preliminary step, GNUN validates the English
+</li><li> HTML validation. As a preliminary step, GNUN validates the English
pages before updating the POT files, and the regenerated translations
before committing them. It often detects typos and other errors in
the markup.
- <li>Simplification of the translation process—lots of errors and
typos
+</li><li> Simplification of the translation process—lots of errors and
typos
come from the fact that translators basically have to duplicate the
whole HTML markup of the original. The PO files eliminate most of the
basic markup, which is where most of the validation errors come from.
- <li>Markup consistency site-wide—it would be substantially easier to
+</li><li> Markup consistency site-wide—it would be substantially easier
to
update the site to a future standard, because translations will
naturally follow the changes in the original articles. This also means
that translation teams do not have to undergo the boring process of
converting their articles to the new SSI-based layout; this will be done
automatically.
- <li>Easy updates by translators. Modified paragraphs, links, etc. will
+</li><li> Easy updates by translators. Modified paragraphs, links, etc. will
appear as “fuzzy” strings in the PO files, newly added ones will
appear as “untranslated”, and deleted will appear as
“obsolete”.
It is substantially easier to update a PO file, where a keystroke
takes you to the part that needs updating, whatever it may be.
- <li>Reporting and statistics. Since the basis is standard PO files, which
+</li><li> Reporting and statistics. Since the basis is standard PO files,
which
are the canonical source of the translations, it is easy to manipulate
them and extract useful information.
-</ul>
+</li></ul>
-<div class="node">
+<hr>
<a name="Disadvantages"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p"
href="#Advantages">Advantages</a>,
-Up: <a rel="up" accesskey="u" href="#Introduction">Introduction</a>
-
+<div class="header">
+<p>
+Previous: <a href="#Advantages" accesskey="p" rel="previous">Advantages</a>,
Up: <a href="#Introduction" accesskey="u" rel="up">Introduction</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
-
+<a name="Known-Bugs-and-Limitations"></a>
<h3 class="section">1.4 Known Bugs and Limitations</h3>
-<p>As it happens in real life, we don't wear pink glasses and are aware
+<p>As it happens in real life, we don’t wear pink glasses and are aware
of certain limitations and annoyances of this semi-automatic system.
+</p>
+<ul>
+<li> There is no easy way to preview the translations. The official build
+is invoked twice an hour, because doing it much more often is not
+feasible with current build server hardware. Additionally, any errors
+interrupt the build so they have to be fixed before the next articles
+are processed.
+</li></ul>
- <ul>
-<li>The official build is invoked thrice daily<a rel="footnote" href="#fn-3"
name="fnd-3"><sup>3</sup></a>, because doing it more often
-will potentially generate more messages to the mailing list in the form
-of commit notifications. This has its drawback, since translators have
-to wait 8 hours until their PO files are updated, and another period
-for the <samp><span class="file">.</span><var>lang</var><span
class="file">.html</span></samp> articles to get generated, after they
-commit the updated POs. Additionally, any errors interrupt the build so
-they have to be fixed before the next articles are processed.
-</ul>
-
-<div class="node">
+<hr>
<a name="Usage"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Internals">Internals</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Introduction">Introduction</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</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>
</div>
-
+<a name="General-Usage"></a>
<h2 class="chapter">2 General Usage</h2>
-<div align="right">If anything may go wrong, it will definitely go wrong.
- <p>—Murphy's Law
-
- <p>Murphy is an optimist.
- <p>—O'Rielly's Law
-</div>
-
- <pre class="sp">
-
-</pre>
+<p align="right">If anything may go wrong, it will definitely go wrong.
+—Murphy’s Law
+</p>
+<p align="right">Murphy is an optimist.
+—O’Rielly’s Law
+</p><br>
-GNUN currently consists of a few makefiles, scripts and optional
-<samp><span class="file">generic.</span><var>lang</var><span
class="file">.html</span></samp> files, intended to contain
+<p>GNUN currently consists of a few makefiles, scripts and optional
+<samp>generic.<var>lang</var>.html</samp> files, intended to contain
article-independent but team-specific information. They are designed
-to reside in the <samp><span class="file">server/gnun</span></samp> directory,
but this may change.
+to reside in the <samp>server/gnun</samp> directory, but this may change.
In all examples in this manual, “invoking” means executing on the
-command line <code>make -C server/gnun [</code><var>target</var><code>]
-[</code><var>variable</var><code>=</code><var>value</var><code> ...]</code>
while the working directory is
-the root in the `www' web repository. For the purpose of brevity, we
-will refer to the above command as simply <samp><span
class="command">make</span></samp>, which is
+command line <code>make -C server/gnun [<var>target</var>]
+[<var>variable</var>=<var>value</var> …]</code> while the working
directory is
+the root in the ‘www’ web repository. For the purpose of brevity,
we
+will refer to the above command as simply <code>make</code>, which is
equivalent to <code>cd server/gnun; make</code>. It is desirable never to
-invoke <samp><span class="command">make</span></samp> with the <samp><span
class="option">-k</span></samp> (<samp><span
class="option">--keep-going</span></samp>)
+invoke <code>make</code> with the <samp>-k</samp> (<samp>--keep-going</samp>)
option, because an eventual error in only one make recipe might create
a mess in many articles, both original and translated. Do this with
caution, and generally only when debugging in a safe environment.
-
- <p>The build process is intended to be invoked by a cron job, although
+</p>
+<p>The build process is intended to be invoked by a cron job, although
manual intervention to a certain degree is possible.
-
-<ul class="menu">
-<li><a accesskey="1" href="#Invoking-GNUN">Invoking GNUN</a>: How to
trigger a (re)build.
-<li><a accesskey="2" href="#Main-Variables">Main Variables</a>:
Specifying what to build.
-<li><a accesskey="3" href="#PO-Files">PO Files</a>: The gentle art
of editing PO files.
-<li><a accesskey="4" href="#Webmaster-Tips">Webmaster Tips</a>: The
webmaster's guide to GNUnited Nations'
+</p>
+<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.
+</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.
+</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.
-</ul>
+</td></tr>
+</table>
-<div class="node">
+<hr>
<a name="Invoking-GNUN"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Main-Variables">Main
Variables</a>,
-Up: <a rel="up" accesskey="u" href="#Usage">Usage</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>
</div>
-
+<a name="Invoking-GNUN-1"></a>
<h3 class="section">2.1 Invoking GNUN</h3>
+<a name="index-invoking"></a>
+<a name="index-invocation"></a>
+<a name="index-triggering_002c-build"></a>
+<a name="index-GNUmakefile"></a>
-<p><a name="index-invoking-1"></a><a name="index-invocation-2"></a><a
name="index-triggering_002c-build-3"></a><a name="index-GNUmakefile-4"></a>
-The central part of GNUnited Nations is a makefile; actually a
-<samp><span class="file">GNUmakefile</span></samp> since it heavily relies on
features and extensions
+<p>The central part of GNUnited Nations is a makefile; actually a
+<samp>GNUmakefile</samp> since it heavily relies on features and extensions
available in GNU Make. Thus, invoking a build consists of typing
-<samp><span class="command">make</span></samp> on the command line, or within
cron. If you are
+<code>make</code> on the command line, or within cron. If you are
deploying the software on a non-GNU machine, probably GNU Make is
-installed and available as <samp><span class="command">gmake</span></samp> or
<samp><span class="command">gnumake</span></samp>. If
+installed and available as <code>gmake</code> or <code>gnumake</code>. If
not, you should consider installing it, since the build will fail
otherwise. See <a
href="http://www.gnu.org/software/make";>http://www.gnu.org/software/make</a>
for information
how to download and install GNU Make.
-
- <p>If you don't specify a target, <samp><span
class="command">make</span></samp> by default builds the
+</p>
+<p>If you don’t specify a target, <code>make</code> by default builds the
target <code>all</code>, which in this case is to rebuild all translations
that are not up-to-date. However, there are special targets that do not
depend on the standard <code>all</code> target, which can be built by
-<code>make </code><var>target</var>. Some of the variables in the next section
+<code>make <var>target</var></code>. Some of the variables in the next section
apply to them, and some do not.
-
- <p><a name="index-config_002emk-5"></a><a name="index-gnun_002emk-6"></a><a
name="index-priorities_002emk-7"></a>Note that GNUN expects <samp><span
class="file">GNUmakefile</span></samp>, <samp><span
class="file">config.mk</span></samp> and
-<samp><span class="file">gnun.mk</span></samp> to be <em>present</em> under
<samp><span class="file">server/gnun</span></samp> of the
-`www' web repository, otherwise <samp><span class="command">make</span></samp>
has no way to know what
-and how should be built. Another file, <samp><span
class="file">priorities.mk</span></samp>, is
-expected to be present under <samp><span
class="file">server/gnun</span></samp> in order to define
+</p>
+<a name="index-config_002emk"></a>
+<a name="index-gnun_002emk"></a>
+<a name="index-priorities_002emk"></a>
+<p>Note that GNUN expects <samp>GNUmakefile</samp>, <samp>config.mk</samp> and
+<samp>gnun.mk</samp> to be <em>present</em> under <samp>server/gnun</samp> of
the
+‘www’ web repository, otherwise <code>make</code> has no way to
know what
+and how should be built. Another file, <samp>priorities.mk</samp>, is
+expected to be present under <samp>server/gnun</samp> in order to define
the priorities when reporting about the outdated translations. If
absent, the <code>report</code> target will not sort the translations by
priority. Since the location of the repository working
copy is strictly user-specific and cannot be determined in any way,
-<samp><span class="file">GNUmakefile</span></samp> and <samp><span
class="file">config.mk</span></samp> must be copied there manually
+<samp>GNUmakefile</samp> and <samp>config.mk</samp> must be copied there
manually
after the package installation. For convenience, these files are
-installed in ‘<samp><span
class="samp">$(pkgdatadadir)</span></samp>’ (<samp><span
class="file">/usr/local/share/gnun</span></samp> with
-the default ‘<samp><span class="samp">prefix</span></samp>’) so
you can just create symlinks pointing to
+installed in ‘<samp>$(pkgdatadadir)</samp>’
(<samp>/usr/local/share/gnun</samp> with
+the default ‘<samp>prefix</samp>’) so you can just create symlinks
pointing to
them, e.g.:
+</p>
+<div class="example">
+<pre class="example">ln -s /usr/local/share/gnun/config.mk
/path/to/www/server/gnun/
+ln -s /usr/local/share/gnun/GNUmakefile /path/to/www/server/gnun/
+</pre></div>
-<pre class="example"> ln -s /usr/local/share/gnun/config.mk
/path/to/www/server/gnun/
- ln -s /usr/local/share/gnun/GNUmakefile /path/to/www/server/gnun/
-</pre>
- <p>If next GNUN releases are installed with the same <samp><span
class="option">--prefix</span></samp>, you
+<p>If next GNUN releases are installed with the same <samp>--prefix</samp>, you
will always use the latest versions without the need for any manual
intervention.
-
- <p>If you are playing with non-gnu.org setup, you also have to take care of
-<samp><span class="file">gnun.mk</span></samp> and put a modified version
under <samp><span class="file">server/gnun</span></samp> of
+</p>
+<p>If you are playing with non-gnu.org setup, you also have to take care of
+<samp>gnun.mk</samp> and put a modified version under <samp>server/gnun</samp>
of
your hypothetical tree. (For gnu.org, that is not necessary since
-a proper <samp><span class="file">gnun.mk</span></samp> is maintained in
`www'.)
+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>
-<ul class="menu">
-<li><a accesskey="1" href="#Runtime-Variables">Runtime Variables</a>:
Variables to control the build process.
-<li><a accesskey="2" href="#Special-Targets">Special Targets</a>: Targets
that are not built by default.
-</ul>
-
-<div class="node">
+<hr>
<a name="Runtime-Variables"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Special-Targets">Special
Targets</a>,
-Up: <a rel="up" accesskey="u" href="#Invoking-GNUN">Invoking GNUN</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>
</div>
-
+<a name="Variables-to-Control-the-Build-Process"></a>
<h4 class="subsection">2.1.1 Variables to Control the Build Process</h4>
+<a name="index-variables"></a>
+<a name="index-variable_002c-behavior"></a>
-<p><a name="index-variables-8"></a><a
name="index-variable_002c-behavior-9"></a>
-The build process has several modes of operation, and they all relate to
+<p>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
performing certain sanity checks at build time. The variables are
-specified on the command line, after <samp><span
class="command">make</span></samp>, in the form
+specified on the command line, after <code>make</code>, in the form
<code>VARIABLE=value</code>, e.g. <code>make VCS=yes</code>. In the future,
additional features will be implemented in a similar fashion.
-
-
-<a name="index-VCS-10"></a>
-<a name="index-CVS-11"></a>
-<a name="index-Subversion-12"></a>
-<a name="index-SVN-13"></a>
-<a name="index-Bazaar-14"></a>
-<a name="index-bzr-15"></a>
-<dl><dt>‘<samp><span
class="samp">VCS=no</span></samp>’<dt>‘<samp><span
class="samp">...</span></samp>’<dd>
-Do not add any files to the repository. This is the default. You may
+</p>
+<dl compact="compact">
+<dd><a name="index-VCS"></a>
+<a name="index-CVS"></a>
+<a name="index-Subversion"></a>
+<a name="index-SVN"></a>
+<a name="index-Bazaar"></a>
+<a name="index-bzr"></a>
+</dd>
+<dt>‘<samp>VCS=no</samp>’</dt>
+<dt>‘<samp>…</samp>’</dt>
+<dd>
+<p>Do not add any files to the repository. This is the default. You may
as well omit to define <code>VCS</code> entirely; there is no special code
-that expects assigning the value `no'.
-
- <br><dt>‘<samp><span
class="samp">VCS=yes</span></samp>’<dd>Automatically add any new files in
the repository (CVS, Subversion or
+that expects assigning the value ‘no’.
+</p>
+</dd>
+<dt>‘<samp>VCS=yes</samp>’</dt>
+<dd><p>Automatically add any new files in the repository (CVS, Subversion or
GNU Bazaar—the repository type is auto-determined at build time,
-<samp><span class="command">bzr</span></samp> being a fallback).<a
rel="footnote" href="#fn-4" name="fnd-4"><sup>4</sup></a> These are
+<code>bzr</code> being a fallback).<a name="DOCF3"
href="#FOOT3"><sup>3</sup></a> These are
any POT files, if they are generated for the first time, and the
-translated articles (<samp><span class="file">.</span><var>lang</var><span
class="file">.html</span></samp>) in HTML format. In
-addition, if there is no <samp><span
class="file">server/gnun/generic.</span><var>lang</var><span
class="file">.html</span></samp> file
+translated articles (<samp>.<var>lang</var>.html</samp>) in HTML format. In
+addition, if there is no <samp>server/gnun/generic.<var>lang</var>.html</samp>
file
for the specific language an article is being generated, an empty file
will be added. Finally, any missing PO and their HTML counterparts of
the server templates will be added, computed on the basis of the
-<code>template-files</code> variable.
-
- <br><dt>‘<samp><span
class="samp">VCS=always</span></samp>’<dd>Because GNU Make considers the
targets up-to-date after a successful
+<code>extra-templates</code> and <code>optional-templates</code> variables.
+</p>
+</dd>
+<dt>‘<samp>VCS=always</samp>’</dt>
+<dd><p>Because GNU Make considers the targets up-to-date after a successful
build, if it was performed with no VCS interaction, the important newly
created files will not be added (and committed when you do
<code>cvs|svn|bzr commit</code>) in the repository. Assigning this value
enables additional check and forcefully adds all files. Use it
sparingly, since it is very slow and generally less reliable.
-
- <p><a name="index-VALIDATE-16"></a><a name="index-validation-17"></a><a
name="index-sanity-checks-18"></a><br><dt>‘<samp><span
class="samp">VALIDATE=no</span></samp>’<dt>‘<samp><span
class="samp">...</span></samp>’<dd>Does not perform validation of the
HTML articles and PO files. This
+</p>
+<a name="index-VALIDATE"></a>
+<a name="index-validation"></a>
+<a name="index-sanity-checks"></a>
+</dd>
+<dt>‘<samp>VALIDATE=no</samp>’</dt>
+<dt>‘<samp>…</samp>’</dt>
+<dd><p>Does not perform validation of the HTML articles and PO files. This
is the default, and not defining this variable has the same effect.
-
- <br><dt>‘<samp><span
class="samp">VALIDATE=yes</span></samp>’<dd>Validates all original
articles before generating the POTs, to ensure
+</p>
+</dd>
+<dt>‘<samp>VALIDATE=yes</samp>’</dt>
+<dd><p>Validates all original articles before generating the POTs, to ensure
that the ultimate source is valid (X)HMTL. Also, validates all
generated translations in HTML format and all PO files. It is highly
recommended to run the build this way, even if it is a bit tedious to
fix the errors that are reported as a result of enforcing validation.
-
- <p>Articles defined in the variable <code>no-validate-articles</code> are
never
+</p>
+<p>Articles defined in the variable <code>no-validate-articles</code> are never
checked for HTML validity. Its purpose was to skip validation of HTML
5 articles, until the command-line validation tools are updated to
parse files that comply with this new standard. As of version 0.5
GNUN supports HTML 5, so resorting to <code>no-validate-articles</code>
should not be necessary.
-
- <p><a name="index-NOTIFY-19"></a><a
name="index-mail_002c-notifications-20"></a><br><dt>‘<samp><span
class="samp">NOTIFY=no</span></samp>’<dt>‘<samp><span
class="samp">...</span></samp>’<dd>Do not send email notifications about
errors. This is the default.
-
- <br><dt>‘<samp><span
class="samp">NOTIFY=yes</span></samp>’<dd>If an error occurs, send a mail
with a meaningful subject and the error
+</p>
+<a name="index-NOTIFY"></a>
+<a name="index-mail_002c-notifications"></a>
+</dd>
+<dt>‘<samp>NOTIFY=no</samp>’</dt>
+<dt>‘<samp>…</samp>’</dt>
+<dd><p>Do not send email notifications about errors. This is the default.
+</p>
+</dd>
+<dt>‘<samp>NOTIFY=yes</samp>’</dt>
+<dd><p>If an error occurs, send a mail with a meaningful subject and the error
message as body to the concerned party. The variables
<code>devel-addr</code>, <code>web-addr</code> and <code>transl-addr</code>
control the
recipients; normally they should be set to the GNUN maintainers,
webmasters and translators accordingly. These variables are defined in
-the configuration file <samp><span class="file">gnun.conf</span></samp> and by
default are set to
+the configuration file <samp>gnun.conf</samp> and by default are set to
<a href="mailto:address@hidden";>address@hidden</a>.
-
- <p><a
name="index-new-translations_002c-notifications_002fannouncements-21"></a><a
name="index-announce-22"></a><br><dt>‘<samp><span
class="samp">ANNOUNCE=yes</span></samp>’<dd>If defined, automatic
announcements for new translations will be sent to
+</p>
+<a name="index-new-translations_002c-notifications_002fannouncements"></a>
+<a name="index-announce"></a>
+</dd>
+<dt>‘<samp>ANNOUNCE=yes</samp>’</dt>
+<dd><p>If defined, automatic announcements for new translations will be sent to
the address defined in the <code>ann-addr</code> variable (in
-<samp><span class="file">gnun.conf</span></samp>). The email messages contain
the translated article
+<samp>gnun.conf</samp>). The email messages contain the translated article
title as Subject, and the URL of the translation as its body. For the
official GNUN build, they are delivered to the
<a href="mailto:address@hidden";>address@hidden</a> mailing list and each
language has its
-own Mailman <dfn>topic</dfn>. It is possible to subscribe to the list and
-receive only traffic related to a specific language. See <a
href="web-trans.html#Mailing-Lists">Mailing Lists</a>.
-
- <p>The default behavior is not to send such announcements.
-
- <p><a name="index-VERBOSE-23"></a><a
name="index-output_002c-detailed-24"></a><br><dt>‘<samp><span
class="samp">VERBOSE=yes</span></samp>’<dd>If defined, the value of the
variables <code>templates-translated</code>,
-<code>home-translated</code>, <code>ALL_POTS</code>,
<code>articles-translated</code> and
+own Mailman <em>topic</em>. It is possible to subscribe to the list and
+receive only traffic related to a specific language. See <a
href="http://www.gnu.org/software/trans-coord/manual/web-trans/web-trans.html#Mailing-Lists";>Mailing
+Lists</a> in <cite>GNU Web Translators Manual</cite>.
+</p>
+<p>The default behavior is not to send such announcements.
+</p>
+<a name="index-VERBOSE"></a>
+<a name="index-output_002c-detailed"></a>
+</dd>
+<dt>‘<samp>VERBOSE=yes</samp>’</dt>
+<dd><p>If defined, the value of the variables
<code>templates-translated</code>,
+<code>ALL_POTS</code>, <code>articles-translated</code> and
<code>gnunews</code> will be printed to the standard output. This is off by
default, but recommended in general since it will show a bug in the
computation of the basic variables.
-
- <p><a name="index-GRACE-25"></a><a name="index-fuzzy-strings-26"></a><a
name="index-grace-period-27"></a><a
name="index-deferred-generation-of-articles-28"></a><a
name="GRACE"></a><br><dt>‘<samp><span
class="samp">GRACE=</span><var>days</var></samp>’<dd>If defined, ordinary
articles that have fuzzy strings and are not older
+</p>
+<a name="index-GRACE"></a>
+<a name="index-fuzzy-strings"></a>
+<a name="index-grace-period"></a>
+<a name="index-deferred-generation-of-articles"></a>
+<a name="GRACE"></a></dd>
+<dt>‘<samp>GRACE=<var>days</var></samp>’</dt>
+<dd><p>If defined, ordinary articles that have fuzzy strings and are not older
than <var>days</var> will not be regenerated. This functionality is
implemented specifically to prevent gratuitous replacement of translated
strings with the English text when there are only minor formatting
changes in the original. The translator has time (the “grace”
period
as defined in this variable) to review the changes and unfuzzy the
strings, while keeping the online translation intact. Note that this
-variable has no effect on the homepage, the server templates, gnunews
+variable has no effect on the server templates, gnunews
and all articles defined in the variable <code>no-grace-articles</code>.
-
- <p><a name="index-OUTDATED_002dGRACE-29"></a><br><dt>‘<samp><span
class="samp">OUTDATED-GRACE=</span><var>days</var></samp>’<dd>Grace
period for the out-of-date notice. When the variable
+</p>
+<a name="index-OUTDATED_002dGRACE"></a>
+</dd>
+<dt>‘<samp>OUTDATED-GRACE=<var>days</var></samp>’</dt>
+<dd><p>Grace period for the out-of-date notice. When the variable
<code>GRACE</code> is defined, <code>OUTDATED-GRACE</code> defaults to 60 days
(see <a href="#GRACE">grace period</a>). The out-of-date notice is a special
-text (<samp><span class="file">server/outdated.html</span></samp> in the `www'
repository) that is
+text (<samp>server/outdated.html</samp> in the ‘www’ repository)
that is
inserted into every outdated translation when the period defined in
this variable is over; its purpose is to inform the reader that the
translation may not correspond to the original English article.
-
- <p><a name="index-TEAM-30"></a><a
name="index-variable_002c-team-31"></a><br><dt>‘<samp><span
class="samp">TEAM=</span><var>lang</var></samp>’<dd>The translation team
whose articles need to be checked for
+</p>
+<a name="index-TEAM"></a>
+<a name="index-variable_002c-team"></a>
+</dd>
+<dt>‘<samp>TEAM=<var>lang</var></samp>’</dt>
+<dd><p>The translation team whose articles need to be checked for
completeness. This variable is applicable only for the <code>report</code>
target, and is mandatory for it. See <a href="#report">report</a>.
+</p>
+</dd>
+</dl>
- </dl>
-
- <p>Note that <code>VCS=yes,always</code> is a valid combination: because POT
+<p>Note that <code>VCS=yes,always</code> is a valid combination: because POT
files of the server templates are not handled by <code>always</code>, running
the build this way will commit any newly added files as specified in
<code>TEMPLATE_LINGUAS</code> and will perform additional check at the end,
<code>cvs|svn|bzr add</code>-ing all necessary files.
-
- <p><a name="index-validation-32"></a>When validation is enabled (i.e. with
<code>VALIDATE=yes</code>), the
+</p>
+<a name="index-validation-1"></a>
+<p>When validation is enabled (i.e. with <code>VALIDATE=yes</code>), the
original English articles are validated first, before any commands
-that generate the other files, and <samp><span
class="command">make</span></samp> exits with an error
+that generate the other files, and <code>make</code> exits with an error
on the first encountered article. This is done on purpose, to prevent
the propagation of an eventual error in the markup of the original
article to all translations.
-
- <p>Validation of the translated <samp><span
class="file">.</span><var>lang</var><span class="file">.html</span></samp> is
+</p>
+<p>Validation of the translated <samp>.<var>lang</var>.html</samp> is
performed after it is preliminarily generated as a temporary file.
When no errors are found, the translation is updated; otherwise
the real file is not changed (and it is not added if absent)—the build
will fail and further processing of the remaining articles will not be
performed. The translator has time
until the next run to fix the error—usually by modifying the
-corresponding <samp><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp> file.
-
- <p>If notification is enabled (<code>NOTIFY=yes</code>), and the build
system
+corresponding <samp>.<var>lang</var>.po</samp> file.
+</p>
+<p>If notification is enabled (<code>NOTIFY=yes</code>), and the build system
encounters errors (mostly when validating articles), email messages
will be sent to the party that is expected to fix the error. The
subject of the messages always includes the problematic article, for
example:
+</p>
+<div class="example">
+<pre class="example">Subject: [GNUN Error] gnu/gnu.fa.html is not valid HTML
+</pre></div>
-<pre class="example"> Subject: [GNUN Error] gnu/gnu.fa.html is not valid
HTML
-</pre>
- <div class="node">
+<hr>
<a name="Special-Targets"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p"
href="#Runtime-Variables">Runtime Variables</a>,
-Up: <a rel="up" accesskey="u" href="#Invoking-GNUN">Invoking GNUN</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>
</div>
-
+<a name="Targets-Specified-on-the-Command-Line"></a>
<h4 class="subsection">2.1.2 Targets Specified on the Command Line</h4>
<p>Some targets are not built by default, because they are only useful
under certain circumstances. Think of them like semi-automated
commands or canned command sequences that are more complicated, and
more importantly, whose arguments are variables computed at the time
-<samp><span class="command">make</span></samp> reads the makefiles—the
filesets they affect are
+<code>make</code> reads the makefiles—the filesets they affect are
specific and already defined, one way or another.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#no_002dgrace_002ditems"
accesskey="1">no-grace-items</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#update_002dlocalized_002dURLs"
accesskey="2">update-localized-URLs</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#sync"
accesskey="3">sync</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#report"
accesskey="4">report</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#triggers"
accesskey="5">triggers</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#validate_002dall"
accesskey="6">validate-all</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+</table>
-<ul class="menu">
-<li><a accesskey="1" href="#no_002dgrace_002ditems">no-grace-items</a>
-<li><a accesskey="2"
href="#update_002dlocalized_002dURLs">update-localized-URLs</a>
-<li><a accesskey="3" href="#sync">sync</a>
-<li><a accesskey="4" href="#report">report</a>
-<li><a accesskey="5" href="#triggers">triggers</a>
-<li><a accesskey="6" href="#validate_002dall">validate-all</a>
-</ul>
-
-<div class="node">
-<a name="no-grace-items"></a>
+<hr>
<a name="no_002dgrace_002ditems"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#update_002dlocalized_002dURLs">update-localized-URLs</a>,
-Up: <a rel="up" accesskey="u" href="#Special-Targets">Special Targets</a>
-
+<div class="header">
+<p>
+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>
-
-<h5 class="subsubsection">2.1.2.1 The <code>no-grace-items</code> Target</h5>
+<a name="The-no_002dgrace_002ditems-Target"></a>
+<h4 class="subsubsection">2.1.2.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 homepage, the
+that are not affected by the grace period, namely, the
server templates, gnunews, and all articles defined in the variable
<code>no-grace-articles</code> (see <a href="#GRACE">grace period</a>).
-
- <p>This target can be rebuilt more often than <code>all</code>; it is
invoked
-hourly by the official GNUN cron job.
-
-<div class="node">
-<a name="update-localized-URLs"></a>
+</p>
+<p>This target can be rebuilt more often than <code>all</code>; however, it is
+currently not used.
+</p>
+<hr>
<a name="update_002dlocalized_002dURLs"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#sync">sync</a>,
-Previous: <a rel="previous" accesskey="p"
href="#no_002dgrace_002ditems">no-grace-items</a>,
-Up: <a rel="up" accesskey="u" href="#Special-Targets">Special Targets</a>
-
+<div class="header">
+<p>
+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>
-
-<h5 class="subsubsection">2.1.2.2 The <code>update-localized-URLs</code>
Target</h5>
+<a name="The-update_002dlocalized_002dURLs-Target"></a>
+<h4 class="subsubsection">2.1.2.2 The <code>update-localized-URLs</code>
Target</h4>
<p>The <code>update-localized-URLs</code> target invokes a script that
-generates the <samp><span class="file">localized-urls.mk</span></samp> file.
This file includes the
+generates the <samp>localized-urls.mk</samp> file. This file includes the
list of URLs that should be localized, it is extracted from special
comments in the HTML source (see <a href="#Localized-URLs">Localized URLs</a>).
-
- <p>This target is meant to be rebuilt nightly.
-
-<div class="node">
+</p>
+<p>This target is meant to be rebuilt nightly.
+</p>
+<hr>
<a name="sync"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#report">report</a>,
-Previous: <a rel="previous" accesskey="p"
href="#update_002dlocalized_002dURLs">update-localized-URLs</a>,
-Up: <a rel="up" accesskey="u" href="#Special-Targets">Special Targets</a>
-
-</div>
-
-<h5 class="subsubsection">2.1.2.3 The <code>sync</code> Target</h5>
+<div class="header">
+<p>
+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>
+<a name="index-synchronization_002c-repository"></a>
-<p><a name="index-synchronization_002c-repository-33"></a>
-The <code>sync</code> target has a simple task: synchronize the
+<p>The <code>sync</code> target has a simple task: synchronize the
<em>original English</em> articles from a canonical repository, like
-`www'. It is very important that such synchronization happens,
+‘www’. It is very important that such synchronization happens,
because it is desirable to develop the software and add more features
-in a testbed, while the `official instance' operates on the official
+in a testbed, while the ‘official instance’ operates on the
official
repository in a predictable way.
-
- <p>It is recommended that you `build' the <code>sync</code> target from a
cron
+</p>
+<p>It is recommended that you ‘build’ the <code>sync</code> target
from a cron
job, some time before the general build occurs. That way,
-prerequisites (e.g. original <samp><span class="file">.html</span></samp>
articles) will be updated
-from the canonical repository and the subsequent <samp><span
class="command">make</span></samp>
+prerequisites (e.g. original <samp>.html</samp> articles) will be updated
+from the canonical repository and the subsequent <code>make</code>
invocation, possibly run by cron as well, will update all
translations.
-
- <p>The <code>VCS</code> variable affects the behavior: if it is defined to
-`yes' then the synchronized files are committed to the `testing'
+</p>
+<p>The <code>VCS</code> variable affects the behavior: if it is defined to
+‘yes’ then the synchronized files are committed to the
‘testing’
repository, i.e. the <var>destination</var>. In addition, if a file meant
to be synchronized disappeared from the <var>source</var>, a warning mail
will be sent to the address defined in the <code>devel-addr</code> variable
-(defined in <samp><span class="file">gnun.conf</span></samp>). The build will
continue without
+(defined in <samp>gnun.conf</samp>). The build will continue without
failure, and will sync and commit all other files, but will send the
same email message again if the file is still present in the
<code>files-to-sync</code> variable during a subsequent invocation.
-
- <p>In addition, <code>sync</code> synchronizes all “verbatim”
server templates
-that are not under GNUN's control, such as <samp><span
class="file">server/header.html</span></samp>,
-<samp><span class="file">server/banner.html</span></samp>, <samp><span
class="file">server/footer.html</span></samp> and their
+</p>
+<p>In addition, <code>sync</code> synchronizes all “verbatim”
server templates
+that are not under GNUN’s control, such as
<samp>server/header.html</samp>,
+<samp>server/banner.html</samp>, <samp>server/footer.html</samp> and their
translations, as defined in the <code>verbatim-templates</code> variable.
This is important, as these files may change in the master repository,
while the validation of the HTML files in the development repository
will be performed with the old templates expanded, thus making this
specific test more or less bogus.
-
- <p><code>VCS=always</code> has no effect on this target, as well as
+</p>
+<p><code>VCS=always</code> has no effect on this target, as well as
<code>VALIDATE</code>.
-
-<div class="node">
+</p>
+<hr>
<a name="report"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#triggers">triggers</a>,
-Previous: <a rel="previous" accesskey="p" href="#sync">sync</a>,
-Up: <a rel="up" accesskey="u" href="#Special-Targets">Special Targets</a>
-
-</div>
+<div class="header">
+<p>
+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>
+<a name="index-reporting"></a>
+<a name="index-status_002c-translations"></a>
-<h5 class="subsubsection">2.1.2.4 The <code>report</code> Target</h5>
-
-<p><a name="index-reporting-34"></a><a
name="index-status_002c-translations-35"></a>
-This target exists solely for convenience to translators, enabling them
+<p>This target exists solely for convenience to translators, enabling them
to check which articles are not 100% translated and have to be updated.
-The way to check this is by running <code>make report
TEAM=</code><var>lang</var>,
+The way to check this is by running <code>make report
TEAM=<var>lang</var></code>,
where <var>lang</var> is the language code, as usual. Thus, to check all
French translations, one would run
+</p>
+<div class="example">
+<pre class="example">make report TEAM=fr
+</pre></div>
-<pre class="example"> make report TEAM=fr
-</pre>
- <p>This target checks only the PO files; the old translations that haven't
+<p>This target checks only the PO files; the old translations that
haven’t
been converted to PO files are reported, but there is no reasonable way
to check if they are up-to-date. In fact, this is one of the main
reasons GNUN is being developed, if you recall.
-
- <p><a name="index-priorities_002emk-36"></a>When present, <samp><span
class="file">priorities.mk</span></samp> defines four classes of articles by
+</p>
+<a name="index-priorities_002emk-1"></a>
+<p>When present, <samp>priorities.mk</samp> defines four classes of articles by
priority: <var>priority-articles</var> for the most important translations,
<var>important-articles</var> for the second priority level,
<var>important-directories</var> for the directories with important articles;
all other translations are reported as less important.
-
-<div class="node">
+</p>
+<p>There is also a script, <code>gnun-report</code>, to generate HTML reports.
+See <a href="#gnun_002dreport">gnun-report</a>.
+</p>
+<hr>
<a name="triggers"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#validate_002dall">validate-all</a>,
-Previous: <a rel="previous" accesskey="p" href="#report">report</a>,
-Up: <a rel="up" accesskey="u" href="#Special-Targets">Special Targets</a>
-
+<div class="header">
+<p>
+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>
-
-<h5 class="subsubsection">2.1.2.5 The <code>triggers</code> Target</h5>
+<a name="The-triggers-Target"></a>
+<h4 class="subsubsection">2.1.2.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>.
+</p>
-<!-- FIXME: Check how Subversion behaves with keywords and update the -->
-<!-- paragraph below. -->
-<!-- ineiev: In fact, "the result" is _not_ "checked in" the repository. -->
-<!-- When a GNUN build completes and some translations fail at the HTML -->
-<!-- validation stage, the result is checked in the repository, as -->
-<!-- explained earlier (@pxref{Runtime Variables}). Thus, CVS updates the -->
-<!-- @w{$}Date$ RCS keyword (or any other keywords, for that matter) and -->
-<!-- resets the file(s) timestamp. Next time @command{make} is invoked, -->
-<!-- the target appears newer than the prerequisite so no rebuild is -->
-<!-- triggered. The purpose of the @code{triggers} target is to ``save'' -->
-<!-- the information of the faulty targets during the main build, and to -->
-<!-- touch their prerequisites in order such invalid articles not to remain -->
-<!-- online unnoticed. -->
- <p>The <code>triggers</code> target currently executes the files named
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.html.hook</span></samp> in the <samp><span
class="file">server/gnun</span></samp>
+<p>The <code>triggers</code> target currently executes the files named
+<samp><var>article</var>.<var>lang</var>.html.hook</samp> in the
<samp>server/gnun</samp>
directory—these files are created during the main build and each of
them contains the command to update the timestamp of the prerequisite
based on the timestamp of the target that must be rebuilt. Finally, it
-deletes all those <samp><span class="file">*.hook</span></samp> files.
-
- <p>This is the rule that takes care of actually sending the
+deletes all those <samp>*.hook</samp> files.
+</p>
+<p>This is the rule that takes care of actually sending the
announcements if <code>ANNOUNCE=yes</code>. Since it is a completely valid
scenario to have a new translation which is initially invalid HTML,
the canned command sequence for announcements is recorded in
-<samp><span class="file">*.hook-ann</span></samp> files, and they are treated
by <code>triggers</code> in a
-different way. A newly added <samp><span
class="file">.</span><var>lang</var><span class="file">.po</span></samp> file
may be
+<samp>*.hook-ann</samp> files, and they are treated by <code>triggers</code>
in a
+different way. A newly added <samp>.<var>lang</var>.po</samp> file may be
invalid, in which case the HTML file is not added, and it is not
appropriate to announce it as a new translation as it is completely
useless for the
general public. The <code>triggers</code> rule detects this case, and
postpones the announcement to the next build attempt, when the
generated HTML translation is supposed to be human-readable.
-
- <p>To summarize, for effective operation GNUN should be invoked
-automatically as <code>make; cvs|svn|bzr commit -m ...; make
+</p>
+<p>To summarize, for effective operation GNUN should be invoked
+automatically as <code>make; cvs|svn|bzr commit -m …; make
triggers</code>. To illustrate this, here is a concrete example showing the
official job running at fencepost.gnu.org:
-
-<pre class="example"> 25 4,12,20 * * * cd $HOME/projects/www; cvs -q
update &>/dev/null; \
+</p>
+<div class="example">
+<pre class="example">25 4,12,20 * * * cd $HOME/projects/www; cvs -q update
&>/dev/null; \
make -j1 -C server/gnun VCS=yes VALIDATE=yes; \
NOTIFY=yes VERBOSE=yes GRACE=5000; ANNOUNCE=yes; \
cvs commit -m \
- "Automatic update by GNUnited Nations."; \
+ "Automatic update by GNUnited Nations."; \
make -C server/gnun triggers
-</pre>
- <p>The above example is for CVS; if the underlying repository is
+</pre></div>
+
+<p>The above example is for CVS; if the underlying repository is
Subversion, they need to be amended accordingly. If it is GNU Bzr,
-remember to add a <samp><span class="command">bzr push</span></samp> after
commit (in the usual
+remember to add a <code>bzr push</code> after commit (in the usual
scenario), otherwise changes will be committed only locally. Since a
distributed Version Control System can be used in multiple (sometimes
radically different) ways, this step cannot be anticipated and therefore
-cannot be automated. Adding the <samp><span
class="command">push</span></samp> command in the makefile
+cannot be automated. Adding the <code>push</code> command in the makefile
rules would not work if a so called “bound branch” is used, for
instance.
-
- <p>In the future, this target may be extended further to do other useful
+</p>
+<p>In the future, this target may be extended further to do other useful
things that should be “triggered” after the main build.
-
-<div class="node">
-<a name="validate-all"></a>
+</p>
+<hr>
<a name="validate_002dall"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#triggers">triggers</a>,
-Up: <a rel="up" accesskey="u" href="#Special-Targets">Special Targets</a>
+<div class="header">
+<p>
+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>
+<a name="index-validation-2"></a>
-</div>
-
-<h5 class="subsubsection">2.1.2.6 The <code>validate-all</code> Target</h5>
-
-<p><a name="index-validation-37"></a>
-The <code>validate-all</code> target validates all HTML pages under GNUN's
-control. It is needed because GNUN doesn't track dependencies on the
+<p>The <code>validate-all</code> target validates all HTML pages under
GNUN’s
+control. It is needed because GNUN doesn’t track dependencies on the
included files, so errors in those included files could pass unnoticed.
-
- <p>This target is invoked once a day by the official GNUN cron job.
-
-<div class="node">
+</p>
+<p>This target is invoked once a day by the official GNUN cron job.
+</p>
+<hr>
<a name="Main-Variables"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#PO-Files">PO Files</a>,
-Previous: <a rel="previous" accesskey="p" href="#Invoking-GNUN">Invoking
GNUN</a>,
-Up: <a rel="up" accesskey="u" href="#Usage">Usage</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>
</div>
-
+<a name="Defining-Articles-to-be-Built"></a>
<h3 class="section">2.2 Defining Articles to be Built</h3>
+<a name="index-variables-1"></a>
+<a name="index-gnun_002emk-1"></a>
-<p><a name="index-variables-38"></a><a name="index-gnun_002emk-39"></a>
-The file <samp><span class="file">gnun.mk</span></samp> contains variable
definitions, based on which
+<p>The file <samp>gnun.mk</samp> contains variable definitions, based on which
almost all other important variables are computed. In other words,
the variables defined in that file directly affect the overall
behavior of the build process.
-
- <p>There are two types of variables, which are specifically separated in
-order to make translators' life easier: variables that translators are
+</p>
+<p>There are two types of variables, which are specifically separated in
+order to make translators’ life easier: variables that translators are
free to modify and variables that are modified by the web-translators
-staff<a rel="footnote" href="#fn-5" name="fnd-5"><sup>5</sup></a>, ideally
after performing some local tests. A
+staff<a name="DOCF4" href="#FOOT4"><sup>4</sup></a>, ideally after performing
some local tests. A
translation team leader should update only <code>FUZZY_DIFF_LINGUAS</code>,
-<code>TEMPLATE_LINGUAS</code> and
-<code>HOME_LINGUAS</code>; everything else is supposed to be built
+<code>TEMPLATE_LINGUAS</code>; everything else is supposed to be built
automagically, without manual intervention. If not, that is a bug that
should be reported and fixed.
-
-
-<a name="index-TEMPLATE_005fLINGUAS-40"></a>
-<a name="index-templates_002c-defining-41"></a>
-<a name="index-defining-templates-42"></a>
-<dl><dt>‘<samp><span
class="samp">TEMPLATE_LINGUAS</span></samp>’<dd>A space-separated list
with languages. Add here your language code
+</p>
+<dl compact="compact">
+<dd><a name="index-TEMPLATE_005fLINGUAS"></a>
+<a name="index-templates_002c-defining"></a>
+<a name="index-defining-templates"></a>
+</dd>
+<dt>‘<samp>TEMPLATE_LINGUAS</samp>’</dt>
+<dd><p>A space-separated list with languages. Add here your language code
<em>if and only if</em> you have all the SSI templates translated, and
-have already committed all <a name="hardcoded-templates"></a>template files:
-
- <ul>
-<li><samp><span
class="file">server/po/head-include-2.</span><var>lang</var><span
class="file">.po</span></samp>
-<li><samp><span
class="file">server/po/body-include-1.</span><var>lang</var><span
class="file">.po</span></samp>
-<li><samp><span
class="file">server/po/body-include-2.</span><var>lang</var><span
class="file">.po</span></samp>
-<li><samp><span class="file">server/po/footer-text.</span><var>lang</var><span
class="file">.po</span></samp>
-<li><samp><span class="file">server/po/outdated.</span><var>lang</var><span
class="file">.po</span></samp>,
-</ul>
-
- <p>as well as the templates that are not under GNUN's control and are
+have already committed all template files listed in
+the <code>extra-templates</code> variable in <samp>server/gnun/gnun.mk</samp>,
+as well as the templates that are not under GNUN’s control and are
translated manually, like
+</p>
+<ul class="no-bullet">
+<li>- <samp>server/header.<var>lang</var>.html</samp>
+</li><li>- <samp>server/head-include-1.<var>lang</var>.html</samp>
+</li><li>- <samp>server/html5-header.<var>lang</var>.html</samp>
+</li><li>- <samp>server/html5-head-include-1.<var>lang</var>.html</samp>
+</li><li>- <samp>server/banner.<var>lang</var>.html</samp>
+</li><li>- <samp>server/footer.<var>lang</var>.html</samp>.
+</li></ul>
- <ul>
-<li><samp><span class="file">server/header.</span><var>lang</var><span
class="file">.html</span></samp>
-<li><samp><span class="file">server/head-include-1.</span><var>lang</var><span
class="file">.html</span></samp>
-<li><samp><span class="file">server/html5-header.</span><var>lang</var><span
class="file">.html</span></samp>
-<li><samp><span
class="file">server/html5-head-include-1.</span><var>lang</var><span
class="file">.html</span></samp>
-<li><samp><span class="file">server/banner.</span><var>lang</var><span
class="file">.html</span></samp>
-<li><samp><span class="file">server/footer.</span><var>lang</var><span
class="file">.html</span></samp>.
-</ul>
-
- <p><a name="index-extra_002dtemplates-43"></a><a
name="index-templates_002c-additional-44"></a><a
name="index-defining-templates-45"></a><a
name="extra_002dtemplates"></a><br><dt>‘<samp><span
class="samp">extra-templates</span></samp>’<dd>
-The <var>extra-templates</var> variable lists additional templates under GNUN
+<a name="index-extra_002dtemplates"></a>
+<a name="index-templates_002c-additional"></a>
+<a name="index-defining-templates-1"></a>
+<a name="extra_002dtemplates"></a></dd>
+<dt>‘<samp>extra-templates</samp>’</dt>
+<dd>
+<p>The <code>extra-templates</code> variable lists templates under GNUN
control; they are rebuilt from corresponding
-<var>template</var>.<var>lang</var>.po files like those hardcoded in
GNUmakefile
-(see <a href="#hardcoded-templates">hardcoded templates</a>);
+<var>template</var>.<var>lang</var>.po files;
when the <var>template</var>.<var>lang</var>.po file is absent, GNUN
initializes
and commits a file with empty <code>msgstr</code>s.
-
- <p><a name="index-optional_002dtemplates-46"></a><a
name="index-templates_002c-optional-47"></a><a
name="index-defining-templates-48"></a><a
name="optional_002dtemplates"></a><br><dt>‘<samp><span
class="samp">optional-templates</span></samp>’<dd>
-The <var>optional-templates</var> variable defines optional templates under
+</p>
+<a name="index-optional_002dtemplates"></a>
+<a name="index-templates_002c-optional"></a>
+<a name="index-defining-templates-2"></a>
+<a name="optional_002dtemplates"></a></dd>
+<dt>‘<samp>optional-templates</samp>’</dt>
+<dd>
+<p>The <code>optional-templates</code> variable defines optional templates
under
GNUN control. Those are the templates of low priority items, like news
lines included in some pages. They are managed like the additional
templates listed in the <var>extra-templates</var> variable, except
+</p>
+<ul class="no-bullet">
+<li>- <var>template</var>.<var>lang</var>.po is not added when absent, and
+</li><li>- their POTs end in <code>.pot.opt</code> rather than
<code>.pot</code>.
+</li></ul>
- <ul>
-<li><var>template</var>.<var>lang</var>.po is not added when absent, and
-<li>their POTs end in <code>.pot.opt</code> rather than <code>.pot</code>.
-</ul>
-
- <p>This way, the scripts reporting outdated translations and translations
-that hasn't been converted to PO files won't complain about them unless
+<p>This way, the scripts reporting outdated translations and translations
+that hasn’t been converted to PO files won’t complain about them
unless
the team decides to actually commit <var>template</var>.<var>lang</var>.po.
-
- <p><a name="index-FUZZY_005fDIFF_005fLINGUAS-49"></a><a
name="index-previous_002c-diff-50"></a><br><dt>‘<samp><span
class="samp">FUZZY_DIFF_LINGUAS</span></samp>’<dd>Add your language code
here if you want GNUN to add differences to
+</p>
+<a name="index-FUZZY_005fDIFF_005fLINGUAS"></a>
+<a name="index-previous_002c-diff"></a>
+</dd>
+<dt>‘<samp>FUZZY_DIFF_LINGUAS</samp>’</dt>
+<dd><p>Add your language code here if you want GNUN to add differences to
previous <code>msgid</code>s in your PO files. The differences are shown in
-the default <samp><span class="command">wdiff</span></samp> format. See <a
href="wdiff.html#wdiff">wdiff</a>, for more information.
-
- <p><a name="index-HOME_005fLINGUAS-51"></a><a
name="index-homepage_002c-defining-52"></a><a
name="index-defining-homepage-53"></a><br><dt>‘<samp><span
class="samp">HOME_LINGUAS</span></samp>’<dd>Add your language code if you
have already committed
-<samp><span class="file">po/home.</span><var>lang</var><span
class="file">.po</span></samp>, that way the homepage for your language
-will be built. It is not acceptable to have your language code
-defined in this variable, but not in <code>TEMPLATE_LINGUAS</code>.
-
- <p><a name="index-ROOT-54"></a><a
name="index-articles-in-root-directory_002c-defining-55"></a><a
name="index-defining-articles-in-the-root-dir-56"></a><br><dt>‘<samp><span
class="samp">ROOT</span></samp>’<dd>Add here articles that are in the
server root, like
-<samp><span class="file">keepingup.html</span></samp> and <samp><span
class="file">provide.html</span></samp>. Always write only the
+the default <code>wdiff</code> format. See <a
href="http://www.gnu.org/software/wdiff/manual/wdiff.html#wdiff";>The word
+difference finder</a> in <cite>GNU wdiff</cite>, for more information.
+</p>
+<a name="index-ROOT"></a>
+<a name="index-articles-in-root-directory_002c-defining"></a>
+<a name="index-defining-articles-in-the-root-dir"></a>
+</dd>
+<dt>‘<samp>ROOT</samp>’</dt>
+<dd><p>Add here articles that are in the server root, like
<samp>home.html</samp>,
+<samp>keepingup.html</samp> and <samp>provide.html</samp>. Always write only
the
basename of the article, i.e. if you add these two articles, the value
of <code>ROOT</code> should be <code>keepingup provide</code>. This is true
for
all the variables that expect values in the form of article names.
-
- <p><a name="index-ALL_005fDIRS-57"></a><a
name="index-directories_002c-defining-58"></a><a
name="index-defining-directories-59"></a><br><dt>‘<samp><span
class="samp">ALL_DIRS</span></samp>’<dd>The list of directories
containing articles, like <samp><span class="file">philosophy</span></samp>,
-<samp><span class="file">gnu</span></samp>, <samp><span
class="file">licenses</span></samp>, etc.
-
- <p><a
name="index-POT-generation_002c-articles-60"></a><br><dt>‘<samp><span
class="samp">gnu</span></samp>’<dt>‘<samp><span
class="samp">philosophy</span></samp>’<dt>‘<samp><span
class="samp">...directory...</span></samp>’<dd>A space-separated list of
basenames for articles residing in
+</p>
+<a name="index-ALL_005fDIRS"></a>
+<a name="index-directories_002c-defining"></a>
+<a name="index-defining-directories"></a>
+</dd>
+<dt>‘<samp>ALL_DIRS</samp>’</dt>
+<dd><p>The list of directories containing articles, like
<samp>philosophy</samp>,
+<samp>gnu</samp>, <samp>licenses</samp>, etc.
+</p>
+<a name="index-POT-generation_002c-articles"></a>
+</dd>
+<dt>‘<samp>gnu</samp>’</dt>
+<dt>‘<samp>philosophy</samp>’</dt>
+<dt>‘<samp>…directory…</samp>’</dt>
+<dd><p>A space-separated list of basenames for articles residing in
<var>directory</var>, for which POTs will be generated and updated when the
original article changes. If an article is missing here, there is no
way its translations to be maintained via GNUN.
+</p></dd>
</dl>
-<div class="node">
+<hr>
<a name="PO-Files"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Webmaster-Tips">Webmaster
Tips</a>,
-Previous: <a rel="previous" accesskey="p" href="#Main-Variables">Main
Variables</a>,
-Up: <a rel="up" accesskey="u" href="#Usage">Usage</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>
</div>
-
+<a name="Working-with-PO-Files"></a>
<h3 class="section">2.3 Working with PO Files</h3>
+<a name="index-PO_002c-editing"></a>
-<p><a name="index-PO_002c-editing-61"></a>
-We anticipate that some gnu.org translators will find this format odd
+<p>We anticipate that some gnu.org translators will find this format odd
or inconvenient, if they never happened to work with PO files before.
-Don't worry, you will soon get accustomed to it. It is the
+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>The most efficient way to edit a PO file is using a specialized PO
+</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:
-
-
-<a name="index-PO-editors-62"></a>
-<ul><li>PO mode. We recommend using GNU Emacs in PO mode, because Emacs is
+</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><span class="file">.po</span></samp> file you
visit should automatically
+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
-<RET></code>. On some GNU/Linux distros such as gNewSense, PO mode is
+<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>Gtranslator—the GNOME PO editor. See
+</li><li> Gtranslator—the GNOME PO editor. See
<a
href="http://projects.gnome.org/gtranslator/";>http://projects.gnome.org/gtranslator/</a>.
- <li>Lokalize—the KDE 4 editor. See
+</li><li> Lokalize—the KDE 4 editor. See
<a
href="http://userbase.kde.org/Lokalize";>http://userbase.kde.org/Lokalize</a>.
- <li>KBabel—the KDE 3 editor. No longer supported, but might be
+</li><li> KBabel—the KDE 3 editor. No longer supported, but might be
available on some old systems.
- <li>Poedit—another popular editor that is based on the
<code>wxWidgets</code>
+</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>Virtaal—a relevantly new editor that supports also the XLIFF
format
+</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><!-- @heresy -->
-<!-- Please forgive them, they don't know what they are doing... -->
-po.vim—ftplugin for the Vim editor. The best option for people who
+</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>.
-<!-- @end heresy -->
- <li>Various web-based editors. See <a
href="web-trans.html#Savannah-VCS">Savannah VCS</a>.
-</ul>
+</li><li> Various web-based editors. See <a
href="http://www.gnu.org/software/trans-coord/manual/web-trans/web-trans.html#Savannah-VCS";>Savannah
VCS</a> in <cite>GNU Web
+Translators Manual</cite>.
+</li></ul>
-<ul class="menu">
-<li><a accesskey="1" href="#New-Translation">New Translation</a>: How to
start a new translation.
-<li><a accesskey="2" href="#Migrating">Migrating</a>: How to
migrate an existing translation to a PO
- format under GNUN's control.
-<li><a accesskey="3" href="#GNU-News">GNU News</a>: How to handle
``whatsnew'' (a.k.a. ``gnunews'').
-<li><a accesskey="4" href="#PO-Tips">PO Tips</a>: Tips and hints
for translators.
-<li><a accesskey="5" href="#generic_002eLANG_002ehtml">generic.LANG.html</a>:
Specifying information that will propagate in
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#New-Translation"
accesskey="1">New Translation</a>:</td><td> </td><td align="left"
valign="top">How to start a new translation.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Migrating"
accesskey="2">Migrating</a>:</td><td> </td><td align="left"
valign="top">How to migrate an existing translation to a PO
+ format under GNUN’s control.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#GNU-News" accesskey="3">GNU
News</a>:</td><td> </td><td align="left" valign="top">How to handle
“whatsnew” (a.k.a. “gnunews”).
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#PO-Tips" accesskey="4">PO
Tips</a>:</td><td> </td><td align="left" valign="top">Tips and hints
for translators.
+</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.
-<li><a accesskey="6" href="#languages_002etxt">languages.txt</a>:
Specifying canonical names for languages.
-<li><a accesskey="7" href="#PO-Files-and-Team">PO Files and Team</a>: How
to maintain translations in the team's
+</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="#PO-Files-and-Team"
accesskey="7">PO Files and Team</a>:</td><td> </td><td align="left"
valign="top">How to maintain translations in the team’s
repository.
-<li><a accesskey="8" href="#Compendia">Compendia</a>: Using
translation memory.
-
- </ul>
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Compendia"
accesskey="8">Compendia</a>:</td><td> </td><td align="left"
valign="top">Using translation memory.
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+</pre></th></tr></table>
-<div class="node">
+<hr>
<a name="New-Translation"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Migrating">Migrating</a>,
-Up: <a rel="up" accesskey="u" href="#PO-Files">PO Files</a>
-
+<div class="header">
+<p>
+Next: <a href="#Migrating" accesskey="n" rel="next">Migrating</a>, Up: <a
href="#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</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>
-<p><a name="index-translation_002c-new-63"></a><a
name="index-new-translation-64"></a>
-To start a new translation, the most simple way is to copy the
-existing POT as <samp><span class="file">article.</span><var>lang</var><span
class="file">.po</span></samp>, where <var>lang</var> is your
+<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.</code><var>lang</var><code>.po</code> and then edit the latter. If
-<samp><span class="file">free-sw.pot</span></samp> does not exist it is
because either the article is
+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><span class="file">server/gnun/gnun.mk</span></samp>. In
that case, just ask them
+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>You could also use the <samp><span class="command">msginit</span></samp>
utility that would populate
+</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="gettext.html#msginit-Invocation">msginit Invocation</a>.
-
- <p>GNUN also provides a customized script to automatically fill more
+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>The PO file header as generated usually looks like this:
-
-<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>
- <p>You have to edit the header to match the already established
+<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-65"></a>
- <dl>
-<dt>‘<samp><span
class="samp">Project-Id-Version</span></samp>’<dd>Add here the filename
of the original article, without the
+</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”.
-
- <br><dt>‘<samp><span
class="samp">POT-Creation-Date</span></samp>’<dd>Do not edit this field,
it is already set when the POT is created.
-
- <br><dt>‘<samp><span
class="samp">PO-Revision-Date</span></samp>’<dd>Likewise, do not edit.
This field is automatically filled in when you
+</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.
-
- <br><dt>‘<samp><span
class="samp">Last-Translator</span></samp>’<dd>The name and email address
of the last translator who has edited the
+</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:
-
- <pre class="example"> Elvis Parsley <address@hidden>
-</pre>
- <br><dt>‘<samp><span
class="samp">Language-Team</span></samp>’<dd>This field should contain
the mailing list on which the translation
-team can be reached—usually <a
href="mailto:address@hidden";>www-LANG-<small
class="dots">...</small>@gnu.org</a>.
+</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:
-
- <pre class="example"> Czech <address@hidden>
-</pre>
- <br><dt>‘<samp><span
class="samp">MIME-Version</span></samp>’<dd>Leave it like it is.
-
- <br><dt>‘<samp><span
class="samp">Content-Type</span></samp>’<dd>Usually this is
<code>text/plain; charset=UTF-8</code>; change the charset
+</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.
-
- <br><dt>‘<samp><span
class="samp">Content-Transfer-Encoding</span></samp>’<dd>Set this to
<code>8bit</code>. Note that the PO file header ends with this
-field, and it should contain a newline (‘<samp><span
class="samp">\n</span></samp>’). Unfortunately, some
+</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.
+the file is automatically modified by GNUN’s rules.
+</p></dd>
</dl>
- <p>Here is an example of a properly edited header:
+<p>Here is an example of a properly edited header:
+</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>
-<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>
- <p>Notice the absence of the “fuzzy” marker; you should
“unfuzzy” the
+<p>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).
-
- <p>It is recommended that you wrap all lines in the comments to be less
+simply pressing <tt class="key">TAB</tt> in PO mode).
+</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><span
class="file">GNUmakefile.team</span></samp>'s <code>publish</code>
+and improves the performance of <samp>GNUmakefile.team</samp>’s
<code>publish</code>
rule (see <a href="#GNUmakefile_002eteam-Variables">GNUmakefile.team
Variables</a>).
-
- <p>There are some special messages that appear in the POT and PO:
-
-
-<a name="index-notes_002c-translators-66"></a>
-<a name="index-translators_0027-notes-67"></a>
-<dl><dt>‘<samp><span class="samp">*GNUN-SLOT: TRANSLATOR'S
NOTES*</span></samp>’<dd>This is for translator's notes that are injected
in the resulting
+</p>
+<p>There are some special messages that appear in the POT and PO:
+</p>
+<dl compact="compact">
+<dd><a name="index-notes_002c-translators"></a>
+<a name="index-translators_0027-notes"></a>
+</dd>
+<dt>‘<samp>*GNUN-SLOT: TRANSLATOR'S NOTES*</samp>’</dt>
+<dd><p>This is for translator’s notes that are injected in the resulting
translation. See <a href="#Notes-Slot">Notes Slot</a>, for more information.
If your
translation does not have notes, you <em>must</em> translate this as a
-space, that is, <SPC>.
-
- <p><a name="index-credits_002c-translators-68"></a><a
name="index-translators_0027-credits-69"></a><br><dt>‘<samp><span
class="samp">*GNUN-SLOT: TRANSLATOR'S CREDITS*</span></samp>’<dd>This is
again optional, and should contain the name (and address) of
+space, that is, <tt class="key">SPC</tt>.
+</p>
+<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 (<SPC>) if you do not want your name to appear there.
+space (<tt class="key">SPC</tt>) if you do not want your name to appear there.
See <a href="#Credits-Slot">Credits Slot</a>.
+</p></dd>
</dl>
- <p><a name="index-wrapping-long-lines-70"></a><a
name="index-long-lines_002c-wrap-71"></a>Most of the PO editors do not wrap
long lines that inevitably appear in
+<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
</code><var>file</var><code>.po
-</code><var>file</var><code>.po</code>, before installing it in the
repository. Either way, the
+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>For those lucky Emacs users, here is a code snippet that you can put
-in your <samp><span class="file">.emacs</span></samp>; doing <kbd>M-x
po-wrap</kbd> while in PO mode will
+</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:
-
-<pre class="lisp"> (defun po-wrap ()
- "Filter current po-mode buffer through `msgcat' tool to wrap all 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*")))
+ (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)))
+ "msgcat" nil tmp-buf t (shell-quote-argument
tmp-file)))
(let ((saved (point))
(inhibit-read-only t))
(delete-region (point-min) (point-max))
@@ -1284,128 +1407,134 @@
(error (buffer-string)))))
(kill-buffer tmp-buf)
(delete-file tmp-file)))))
-</pre>
- <p>It is highly desirable that you check if the PO file you finished
+</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 </code><var>file</var> or by simply
+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
+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>
-<ul class="menu">
-<li><a accesskey="1" href="#Notes-Slot">Notes Slot</a>: How to
handle translator's notes.
-<li><a accesskey="2" href="#Credits-Slot">Credits Slot</a>:
Translator's credits.
-</ul>
-
-<div class="node">
+<hr>
<a name="Notes-Slot"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Credits-Slot">Credits Slot</a>,
-Up: <a rel="up" accesskey="u" href="#New-Translation">New Translation</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>
+</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>
-</div>
-
-<h5 class="subsubsection">2.3.1.1 The Special Slot for Translator's Notes</h5>
-
-<p><a name="index-notes_002c-translators-72"></a><a
name="index-translators_0027-notes-73"></a>
-Sometimes it is necessary to complement the translation of an essay
-with translator's notes. The special message <code>*GNUN-SLOT:
+<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 (<SPC>)—otherwise the PO file will
be
+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:
+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>
-<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>
- <p>Certainly, everything in the <code>msgstr</code>s should be in your
native
+<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><span
class="samp">TransNote2</span></samp>’, ‘<samp><span
class="samp">TransNote3</span></samp>’, etc. and
+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>Do not worry about the <code>\n</code> character—it is inserted
-automatically when you press <RET>. It is not compulsory that
+</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>It is important to follow this specification, because notes will look
+</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
+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.
-
-<div class="node">
+</p>
+<hr>
<a name="Credits-Slot"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Notes-Slot">Notes
Slot</a>,
-Up: <a rel="up" accesskey="u" href="#New-Translation">New Translation</a>
-
-</div>
-
-<h5 class="subsubsection">2.3.1.2 The Special Slot for Translator's
Credits</h5>
+<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><a name="index-credits_002c-translators-74"></a><a
name="index-translators_0027-credits-75"></a>
-Most of the translators usually put their name under the translation,
+<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>Like the previous slot, you should “translate” it as a
<SPC> if
-you don't want your name to appear there.
-
- <p>Here is an example of the recommended way to specify credits:
-
-<pre class="example"> <b>Traduction</b>: Benjamin Drieu
- <a
href="mailto:address@hidden">&lt;address@hidden&gt;</a>,
- 2007, 2008.
-</pre>
- <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,
+<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.
-
-<div class="node">
+</p>
+<hr>
<a name="Migrating"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#GNU-News">GNU News</a>,
-Previous: <a rel="previous" accesskey="p" href="#New-Translation">New
Translation</a>,
-Up: <a rel="up" accesskey="u" href="#PO-Files">PO Files</a>
-
+<div class="header">
+<p>
+Next: <a href="#GNU-News" accesskey="n" rel="next">GNU News</a>, Previous: <a
href="#New-Translation" accesskey="p" rel="previous">New Translation</a>, Up:
<a href="#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
-
+<a name="Transforming-Existing-Translation-in-PO-Format"></a>
<h4 class="subsection">2.3.2 Transforming Existing Translation in PO
Format</h4>
+<a name="index-migration_002c-translations"></a>
+<a name="index-conversion-of-existing-translations"></a>
-<p><a name="index-migration_002c-translations-76"></a><a
name="index-conversion-of-existing-translations-77"></a>
-Migrating an existing translation to a PO file format is basically
+<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>Typically, you will visit <samp><span
class="file">po/foo.</span><var>lang</var><span class="file">.po</span></samp>
(in PO mode) and
-<samp><span class="file">foo.</span><var>lang</var><span
class="file">.html</span></samp> (in HTML mode) in another buffer. Then you
+</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
@@ -1417,128 +1546,130 @@
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>There is also a semi-automatic way to produce an initial PO file. You
-checkout the revision of the English page, <samp><span
class="file">foo.html</span></samp>, that
+</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><span class="file">foo.</span><var>lang</var><span
class="file">.html</span></samp>. Then you run <samp><span
class="command">gnun-preconvert</span></samp>
-which invokes <samp><span class="command">po4a-gettextize</span></samp> (See
<a href="#gnun_002dpreconvert">gnun-preconvert</a>.):
+<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>
-<pre class="example"> gnun-preconvert foo.lang.html foo.html
-</pre>
- <p>If some passages in <samp><span
class="file">foo.</span><var>lang</var><span class="file">.html</span></samp>
don't match the structure
-of <samp><span class="file">foo.html</span></samp>, error messages will be
displayed. Check them,
+<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
-<samp><span class="command">gnun-merge-preconverted</span></samp> (See <a
href="#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a>.):
+<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>
-<pre class="example"> gnun-merge-preconverted -C compendium.lang.po
foo.lang.po foo.pot
-</pre>
- <p>If you have no compendium, just omit the “<code>-C
+<p>If you have no compendium, just omit the “<code>-C
compendium.lang.po</code>” part.
-
- <p>You get <samp><span class="file">foo.</span><var>lang</var><span
class="file">.po</span></samp> where all messages are marked as
+</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>There is no need to delete the existing HTML translation, GNUN will
+</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>When an essay has been translated by several people through the years,
+</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>A recommended way to do this is as follows:
-
-<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>
- <p>In this example, it is clear that Cédric made the initial
+<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.
-
-<div class="node">
+</p>
+<hr>
<a name="GNU-News"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#PO-Tips">PO Tips</a>,
-Previous: <a rel="previous" accesskey="p" href="#Migrating">Migrating</a>,
-Up: <a rel="up" accesskey="u" href="#PO-Files">PO Files</a>
-
+<div class="header">
+<p>
+Next: <a href="#PO-Tips" accesskey="n" rel="next">PO Tips</a>, Previous: <a
href="#Migrating" accesskey="p" rel="previous">Migrating</a>, Up: <a
href="#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
-
+<a name="Special-Handling-for-GNU-News"></a>
<h4 class="subsection">2.3.3 Special Handling for GNU News</h4>
+<a name="index-gnunews"></a>
+<a name="index-whatsnew"></a>
+<a name="index-gnusflashes"></a>
-<p><a name="index-gnunews-78"></a><a name="index-whatsnew-79"></a><a
name="index-gnusflashes-80"></a>
-<strong>Pay attention:</strong> The practice of news handling that is
+<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>The GNU website has infrastructure for supporting “What's
New”, also
+</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><span class="file">server/whatsnew.txt</span></samp> and are used
to build
-<samp><span class="file">server/whatsnew.include</span></samp> and <samp><span
class="file">gnusflashes.include</span></samp>. The
-former is used by <samp><span class="file">server/whatsnew.html</span></samp>,
while the latter is
+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>GNUN has additional rules for building <samp><span
class="file">whatsnew.pot</span></samp>, which
+</p>
+<p>GNUN has additional rules for building <samp>whatsnew.pot</samp>, which
contains a combination of all necessary strings for
-<samp><span class="file">server/whatsnew.</span><var>lang</var><span
class="file">.html</span></samp>,
-<samp><span class="file">server/whatsnew.</span><var>lang</var><span
class="file">.include</span></samp> and
-<samp><span class="file">gnusflashes.</span><var>lang</var><span
class="file">.include</span></samp>. There is nothing unusual in this
+<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><span class="file">whatsnew.</span><var>lang</var><span
class="file">.po</span></samp>, it will be used to generate all three
-localized files. In addition, if there is a homepage for this language,
-it will be rebuilt when <samp><span
class="file">gnusflashes.</span><var>lang</var><span
class="file">.include</span></samp> is
-generated for the first time in order the translated homepage to include
-it instead of <samp><span class="file">gnusflashes.include</span></samp>.
-
- <p>Note that localized RSS feeds are not supported on purpose, as it would
+<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.
-
-<div class="node">
+</p>
+<hr>
<a name="PO-Tips"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#generic_002eLANG_002ehtml">generic.LANG.html</a>,
-Previous: <a rel="previous" accesskey="p" href="#GNU-News">GNU News</a>,
-Up: <a rel="up" accesskey="u" href="#PO-Files">PO Files</a>
-
+<div class="header">
+<p>
+Next: <a href="#generic_002eLANG_002ehtml" accesskey="n"
rel="next">generic.LANG.html</a>, Previous: <a href="#GNU-News" accesskey="p"
rel="previous">GNU News</a>, Up: <a href="#PO-Files" accesskey="u" rel="up">PO
Files</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-
+<a name="Useful-Hints-for-Editing-PO-Files"></a>
<h4 class="subsection">2.3.4 Useful Hints for Editing PO Files</h4>
+<a name="index-tips_002c-translators"></a>
+<a name="index-recommendations_002c-PO-files"></a>
-<p><a name="index-tips_002c-translators-81"></a><a
name="index-recommendations_002c-PO-files-82"></a>
-This section contains additional explanations, some in the form of
+<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.
- <ul>
-<li>When you install a new translation of an article (that is different
-from a server template or the homepage), all you need to do is to add
-your PO file in the appropriate <samp><span class="file">/po</span></samp>
sub-directory.
-
- <p>In the next build, your <samp><var>article</var><span
class="file">.</span><var>lang</var><span class="file">.html</span></samp> will
be
+<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.
-
- <li>If you don't feel comfortable editing <samp><span
class="file">gnun.mk</span></samp>, do not worry.
+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> or <code>HOME_LINGUAS</code> for you, as
appropriate.
+<code>TEMPLATE_LINGUAS</code> for you, as appropriate.
- <li>Dealing with obsolete strings. Elements which are removed from the
+</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
+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
@@ -1548,33 +1679,35 @@
Failing that, you can still copy it and yank it at the appropriate
place.
- <li>You can add comments to every message in a PO file—for example
if
+</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>Sometimes, especially when the original message contains many links,
+</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>If you translate “Free Software Foundation, Inc.” in your
native
+</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:
- <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>
- <li>There is absolutely no reason to use HTML entities in translations as
a
+<div class="example">
+<pre class="example"># type: Content of: <div><address>
+msgid "51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA"
+msgstr ""
+"Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, "
+"Boston, MA 02110-1301, USA"
+</pre></div>
+
+</li><li> There is absolutely no reason to use HTML entities in translations
as a
replacement for common non-ASCII characters. They are harder to write
and serve no purpose.
- <li>Wrapping of <code>msgstr</code> using <kbd>M-q</kbd> in Emacs (or
other means) is
+</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
@@ -1582,154 +1715,160 @@
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.
-</ul>
+</li></ul>
-<div class="node">
-<a name="generic.LANG.html"></a>
+<hr>
<a name="generic_002eLANG_002ehtml"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#languages_002etxt">languages.txt</a>,
-Previous: <a rel="previous" accesskey="p" href="#PO-Tips">PO Tips</a>,
-Up: <a rel="up" accesskey="u" href="#PO-Files">PO Files</a>
-
-</div>
+<div class="header">
+<p>
+Next: <a href="#languages_002etxt" accesskey="n" rel="next">languages.txt</a>,
Previous: <a href="#PO-Tips" accesskey="p" rel="previous">PO Tips</a>, Up: <a
href="#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="The-generic_002elang_002ehtml-File"></a>
+<h4 class="subsection">2.3.5 The <samp>generic.<var>lang</var>.html</samp>
File</h4>
+<a name="index-team-information"></a>
+<a name="index-generic-notice_002c-translations"></a>
-<h4 class="subsection">2.3.5 The <samp><span
class="file">generic.</span><var>lang</var><span
class="file">.html</span></samp> File</h4>
-
-<p><a name="index-team-information-83"></a><a
name="index-generic-notice_002c-translations-84"></a>
-The files <samp><span
class="file">server/gnun/generic.</span><var>lang</var><span
class="file">.html</span></samp> are special: if
+<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>
-<pre class="example"> <p>To join the Fooish translation team, see
<a
- href="http://gnu.org/server/standards/translations/www-foo">the
- Foo team homepage</a>.</p>
-</pre>
- <p>The contents of <samp><span
class="file">generic.</span><var>lang</var><span
class="file">.html</span></samp> is injected right after
-the translators' credits, if any, and before the timestamp. It should
+<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>When you modify this file, for example, adding a message to the
+</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><span class="file">generic.</span><var>lang</var><span
class="file">.html</span></samp>. The next time a build occurs, all
+<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><span class="file">.</span><var>lang</var><span
class="file">.html</span></samp>, including the homepage), will be modified to
+<samp>.<var>lang</var>.html</samp>, including the homepage), will be modified
to
include the contents of this special file.
-
-<div class="node">
-<a name="languages.txt"></a>
+</p>
+<hr>
<a name="languages_002etxt"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#PO-Files-and-Team">PO Files and
Team</a>,
-Previous: <a rel="previous" accesskey="p"
href="#generic_002eLANG_002ehtml">generic.LANG.html</a>,
-Up: <a rel="up" accesskey="u" href="#PO-Files">PO Files</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.6 The <samp>languages.txt</samp> File</h4>
-<h4 class="subsection">2.3.6 The <samp><span
class="file">languages.txt</span></samp> File</h4>
-
-<p>The file <samp><span class="file">server/gnun/languages.txt</span></samp>
is used when generating
+<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 <TAB>-separated fields. The first field
+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>
-<pre class="example"> de German Deutsch
-</pre>
- <p>The generated list of translations may look like this:
-
-<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 class="node">
+<hr>
<a name="PO-Files-and-Team"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Compendia">Compendia</a>,
-Previous: <a rel="previous" accesskey="p"
href="#languages_002etxt">languages.txt</a>,
-Up: <a rel="up" accesskey="u" href="#PO-Files">PO Files</a>
-
-</div>
+<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.7 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>
-<h4 class="subsection">2.3.7 Maintaining Translations in Your Team's
Repository</h4>
-
-<p><a name="index-project-repository-85"></a><a
name="index-repository_002c-translation-project-86"></a><a
name="index-team-maintenance-87"></a><a
name="index-GNUmakefile_002eteam-88"></a>
-GNUN operates on the “official” Web repository of the Savannah
project
-`www', where normally only the coordinators of translation teams have
+<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>The PO files provide an excellent and natural way to review each other's
+</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>The file <samp><span class="file">GNUmakefile.team</span></samp> in the
‘<samp><span class="samp">gnun</span></samp>’ package is a
+</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
+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-89"></a>The following diagram illustrates a
typical workflow—it is applicable
+</p>
+<a name="index-team-workflow"></a>
+<p>The following diagram illustrates a typical workflow—it is applicable
for small, medium and large teams:
-
-<pre class="example"> +----------+ +-------------------+
- | ``www'' | | ``www-LANG'' |
- | Web |------>---->-------|Sources repository |
- |repository| automatic merge +-------------------+
- +----------+ | | |
+</p>
+<div class="example">
+<pre class="example">+----------+ +-------------------+
+| ``www'' | | ``www-LANG'' |
+| Web |------>---->-------|Sources repository |
+|repository| automatic merge +-------------------+
++----------+ | | |
| | | `-- Member A
+------------<----<-------------' |
Leader `---Member B
-</pre>
- <p>All members and the team leader commit in their project's
+</pre></div>
+
+<p>All members and the team leader commit in their project’s
repository—when a translation is ready, the leader checks it in in the
-official `www' repository. If an original article changes,
+official ‘www’ repository. If an original article changes,
a build could be invoked to synchronize (i.e. merge) the changes and
optionally automatically commit them so that the draft PO files are
updated. A translator would then normally update the PO file, and
-commit it again in the project's Sources repository, from where the
-coordinator will pick it up and install it in `www'.
-
- <p>To take advantage of this semi-automation, rename this template
-<samp><span class="file">GNUmakefile.team</span></samp> as <samp><span
class="file">GNUmakefile</span></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><span class="file">/po</span></samp> sub-directories; they are redundant
here. Instead, install
+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><span class="file">.</span><var>lang</var><span
class="file">.html</span></samp> resides in `www', for example:
-
-<pre class="example"> Root
+<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
@@ -1738,143 +1877,176 @@
| +--free-sw.<var>lang</var>.po
| +--not-ipr.<var>lang</var>.po
| +--open-source-misses-the-point.<var>lang</var>.po
- | +--...
+ | +--…
|
- +--...
-</pre>
- <p><a name="index-priorities_002emk-90"></a>Add <samp><span
class="file">priorities.mk</span></samp> in order to make the
<code>report</code> target sort
-the files by priority.
+ +--…
+</pre></div>
- <p>The next sections explain how to adopt the makefile for your team and
+<a name="index-priorities_002emk-2"></a>
+<p>Add <samp>priorities.mk</samp> in order to make the <code>report</code>
target sort
+the files by priority.
+</p>
+<p>The next sections explain how to adopt the makefile for your team and
how to invoke a “build”.
+</p>
+<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>
-<ul class="menu">
-<li><a accesskey="1" href="#GNUmakefile_002eteam-Variables">GNUmakefile.team
Variables</a>
-<li><a accesskey="2" href="#GNUmakefile_002eteam-and-Cron">GNUmakefile.team
and Cron</a>
-</ul>
-
-<div class="node">
-<a name="GNUmakefile.team-Variables"></a>
+<hr>
<a name="GNUmakefile_002eteam-Variables"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#GNUmakefile_002eteam-and-Cron">GNUmakefile.team and Cron</a>,
-Up: <a rel="up" accesskey="u" href="#PO-Files-and-Team">PO Files and
Team</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>
-
-<h5 class="subsubsection">2.3.7.1 Adopting <samp><span
class="file">GNUmakefile.team</span></samp> for a Specific Team</h5>
+<a name="Adopting-GNUmakefile_002eteam-for-a-Specific-Team"></a>
+<h4 class="subsubsection">2.3.7.1 Adopting <samp>GNUmakefile.team</samp> for a
Specific Team</h4>
<p>To adjust the makefile for your team, you need to edit two variables.
-
- <dl>
-<dt>‘<samp><span class="samp">TEAM</span></samp>’<dd>Set this to
the language code, like <code>bg</code> or <code>pt-br</code>.
-
- <br><dt>‘<samp><span
class="samp">wwwdir</span></samp>’<dd>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><span
class="file">~/projects/www-</span><var>lang</var></samp> and the `www' Web
-repository at <samp><span class="file">~/projects/www</span></samp>, the value
of <code>wwwdir</code> should
-be <code>../www/</code> or <samp><span
class="file">/home/</span><var>user</var><span
class="file">/projects/www/</span></samp>. Note the
+</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>.
+</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>
</dl>
- <p>If two variants of one language share the same project and repository
+<p>If two variants of one language share the same project and repository
(such as <code>zh-cn</code> and <code>zh-tw</code>), they should maintain two
-directories with two <samp><span class="file">GNUmakefile</span></samp>s and
each directory having its
+directories with two <samp>GNUmakefile</samp>s and each directory having its
own tree.
-
- <p>Some variables are specified on the command line, and alter the behavior
+</p>
+<p>Some variables are specified on the command line, and alter the behavior
of the build process.
-
- <dl>
-<dt>‘<samp><span class="samp">VERBOSE=yes</span></samp>’<dd>Print
more information from <samp><span class="command">cvs</span></samp>,
<samp><span class="command">svn</span></samp> and
-<samp><span class="command">msgmerge</span></samp>; off by default. Note that
<code>VERBOSE</code> can be
+</p>
+<dl compact="compact">
+<dt>‘<samp>VERBOSE=yes</samp>’</dt>
+<dd><p>Print more information from <code>cvs</code>, <code>svn</code> and
+<code>msgmerge</code>; off by default. Note that <code>VERBOSE</code> can be
defined to any string, it will have the same effect.
-
- <br><dt>‘<samp><span
class="samp">VCS=yes</span></samp>’<dd>Update both ‘<samp><span
class="samp">www</span></samp>’ and ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’ repositories, then
+</p>
+</dd>
+<dt>‘<samp>VCS=yes</samp>’</dt>
+<dd><p>Update both ‘<samp>www</samp>’ and
‘<samp>www-<var>lang</var></samp>’ 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.
-
- <p><strong>Caution:</strong> The makefile rule will commit all local
changes, not
-only those that resulted from running <samp><span
class="command">msgmerge</span></samp>. Thus, it is
+</p>
+<p><strong>Caution:</strong> The makefile rule will commit all local changes,
not
+only those that resulted from running <code>msgmerge</code>. Thus, it is
better to use a separate working copy dedicated solely for this
purpose.
+</p></dd>
</dl>
-<h5 class="unnumberedsubsubsec">Targets in <samp><span
class="file">GNUmakefile.team</span></samp></h5>
-
- <dl>
-<dt><code>update</code><dd>Updates the repositories. Does nothing unless
<code>VCS=yes</code>.
-
- <br><dt><code>sync</code><dd>Merges all available PO files from the
corresponding POT in <dfn>www</dfn>.
+<hr>
+<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>
+</div>
+<a name="Targets-in-GNUmakefile_002eteam"></a>
+<h4 class="subsubsection">2.3.7.2 Targets in <samp>GNUmakefile.team</samp></h4>
+
+<dl compact="compact">
+<dt><code>update</code></dt>
+<dd><p>Updates the repositories. Does nothing unless <code>VCS=yes</code>.
+</p>
+</dd>
+<dt><code>sync</code></dt>
+<dd><p>Merges all available PO files from the corresponding POT in
<em>www</em>.
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.
-
- <br><dt><code>report</code><dd>Verifies which translations are complete,
and prints a list (with
+</p>
+</dd>
+<dt><code>report</code></dt>
+<dd><p>Verifies which translations are complete, and prints a list (with
statistics) of those that need to be updated.
-
- <br><dt><code>format</code><dd>A convenience rule to re-wrap all files
upto the standard length. Most
+</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>This rule checks for all translations that have lines longer than 80,
-and runs <samp><span class="command">msgcat</span></samp> accordingly to
reformat them. For that
+</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 <samp><span class="command">msgcat</span></samp> for any
file that has a longer
+unnecessarily invoke <code>msgcat</code> for any file that has a longer
line, wherever it may occur.
-
- <br><dt><code>publish</code><dd>The <code>publish</code> rule's task is
to copy all modified files to the
-official <dfn>www</dfn> repository. It depends on the <code>format</code>
target
+</p>
+</dd>
+<dt><code>publish</code></dt>
+<dd><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 <samp><span
class="command">cp</span></samp> invocations.
+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 <dfn>fuzzy</dfn> messages and other
problems, if
+<code>sync</code> and correct any <em>fuzzy</em> messages and other problems,
if
necessary.
-
- <p>The <code>publish</code> rule does not depend on <code>sync</code>
explicitly,
+</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>As usual, when committing to the official repository, it is always a
-good practice to examine the output of <samp><span class="command">cvs
diff</span></samp>.
-
- <p>Invoking <code>make publish</code> prints warnings and does not
actually copy
+</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><span class="file">.pot</span></samp> is missing.
-
- <p>Typically, after an editing session (whether it involves actual editing
+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:
-
- <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>
- <br><dt><code>clean</code><dd>Deletes all backup and auto-generated files
that some PO editors leave
-behind, namely—<samp><var>file</var><span
class="file">.po~</span></samp>, <samp><var>file</var><span
class="file">.po.bak</span></samp> and
-<samp><var>file</var><span class="file">.mo</span></samp>.
+</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 that some PO editors leave
+behind, namely—<samp><var>file</var>.po~</samp>,
<samp><var>file</var>.po.bak</samp> and
+<samp><var>file</var>.mo</samp>.
+</p></dd>
</dl>
- <p><code>make VCS=yes</code> is the recommended command to be run
periodically.
+<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>Feel free to replace all strings with equivalents in your native
+</p>
+<p>Feel free to replace all strings with equivalents in your native
language and of course—do not hesitate to extend this file and modify
it as much as you like. For example, useful extra functionality would
be a target that will check which files have not yet been committed in
@@ -1882,303 +2054,315 @@
(i.e. they were updated by the team members but not installed by the
coordinator). Either way, if you come up with something interesting, it
would be nice to send a message to <a
href="mailto:address@hidden";>address@hidden</a>, so that
-<samp><span class="file">GNUmakefile.team</span></samp> gets updated for all
teams' benefit.
-
-<div class="node">
-<a name="GNUmakefile.team-and-Cron"></a>
+<samp>GNUmakefile.team</samp> gets updated for all teams’ benefit.
+</p>
+<hr>
<a name="GNUmakefile_002eteam-and-Cron"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p"
href="#GNUmakefile_002eteam-Variables">GNUmakefile.team Variables</a>,
-Up: <a rel="up" accesskey="u" href="#PO-Files-and-Team">PO Files and
Team</a>
-
-</div>
-
-<h5 class="subsubsection">2.3.7.2 Automatic Synchronization and Status
Reports</h5>
+<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>
+</div>
+<a name="Automatic-Synchronization-and-Status-Reports"></a>
+<h4 class="subsubsection">2.3.7.3 Automatic Synchronization and Status
Reports</h4>
+<a name="index-team-maintenance_002c-cron"></a>
+<a name="index-cron_002c-team-maintenance"></a>
-<p><a name="index-team-maintenance_002c-cron-91"></a><a
name="index-cron_002c-team-maintenance-92"></a>
-It is convenient to invoke such synchronization automatically, for
+<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
+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>
-<pre class="example"> # m h dom mon dow command
- @daily cd $HOME/projects/www-<var>lang</var>; make VCS=yes
-</pre>
- <p>It is not necessary the job to be run on the team leader's machine,
+<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>If desired, you could set up another job to report the status of the
+</p>
+<p>If desired, you could set up another job to report the status of the
translations weekly or fortnightly, for example:
-
-<pre class="example"> # m h dom mon dow command
- @weekly cd $HOME/projects/www-<var>lang</var>; \
- make report | mail -s "Weekly statistics" \
+</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>
- <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.
+</pre></div>
-<div class="node">
+<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="Compendia"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#PO-Files-and-Team">PO
Files and Team</a>,
-Up: <a rel="up" accesskey="u" href="#PO-Files">PO Files</a>
-
+<div class="header">
+<p>
+Previous: <a href="#PO-Files-and-Team" accesskey="p" rel="previous">PO Files
and Team</a>, Up: <a href="#PO-Files" accesskey="u" rel="up">PO Files</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-
+<a name="Using-Compendia"></a>
<h4 class="subsection">2.3.8 Using Compendia</h4>
-
-<p><a name="index-compendia-93"></a><a
name="index-translation-memory-94"></a><a
name="index-exclude_002epot-95"></a><a name="index-compendium_002epot-96"></a>
-Compendium is a PO file including translations for common strings; it is
-used to fill other PO files. See <a
href="gettext.html#Compendium">Compendium</a>. One example of such
+<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>GNUN uses compendia located in the <samp><span
class="file">server/gnun/compendia</span></samp>
-directory of the `www' web repository. There are two kinds of
-compendia: <samp><span class="file">master.</span><var>lang</var><span
class="file">.po</span></samp> and
-<samp><span class="file">compendium.</span><var>lang</var><span
class="file">.po</span></samp>.
-
- <p>The first kind, <samp><span
class="file">master.</span><var>lang</var><span class="file">.po</span></samp>,
can be used to
+</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><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>. When <samp><span
class="file">master.</span><var>lang</var><span class="file">.po</span></samp>
is
-updated, the translations will be rebuilt. GNUN doesn't modify this
+<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>The second kind, <samp><span
class="file">compendium.</span><var>lang</var><span
class="file">.po</span></samp>, is updated
+</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><span
class="file">compendium.pot</span></samp>. Then it checks
-all available <samp><var>article</var><span
class="file">.</span><var>lang</var><span class="file">.po</span></samp> files
for
+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><span class="file">compendium.</span><var>lang</var><span
class="file">.po</span></samp>. This file is also used to fill
-missing translations, but it doesn't override the translations from
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>, and the strings coming from
-<samp><span class="file">compendium.</span><var>lang</var><span
class="file">.po</span></samp> are always marked as “fuzzy” to
+<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>When updating <samp><span class="file">compendium.pot</span></samp>,
some strings should be excluded
+</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
+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><span
class="file">exclude.pot</span></samp>, and when that file
-contains the string, it won't be added to <samp><span
class="file">compendium.pot</span></samp>.
-
-<div class="node">
+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>
+<hr>
<a name="Webmaster-Tips"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#PO-Files">PO Files</a>,
-Up: <a rel="up" accesskey="u" href="#Usage">Usage</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>
</div>
-
+<a name="Tips-and-Hints-for-Webmasters"></a>
<h3 class="section">2.4 Tips and Hints for Webmasters</h3>
+<a name="index-tips_002c-webmasters"></a>
+<a name="index-webmaster-tips"></a>
-<p><a name="index-tips_002c-webmasters-97"></a><a
name="index-webmaster-tips-98"></a>
-This section contains some tips and general recommendations for
+<p>This section contains some tips and general recommendations for
webmasters in no particular order—it is not mandatory to follow them,
-but doing so will make translators' lives substantially easier.
-
- <p>First and foremost, respect translators' work—it is ungrateful and
+but doing so will make translators’ lives substantially easier.
+</p>
+<p>First and foremost, respect translators’ work—it is ungrateful
and
hard, undoubtedly much harder than translation of programs. It is
important to have as many and as better as possible translations, and
-you don't have to make titanic efforts to help.
-
- <p>If you plan to edit a certain page extensively, please do so within the
+you don’t have to make titanic efforts to help.
+</p>
+<p>If you plan to edit a certain page extensively, please do so within the
period between two adjacent GNUN builds—i.e. within a day. That way,
the POT will be regenerated only once, and translators who are quick to
-update it immediately won't be disappointed if it changes again in the
+update it immediately won’t be disappointed if it changes again in the
next run.
-
-<ul class="menu">
-<li><a accesskey="1" href="#Validation">Validation</a>: How to
verify the documents.
-<li><a accesskey="2" href="#Comments-for-Translators">Comments for
Translators</a>: Passing comments to translators.
-<li><a accesskey="3" href="#Modifying-Boilerplates">Modifying Boilerplates</a>
-<li><a accesskey="4" href="#Localized-URLs">Localized URLs</a>:
Specifying URLs of diagrams
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#Validation"
accesskey="1">Validation</a>:</td><td> </td><td align="left"
valign="top">How to verify the documents.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Comments-for-Translators"
accesskey="2">Comments for Translators</a>:</td><td> </td><td
align="left" valign="top">Passing comments to translators.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Modifying-Boilerplates"
accesskey="3">Modifying Boilerplates</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Localized-URLs"
accesskey="4">Localized URLs</a>:</td><td> </td><td align="left"
valign="top">Specifying URLs of diagrams
to be translated.
-<li><a accesskey="5" href="#Splitting-Long-Passages">Splitting Long
Passages</a>: How to avoid too long strings
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Splitting-Long-Passages"
accesskey="5">Splitting Long Passages</a>:</td><td> </td><td
align="left" valign="top">How to avoid too long strings
in PO files.
-</ul>
+</td></tr>
+</table>
-<div class="node">
+<hr>
<a name="Validation"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#Comments-for-Translators">Comments for Translators</a>,
-Up: <a rel="up" accesskey="u" href="#Webmaster-Tips">Webmaster Tips</a>
-
+<div class="header">
+<p>
+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>
+<a name="index-validation-3"></a>
-<p><a name="index-validation-99"></a>
-The script <samp><span class="command">gnun-validate-html</span></samp> is
useful for webmasters who
+<p>The script <code>gnun-validate-html</code> is useful for webmasters who
want to verify if their (potentially intrusive) changes result in a
valid markup. Before committing your changes, you can check whether
the file is valid by running
+</p>
+<div class="example">
+<pre class="example">gnun-validate-html --root . philosophy/not-ipr.html
+</pre></div>
-<pre class="example"> gnun-validate-html --root . philosophy/not-ipr.html
-</pre>
- <p>See <a href="#gnun_002dvalidate_002dhtml">gnun-validate-html</a>, for
more information.
-
-<div class="node">
+<p>See <a href="#gnun_002dvalidate_002dhtml">gnun-validate-html</a>, for more
information.
+</p>
+<hr>
<a name="Comments-for-Translators"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#Modifying-Boilerplates">Modifying Boilerplates</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Validation">Validation</a>,
-Up: <a rel="up" accesskey="u" href="#Webmaster-Tips">Webmaster Tips</a>
-
+<div class="header">
+<p>
+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>
+<a name="index-comments-for-translators"></a>
-<p><a name="index-comments-for-translators-100"></a>
-<!-- Emacs Lisp code goes here... -->
- <p>If you want a comment to be visible for translators, place it
+<p>If you want a comment to be visible for translators, place it
<em>inside</em> the element, for example:
+</p>
+<div class="example">
+<pre class="example"><p>
+<!--TRANSLATORS: Note that foo is bar in this context.-->
+The fooish bar mumbles bazzling.
+</p>
+</pre></div>
+
+<p>This will result in:
+</p>
+<div class="example">
+<pre class="example"># type: Content of: <p>
+#. TRANSLATORS: Note that foo is bar in this context.
+msgid "The fooish bar mumbles bazzling."
+msgstr ""
+</pre></div>
-<pre class="example"> <p>
- <!--TRANSLATORS: Note that foo is bar in this context.-->
- The fooish bar mumbles bazzling.
- </p>
-</pre>
- <p>This will result in:
-
-<pre class="example"> # type: Content of: <p>
- #. TRANSLATORS: Note that foo is bar in this context.
- msgid "The fooish bar mumbles bazzling."
- msgstr ""
-</pre>
- <p>As per the established convention, start the comment with
+<p>As per the established convention, start the comment with
<code>TRANSLATORS:</code> to catch their attention, and do not add a space
after the beginning of the HTML comment (<code><!--</code>), since this will
unnecessarily indent the comment in the POT.
-
-<div class="node">
+</p>
+<hr>
<a name="Modifying-Boilerplates"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Localized-URLs">Localized
URLs</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Comments-for-Translators">Comments for Translators</a>,
-Up: <a rel="up" accesskey="u" href="#Webmaster-Tips">Webmaster Tips</a>
-
+<div class="header">
+<p>
+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>
+<a name="index-boilerplates"></a>
-<p><a name="index-boilerplates-101"></a>
-<strong>Warning:</strong> Any significant structural diversion from
-<samp><span class="file">boilerplate.html</span></samp> in a specific article
may result in errors from
+<p><strong>Warning:</strong> Any significant structural diversion from
+<samp>boilerplate.html</samp> in a specific article may result in errors from
GNUN. Any untested intrusive updates to the server templates (such as
changing the entire look & feel of the site) will probably break
-<em>all</em> translations under GNUN's control. Of course, this does not
+<em>all</em> translations under GNUN’s control. Of course, this does not
mean that no changes should happen—only that they must be applied in
our sandbox first, to ensure a smooth transition.
-
-<div class="node">
+</p>
+<hr>
<a name="Localized-URLs"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#Splitting-Long-Passages">Splitting Long Passages</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Modifying-Boilerplates">Modifying Boilerplates</a>,
-Up: <a rel="up" accesskey="u" href="#Webmaster-Tips">Webmaster Tips</a>
-
+<div class="header">
+<p>
+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>
+<a name="index-localized-URLs"></a>
-<p><a name="index-localized-URLs-102"></a>
-Some articles may contain diagrams or other images with English text
+<p>Some articles may contain diagrams or other images with English text
that can and should be translated. In order to make the translated
versions appear in the respective translations, GNUN should be told
what URLs need localization. It can be done with HTML comments like
-
-<pre class="example"> <!-- GNUN: localize URL /philosophy/category.png,
+</p>
+<div class="example">
+<pre class="example"><!-- GNUN: localize URL /philosophy/category.png,
/licenses/template-diagram.png and /graphics/jesus-cartoon.jpg -->
-</pre>
- <p>The URLs are separated with spaces. One trailing comma at the end of
-every word is removed if present. Words without a dot, such as `and',
-do not count as URLs; they are ignored.
-
- <p>Such comments will be extracted nightly and compiled into per-article
-lists of URLs in <samp><span class="file">localized-urls.mk</span></samp>.
+</pre></div>
- <p>After every build GNUN will check if the respective
-<samp><span class="file">philosophy/category.</span><var>lang</var><span
class="file">.png</span></samp> and other files are present in
+<p>The URLs are separated with spaces. One trailing comma at the end of
+every word is removed if present. Words without a dot, such as
‘and’,
+do not count as URLs; they are ignored.
+</p>
+<p>Such comments will be extracted nightly and compiled into per-article
+lists of URLs in <samp>localized-urls.mk</samp>.
+</p>
+<p>After every build GNUN will check if the respective
+<samp>philosophy/category.<var>lang</var>.png</samp> and other files are
present in
the working copy and substitute the strings in the HTML file of the
translation.
-
- <p>GNUN relies on URLs being absolute, starting from the root homepage
+</p>
+<p>GNUN relies on URLs being absolute, starting from the root directory
as required in
<a
href="http://www.gnu.org/server/fsf-html-style-sheet.html#FilenameAndURLGuidelines";>http://www.gnu.org/server/fsf-html-style-sheet.html#FilenameAndURLGuidelines</a>.
-
- <p>And please don't forget to commit the image in its source form
+</p>
+<p>And please don’t forget to commit the image in its source form
(typically, in SVG format).
-
-<div class="node">
+</p>
+<hr>
<a name="Splitting-Long-Passages"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p"
href="#Localized-URLs">Localized URLs</a>,
-Up: <a rel="up" accesskey="u" href="#Webmaster-Tips">Webmaster Tips</a>
-
+<div class="header">
+<p>
+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>
+<a name="index-long-passages_002c-avoiding"></a>
+<a name="index-conventional-separator-for-strings"></a>
-<p><a name="index-long-passages_002c-avoiding-103"></a><a
name="index-conventional-separator-for-strings-104"></a>
-GNUN splits typical text by paragraphs, and translators write the
+<p>GNUN splits typical text by paragraphs, and translators write the
translations for the resulting parts of the text one by one. When a
part is too long, it is hard to translate and proofread the translation;
the likelihood of skipping some phrases is relatively high.
-
- <p>In order to make our translators' life easier, it is desirable to keep
+</p>
+<p>In order to make our translators’ life easier, it is desirable to keep
the paragraphs short (no more than 350–700 characters). If rearranging
the paragraphs is not an option, you can use a conventional separator,
-<code><span class="gnun-split"></span></code>:
+<code><span class="gnun-split"></span></code>:
+</p>
+<div class="example">
+<pre class="example"><p>GNUN splits typical text by paragraphs, and
translators write
+the translations for the resulting parts of the text
+one by one. <span class="gnun-split"></span> When a part
+is too long, it is hard to translate and proofread the translation;
+the likelihood of skipping some phrases is relatively high.</p>
+</pre></div>
-<pre class="example"> <p>GNUN splits typical text by paragraphs, and
translators write
- the translations for the resulting parts of the text
- one by one. <span class="gnun-split"></span> When a part
- is too long, it is hard to translate and proofread the translation;
- the likelihood of skipping some phrases is relatively high.</p>
-</pre>
- <p>It is important that the separator be inserted between complete
+<p>It is important that the separator be inserted between complete
sentences, because different languages may require different orders
of parts of the sentence, and the translator has no control over
the sequence of the strings in the translation.
-
-<div class="node">
+</p>
+<hr>
<a name="Internals"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Bugs">Bugs</a>,
-Previous: <a rel="previous" accesskey="p" href="#Usage">Usage</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</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>
</div>
-
-<h2 class="chapter">3 Unexciting Information for GNUN's Operation</h2>
+<a name="Unexciting-Information-for-GNUN_0027s-Operation"></a>
+<h2 class="chapter">3 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
front-end, except the section about scripts that includes descriptions
of programs that may also be useful for the translators.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#Scripts"
accesskey="1">Scripts</a>:</td><td> </td><td align="left"
valign="top">Helper scripts.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Rules"
accesskey="2">Rules</a>:</td><td> </td><td align="left"
valign="top">The knotty rules explained.
+</td></tr>
+</table>
-<ul class="menu">
-<li><a accesskey="1" href="#Scripts">Scripts</a>: Helper scripts.
-<li><a accesskey="2" href="#Rules">Rules</a>: The knotty rules
explained.
-</ul>
-
-<div class="node">
+<hr>
<a name="Scripts"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Rules">Rules</a>,
-Up: <a rel="up" accesskey="u" href="#Internals">Internals</a>
-
+<div class="header">
+<p>
+Next: <a href="#Rules" accesskey="n" rel="next">Rules</a>, Up: <a
href="#Internals" accesskey="u" rel="up">Internals</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
-
+<a name="GNUN-Scripts"></a>
<h3 class="section">3.1 GNUN Scripts</h3>
<p>For the time being there are several helper scripts. Some of them are
@@ -2186,434 +2370,816 @@
rules; other scripts were written specifically to facilitate some
mechanical actions, like initially filling the headers in the PO files.
They all can be invoked separately, as stand-alone programs.
-
-<ul class="menu">
-<li><a accesskey="1" href="#make_002dprototype">make-prototype</a>
-<li><a accesskey="2"
href="#gnun_002dadd_002dfuzzy_002ddiff">gnun-add-fuzzy-diff</a>: Add
differences to previous
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a
href="#gnun_002dadd_002dfuzzy_002ddiff"
accesskey="1">gnun-add-fuzzy-diff</a>:</td><td> </td><td
align="left" valign="top">Add differences to previous
<code>msgid</code>s.
-<li><a accesskey="3" href="#gnun_002dinit_002dpo">gnun-init-po</a>:
Initialize a new translation.
-<li><a accesskey="4" href="#gnun_002dpreconvert">gnun-preconvert</a>:
Invoke the first step in converting
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#gnun_002ddiff_002dpo"
accesskey="2">gnun-diff-po</a>:</td><td> </td><td align="left"
valign="top">Compare two revisions of a PO file.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#gnun_002dinit_002dpo"
accesskey="3">gnun-init-po</a>:</td><td> </td><td align="left"
valign="top">Initialize a new translation.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#gnun_002dpreconvert"
accesskey="4">gnun-preconvert</a>:</td><td> </td><td align="left"
valign="top">Invoke the first step in converting
HTML translation to PO format.
-<li><a accesskey="5"
href="#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a>: Run the
second step of the conversion.
-<li><a accesskey="6"
href="#gnun_002dvalidate_002dhtml">gnun-validate-html</a>: Validate HTML
file.
-<li><a accesskey="7" href="#mailfail">mailfail</a>
-<li><a accesskey="8"
href="#validate_002dhtml_002dnotify">validate-html-notify</a>
-<li><a accesskey="9"
href="#gnun_002dclear_002dprevious">gnun-clear-previous</a>
-</ul>
-
-<div class="node">
-<a name="make-prototype"></a>
-<a name="make_002dprototype"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#gnun_002dadd_002dfuzzy_002ddiff">gnun-add-fuzzy-diff</a>,
-Up: <a rel="up" accesskey="u" href="#Scripts">Scripts</a>
-
-</div>
-
-<h4 class="subsection">3.1.1 The <samp><span
class="command">make-prototype</span></samp> Script</h4>
-
-<p><a name="index-POT-generation-105"></a><a
name="index-prototype-generation-106"></a><a
name="index-generation_002c-POT_002c-_002eproto-107"></a>
-This is a Guile script which makes the “prototype” file,
-<samp><span class="file">foo.</span><var>lang</var><span
class="file">.proto</span></samp>, from which the POT is generated. GNUN is
-designed in such a way, because it would be no big improvement if links
-to other translations ended up in the POT—it would mean that
-translators would have to manually update their PO file when a new
-translation is added.<a rel="footnote" href="#fn-6"
name="fnd-6"><sup>6</sup></a>
-
- <p>In addition, <samp><span class="command">make-prototype</span></samp>
guards the timestamp (the
-$<!-- /@w -->Date$ RCS keyword) in order the timestamp of the translation to
-be updated <em>only</em> when there are actual changes, being automatic
-or not.
-
- <p>Finally, <samp><span class="command">make-prototype</span></samp>
“injects” the artificial elements
-`*GNUN-SLOT: TRANSLATOR'S NOTES*' and `*GNUN-SLOT: TRANSLATOR'S
-CREDITS*', thanks to which it is possible to insert the name of the
-translator and translator's notes, if necessary. See <a
href="#New-Translation">New Translation</a>.
-
- <p>Here are the options that <samp><span
class="command">make-prototype</span></samp> accepts:
-
- <dl>
-<dt><samp><span class="option">--article</span></samp><dd>Process the input
file as an article. This is the default.<a rel="footnote" href="#fn-7"
name="fnd-7"><sup>7</sup></a>
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#gnun_002dmerge_002dpreconverted"
accesskey="5">gnun-merge-preconverted</a>:</td><td> </td><td
align="left" valign="top">Run the second step of the conversion.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#gnun_002dreport"
accesskey="6">gnun-report</a>:</td><td> </td><td align="left"
valign="top">Generate report in HTML format.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#gnun_002dvalidate_002dhtml"
accesskey="7">gnun-validate-html</a>:</td><td> </td><td align="left"
valign="top">Validate HTML file.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#mailfail"
accesskey="8">mailfail</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#validate_002dhtml_002dnotify"
accesskey="9">validate-html-notify</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#gnun_002dclear_002dprevious">gnun-clear-previous</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+</table>
- <br><dt><samp><span class="option">--home</span></samp><dd>Process the
input article as a homepage. Specify this when you want
-to create a <samp><span class="file">.proto</span></samp> file for a homepage.
-
- <br><dt><samp><span class="option">-i</span></samp><dt><samp><span
class="option">--input=</span><var>file</var></samp><dd>Input file, which can
be a common article (essay) or a homepage.
-
- <br><dt><samp><span class="option">-g</span></samp><dt><samp><span
class="option">--generic=</span><var>file</var></samp><dd>Common notes for a
translation team; this is the
-<samp><span class="file">generic.</span><var>lang</var><span
class="file">.html</span></samp> file. See <a
href="#generic_002eLANG_002ehtml">generic.LANG.html</a>.
-
- <br><dt><samp><span class="option">-o</span></samp><dt><samp><span
class="option">--output=</span><var>file</var></samp><dd>The file where to
write the output of the script.
-
- <br><dt><samp><span class="option">--version</span></samp><dd>Print
copyright and version information on the standard output.
-
- <br><dt><samp><span class="option">--help</span></samp><dd>Print usage
information on stdout.
-</dl>
-
-<div class="node">
-<a name="gnun-add-fuzzy-diff"></a>
+<hr>
<a name="gnun_002dadd_002dfuzzy_002ddiff"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#gnun_002dinit_002dpo">gnun-init-po</a>,
-Previous: <a rel="previous" accesskey="p"
href="#make_002dprototype">make-prototype</a>,
-Up: <a rel="up" accesskey="u" href="#Scripts">Scripts</a>
+<div class="header">
+<p>
+Next: <a href="#gnun_002ddiff_002dpo" accesskey="n"
rel="next">gnun-diff-po</a>, Up: <a href="#Scripts" accesskey="u"
rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
+<a name="The-gnun_002dadd_002dfuzzy_002ddiff-Script"></a>
+<h4 class="subsection">3.1.1 The <code>gnun-add-fuzzy-diff</code> Script</h4>
+<a name="index-previous_002c-diff-1"></a>
-</div>
-
-<h4 class="subsection">3.1.2 The <samp><span
class="command">gnun-add-fuzzy-diff</span></samp> Script</h4>
-
-<p><a name="index-previous_002c-diff-108"></a>
-This script adds comments with differences of current <code>msgid</code>s
+<p>This script adds comments with differences of current <code>msgid</code>s
against previous ones to fuzzy translations in a PO file. To produce
-the differences <samp><span class="command">wdiff</span></samp> is used. This
may be useful to figure
-out what has changed. In fact, it wraps around a <samp><span
class="command">sed</span></samp> script
+the differences <code>wdiff</code> is used. This may be useful to figure
+out what has changed. In fact, it wraps around a <code>sed</code> script
used in GNUN internally.
+</p>
+<div class="example">
+<pre class="example">gnun-add-fuzzy-diff [OPTION...] [FILE]
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>-i</samp></dt>
+<dt><samp>--in-place</samp></dt>
+<dd><p>Edit the file in place.
+</p>
+</dd>
+<dt><samp>--version</samp></dt>
+<dd><p>Display copyright and version information and exit.
+</p>
+</dd>
+<dt><samp>--help</samp></dt>
+<dd><p>Display usage information and exit.
+</p></dd>
+</dl>
-<pre class="example"> gnun-add-fuzzy-diff [OPTION...] [FILE]
-</pre>
- <dl>
-<dt><samp><span class="option">-i</span></samp><dt><samp><span
class="option">--in-place</span></samp><dd>Edit the file in place.
-
- <br><dt><samp><span class="option">--version</span></samp><dd>Display
copyright and version information and exit.
-
- <br><dt><samp><span class="option">--help</span></samp><dd>Display usage
information and exit.
+<hr>
+<a name="gnun_002ddiff_002dpo"></a>
+<div class="header">
+<p>
+Next: <a href="#gnun_002dinit_002dpo" accesskey="n"
rel="next">gnun-init-po</a>, Previous: <a
href="#gnun_002dadd_002dfuzzy_002ddiff" accesskey="p"
rel="previous">gnun-add-fuzzy-diff</a>, Up: <a href="#Scripts" accesskey="u"
rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
+<a name="The-gnun_002ddiff_002dpo-Script"></a>
+<h4 class="subsection">3.1.2 The <code>gnun-diff-po</code> Script</h4>
+<a name="index-comparing_002c-translations"></a>
+
+<p>This script compares two versions of a PO file. It produces a HTML page
+with a table that contains original strings with highlighted differences
+of their translations.
+</p>
+<p>If the sets of original strings in the input PO files differ, one of
+them will be merged with the other in order to eliminate the differences
+in the original strings.
+</p>
+<p>The results are written to standard output. Example:
+</p>
+<div class="example">
+<pre class="example">gnun-diff-po [OPTION...] PO_FILE1 PO_FILE2 > diff.html
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>-1</samp></dt>
+<dt><samp>--merge-against-first</samp></dt>
+<dd><p>Adjust the original strings of PO_FILE2 against PO_FILE1 when their
+sets differ. This is the default.
+</p>
+</dd>
+<dt><samp>-2</samp></dt>
+<dt><samp>--merge-against-second</samp></dt>
+<dd><p>Adjust the original strings of PO_FILE1 against PO_FILE2 when their
+sets differ.
+</p>
+</dd>
+<dt><samp>-t</samp></dt>
+<dt><samp>--title=<var>title</var></samp></dt>
+<dd><p>Specify the title of the output HTML page.
+</p>
+</dd>
+<dt><samp>--version</samp></dt>
+<dd><p>Display copyright and version information and exit.
+</p>
+</dd>
+<dt><samp>--help</samp></dt>
+<dd><p>Display usage information and exit.
+</p></dd>
</dl>
-<div class="node">
-<a name="gnun-init-po"></a>
+<hr>
<a name="gnun_002dinit_002dpo"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#gnun_002dpreconvert">gnun-preconvert</a>,
-Previous: <a rel="previous" accesskey="p"
href="#gnun_002dadd_002dfuzzy_002ddiff">gnun-add-fuzzy-diff</a>,
-Up: <a rel="up" accesskey="u" href="#Scripts">Scripts</a>
+<div class="header">
+<p>
+Next: <a href="#gnun_002dpreconvert" accesskey="n"
rel="next">gnun-preconvert</a>, Previous: <a href="#gnun_002ddiff_002dpo"
accesskey="p" rel="previous">gnun-diff-po</a>, Up: <a href="#Scripts"
accesskey="u" rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table
of contents" rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
+<a name="The-gnun_002dinit_002dpo-Script"></a>
+<h4 class="subsection">3.1.3 The <code>gnun-init-po</code> Script</h4>
+<a name="index-initializing_002c-translations"></a>
-</div>
-
-<h4 class="subsection">3.1.3 The <samp><span
class="command">gnun-init-po</span></samp> Script</h4>
-
-<p><a name="index-initializing_002c-translations-109"></a>
-This script initializes a PO file using POT generated with GNUN,
+<p>This script initializes a PO file using POT generated with GNUN,
and fills some fields in the header. It also optionally uses
a compendium (or compendia) to fill translations.
-
-<pre class="example"> gnun-init-po [OPTION...] POT
-</pre>
- <dl>
-<dt><samp><span class="option">-C</span></samp><dt><samp><span
class="option">--compendium=</span><var>comp</var></samp><dd>Specify a
compendium to use. You can issue this option
+</p>
+<div class="example">
+<pre class="example">gnun-init-po [OPTION...] POT
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>-C</samp></dt>
+<dt><samp>--compendium=<var>comp</var></samp></dt>
+<dd><p>Specify a compendium to use. You can issue this option
many times to use multiple compendia simultaneously. The suffix
of compendium is used when the language suffix is not specified
with the <code>--language</code> option.
-
- <br><dt><samp><span class="option">-d</span></samp><dt><samp><span
class="option">--disable-diffs</span></samp><dd>Don't add diffs to previous
messages.
-
- <br><dt><samp><span class="option">-g</span></samp><dt><samp><span
class="option">--team="</span><var>team <list></var><span
class="option">"</span></samp><dd>Specify team's name and mailing list.
-
- <br><dt><samp><span class="option">-l</span></samp><dt><samp><span
class="option">--language=</span><var>lang</var></samp><dd>Specify language
suffix, e.g “bg”. The suffix also defines
+</p>
+</dd>
+<dt><samp>-d</samp></dt>
+<dt><samp>--disable-diffs</samp></dt>
+<dd><p>Don’t add diffs to previous messages.
+</p>
+</dd>
+<dt><samp>-g</samp></dt>
+<dt><samp>--team="<var>team <list></var>"</samp></dt>
+<dd><p>Specify team’s name and mailing list.
+</p>
+</dd>
+<dt><samp>-l</samp></dt>
+<dt><samp>--language=<var>lang</var></samp></dt>
+<dd><p>Specify language suffix, e.g “bg”. The suffix also defines
the name of the language which is used in some fields of PO file header.
-
- <br><dt><samp><span class="option">-t</span></samp><dt><samp><span
class="option">--translator="</span><var>full name <email></var><span
class="option">"</span></samp><dd>Specify translator.
-
- <br><dt><samp><span class="option">--version</span></samp><dd>Display
copyright and version information and exit.
-
- <br><dt><samp><span class="option">--help</span></samp><dd>Display usage
information and exit.
+</p>
+</dd>
+<dt><samp>-t</samp></dt>
+<dt><samp>--translator="<var>full name
<email></var>"</samp></dt>
+<dd><p>Specify translator.
+</p>
+</dd>
+<dt><samp>--version</samp></dt>
+<dd><p>Display copyright and version information and exit.
+</p>
+</dd>
+<dt><samp>--help</samp></dt>
+<dd><p>Display usage information and exit.
+</p></dd>
</dl>
- <p>The PO file name is guessed from the name of POT and language
+<p>The PO file name is guessed from the name of POT and language
suffix; the file is created in current working directory.
-
-<div class="node">
-<a name="gnun-preconvert"></a>
+</p>
+<hr>
<a name="gnun_002dpreconvert"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a>,
-Previous: <a rel="previous" accesskey="p"
href="#gnun_002dinit_002dpo">gnun-init-po</a>,
-Up: <a rel="up" accesskey="u" href="#Scripts">Scripts</a>
+<div class="header">
+<p>
+Next: <a href="#gnun_002dmerge_002dpreconverted" accesskey="n"
rel="next">gnun-merge-preconverted</a>, Previous: <a
href="#gnun_002dinit_002dpo" accesskey="p" rel="previous">gnun-init-po</a>, Up:
<a href="#Scripts" accesskey="u" rel="up">Scripts</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="The-gnun_002dpreconvert-Script"></a>
+<h4 class="subsection">3.1.4 The <code>gnun-preconvert</code> Script</h4>
+<a name="index-migration_002c-translations-1"></a>
+<a name="index-conversion-of-existing-translations-1"></a>
-</div>
-
-<h4 class="subsection">3.1.4 The <samp><span
class="command">gnun-preconvert</span></samp> Script</h4>
-
-<p><a name="index-migration_002c-translations-110"></a><a
name="index-conversion-of-existing-translations-111"></a>
-This script uses <samp><span class="command">po4a-gettextize</span></samp> to
convert a translation
+<p>This script uses <code>po4a-gettextize</code> to convert a translation
from HTML to PO format (see
<a
href="http://po4a.alioth.debian.org/man/man7/po4a.7.php#lbAO";>http://po4a.alioth.debian.org/man/man7/po4a.7.php#lbAO</a>).
If
the conversion is successful, you can merge the result with the new
-POT using <samp><span class="command">gnun-merge-preconverted</span></samp>.
-
-<pre class="example"> gnun-preconvert [OPTION...] TRANSLATION MASTER
-</pre>
- <dl>
-<dt><samp><span class="option">-e</span></samp><dt><samp><span
class="option">--encoding</span></samp><dd>Specify the encoding of TRANSLATION
(if other than UTF-8).
-
- <br><dt><samp><span class="option">--version</span></samp><dd>Display
copyright and version information and exit.
-
- <br><dt><samp><span class="option">--help</span></samp><dd>Display usage
information and exit.
+POT using <code>gnun-merge-preconverted</code>.
+</p>
+<div class="example">
+<pre class="example">gnun-preconvert [OPTION...] TRANSLATION MASTER
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>-e</samp></dt>
+<dt><samp>--encoding</samp></dt>
+<dd><p>Specify the encoding of TRANSLATION (if other than UTF-8).
+</p>
+</dd>
+<dt><samp>--version</samp></dt>
+<dd><p>Display copyright and version information and exit.
+</p>
+</dd>
+<dt><samp>--help</samp></dt>
+<dd><p>Display usage information and exit.
+</p></dd>
</dl>
-<div class="node">
-<a name="gnun-merge-preconverted"></a>
+<hr>
<a name="gnun_002dmerge_002dpreconverted"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#gnun_002dvalidate_002dhtml">gnun-validate-html</a>,
-Previous: <a rel="previous" accesskey="p"
href="#gnun_002dpreconvert">gnun-preconvert</a>,
-Up: <a rel="up" accesskey="u" href="#Scripts">Scripts</a>
-
-</div>
-
-<h4 class="subsection">3.1.5 The <samp><span
class="command">gnun-merge-preconverted</span></samp> Script</h4>
+<div class="header">
+<p>
+Next: <a href="#gnun_002dreport" accesskey="n" rel="next">gnun-report</a>,
Previous: <a href="#gnun_002dpreconvert" accesskey="p"
rel="previous">gnun-preconvert</a>, Up: <a href="#Scripts" accesskey="u"
rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
+<a name="The-gnun_002dmerge_002dpreconverted-Script"></a>
+<h4 class="subsection">3.1.5 The <code>gnun-merge-preconverted</code>
Script</h4>
+<a name="index-migration_002c-translations-2"></a>
+<a name="index-conversion-of-existing-translations-2"></a>
-<p><a name="index-migration_002c-translations-112"></a><a
name="index-conversion-of-existing-translations-113"></a>
-This script takes <samp><span class="command">po4a-gettextize</span></samp>
output, adds current
+<p>This script takes <code>po4a-gettextize</code> output, adds current
<code>msgid</code>s as “previous” values, merges the file with the
new
POT, and adds differences against previous values like
-<samp><span class="command">gnun-add-fuzzy-diff</span></samp> does.
-
-<pre class="example"> gnun-merge-preconverted [OPTION...] PO POT
-</pre>
- <dl>
-<dt><samp><span class="option">-C</span></samp><dt><samp><span
class="option">--compendium</span></samp><dd>Specify the compendium (if any).
This option can be used
+<code>gnun-add-fuzzy-diff</code> does.
+</p>
+<div class="example">
+<pre class="example">gnun-merge-preconverted [OPTION...] PO POT
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>-C</samp></dt>
+<dt><samp>--compendium</samp></dt>
+<dd><p>Specify the compendium (if any). This option can be used
more than once to specify multiple compendia.
+</p>
+</dd>
+<dt><samp>--version</samp></dt>
+<dd><p>Display copyright and version information and exit.
+</p>
+</dd>
+<dt><samp>--help</samp></dt>
+<dd><p>Display usage information and exit.
+</p></dd>
+</dl>
- <br><dt><samp><span class="option">--version</span></samp><dd>Display
copyright and version information and exit.
-
- <br><dt><samp><span class="option">--help</span></samp><dd>Display usage
information and exit.
+<hr>
+<a name="gnun_002dreport"></a>
+<div class="header">
+<p>
+Next: <a href="#gnun_002dvalidate_002dhtml" accesskey="n"
rel="next">gnun-validate-html</a>, Previous: <a
href="#gnun_002dmerge_002dpreconverted" accesskey="p"
rel="previous">gnun-merge-preconverted</a>, Up: <a href="#Scripts"
accesskey="u" rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table
of contents" rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
+<a name="The-gnun_002dreport-Script"></a>
+<h4 class="subsection">3.1.6 The <code>gnun-report</code> Script</h4>
+<a name="index-reporting-1"></a>
+<a name="index-status_002c-translations-1"></a>
+
+<p>This script generates HTML reports about translations of a given team.
+The HTML contains a set of tables sorted by priority and translation
+status (existing translations that need maintenance, untranslated
+files, complete translations).
+</p>
+<a name="index-priorities_002emk-3"></a>
+<p>The script depends on the presence of the <samp>priorities.mk</samp> file
+in the <samp>server/gnun</samp> subdirectory of the working copy of
‘www’
+repository.
+</p>
+<p>The results are written to standard output. Example:
+</p>
+<div class="example">
+<pre class="example">gnun-report --root=../www -t bg > report-bg.html
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>-t</samp></dt>
+<dt><samp>--team=<var>lang</var></samp></dt>
+<dd><p>Specify the language code of the team, for example, ‘ml’.
+</p>
+</dd>
+<dt><samp>--root</samp></dt>
+<dd><p>Specify the top directory of the working copy; the default
+is the current directory.
+</p>
+</dd>
+<dt><samp>-l</samp></dt>
+<dt><samp>--language=<var>language</var></samp></dt>
+<dd><p>Specify the language name, for example, ‘Malayalam’. When
this option
+is missing, <code>gnun-report</code> tries to figure out the language name
+based on the language code provided with the “-t” option.
+</p>
+</dd>
+<dt><samp>--version</samp></dt>
+<dd><p>Display copyright and version information and exit.
+</p>
+</dd>
+<dt><samp>--help</samp></dt>
+<dd><p>Display usage information and exit.
+</p></dd>
</dl>
-<div class="node">
-<a name="gnun-validate-html"></a>
+<p>There is also a target in <samp>GNUmakefile</samp> to generate text reports
+intended for monthly messages sent to the teams. See <a
href="#report">report</a>.
+</p>
+<hr>
<a name="gnun_002dvalidate_002dhtml"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#mailfail">mailfail</a>,
-Previous: <a rel="previous" accesskey="p"
href="#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a>,
-Up: <a rel="up" accesskey="u" href="#Scripts">Scripts</a>
-
-</div>
-
-<h4 class="subsection">3.1.6 The <samp><span
class="command">gnun-validate-html</span></samp> Script</h4>
+<div class="header">
+<p>
+Next: <a href="#mailfail" accesskey="n" rel="next">mailfail</a>, Previous: <a
href="#gnun_002dreport" accesskey="p" rel="previous">gnun-report</a>, Up: <a
href="#Scripts" accesskey="u" rel="up">Scripts</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="The-gnun_002dvalidate_002dhtml-Script"></a>
+<h4 class="subsection">3.1.7 The <code>gnun-validate-html</code> Script</h4>
+<a name="index-validation_002c-HTML_002c-XHTML"></a>
-<p><a name="index-validation_002c-HTML_002c-XHTML-114"></a>
-This is a Bash script whose purpose is to “validate” both the
+<p>This is a Bash script whose purpose is to “validate” both the
original and translated articles to make sure that they conform to the
respective W3C standard. Sometimes webmasters make mistakes, and
translators too, so this tool is useful to catch errors of that kind.
-
- <p>GNUN enforces HTML validation at build time if invoked with
+</p>
+<p>GNUN enforces HTML validation at build time if invoked with
<code>VALIDATE=yes</code>.
-
- <p>The script expects only one <var>file</var> as the last argument and
will exit
+</p>
+<p>The script expects only one <var>file</var> as the last argument and will
exit
with an error if it is not specified (which might be the case when an
automatic variable is not expanded properly due to a bug in the
makefile). Example:
-
-<pre class="example"> gnun-validate-html --root . philosophy/free-sw.html
-</pre>
- <dl>
-<dt><samp><span
class="option">--root=</span><var>directory</var></samp><dd>Specify the top
<var>directory</var> of the working copy; the default value
-is <samp><span class="file">../..</span></samp>.
-
- <br><dt><samp><span
class="option">--expand-to=</span><var>file</var></samp><dd>Save the expanded
HTML as <var>file</var>.
-
- <br><dt><samp><span class="option">--version</span></samp><dd>Display
copyright and version information and exit.
-
- <br><dt><samp><span class="option">--help</span></samp><dd>Display usage
information and exit.
+</p>
+<div class="example">
+<pre class="example">gnun-validate-html --root . philosophy/free-sw.html
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>--root=<var>directory</var></samp></dt>
+<dd><p>Specify the top <var>directory</var> of the working copy; the default
value
+is <samp>../..</samp>.
+</p>
+</dd>
+<dt><samp>--expand-to=<var>file</var></samp></dt>
+<dd><p>Save the expanded HTML as <var>file</var>.
+</p>
+</dd>
+<dt><samp>-v, --verbose</samp></dt>
+<dd><p>Produce more detailed output intended for automatic email reports;
+essentially, it adds the expanded HTML to facilitate finding errors
+by people who receive the report.
+</p>
+</dd>
+<dt><samp>--version</samp></dt>
+<dd><p>Display copyright and version information and exit.
+</p>
+</dd>
+<dt><samp>--help</samp></dt>
+<dd><p>Display usage information and exit.
+</p></dd>
</dl>
-<div class="node">
+<hr>
<a name="mailfail"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#validate_002dhtml_002dnotify">validate-html-notify</a>,
-Previous: <a rel="previous" accesskey="p"
href="#gnun_002dvalidate_002dhtml">gnun-validate-html</a>,
-Up: <a rel="up" accesskey="u" href="#Scripts">Scripts</a>
-
-</div>
-
-<h4 class="subsection">3.1.7 The <samp><span
class="command">mailfail</span></samp> Script</h4>
+<div class="header">
+<p>
+Next: <a href="#validate_002dhtml_002dnotify" accesskey="n"
rel="next">validate-html-notify</a>, Previous: <a
href="#gnun_002dvalidate_002dhtml" accesskey="p"
rel="previous">gnun-validate-html</a>, Up: <a href="#Scripts" accesskey="u"
rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
+<a name="The-mailfail-Script"></a>
+<h4 class="subsection">3.1.8 The <code>mailfail</code> Script</h4>
+<a name="index-mail_002c-notifications-1"></a>
-<p><a name="index-mail_002c-notifications-115"></a>
-This is a helper script that runs a command, and mails the output of
+<p>This is a helper script that runs a command, and mails the output of
that command in case it exits with a non-zero exit status.
-<samp><span class="command">mailfail</span></samp> depends on GNU Mailutils,
or a compatible
-implementation, such as BSD's mailx.
-
- <p>Usage:
-
-<pre class="example"> mailfail [--dry-run] RCPT SUBJECT CMD [ARG ...]
-</pre>
- <p>The <samp><span class="command">mailfail</span></samp> script accepts
the following options:
-
- <dl>
-<dt><samp><span class="option">--dry-run</span></samp><dd>Does not send the
email message.
-
- <br><dt><samp><span class="option">RCPT</span></samp><dd>The recipient of
the message in a valid format, like
+<code>mailfail</code> depends on GNU Mailutils, or a compatible
+implementation, such as BSD’s mailx.
+</p>
+<p>Usage:
+</p>
+<div class="example">
+<pre class="example">mailfail [--dry-run] RCPT SUBJECT CMD [ARG ...]
+</pre></div>
+
+<p>The <code>mailfail</code> script accepts the following options:
+</p>
+<dl compact="compact">
+<dt><samp>--dry-run</samp></dt>
+<dd><p>Does not send the email message.
+</p>
+</dd>
+<dt><samp>RCPT</samp></dt>
+<dd><p>The recipient of the message in a valid format, like
<code>address@hidden</code>.
-
- <br><dt><samp><span class="option">SUBJECT</span></samp><dd>The subject
of the message; if it is longer than a word you should
+</p>
+</dd>
+<dt><samp>SUBJECT</samp></dt>
+<dd><p>The subject of the message; if it is longer than a word you should
guard it with quotes.
-
- <br><dt><samp><span class="option">CMD</span></samp><dd>The command you
want to run and send a mail in case it fails.
-
- <br><dt><samp><span class="option">ARG...</span></samp><dd>The arguments
of <code>CMD</code>, if any.
+</p>
+</dd>
+<dt><samp>CMD</samp></dt>
+<dd><p>The command you want to run and send a mail in case it fails.
+</p>
+</dd>
+<dt><samp>ARG…</samp></dt>
+<dd><p>The arguments of <code>CMD</code>, if any.
+</p></dd>
</dl>
- <p>Here is a typical example, similar to the way it is used in GNUN:
+<p>Here is a typical example, similar to the way it is used in GNUN:
+</p>
+<div class="example">
+<pre class="example">mailfail address@hidden "Bad PO" msgfmt -cv -o
/dev/null bg.po
+</pre></div>
-<pre class="example"> mailfail address@hidden "Bad PO" msgfmt -cv -o
/dev/null bg.po
-</pre>
- <p>This will check the validity of <samp><span
class="file">bg.po</span></samp> with the <samp><span
class="command">msgfmt</span></samp>
+<p>This will check the validity of <samp>bg.po</samp> with the
<code>msgfmt</code>
program and in case there are errors, a message will be sent to the
-specified address with `Bad PO' as subject and the error output from
-<samp><span class="command">msgfmt</span></samp> as body.
-
- <p><samp><span class="command">mailfail</span></samp> inherits the exit
status of the command being run.
+specified address with ‘Bad PO’ as subject and the error output
from
+<code>msgfmt</code> as body.
+</p>
+<p><code>mailfail</code> inherits the exit status of the command being run.
If an argument is missing, the usage information is printed to the
standard output and the exit code is 1.
-
-<div class="node">
-<a name="validate-html-notify"></a>
+</p>
+<hr>
<a name="validate_002dhtml_002dnotify"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#gnun_002dclear_002dprevious">gnun-clear-previous</a>,
-Previous: <a rel="previous" accesskey="p" href="#mailfail">mailfail</a>,
-Up: <a rel="up" accesskey="u" href="#Scripts">Scripts</a>
-
+<div class="header">
+<p>
+Next: <a href="#gnun_002dclear_002dprevious" accesskey="n"
rel="next">gnun-clear-previous</a>, Previous: <a href="#mailfail" accesskey="p"
rel="previous">mailfail</a>, Up: <a href="#Scripts" accesskey="u"
rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
</div>
+<a name="The-validate_002dhtml_002dnotify-Script"></a>
+<h4 class="subsection">3.1.9 The <code>validate-html-notify</code> Script</h4>
-<h4 class="subsection">3.1.8 The <samp><span
class="command">validate-html-notify</span></samp> Script</h4>
-
-<p>This script is a wrapper around <samp><span
class="command">gnun-validate-html</span></samp>
+<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
capture the output of the program from a program that itself captures
the output of another program that it runs.
-
- <p>Usage:
-
-<pre class="example"> validate-html-notify [--dry-run] RCPT FILE
-</pre>
- <dl>
-<dt><samp><span class="option">--dry-run</span></samp><dd>Does not actually
send the message, just like <samp><span class="command">mailfail</span></samp>.
-
- <br><dt><samp><span class="option">RCPT</span></samp><dd>The recipient of
the message.
-
- <br><dt><samp><span class="option">FILE</span></samp><dd>The HTML file
that has to be validated for compliance with the W3C
+</p>
+<p>Usage:
+</p>
+<div class="example">
+<pre class="example">validate-html-notify [--dry-run] RCPT FILE
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>--dry-run</samp></dt>
+<dd><p>Does not actually send the message, just like <code>mailfail</code>.
+In this case it runs <code>gnun-validate-html</code> without
+<samp>--verbose</samp> because it is expected that the expanded file
+will be available locally.
+</p>
+</dd>
+<dt><samp>RCPT</samp></dt>
+<dd><p>The recipient of the message.
+</p>
+</dd>
+<dt><samp>FILE</samp></dt>
+<dd><p>The HTML file that has to be validated for compliance with the W3C
standard.
+</p></dd>
</dl>
- <p>The subject of the message is hardcoded in the script, since this
+<p>The subject of the message is hardcoded in the script, since this
wrapper has a specific task and cannot be used to invoke an arbitrary
-command—use <samp><span class="command">mailfail</span></samp> for that.
See <a href="#mailfail">mailfail</a>.
-
-<div class="node">
-<a name="gnun-clear-previous"></a>
+command—use <code>mailfail</code> for that. See <a
href="#mailfail">mailfail</a>.
+</p>
+<hr>
<a name="gnun_002dclear_002dprevious"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p"
href="#validate_002dhtml_002dnotify">validate-html-notify</a>,
-Up: <a rel="up" accesskey="u" href="#Scripts">Scripts</a>
-
-</div>
+<div class="header">
+<p>
+Previous: <a href="#validate_002dhtml_002dnotify" accesskey="p"
rel="previous">validate-html-notify</a>, Up: <a href="#Scripts" accesskey="u"
rel="up">Scripts</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
+<a name="The-gnun_002dclear_002dprevious-Script"></a>
+<h4 class="subsection">3.1.10 The <code>gnun-clear-previous</code> Script</h4>
+<a name="index-previous_002c-manipulating-PO-files"></a>
-<h4 class="subsection">3.1.9 The <samp><span
class="command">gnun-clear-previous</span></samp> Script</h4>
-
-<p><a name="index-previous_002c-manipulating-PO-files-116"></a>
-This simple script is not used internally in GNUN. It is merely for
+<p>This simple script is not used internally in GNUN. It is merely for
convenience only, for those who find it hard to remember the various
-‘<samp><span class="samp">gettext</span></samp>’ tools and their
options.
-
- <p><samp><span class="command">gnun-clear-previous</span></samp> deletes
the <dfn>previous</dfn> messages in a
+‘<samp>gettext</samp>’ tools and their options.
+</p>
+<p><code>gnun-clear-previous</code> deletes the <em>previous</em> messages in a
PO file, which is a good thing to do after the corresponding translation
-is updated and the <dfn>fuzzy</dfn> marker removed. It can also be used to
+is updated and the <em>fuzzy</em> marker removed. It can also be used to
wrap long lines in PO files.
-
- <p>Usage:
-
-<pre class="example"> gnun-clear-previous FILE
-</pre>
- <dl>
-<dt><samp><span class="option">--version</span></samp><dd>Print copyright and
version information on the standard output.
-
- <br><dt><samp><span class="option">--help</span></samp><dd>Print usage
information on stdout.
+</p>
+<p>Usage:
+</p>
+<div class="example">
+<pre class="example">gnun-clear-previous FILE
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>--version</samp></dt>
+<dd><p>Print copyright and version information on the standard output.
+</p>
+</dd>
+<dt><samp>--help</samp></dt>
+<dd><p>Print usage information on stdout.
+</p></dd>
</dl>
-<div class="node">
+<hr>
<a name="Rules"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Scripts">Scripts</a>,
-Up: <a rel="up" accesskey="u" href="#Internals">Internals</a>
-
+<div class="header">
+<p>
+Previous: <a href="#Scripts" accesskey="p" rel="previous">Scripts</a>, Up: <a
href="#Internals" accesskey="u" rel="up">Internals</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="#Index" title="Index" rel="index">Index</a>]</p>
</div>
-
+<a name="How-The-Recipes-Work"></a>
<h3 class="section">3.2 How The Recipes Work</h3>
<p>Read the source code, then please tell us :-)
-
-<div class="node">
+</p>
+<hr>
<a name="Bugs"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Index">Index</a>,
-Previous: <a rel="previous" accesskey="p" href="#Internals">Internals</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+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>
+<a name="index-bugs_002c-reporting"></a>
+<a name="index-reporting-bugs"></a>
-<p><a name="index-bugs_002c-reporting-117"></a><a
name="index-reporting-bugs-118"></a>
-GNUnited Nations, like any other software, is not bug free. There are
-some known bugs and annoyances, which are listed in the <samp><span
class="file">TODO</span></samp>
+<p>GNUnited Nations, like any other software, is not bug free. There are
+some known bugs and annoyances, which are listed in the <samp>TODO</samp>
file, but it is absolutely certain that there are more which we know
nothing about.
-
- <p>If you encounter a bug, or if you have suggestions of any kind, please
+</p>
+<p>If you encounter a bug, or if you have suggestions of any kind, please
do not hesitate to report them at <a
href="mailto:address@hidden";>address@hidden</a> or
<a
href="https://savannah.gnu.org/bugs/?group=gnun";>https://savannah.gnu.org/bugs/?group=gnun</a>.
+</p>
+<hr>
+<a name="Index"></a>
+<div class="header">
+<p>
+Next: <a href="#Copying-This-Manual" accesskey="n" rel="next">Copying This
Manual</a>, Previous: <a href="#Bugs" accesskey="p" rel="previous">Bugs</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="Index-1"></a>
+<h2 class="unnumbered">Index</h2>
+
+<table><tr><th valign="top">Jump to: </th><td><a class="summary-letter"
href="#Index_cp_letter-A"><b>A</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-B"><b>B</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-C"><b>C</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-D"><b>D</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-E"><b>E</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-F"><b>F</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-G"><b>G</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-I"><b>I</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-L"><b>L</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-M"><b>M</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-N"><b>N</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-O"><b>O</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-P"><b>P</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-R"><b>R</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-S"><b>S</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-T"><b>T</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-V"><b>V</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-W"><b>W</b></a>
+
+</td></tr></table>
+<table class="index-cp" border="0">
+<tr><td></td><th align="left">Index Entry</th><td> </td><th align="left">
Section</th></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-A">A</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-ALL_005fDIRS">ALL_DIRS</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-announce">announce</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-articles-in-root-directory_002c-defining">articles in root
directory, defining</a>:</td><td> </td><td valign="top"><a
href="#Main-Variables">Main Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-B">B</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-Bazaar">Bazaar</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-boilerplates">boilerplates</a>:</td><td> </td><td
valign="top"><a href="#Modifying-Boilerplates">Modifying
Boilerplates</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-bugs_002c-reporting">bugs,
reporting</a>:</td><td> </td><td valign="top"><a
href="#Bugs">Bugs</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-bzr">bzr</a>:</td><td> </td><td valign="top"><a
href="#Runtime-Variables">Runtime Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-C">C</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-comments-for-translators">comments for
translators</a>:</td><td> </td><td valign="top"><a
href="#Comments-for-Translators">Comments for Translators</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-comparing_002c-translations">comparing,
translations</a>:</td><td> </td><td valign="top"><a
href="#gnun_002ddiff_002dpo">gnun-diff-po</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-compendia">compendia</a>:</td><td> </td><td valign="top"><a
href="#Compendia">Compendia</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-compendium_002epot">compendium.pot</a>:</td><td> </td><td
valign="top"><a href="#Compendia">Compendia</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-config_002emk">config.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-conventional-separator-for-strings">conventional separator for
strings</a>:</td><td> </td><td valign="top"><a
href="#Splitting-Long-Passages">Splitting Long Passages</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-conversion-of-existing-translations">conversion of existing
translations</a>:</td><td> </td><td valign="top"><a
href="#Migrating">Migrating</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-conversion-of-existing-translations-1">conversion of existing
translations</a>:</td><td> </td><td valign="top"><a
href="#gnun_002dpreconvert">gnun-preconvert</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-conversion-of-existing-translations-2">conversion of existing
translations</a>:</td><td> </td><td valign="top"><a
href="#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-credits_002c-translators">credits,
translators</a>:</td><td> </td><td valign="top"><a
href="#New-Translation">New Translation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-credits_002c-translators-1">credits,
translators</a>:</td><td> </td><td valign="top"><a
href="#Credits-Slot">Credits Slot</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-cron_002c-team-maintenance">cron, team
maintenance</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-CVS">CVS</a>:</td><td> </td><td valign="top"><a
href="#Runtime-Variables">Runtime Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-D">D</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-deferred-generation-of-articles">deferred generation of
articles</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-defining-articles-in-the-root-dir">defining articles in the root
dir</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-defining-directories">defining
directories</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-defining-templates">defining
templates</a>:</td><td> </td><td valign="top"><a
href="#Main-Variables">Main Variables</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-defining-templates-1">defining
templates</a>:</td><td> </td><td valign="top"><a
href="#Main-Variables">Main Variables</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-defining-templates-2">defining
templates</a>:</td><td> </td><td valign="top"><a
href="#Main-Variables">Main Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-directories_002c-defining">directories,
defining</a>:</td><td> </td><td valign="top"><a
href="#Main-Variables">Main Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-E">E</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-exclude_002epot">exclude.pot</a>:</td><td> </td><td
valign="top"><a href="#Compendia">Compendia</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-extra_002dtemplates">extra-templates</a>:</td><td> </td><td
valign="top"><a href="#Main-Variables">Main Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-F">F</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-fuzzy-strings">fuzzy
strings</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-FUZZY_005fDIFF_005fLINGUAS">FUZZY_DIFF_LINGUAS</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-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-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>
+<tr><td></td><td valign="top"><a
href="#index-gnusflashes">gnusflashes</a>:</td><td> </td><td
valign="top"><a href="#GNU-News">GNU News</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-GRACE">GRACE</a>:</td><td> </td><td valign="top"><a
href="#Runtime-Variables">Runtime Variables</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-grace-period">grace
period</a>:</td><td> </td><td valign="top"><a
href="#Runtime-Variables">Runtime Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-I">I</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-initializing_002c-translations">initializing,
translations</a>:</td><td> </td><td valign="top"><a
href="#gnun_002dinit_002dpo">gnun-init-po</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-invocation">invocation</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-invoking">invoking</a>:</td><td> </td><td valign="top"><a
href="#Invoking-GNUN">Invoking GNUN</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-L">L</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-localized-URLs">localized
URLs</a>:</td><td> </td><td valign="top"><a
href="#Localized-URLs">Localized URLs</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-long-lines_002c-wrap">long
lines, wrap</a>:</td><td> </td><td valign="top"><a
href="#New-Translation">New Translation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-long-passages_002c-avoiding">long passages,
avoiding</a>:</td><td> </td><td valign="top"><a
href="#Splitting-Long-Passages">Splitting Long Passages</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-M">M</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-mail_002c-notifications">mail,
notifications</a>:</td><td> </td><td valign="top"><a
href="#Runtime-Variables">Runtime Variables</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-mail_002c-notifications-1">mail,
notifications</a>:</td><td> </td><td valign="top"><a
href="#mailfail">mailfail</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-migration_002c-translations">migration,
translations</a>:</td><td> </td><td valign="top"><a
href="#Migrating">Migrating</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-migration_002c-translations-1">migration,
translations</a>:</td><td> </td><td valign="top"><a
href="#gnun_002dpreconvert">gnun-preconvert</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-migration_002c-translations-2">migration,
translations</a>:</td><td> </td><td valign="top"><a
href="#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-N">N</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-new-translation">new
translation</a>:</td><td> </td><td valign="top"><a
href="#New-Translation">New Translation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-new-translations_002c-notifications_002fannouncements">new
translations, notifications/announcements</a>:</td><td> </td><td
valign="top"><a href="#Runtime-Variables">Runtime Variables</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-notes_002c-translators">notes,
translators</a>:</td><td> </td><td valign="top"><a
href="#New-Translation">New Translation</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-notes_002c-translators-1">notes,
translators</a>:</td><td> </td><td valign="top"><a
href="#Notes-Slot">Notes Slot</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-NOTIFY">NOTIFY</a>:</td><td> </td><td valign="top"><a
href="#Runtime-Variables">Runtime Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-O">O</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-optional_002dtemplates">optional-templates</a>:</td><td> </td><td
valign="top"><a href="#Main-Variables">Main Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-OUTDATED_002dGRACE">OUTDATED-GRACE</a>:</td><td> </td><td
valign="top"><a href="#Runtime-Variables">Runtime Variables</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-output_002c-detailed">output,
detailed</a>:</td><td> </td><td valign="top"><a
href="#Runtime-Variables">Runtime Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-P">P</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-PO-editors">PO
editors</a>:</td><td> </td><td valign="top"><a href="#PO-Files">PO
Files</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-PO-headers">PO
headers</a>:</td><td> </td><td valign="top"><a href="#New-Translation">New
Translation</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-PO_002c-editing">PO,
editing</a>:</td><td> </td><td valign="top"><a href="#PO-Files">PO
Files</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-POT-generation_002c-articles">POT generation,
articles</a>:</td><td> </td><td valign="top"><a
href="#Main-Variables">Main Variables</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-previous_002c-diff">previous,
diff</a>:</td><td> </td><td valign="top"><a href="#Main-Variables">Main
Variables</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-previous_002c-diff-1">previous,
diff</a>:</td><td> </td><td valign="top"><a
href="#gnun_002dadd_002dfuzzy_002ddiff">gnun-add-fuzzy-diff</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-previous_002c-manipulating-PO-files">previous, manipulating PO
files</a>:</td><td> </td><td valign="top"><a
href="#gnun_002dclear_002dprevious">gnun-clear-previous</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-priorities_002emk">priorities.mk</a>:</td><td> </td><td
valign="top"><a href="#Invoking-GNUN">Invoking GNUN</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-priorities_002emk-1">priorities.mk</a>:</td><td> </td><td
valign="top"><a href="#report">report</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-priorities_002emk-2">priorities.mk</a>:</td><td> </td><td
valign="top"><a href="#PO-Files-and-Team">PO Files and Team</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-priorities_002emk-3">priorities.mk</a>:</td><td> </td><td
valign="top"><a href="#gnun_002dreport">gnun-report</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-project-repository">project
repository</a>:</td><td> </td><td valign="top"><a
href="#PO-Files-and-Team">PO Files and Team</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-R">R</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-recommendations_002c-PO-files">recommendations, PO
files</a>:</td><td> </td><td valign="top"><a href="#PO-Tips">PO
Tips</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-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-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>
+<tr><td></td><td valign="top"><a href="#index-sanity-checks">sanity
checks</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-status_002c-translations">status,
translations</a>:</td><td> </td><td valign="top"><a
href="#report">report</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-status_002c-translations-1">status,
translations</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-Subversion">Subversion</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-SVN">SVN</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-synchronization_002c-repository">synchronization,
repository</a>:</td><td> </td><td valign="top"><a
href="#sync">sync</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<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_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-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>
+<tr><td></td><td valign="top"><a
href="#index-TEMPLATE_005fLINGUAS">TEMPLATE_LINGUAS</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-tips_002c-translators">tips,
translators</a>:</td><td> </td><td valign="top"><a href="#PO-Tips">PO
Tips</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-tips_002c-webmasters">tips,
webmasters</a>:</td><td> </td><td valign="top"><a
href="#Webmaster-Tips">Webmaster Tips</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-translation-memory">translation
memory</a>:</td><td> </td><td valign="top"><a
href="#Compendia">Compendia</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-translation_002c-new">translation, new</a>:</td><td> </td><td
valign="top"><a href="#New-Translation">New Translation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-translators_0027-credits">translators’
credits</a>:</td><td> </td><td valign="top"><a href="#New-Translation">New
Translation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-translators_0027-credits-1">translators’
credits</a>:</td><td> </td><td valign="top"><a
href="#Credits-Slot">Credits Slot</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-translators_0027-notes">translators’
notes</a>:</td><td> </td><td valign="top"><a href="#New-Translation">New
Translation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-translators_0027-notes-1">translators’
notes</a>:</td><td> </td><td valign="top"><a href="#Notes-Slot">Notes
Slot</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-triggering_002c-build">triggering,
build</a>:</td><td> </td><td valign="top"><a
href="#Invoking-GNUN">Invoking GNUN</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-V">V</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-VALIDATE">VALIDATE</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-validation">validation</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-validation-1">validation</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-validation-2">validation</a>:</td><td> </td><td
valign="top"><a href="#validate_002dall">validate-all</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-validation-3">validation</a>:</td><td> </td><td
valign="top"><a href="#Validation">Validation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-validation_002c-HTML_002c-XHTML">validation, HTML,
XHTML</a>:</td><td> </td><td valign="top"><a
href="#gnun_002dvalidate_002dhtml">gnun-validate-html</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-variable_002c-behavior">variable,
behavior</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-variable_002c-team">variable,
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-variables">variables</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-variables-1">variables</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-VCS">VCS</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-VERBOSE">VERBOSE</a>:</td><td> </td><td valign="top"><a
href="#Runtime-Variables">Runtime Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-W">W</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-webmaster-tips">webmaster
tips</a>:</td><td> </td><td valign="top"><a
href="#Webmaster-Tips">Webmaster Tips</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-whatsnew">whatsnew</a>:</td><td> </td><td valign="top"><a
href="#GNU-News">GNU News</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-wrapping-long-lines">wrapping
long lines</a>:</td><td> </td><td valign="top"><a
href="#New-Translation">New Translation</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+</table>
+<table><tr><th valign="top">Jump to: </th><td><a class="summary-letter"
href="#Index_cp_letter-A"><b>A</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-B"><b>B</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-C"><b>C</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-D"><b>D</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-E"><b>E</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-F"><b>F</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-G"><b>G</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-I"><b>I</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-L"><b>L</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-M"><b>M</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-N"><b>N</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-O"><b>O</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-P"><b>P</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-R"><b>R</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-S"><b>S</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-T"><b>T</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-V"><b>V</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-W"><b>W</b></a>
+
+</td></tr></table>
-<div class="node">
+<hr>
<a name="Copying-This-Manual"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Index">Index</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
+<div class="header">
+<p>
+Previous: <a href="#Index" accesskey="p" rel="previous">Index</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="GNU-Free-Documentation-License"></a>
+<h2 class="appendix">Appendix A GNU Free Documentation License</h2>
+<div align="center">Version 1.3, 3 November 2008
</div>
-<h2 class="appendix">Appendix A GNU Free Documentation License</h2>
+<div class="display">
+<pre class="display">Copyright © 2000, 2001, 2002, 2007, 2008 Free
Software Foundation, Inc.
+<a href="http://fsf.org/";>http://fsf.org/</a>
-<!-- The GNU Free Documentation License. -->
-<div align="center">Version 1.3, 3 November 2008</div>
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+</pre></div>
-<!-- This file is intended to be included within another document, -->
-<!-- hence no sectioning command or @node. -->
-<pre class="display"> Copyright © 2000, 2001, 2002, 2007, 2008 Free
Software Foundation, Inc.
- <a href="http://fsf.org/";>http://fsf.org/</a>
-
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-</pre>
- <ol type=1 start=0>
-<li>PREAMBLE
+<ol>
+<li> PREAMBLE
- <p>The purpose of this License is to make a manual, textbook, or other
-functional and useful document <dfn>free</dfn> in the sense of freedom: to
+<p>The purpose of this License is to make a manual, textbook, or other
+functional and useful document <em>free</em> in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher a way
to get credit for their work, while not being considered responsible
for modifications made by others.
-
- <p>This License is a kind of “copyleft”, which means that
derivative
+</p>
+<p>This License is a kind of “copyleft”, which means that
derivative
works of the document must themselves be free in the same sense. It
complements the GNU General Public License, which is a copyleft
license designed for free software.
-
- <p>We have designed this License in order to use it for manuals for free
+</p>
+<p>We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free
program should come with manuals providing the same freedoms that the
software does. But this License is not limited to software manuals;
it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
+</p>
+</li><li> APPLICABILITY AND DEFINITIONS
- <li>APPLICABILITY AND DEFINITIONS
-
- <p>This License applies to any manual or other work, in any medium, that
+<p>This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
@@ -2622,14 +3188,14 @@
licensee, and is addressed as “you”. You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.
-
- <p>A “Modified Version” of the Document means any work
containing the
+</p>
+<p>A “Modified Version” of the Document means any work containing
the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
-
- <p>A “Secondary Section” is a named appendix or a
front-matter section
+</p>
+<p>A “Secondary Section” is a named appendix or a front-matter
section
of the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document's overall
+publishers or authors of the Document to the Document’s overall
subject (or to related matters) and contains nothing that could fall
directly within that overall subject. (Thus, if the Document is in
part a textbook of mathematics, a Secondary Section may not explain
@@ -2637,21 +3203,21 @@
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
-
- <p>The “Invariant Sections” are certain Secondary Sections
whose titles
+</p>
+<p>The “Invariant Sections” are certain Secondary Sections whose
titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.
-
- <p>The “Cover Texts” are certain short passages of text that
are listed,
+</p>
+<p>The “Cover Texts” are certain short passages of text that are
listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.
-
- <p>A “Transparent” copy of the Document means a
machine-readable copy,
+</p>
+<p>A “Transparent” copy of the Document means a machine-readable
copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
@@ -2663,9 +3229,9 @@
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
of text. A copy that is not “Transparent” is called
“Opaque”.
-
- <p>Examples of suitable formats for Transparent copies include plain
-<span class="sc">ascii</span> without markup, Texinfo input format, LaTeX input
+</p>
+<p>Examples of suitable formats for Transparent copies include plain
+<small>ASCII</small> without markup, Texinfo input format, LaTeX input
format, <acronym>SGML</acronym> or <acronym>XML</acronym> using a publicly
available
<acronym>DTD</acronym>, and standard-conforming simple <acronym>HTML</acronym>,
PostScript or <acronym>PDF</acronym> designed for human modification. Examples
@@ -2676,35 +3242,35 @@
not generally available, and the machine-generated <acronym>HTML</acronym>,
PostScript or <acronym>PDF</acronym> produced by some word processors for
output purposes only.
-
- <p>The “Title Page” means, for a printed book, the title page
itself,
+</p>
+<p>The “Title Page” means, for a printed book, the title page
itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, “Title Page”
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work’s title,
preceding the beginning of the body of the text.
-
- <p>The “publisher” means any person or entity that
distributes copies
+</p>
+<p>The “publisher” means any person or entity that distributes
copies
of the Document to the public.
-
- <p>A section “Entitled XYZ” means a named subunit of the
Document whose
+</p>
+<p>A section “Entitled XYZ” means a named subunit of the Document
whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
specific section name mentioned below, such as “Acknowledgements”,
“Dedications”, “Endorsements”, or
“History”.) To “Preserve the Title”
of such a section when you modify the Document means that it remains a
section “Entitled XYZ” according to this definition.
-
- <p>The Document may include Warranty Disclaimers next to the notice which
+</p>
+<p>The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document. These Warranty
Disclaimers are considered to be included by reference in this
License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
+</p>
+</li><li> VERBATIM COPYING
- <li>VERBATIM COPYING
-
- <p>You may copy and distribute the Document in any medium, either
+<p>You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies
to the Document are reproduced in all copies, and that you add no other
@@ -2713,15 +3279,15 @@
copying of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough
number of copies you must also follow the conditions in section 3.
-
- <p>You may also lend copies, under the same conditions stated above, and
+</p>
+<p>You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
+</p>
+</li><li> COPYING IN QUANTITY
- <li>COPYING IN QUANTITY
-
- <p>If you publish printed copies (or copies in media that commonly have
+<p>If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
-Document's license notice requires Cover Texts, you must enclose the
+Document’s license notice requires Cover Texts, you must enclose the
copies in covers that carry, clearly and legibly, all these Cover
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
the back cover. Both covers must also clearly and legibly identify
@@ -2731,13 +3297,13 @@
Copying with changes limited to the covers, as long as they preserve
the title of the Document and satisfy these conditions, can be treated
as verbatim copying in other respects.
-
- <p>If the required texts for either cover are too voluminous to fit
+</p>
+<p>If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto adjacent
pages.
-
- <p>If you publish or distribute Opaque copies of the Document numbering
+</p>
+<p>If you publish or distribute Opaque copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy
a computer-network location from which the general network-using
@@ -2749,51 +3315,51 @@
location until at least one year after the last time you distribute an
Opaque copy (directly or through your agents or retailers) of that
edition to the public.
-
- <p>It is requested, but not required, that you contact the authors of the
+</p>
+<p>It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
+</p>
+</li><li> MODIFICATIONS
- <li>MODIFICATIONS
-
- <p>You may copy and distribute a Modified Version of the Document under
+<p>You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
the Modified Version under precisely this License, with the Modified
Version filling the role of the Document, thus licensing distribution
and modification of the Modified Version to whoever possesses a copy
of it. In addition, you must do these things in the Modified Version:
-
- <ol type=A start=1>
-<li>Use in the Title Page (and on the covers, if any) a title distinct
+</p>
+<ol>
+<li> Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions
(which should, if there were any, be listed in the History section
of the Document). You may use the same title as a previous version
if the original publisher of that version gives permission.
- <li>List on the Title Page, as authors, one or more persons or
entities
+</li><li> List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.
- <li>State on the Title page the name of the publisher of the
+</li><li> State on the Title page the name of the publisher of the
Modified Version, as the publisher.
- <li>Preserve all the copyright notices of the Document.
+</li><li> Preserve all the copyright notices of the Document.
- <li>Add an appropriate copyright notice for your modifications
+</li><li> Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
- <li>Include, immediately after the copyright notices, a license
notice
+</li><li> Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.
- <li>Preserve in that license notice the full lists of Invariant
Sections
-and required Cover Texts given in the Document's license notice.
+</li><li> Preserve in that license notice the full lists of Invariant Sections
+and required Cover Texts given in the Document’s license notice.
- <li>Include an unaltered copy of this License.
+</li><li> Include an unaltered copy of this License.
- <li>Preserve the section Entitled “History”, Preserve
its Title, and add
+</li><li> Preserve the section Entitled “History”, Preserve its
Title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page. If
there is no section Entitled “History” in the Document, create one
@@ -2801,7 +3367,7 @@
given on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.
- <li>Preserve the network location, if any, given in the Document for
+</li><li> Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the “History” section.
@@ -2809,38 +3375,38 @@
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
- <li>For any section Entitled “Acknowledgements” or
“Dedications”, Preserve
+</li><li> For any section Entitled “Acknowledgements” or
“Dedications”, Preserve
the Title of the section, and preserve in the section all the
substance and tone of each of the contributor acknowledgements and/or
dedications given therein.
- <li>Preserve all the Invariant Sections of the Document,
+</li><li> Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles. Section numbers
or the equivalent are not considered part of the section titles.
- <li>Delete any section Entitled “Endorsements”. Such a
section
+</li><li> Delete any section Entitled “Endorsements”. Such a
section
may not be included in the Modified Version.
- <li>Do not retitle any existing section to be Entitled
“Endorsements” or
+</li><li> Do not retitle any existing section to be Entitled
“Endorsements” or
to conflict in title with any Invariant Section.
- <li>Preserve any Warranty Disclaimers.
- </ol>
+</li><li> Preserve any Warranty Disclaimers.
+</li></ol>
- <p>If the Modified Version includes new front-matter sections or
+<p>If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no material
copied from the Document, you may at your option designate some or all
of these sections as invariant. To do this, add their titles to the
-list of Invariant Sections in the Modified Version's license notice.
+list of Invariant Sections in the Modified Version’s license notice.
These titles must be distinct from any other section titles.
-
- <p>You may add a section Entitled “Endorsements”, provided it
contains
+</p>
+<p>You may add a section Entitled “Endorsements”, provided it
contains
nothing but endorsements of your Modified Version by various
parties—for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a
standard.
-
- <p>You may add a passage of up to five words as a Front-Cover Text, and a
+</p>
+<p>You may add a passage of up to five words as a Front-Cover Text, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version. Only one passage of
Front-Cover Text and one of Back-Cover Text may be added by (or
@@ -2849,21 +3415,21 @@
by arrangement made by the same entity you are acting on behalf of,
you may not add another; but you may replace the old one, on explicit
permission from the previous publisher that added the old one.
-
- <p>The author(s) and publisher(s) of the Document do not by this License
+</p>
+<p>The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
+</p>
+</li><li> COMBINING DOCUMENTS
- <li>COMBINING DOCUMENTS
-
- <p>You may combine the Document with other documents released under this
+<p>You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its
license notice, and that you preserve all their Warranty Disclaimers.
-
- <p>The combined work need only contain one copy of this License, and
+</p>
+<p>The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by
@@ -2871,48 +3437,48 @@
author or publisher of that section if known, or else a unique number.
Make the same adjustment to the section titles in the list of
Invariant Sections in the license notice of the combined work.
-
- <p>In the combination, you must combine any sections Entitled
“History”
+</p>
+<p>In the combination, you must combine any sections Entitled
“History”
in the various original documents, forming one section Entitled
“History”; likewise combine any sections Entitled
“Acknowledgements”,
and any sections Entitled “Dedications”. You must delete all
sections Entitled “Endorsements.”
+</p>
+</li><li> COLLECTIONS OF DOCUMENTS
- <li>COLLECTIONS OF DOCUMENTS
-
- <p>You may make a collection consisting of the Document and other
documents
+<p>You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
License in the various documents with a single copy that is included in
the collection, provided that you follow the rules of this License for
verbatim copying of each of the documents in all other respects.
-
- <p>You may extract a single document from such a collection, and
distribute
+</p>
+<p>You may extract a single document from such a collection, and distribute
it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
+</p>
+</li><li> AGGREGATION WITH INDEPENDENT WORKS
- <li>AGGREGATION WITH INDEPENDENT WORKS
-
- <p>A compilation of the Document or its derivatives with other separate
+<p>A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, is called an “aggregate” if the copyright
resulting from the compilation is not used to limit the legal rights
-of the compilation's users beyond what the individual works permit.
+of the compilation’s users beyond what the individual works permit.
When the Document is included in an aggregate, this License does not
apply to the other works in the aggregate which are not themselves
derivative works of the Document.
-
- <p>If the Cover Text requirement of section 3 is applicable to these
+</p>
+<p>If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half of
-the entire aggregate, the Document's Cover Texts may be placed on
+the entire aggregate, the Document’s Cover Texts may be placed on
covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.
+</p>
+</li><li> TRANSLATION
- <li>TRANSLATION
-
- <p>Translation is considered a kind of modification, so you may
+<p>Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
@@ -2924,48 +3490,48 @@
of those notices and disclaimers. In case of a disagreement between
the translation and the original version of this License or a notice
or disclaimer, the original version will prevail.
-
- <p>If a section in the Document is Entitled
“Acknowledgements”,
+</p>
+<p>If a section in the Document is Entitled “Acknowledgements”,
“Dedications”, or “History”, the requirement (section
4) to Preserve
its Title (section 1) will typically require changing the actual
title.
+</p>
+</li><li> TERMINATION
- <li>TERMINATION
-
- <p>You may not copy, modify, sublicense, or distribute the Document
+<p>You may not copy, modify, sublicense, or distribute the Document
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense, or distribute it is void, and
will automatically terminate your rights under this License.
-
- <p>However, if you cease all violation of this License, then your license
+</p>
+<p>However, if you cease all violation of this License, then your license
from a particular copyright holder is reinstated (a) provisionally,
unless and until the copyright holder explicitly and finally
terminates your license, and (b) permanently, if the copyright holder
fails to notify you of the violation by some reasonable means prior to
60 days after the cessation.
-
- <p>Moreover, your license from a particular copyright holder is
+</p>
+<p>Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
-
- <p>Termination of your rights under this section does not terminate the
+</p>
+<p>Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, receipt of a copy of some or all of the same material does
not give you any rights to use it.
+</p>
+</li><li> FUTURE REVISIONS OF THIS LICENSE
- <li>FUTURE REVISIONS OF THIS LICENSE
-
- <p>The Free Software Foundation may publish new, revised versions
+<p>The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
<a href="http://www.gnu.org/copyleft/";>http://www.gnu.org/copyleft/</a>.
-
- <p>Each version of the License is given a distinguishing version number.
+</p>
+<p>Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
License “or any later version” applies to it, you have the option
of
following the terms and conditions either of that specified version or
@@ -2974,47 +3540,49 @@
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation. If the Document
specifies that a proxy can decide which future versions of this
-License can be used, that proxy's public statement of acceptance of a
+License can be used, that proxy’s public statement of acceptance of a
version permanently authorizes you to choose that version for the
Document.
+</p>
+</li><li> RELICENSING
- <li>RELICENSING
-
- <p>“Massive Multiauthor Collaboration Site” (or “MMC
Site”) means any
+<p>“Massive Multiauthor Collaboration Site” (or “MMC
Site”) means any
World Wide Web server that publishes copyrightable works and also
provides prominent facilities for anybody to edit those works. A
public wiki that anybody can edit is an example of such a server. A
“Massive Multiauthor Collaboration” (or “MMC”)
contained in the
site means any set of copyrightable works thus published on the MMC
site.
-
- <p>“CC-BY-SA” means the Creative Commons Attribution-Share
Alike 3.0
+</p>
+<p>“CC-BY-SA” means the Creative Commons Attribution-Share Alike
3.0
license published by Creative Commons Corporation, a not-for-profit
corporation with a principal place of business in San Francisco,
California, as well as future copyleft versions of that license
published by that same organization.
-
- <p>“Incorporate” means to publish or republish a Document, in
whole or
+</p>
+<p>“Incorporate” means to publish or republish a Document, in
whole or
in part, as part of another Document.
-
- <p>An MMC is “eligible for relicensing” if it is licensed
under this
+</p>
+<p>An MMC is “eligible for relicensing” if it is licensed under
this
License, and if all works that were first published under this License
somewhere other than this MMC, and subsequently incorporated in whole
or in part into the MMC, (1) had no cover texts or invariant sections,
and (2) were thus incorporated prior to November 1, 2008.
-
- <p>The operator of an MMC Site may republish an MMC contained in the site
+</p>
+<p>The operator of an MMC Site may republish an MMC contained in the site
under CC-BY-SA on the same site at any time before August 1, 2009,
provided the MMC is eligible for relicensing.
+</p>
+</li></ol>
- </ol>
-
+<a name="ADDENDUM_003a-How-to-use-this-License-for-your-documents"></a>
<h3 class="heading">ADDENDUM: How to use this License for your documents</h3>
<p>To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
license notices just after the title page:
-
+</p>
+<div class="smallexample">
<pre class="smallexample"> Copyright (C) <var>year</var> <var>your
name</var>.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
@@ -3022,188 +3590,55 @@
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is included in the section entitled ``GNU
Free Documentation License''.
-</pre>
- <p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
-replace the “with<small class="dots">...</small>Texts.” line with
this:
+</pre></div>
+<p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the “with…Texts.” line with this:
+</p>
+<div class="smallexample">
<pre class="smallexample"> with the Invariant Sections being <var>list
their titles</var>, with
the Front-Cover Texts being <var>list</var>, and with the Back-Cover
Texts
being <var>list</var>.
-</pre>
- <p>If you have Invariant Sections without Cover Texts, or some other
+</pre></div>
+
+<p>If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.
-
- <p>If your document contains nontrivial examples of program code, we
+</p>
+<p>If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License,
to permit their use in free software.
+</p>
-<!-- Local Variables: -->
-<!-- ispell-local-pdict: "ispell-dict" -->
-<!-- End: -->
-<div class="node">
-<a name="Index"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Copying-This-Manual">Copying
This Manual</a>,
-Previous: <a rel="previous" accesskey="p" href="#Bugs">Bugs</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
-
-</div>
-
-<h2 class="unnumbered">Index</h2>
-<ul class="index-cp" compact>
-<li><a href="#index-ALL_005fDIRS-57">ALL_DIRS</a>: <a
href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-announce-22">announce</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-articles-in-root-directory_002c-defining-55">articles in
root directory, defining</a>: <a href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-Bazaar-14">Bazaar</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-boilerplates-101">boilerplates</a>: <a
href="#Modifying-Boilerplates">Modifying Boilerplates</a></li>
-<li><a href="#index-bugs_002c-reporting-117">bugs, reporting</a>: <a
href="#Bugs">Bugs</a></li>
-<li><a href="#index-bzr-15">bzr</a>: <a href="#Runtime-Variables">Runtime
Variables</a></li>
-<li><a href="#index-comments-for-translators-100">comments for
translators</a>: <a href="#Comments-for-Translators">Comments for
Translators</a></li>
-<li><a href="#index-compendia-93">compendia</a>: <a
href="#Compendia">Compendia</a></li>
-<li><a href="#index-compendium_002epot-96">compendium.pot</a>: <a
href="#Compendia">Compendia</a></li>
-<li><a href="#index-config_002emk-5">config.mk</a>: <a
href="#Invoking-GNUN">Invoking GNUN</a></li>
-<li><a href="#index-conventional-separator-for-strings-104">conventional
separator for strings</a>: <a href="#Splitting-Long-Passages">Splitting Long
Passages</a></li>
-<li><a href="#index-conversion-of-existing-translations-113">conversion of
existing translations</a>: <a
href="#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a></li>
-<li><a href="#index-conversion-of-existing-translations-111">conversion of
existing translations</a>: <a
href="#gnun_002dpreconvert">gnun-preconvert</a></li>
-<li><a href="#index-conversion-of-existing-translations-77">conversion of
existing translations</a>: <a href="#Migrating">Migrating</a></li>
-<li><a href="#index-credits_002c-translators-74">credits, translators</a>: <a
href="#Credits-Slot">Credits Slot</a></li>
-<li><a href="#index-credits_002c-translators-68">credits, translators</a>: <a
href="#New-Translation">New Translation</a></li>
-<li><a href="#index-cron_002c-team-maintenance-92">cron, team maintenance</a>:
<a href="#GNUmakefile_002eteam-and-Cron">GNUmakefile.team and Cron</a></li>
-<li><a href="#index-CVS-11">CVS</a>: <a href="#Runtime-Variables">Runtime
Variables</a></li>
-<li><a href="#index-deferred-generation-of-articles-28">deferred generation of
articles</a>: <a href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-defining-articles-in-the-root-dir-56">defining articles in
the root dir</a>: <a href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-defining-directories-59">defining directories</a>: <a
href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-defining-homepage-53">defining homepage</a>: <a
href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-defining-templates-42">defining templates</a>: <a
href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-directories_002c-defining-58">directories, defining</a>:
<a href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-exclude_002epot-95">exclude.pot</a>: <a
href="#Compendia">Compendia</a></li>
-<li><a href="#index-extra_002dtemplates-43">extra-templates</a>: <a
href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-fuzzy-strings-26">fuzzy strings</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-FUZZY_005fDIFF_005fLINGUAS-49">FUZZY_DIFF_LINGUAS</a>: <a
href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-generation_002c-POT_002c-_002eproto-107">generation, POT,
.proto</a>: <a href="#make_002dprototype">make-prototype</a></li>
-<li><a href="#index-generic-notice_002c-translations-84">generic notice,
translations</a>: <a
href="#generic_002eLANG_002ehtml">generic.LANG.html</a></li>
-<li><a href="#index-GNUmakefile-4">GNUmakefile</a>: <a
href="#Invoking-GNUN">Invoking GNUN</a></li>
-<li><a href="#index-GNUmakefile_002eteam-88">GNUmakefile.team</a>: <a
href="#PO-Files-and-Team">PO Files and Team</a></li>
-<li><a href="#index-gnun_002emk-39">gnun.mk</a>: <a
href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-gnun_002emk-6">gnun.mk</a>: <a
href="#Invoking-GNUN">Invoking GNUN</a></li>
-<li><a href="#index-gnunews-78">gnunews</a>: <a href="#GNU-News">GNU
News</a></li>
-<li><a href="#index-gnusflashes-80">gnusflashes</a>: <a href="#GNU-News">GNU
News</a></li>
-<li><a href="#index-GRACE-25">GRACE</a>: <a href="#Runtime-Variables">Runtime
Variables</a></li>
-<li><a href="#index-grace-period-27">grace period</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-HOME_005fLINGUAS-51">HOME_LINGUAS</a>: <a
href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-homepage_002c-defining-52">homepage, defining</a>: <a
href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-initializing_002c-translations-109">initializing,
translations</a>: <a href="#gnun_002dinit_002dpo">gnun-init-po</a></li>
-<li><a href="#index-invocation-2">invocation</a>: <a
href="#Invoking-GNUN">Invoking GNUN</a></li>
-<li><a href="#index-invoking-1">invoking</a>: <a
href="#Invoking-GNUN">Invoking GNUN</a></li>
-<li><a href="#index-localized-URLs-102">localized URLs</a>: <a
href="#Localized-URLs">Localized URLs</a></li>
-<li><a href="#index-long-lines_002c-wrap-71">long lines, wrap</a>: <a
href="#New-Translation">New Translation</a></li>
-<li><a href="#index-long-passages_002c-avoiding-103">long passages,
avoiding</a>: <a href="#Splitting-Long-Passages">Splitting Long
Passages</a></li>
-<li><a href="#index-mail_002c-notifications-115">mail, notifications</a>: <a
href="#mailfail">mailfail</a></li>
-<li><a href="#index-mail_002c-notifications-20">mail, notifications</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-migration_002c-translations-112">migration,
translations</a>: <a
href="#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a></li>
-<li><a href="#index-migration_002c-translations-110">migration,
translations</a>: <a href="#gnun_002dpreconvert">gnun-preconvert</a></li>
-<li><a href="#index-migration_002c-translations-76">migration,
translations</a>: <a href="#Migrating">Migrating</a></li>
-<li><a href="#index-new-translation-64">new translation</a>: <a
href="#New-Translation">New Translation</a></li>
-<li><a
href="#index-new-translations_002c-notifications_002fannouncements-21">new
translations, notifications/announcements</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-notes_002c-translators-72">notes, translators</a>: <a
href="#Notes-Slot">Notes Slot</a></li>
-<li><a href="#index-notes_002c-translators-66">notes, translators</a>: <a
href="#New-Translation">New Translation</a></li>
-<li><a href="#index-NOTIFY-19">NOTIFY</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-optional_002dtemplates-46">optional-templates</a>: <a
href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-OUTDATED_002dGRACE-29">OUTDATED-GRACE</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-output_002c-detailed-24">output, detailed</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-PO-editors-62">PO editors</a>: <a href="#PO-Files">PO
Files</a></li>
-<li><a href="#index-PO-headers-65">PO headers</a>: <a
href="#New-Translation">New Translation</a></li>
-<li><a href="#index-PO_002c-editing-61">PO, editing</a>: <a
href="#PO-Files">PO Files</a></li>
-<li><a href="#index-POT-generation-105">POT generation</a>: <a
href="#make_002dprototype">make-prototype</a></li>
-<li><a href="#index-POT-generation_002c-articles-60">POT generation,
articles</a>: <a href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-previous_002c-diff-108">previous, diff</a>: <a
href="#gnun_002dadd_002dfuzzy_002ddiff">gnun-add-fuzzy-diff</a></li>
-<li><a href="#index-previous_002c-diff-50">previous, diff</a>: <a
href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-previous_002c-manipulating-PO-files-116">previous,
manipulating PO files</a>: <a
href="#gnun_002dclear_002dprevious">gnun-clear-previous</a></li>
-<li><a href="#index-priorities_002emk-90">priorities.mk</a>: <a
href="#PO-Files-and-Team">PO Files and Team</a></li>
-<li><a href="#index-priorities_002emk-36">priorities.mk</a>: <a
href="#report">report</a></li>
-<li><a href="#index-priorities_002emk-7">priorities.mk</a>: <a
href="#Invoking-GNUN">Invoking GNUN</a></li>
-<li><a href="#index-project-repository-85">project repository</a>: <a
href="#PO-Files-and-Team">PO Files and Team</a></li>
-<li><a href="#index-prototype-generation-106">prototype generation</a>: <a
href="#make_002dprototype">make-prototype</a></li>
-<li><a href="#index-recommendations_002c-PO-files-82">recommendations, PO
files</a>: <a href="#PO-Tips">PO Tips</a></li>
-<li><a href="#index-reporting-34">reporting</a>: <a
href="#report">report</a></li>
-<li><a href="#index-reporting-bugs-118">reporting bugs</a>: <a
href="#Bugs">Bugs</a></li>
-<li><a href="#index-repository_002c-translation-project-86">repository,
translation project</a>: <a href="#PO-Files-and-Team">PO Files and Team</a></li>
-<li><a href="#index-ROOT-54">ROOT</a>: <a href="#Main-Variables">Main
Variables</a></li>
-<li><a href="#index-sanity-checks-18">sanity checks</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-status_002c-translations-35">status, translations</a>: <a
href="#report">report</a></li>
-<li><a href="#index-Subversion-12">Subversion</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-SVN-13">SVN</a>: <a href="#Runtime-Variables">Runtime
Variables</a></li>
-<li><a href="#index-synchronization_002c-repository-33">synchronization,
repository</a>: <a href="#sync">sync</a></li>
-<li><a href="#index-TEAM-30">TEAM</a>: <a href="#Runtime-Variables">Runtime
Variables</a></li>
-<li><a href="#index-team-information-83">team information</a>: <a
href="#generic_002eLANG_002ehtml">generic.LANG.html</a></li>
-<li><a href="#index-team-maintenance-87">team maintenance</a>: <a
href="#PO-Files-and-Team">PO Files and Team</a></li>
-<li><a href="#index-team-maintenance_002c-cron-91">team maintenance, cron</a>:
<a href="#GNUmakefile_002eteam-and-Cron">GNUmakefile.team and Cron</a></li>
-<li><a href="#index-team-workflow-89">team workflow</a>: <a
href="#PO-Files-and-Team">PO Files and Team</a></li>
-<li><a href="#index-TEMPLATE_005fLINGUAS-40">TEMPLATE_LINGUAS</a>: <a
href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-templates_002c-additional-44">templates, additional</a>:
<a href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-templates_002c-defining-41">templates, defining</a>: <a
href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-templates_002c-optional-47">templates, optional</a>: <a
href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-tips_002c-translators-81">tips, translators</a>: <a
href="#PO-Tips">PO Tips</a></li>
-<li><a href="#index-tips_002c-webmasters-97">tips, webmasters</a>: <a
href="#Webmaster-Tips">Webmaster Tips</a></li>
-<li><a href="#index-translation-memory-94">translation memory</a>: <a
href="#Compendia">Compendia</a></li>
-<li><a href="#index-translation_002c-new-63">translation, new</a>: <a
href="#New-Translation">New Translation</a></li>
-<li><a href="#index-translators_0027-credits-75">translators' credits</a>: <a
href="#Credits-Slot">Credits Slot</a></li>
-<li><a href="#index-translators_0027-credits-69">translators' credits</a>: <a
href="#New-Translation">New Translation</a></li>
-<li><a href="#index-translators_0027-notes-73">translators' notes</a>: <a
href="#Notes-Slot">Notes Slot</a></li>
-<li><a href="#index-translators_0027-notes-67">translators' notes</a>: <a
href="#New-Translation">New Translation</a></li>
-<li><a href="#index-triggering_002c-build-3">triggering, build</a>: <a
href="#Invoking-GNUN">Invoking GNUN</a></li>
-<li><a href="#index-VALIDATE-16">VALIDATE</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-validation-99">validation</a>: <a
href="#Validation">Validation</a></li>
-<li><a href="#index-validation-37">validation</a>: <a
href="#validate_002dall">validate-all</a></li>
-<li><a href="#index-validation-17">validation</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-validation_002c-HTML_002c-XHTML-114">validation, HTML,
XHTML</a>: <a href="#gnun_002dvalidate_002dhtml">gnun-validate-html</a></li>
-<li><a href="#index-variable_002c-behavior-9">variable, behavior</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-variable_002c-team-31">variable, team</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-variables-38">variables</a>: <a
href="#Main-Variables">Main Variables</a></li>
-<li><a href="#index-variables-8">variables</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-VCS-10">VCS</a>: <a href="#Runtime-Variables">Runtime
Variables</a></li>
-<li><a href="#index-VERBOSE-23">VERBOSE</a>: <a
href="#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="#index-webmaster-tips-98">webmaster tips</a>: <a
href="#Webmaster-Tips">Webmaster Tips</a></li>
-<li><a href="#index-whatsnew-79">whatsnew</a>: <a href="#GNU-News">GNU
News</a></li>
-<li><a href="#index-wrapping-long-lines-70">wrapping long lines</a>: <a
href="#New-Translation">New Translation</a></li>
- </ul><div class="footnote">
+<div class="footnote">
<hr>
-<a name="texinfo-footnotes-in-document"></a><h4>Footnotes</h4><p
class="footnote"><small>[<a name="fn-1" href="#fnd-1">1</a>]</small> Actually,
it is
+<h4 class="footnotes-heading">Footnotes</h4>
+
+<h3><a name="FOOT1" href="#DOCF1">(1)</a></h3>
+<p>Actually, it is
much more closer to localization of software documentation, where
-typically strings (also known as “messages” in gettext's context)
are
+typically strings (also known as “messages” in gettext’s
context) are
longer than strings in programs. Nevertheless, all points raised still
apply.</p>
-
- <p class="footnote"><small>[<a name="fn-2" href="#fnd-2">2</a>]</small> The
process of converting
+<h3><a name="FOOT2" href="#DOCF2">(2)</a></h3>
+<p>The process of converting
HTML to PO and the other way around is performed using po4a (“po for
anything”), see <a
href="http://po4a.alioth.debian.org";>http://po4a.alioth.debian.org</a>.</p>
-
- <p class="footnote"><small>[<a name="fn-3" href="#fnd-3">3</a>]</small> The
“no-grace”
-items are rebuilt hourly.</p>
-
- <p class="footnote"><small>[<a name="fn-4" href="#fnd-4">4</a>]</small>
When GNU Bzr is used, files
-are added locally only; you need to take care to use <samp><span
class="command">bzr push</span></samp>
+<h3><a name="FOOT3" href="#DOCF3">(3)</a></h3>
+<p>When GNU Bzr is used, files
+are added locally only; you need to take care to use <code>bzr push</code>
manually (or via cron) to take care of effectively adding them to the
public repository. See <a href="#triggers">triggers</a>, for a short
explanation.</p>
-
- <p class="footnote"><small>[<a name="fn-5" href="#fnd-5">5</a>]</small>
Only because presumably, they are more familiar with
-GNUnited Nations' internals. From a purely technical point of view,
+<h3><a name="FOOT4" href="#DOCF4">(4)</a></h3>
+<p>Only because presumably, they are more familiar with
+GNUnited Nations’ internals. From a purely technical point of view,
there is no difference.</p>
+</div>
+<hr>
- <p class="footnote"><small>[<a name="fn-6" href="#fnd-6">6</a>]</small>
Since version 0.5, those links are
-maintained in a separate file included with SSI directives.</p>
-
- <p class="footnote"><small>[<a name="fn-7" href="#fnd-7">7</a>]</small> As
-of version 0.5, this option is considered obsolete because the lists of
-translations are implemented as an automatically generated file included
-via SSI directive just like the respective list is included in the
-homepage. See <a href="#languages_002etxt">languages.txt</a>. In the future,
both the
-<code>--article</code> and the <code>--home</code> option will be removed.</p>
-
- <hr></div>
-</body></html>
+</body>
+</html>
Index: gnun/gnun.html.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.html.gz,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
Binary files /tmp/cvsXAui4p and /tmp/cvsiWQwtq 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.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
Binary files /tmp/cvsP27MFq and /tmp/cvs9COj6q differ
Index: gnun/gnun.info.tar.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.info.tar.gz,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
Binary files /tmp/cvs1JG1yp and /tmp/cvsSxkK0p differ
Index: gnun/gnun.pdf
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.pdf,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
Binary files /tmp/cvsR3zpxp and /tmp/cvsQVIp3p differ
Index: gnun/gnun.ps.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.ps.gz,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
Binary files /tmp/cvsGLSrZr and /tmp/cvszodZys differ
Index: gnun/gnun.texi.tar.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.texi.tar.gz,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
Binary files /tmp/cvsRICKCt and /tmp/cvstPh4du differ
Index: gnun/gnun.txt
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.txt,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/gnun.txt 26 Sep 2012 14:49:38 -0000 1.16
+++ gnun/gnun.txt 4 Dec 2012 16:24:20 -0000 1.17
@@ -1,6 +1,3 @@
-Table of Contents
-*****************
-
GNUnited Nations
1 Introduction to GNUnited Nations
1.1 Why GNUN is Being Developed
@@ -11,12 +8,12 @@
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.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
@@ -25,12 +22,12 @@
2.3.2 Transforming Existing Translation in PO Format
2.3.3 Special Handling for GNU News
2.3.4 Useful Hints for Editing PO Files
- 2.3.5 The `generic.LANG.html' File
- 2.3.6 The `languages.txt' File
+ 2.3.5 The 'generic.LANG.html' File
+ 2.3.6 The 'languages.txt' File
2.3.7 Maintaining Translations in Your Team's Repository
- 2.3.7.1 Adopting `GNUmakefile.team' for a Specific Team
- Targets in `GNUmakefile.team'
- 2.3.7.2 Automatic Synchronization and Status Reports
+ 2.3.7.1 Adopting 'GNUmakefile.team' for a Specific Team
+ 2.3.7.2 Targets in 'GNUmakefile.team'
+ 2.3.7.3 Automatic Synchronization and Status Reports
2.3.8 Using Compendia
2.4 Tips and Hints for Webmasters
2.4.1 Validation
@@ -40,29 +37,28 @@
2.4.5 Splitting Long Passages
3 Unexciting Information for GNUN's Operation
3.1 GNUN Scripts
- 3.1.1 The `make-prototype' Script
- 3.1.2 The `gnun-add-fuzzy-diff' Script
- 3.1.3 The `gnun-init-po' Script
- 3.1.4 The `gnun-preconvert' Script
- 3.1.5 The `gnun-merge-preconverted' Script
- 3.1.6 The `gnun-validate-html' Script
- 3.1.7 The `mailfail' Script
- 3.1.8 The `validate-html-notify' Script
- 3.1.9 The `gnun-clear-previous' Script
+ 3.1.1 The 'gnun-add-fuzzy-diff' Script
+ 3.1.2 The 'gnun-diff-po' Script
+ 3.1.3 The 'gnun-init-po' Script
+ 3.1.4 The 'gnun-preconvert' Script
+ 3.1.5 The 'gnun-merge-preconverted' Script
+ 3.1.6 The 'gnun-report' Script
+ 3.1.7 The 'gnun-validate-html' Script
+ 3.1.8 The 'mailfail' Script
+ 3.1.9 The 'validate-html-notify' Script
+ 3.1.10 The 'gnun-clear-previous' Script
3.2 How The Recipes Work
4 Reporting Bugs
-Appendix A GNU Free Documentation License
Index
-
-
+Appendix A GNU Free Documentation License
GNUnited Nations
****************
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org essays and
other articles.
-Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software Foundation,
+ Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software Foundation,
Inc.
Permission is granted to copy, distribute and/or modify this
@@ -76,7 +72,7 @@
**********************************
GNUnited Nations (abbreviated GNUN) is a collection of makefiles and
-scripts that are supposed to make the life of `http://gnu.org'
+scripts that are supposed to make the life of <http://gnu.org>
translators easier. Although it is specifically developed for the GNU
Project's website, it could be customized, at least in theory, to fit
the needs of other internationalized sites. GNUN is in early stage of
@@ -106,17 +102,17 @@
1.1 Why GNUN is Being Developed
===============================
-The GNU Project's website, `http://www.gnu.org', has become
-considerably large over the years. Maintaining it requires significant
-effort, and sometimes a new web standard is developed faster than the
-time required to migrate all articles to the next widely adopted one.
+The GNU Project's website, <http://www.gnu.org>, has become considerably
+large over the years. Maintaining it requires significant effort, and
+sometimes a new web standard is developed faster than the time required
+to migrate all articles to the next widely adopted one.
When it comes to internationalization, the problems are so many that
it is hard to enumerate them. It has become apparent that maintaining
translations up-to-date is a major undertaking, involving tedious
skimming through commit logs, reviewing diffs and other medieval
-techniques to catch up. Some translation teams have developed their
-own sets of scripts, but so far there has been no universal solution.
+techniques to catch up. Some translation teams have developed their own
+sets of scripts, but so far there has been no universal solution.
This unpleasant situation, combined with rapid and incompatible
design changes, have lead some teams to neglect the important work of
@@ -126,7 +122,7 @@
The reasons for developing GNUnited Nations are very similar to those
that lead to the inception of GNU gettext, or GNOME Documentation
-Utilities (`gnome-doc-utils') some years later.
+Utilities ('gnome-doc-utils') some years later.
1.2 What GNUnited Nations is and Should be
==========================================
@@ -135,23 +131,22 @@
similar to localization of computer programs(1). In articles, like in
programs, not every string is considered translatable, so translatable
strings must be identified first, and then collected in a file (called
-"PO template") for translation. Articles, like programs, tend to
-change in time, but not every change in the sources calls for a
-translation update. Sometimes the change does not affect the
-translatable strings, but sometimes it does. So, translators must have
-means to identify those changes and apply the appropriate updates to
-the translation.
+"PO template") for translation. Articles, like programs, tend to change
+in time, but not every change in the sources calls for a translation
+update. Sometimes the change does not affect the translatable strings,
+but sometimes it does. So, translators must have means to identify
+those changes and apply the appropriate updates to the translation.
- The GNU `gettext' package already provides the needed infrastructure
+ The GNU 'gettext' package already provides the needed infrastructure
for maintaining translations using PO files. *Note Introduction:
(gettext)Top, for a basic overview. GNUnited Nations fills the gaps to
-apply this infrastructure to articles in `http://gnu.org' web site.(2)
+apply this infrastructure to articles in <http://gnu.org> web site.(2)
The following diagram summarizes the relation between the files
-handled by GNUN. It is followed by somewhat detailed explanations,
-which you should read while keeping an eye on the diagram. Having a
-clear understanding of these interrelations will surely help
-translators and web maintainers.
+handled by GNUN. It is followed by somewhat detailed explanations, which
+you should read while keeping an eye on the diagram. Having a clear
+understanding of these interrelations will surely help translators and
+web maintainers.
.---<--- * Original ARTICLE.html
|
@@ -163,33 +158,33 @@
| +---> Translated ARTICLE.LANG.html
`-------'
- The indication `*' appears in two places in this picture, and means
+ The indication '*' appears in two places in this picture, and means
that the corresponding file is intended to be edited by humans. The
-author or web maintainer edits the original `ARTICLE.html', and
-translators edit `ARTICLE.LANG.po'. All other files are regenerated by
+author or web maintainer edits the original 'ARTICLE.html', and
+translators edit 'ARTICLE.LANG.po'. All other files are regenerated by
GNUN and any manual changes on them will be lost on the next run.
Arrows denote dependency relation between files, where a change in
-one file will affect the other. Those automatic changes will be
-applied by running `make -C server/gnun'. This is the primary way to
-invoke GNUN, since it is implemented as a set of recipes for GNU `make'.
+one file will affect the other. Those automatic changes will be applied
+by running 'make -C server/gnun'. This is the primary way to invoke
+GNUN, since it is implemented as a set of recipes for GNU 'make'.
First, GNUN extracts all translatable strings from the original
-English article `ARTICLE.html' into `ARTICLE.pot'. The resulted file
-is suitable for manipulation with the various GNU `gettext' utilities.
-It contains all original article strings and all translations are set
-to empty. The letter `t' in `.pot' marks this as a Template PO file,
-not yet oriented towards any particular language.
+English article 'ARTICLE.html' into 'ARTICLE.pot'. The resulted file is
+suitable for manipulation with the various GNU 'gettext' utilities. It
+contains all original article strings and all translations are set to
+empty. The letter 't' in '.pot' marks this as a Template PO file, not
+yet oriented towards any particular language.
- The first time though, there is no `ARTICLE.LANG.po' yet, so a
-translator must manually copy `ARTICLE.pot' to `ARTICLE.LANG.po', where
+ The first time though, there is no 'ARTICLE.LANG.po' yet, so a
+translator must manually copy 'ARTICLE.pot' to 'ARTICLE.LANG.po', where
LANG represents the target language. *Note New Translation::, for
details.
- Then comes the initial translation of messages in `ARTICLE.LANG.po'.
-Translation in itself is a whole matter, whose complexity far
-overwhelms the level of this manual. Nevertheless, a few hints are
-given in some other chapter of this manual.
+ Then comes the initial translation of messages in 'ARTICLE.LANG.po'.
+Translation in itself is a whole matter, whose complexity far overwhelms
+the level of this manual. Nevertheless, a few hints are given in some
+other chapter of this manual.
It is possible to make GNUN get translations for common strings from
dedicated PO files, so called compendia. *Note Compendia::, for more
@@ -199,38 +194,37 @@
the PO file. *Note Editing: (gettext)Editing, for more information.
When the PO file actually exists (hopefully populated with initial
-translations), GNUN generates `ARTICLE.LANG.html' file. It takes its
-structure from the original `ARTICLE.html', but all translatable
-strings are replaced with their translations specified in
-`ARTICLE.LANG.po'.
+translations), GNUN generates 'ARTICLE.LANG.html' file. It takes its
+structure from the original 'ARTICLE.html', but all translatable strings
+are replaced with their translations specified in 'ARTICLE.LANG.po'.
Original articles sometimes change. A new paragraph is being added
or a tiny change in the wording is introduced. Also, some articles are
dynamic in nature, like ones containing news entries or a list of other
articles. If the original article changes, GNUN will automatically
-rebuild `ARTICLE.pot', and will merge the changes to `ARTICLE.LANG.po'.
+rebuild 'ARTICLE.pot', and will merge the changes to 'ARTICLE.LANG.po'.
Any outdated translations will be marked as fuzzy, any new strings will
-be added with empty translations, waiting to be translated. In the
-same run `ARTICLE.LANG.html' will be rebuilt so the relevant strings in
-the translation will be substituted with the original English text,
-until the translation teams update them in `ARTICLE.LANG.po'.
+be added with empty translations, waiting to be translated. In the same
+run 'ARTICLE.LANG.html' will be rebuilt so the relevant strings in the
+translation will be substituted with the original English text, until
+the translation teams update them in 'ARTICLE.LANG.po'.
Those changes in the original article that do not affect the
-translatable strings will not lead to changes in `ARTICLE.LANG.po'.
-Thus, no actions from translators will be needed. `ARTICLE.LANG.html'
+translatable strings will not lead to changes in 'ARTICLE.LANG.po'.
+Thus, no actions from translators will be needed. 'ARTICLE.LANG.html'
will be automatically regenerated to reflect the changes.
- The POT for every article under GNUN's control is kept in the `www'
-repository under a special directory `po/', which is a sub-directory of
-the relevant directory in the `www' tree. So, for
-<http://www.gnu.org/philosophy/free-sw.html> that is `philosophy/po/'.
-Except `free-sw.pot', this directory holds the canonical source of
-every translation, like `free-sw.bg.po', `free-sw.ca.po', etc.
+ The POT for every article under GNUN's control is kept in the 'www'
+repository under a special directory 'po/', which is a sub-directory of
+the relevant directory in the 'www' tree. So, for
+'http://www.gnu.org/philosophy/free-sw.html' that is 'philosophy/po/'.
+Except 'free-sw.pot', this directory holds the canonical source of every
+translation, like 'free-sw.bg.po', 'free-sw.ca.po', etc.
Several additional features are implemented, like automatic update of
the list of the available translations. For example, if a new
-`free-sw.ja.po' translation is added, the list of translations included
-in `free-sw.html' and all translated `free-sw.LANG.html' is updated.
+'free-sw.ja.po' translation is added, the list of translations included
+in 'free-sw.html' and all translated 'free-sw.LANG.html' is updated.
This saves a lot of tedious, repetitive work and eliminates a source of
mistakes. There is a basic infrastructure to "inject" general
information about a translation team--like a note how to contact the
@@ -246,20 +240,20 @@
(2) The process of converting HTML to PO and the other way around is
performed using po4a ("po for anything"), see
-`http://po4a.alioth.debian.org'.
+<http://po4a.alioth.debian.org>.
1.3 Major Advantages of GNUN
============================
-Here is a simple list of situations where we hope this suite would
-prove to be useful.
+Here is a simple list of situations where we hope this suite would prove
+to be useful.
* Automatic rebuild of all translations when the original article
changes. This is the most important feature, as it prevents
accumulation of seriously outdated translations.
* Global update of the whole site. Apply the previous point to the
- web server templates (under `server/' in the `www' repository). A
+ web server templates (under 'server/' in the 'www' repository). A
single change to such a file will affect literally _all_ articles,
translated or not.
@@ -271,13 +265,12 @@
whether to translate it or not. For example, the Urdu translation
team may conclude that there are only a few Urdu speakers in
Massachusetts, to participate in an event that will happen in
- Boston, so translating the "urgent" notice may not be very
- "urgent" for Urdu. However, such notice will appear in all
- translated pages and people who usually read gnu.org pages in
- their native language will see it, so they can take action as
- necessary. When the notice is removed, often in a week or two, it
- will disappear without translators' intervention, whether they
- translated it or not.
+ Boston, so translating the "urgent" notice may not be very "urgent"
+ for Urdu. However, such notice will appear in all translated pages
+ and people who usually read gnu.org pages in their native language
+ will see it, so they can take action as necessary. When the notice
+ is removed, often in a week or two, it will disappear without
+ translators' intervention, whether they translated it or not.
* HTML validation. As a preliminary step, GNUN validates the English
pages before updating the POT files, and the regenerated
@@ -287,8 +280,8 @@
* Simplification of the translation process--lots of errors and typos
come from the fact that translators basically have to duplicate the
whole HTML markup of the original. The PO files eliminate most of
- the basic markup, which is where most of the validation errors
- come from.
+ the basic markup, which is where most of the validation errors come
+ from.
* Markup consistency site-wide--it would be substantially easier to
update the site to a future standard, because translations will
@@ -297,11 +290,12 @@
process of converting their articles to the new SSI-based layout;
this will be done automatically.
- * Easy updates by translators. Modified paragraphs, links, etc. will
- appear as "fuzzy" strings in the PO files, newly added ones will
- appear as "untranslated", and deleted will appear as "obsolete".
- It is substantially easier to update a PO file, where a keystroke
- takes you to the part that needs updating, whatever it may be.
+ * Easy updates by translators. Modified paragraphs, links, etc.
+ will appear as "fuzzy" strings in the PO files, newly added ones
+ will appear as "untranslated", and deleted will appear as
+ "obsolete". It is substantially easier to update a PO file, where
+ a keystroke takes you to the part that needs updating, whatever it
+ may be.
* Reporting and statistics. Since the basis is standard PO files,
which are the canonical source of the translations, it is easy to
@@ -313,18 +307,11 @@
As it happens in real life, we don't wear pink glasses and are aware of
certain limitations and annoyances of this semi-automatic system.
- * The official build is invoked thrice daily(1), because doing it
- more often will potentially generate more messages to the mailing
- list in the form of commit notifications. This has its drawback,
- since translators have to wait 8 hours until their PO files are
- updated, and another period for the `.LANG.html' articles to get
- generated, after they commit the updated POs. Additionally, any
- errors interrupt the build so they have to be fixed before the
- next articles are processed.
-
- ---------- Footnotes ----------
-
- (1) The "no-grace" items are rebuilt hourly.
+ * There is no easy way to preview the translations. The official
+ build is invoked twice an hour, because doing it much more often is
+ not feasible with current build server hardware. Additionally, any
+ errors interrupt the build so they have to be fixed before the next
+ articles are processed.
2 General Usage
***************
@@ -335,18 +322,17 @@
Murphy is an optimist.
--O'Rielly's Law
-
GNUN currently consists of a few makefiles, scripts and optional
-`generic.LANG.html' files, intended to contain article-independent but
+'generic.LANG.html' files, intended to contain article-independent but
team-specific information. They are designed to reside in the
-`server/gnun' directory, but this may change. In all examples in this
-manual, "invoking" means executing on the command line `make -C
+'server/gnun' directory, but this may change. In all examples in this
+manual, "invoking" means executing on the command line 'make -C
server/gnun [TARGET] [VARIABLE=VALUE ...]' while the working directory
-is the root in the `www' web repository. For the purpose of brevity, we
-will refer to the above command as simply `make', which is equivalent
-to `cd server/gnun; make'. It is desirable never to invoke `make' with
-the `-k' (`--keep-going') option, because an eventual error in only one
-make recipe might create a mess in many articles, both original and
+is the root in the 'www' web repository. For the purpose of brevity, we
+will refer to the above command as simply 'make', which is equivalent to
+'cd server/gnun; make'. It is desirable never to invoke 'make' with the
+'-k' ('--keep-going') option, because an eventual error in only one make
+recipe might create a mess in many articles, both original and
translated. Do this with caution, and generally only when debugging in
a safe environment.
@@ -357,45 +343,44 @@
=================
The central part of GNUnited Nations is a makefile; actually a
-`GNUmakefile' since it heavily relies on features and extensions
-available in GNU Make. Thus, invoking a build consists of typing
-`make' on the command line, or within cron. If you are deploying the
-software on a non-GNU machine, probably GNU Make is installed and
-available as `gmake' or `gnumake'. If not, you should consider
-installing it, since the build will fail otherwise. See
-`http://www.gnu.org/software/make' for information how to download and
-install GNU Make.
+'GNUmakefile' since it heavily relies on features and extensions
+available in GNU Make. Thus, invoking a build consists of typing 'make'
+on the command line, or within cron. If you are deploying the software
+on a non-GNU machine, probably GNU Make is installed and available as
+'gmake' or 'gnumake'. If not, you should consider installing it, since
+the build will fail otherwise. See <http://www.gnu.org/software/make>
+for information how to download and install GNU Make.
- If you don't specify a target, `make' by default builds the target
-`all', which in this case is to rebuild all translations that are not
+ If you don't specify a target, 'make' by default builds the target
+'all', which in this case is to rebuild all translations that are not
up-to-date. However, there are special targets that do not depend on
-the standard `all' target, which can be built by `make TARGET'. Some
-of the variables in the next section apply to them, and some do not.
+the standard 'all' target, which can be built by 'make TARGET'. Some of
+the variables in the next section apply to them, and some do not.
- Note that GNUN expects `GNUmakefile', `config.mk' and `gnun.mk' to
-be _present_ under `server/gnun' of the `www' web repository, otherwise
-`make' has no way to know what and how should be built. Another file,
-`priorities.mk', is expected to be present under `server/gnun' in order
-to define the priorities when reporting about the outdated
-translations. If absent, the `report' target will not sort the
-translations by priority. Since the location of the repository working
-copy is strictly user-specific and cannot be determined in any way,
-`GNUmakefile' and `config.mk' must be copied there manually after the
-package installation. For convenience, these files are installed in
-`$(pkgdatadadir)' (`/usr/local/share/gnun' with the default `prefix')
-so you can just create symlinks pointing to them, e.g.:
+ Note that GNUN expects 'GNUmakefile', 'config.mk' and 'gnun.mk' to be
+_present_ under 'server/gnun' of the 'www' web repository, otherwise
+'make' has no way to know what and how should be built. Another file,
+'priorities.mk', is expected to be present under 'server/gnun' in order
+to define the priorities when reporting about the outdated translations.
+If absent, the 'report' target will not sort the translations by
+priority. Since the location of the repository working copy is strictly
+user-specific and cannot be determined in any way, 'GNUmakefile' and
+'config.mk' must be copied there manually after the package
+installation. For convenience, these files are installed in
+'$(pkgdatadadir)' ('/usr/local/share/gnun' with the default 'prefix') so
+you can just create symlinks pointing to them, e.g.:
ln -s /usr/local/share/gnun/config.mk /path/to/www/server/gnun/
ln -s /usr/local/share/gnun/GNUmakefile /path/to/www/server/gnun/
- If next GNUN releases are installed with the same `--prefix', you
+ If next GNUN releases are installed with the same '--prefix', you
will always use the latest versions without the need for any manual
intervention.
- If you are playing with non-gnu.org setup, you also have to take
-care of `gnun.mk' and put a modified version under `server/gnun' of
-your hypothetical tree. (For gnu.org, that is not necessary since a
-proper `gnun.mk' is maintained in `www'.)
+ If you are playing with non-gnu.org setup, you also have to take care
+of 'gnun.mk' and put a modified version under 'server/gnun' of your
+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
--------------------------------------------
@@ -403,44 +388,44 @@
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
performing certain sanity checks at build time. The variables are
-specified on the command line, after `make', in the form
-`VARIABLE=value', e.g. `make VCS=yes'. In the future, additional
+specified on the command line, after 'make', in the form
+'VARIABLE=value', e.g. 'make VCS=yes'. In the future, additional
features will be implemented in a similar fashion.
-`VCS=no'
-`...'
+'VCS=no'
+'...'
+
Do not add any files to the repository. This is the default. You
- may as well omit to define `VCS' entirely; there is no special code
- that expects assigning the value `no'.
+ may as well omit to define 'VCS' entirely; there is no special code
+ that expects assigning the value 'no'.
-`VCS=yes'
+'VCS=yes'
Automatically add any new files in the repository (CVS, Subversion
or GNU Bazaar--the repository type is auto-determined at build
- time, `bzr' being a fallback).(1) These are any POT files, if they
+ time, 'bzr' being a fallback).(1) These are any POT files, if they
are generated for the first time, and the translated articles
- (`.LANG.html') in HTML format. In addition, if there is no
- `server/gnun/generic.LANG.html' file for the specific language an
+ ('.LANG.html') in HTML format. In addition, if there is no
+ 'server/gnun/generic.LANG.html' file for the specific language an
article is being generated, an empty file will be added. Finally,
any missing PO and their HTML counterparts of the server templates
- will be added, computed on the basis of the `template-files'
- variable.
+ will be added, computed on the basis of the 'extra-templates' and
+ 'optional-templates' variables.
-`VCS=always'
+'VCS=always'
Because GNU Make considers the targets up-to-date after a
successful build, if it was performed with no VCS interaction, the
- important newly created files will not be added (and committed
- when you do `cvs|svn|bzr commit') in the repository. Assigning
- this value enables additional check and forcefully adds all files.
- Use it sparingly, since it is very slow and generally less
- reliable.
+ important newly created files will not be added (and committed when
+ you do 'cvs|svn|bzr commit') in the repository. Assigning this
+ value enables additional check and forcefully adds all files. Use
+ it sparingly, since it is very slow and generally less reliable.
-`VALIDATE=no'
-`...'
+'VALIDATE=no'
+'...'
Does not perform validation of the HTML articles and PO files.
This is the default, and not defining this variable has the same
effect.
-`VALIDATE=yes'
+'VALIDATE=yes'
Validates all original articles before generating the POTs, to
ensure that the ultimate source is valid (X)HMTL. Also, validates
all generated translations in HTML format and all PO files. It is
@@ -448,47 +433,47 @@
tedious to fix the errors that are reported as a result of
enforcing validation.
- Articles defined in the variable `no-validate-articles' are never
+ Articles defined in the variable 'no-validate-articles' are never
checked for HTML validity. Its purpose was to skip validation of
HTML 5 articles, until the command-line validation tools are
updated to parse files that comply with this new standard. As of
version 0.5 GNUN supports HTML 5, so resorting to
- `no-validate-articles' should not be necessary.
+ 'no-validate-articles' should not be necessary.
-`NOTIFY=no'
-`...'
+'NOTIFY=no'
+'...'
Do not send email notifications about errors. This is the default.
-`NOTIFY=yes'
+'NOTIFY=yes'
If an error occurs, send a mail with a meaningful subject and the
error message as body to the concerned party. The variables
- `devel-addr', `web-addr' and `transl-addr' control the recipients;
- normally they should be set to the GNUN maintainers, webmasters
- and translators accordingly. These variables are defined in the
- configuration file `gnun.conf' and by default are set to
+ 'devel-addr', 'web-addr' and 'transl-addr' control the recipients;
+ normally they should be set to the GNUN maintainers, webmasters and
+ translators accordingly. These variables are defined in the
+ configuration file 'gnun.conf' and by default are set to
<address@hidden>.
-`ANNOUNCE=yes'
+'ANNOUNCE=yes'
If defined, automatic announcements for new translations will be
- sent to the address defined in the `ann-addr' variable (in
- `gnun.conf'). The email messages contain the translated article
+ sent to the address defined in the 'ann-addr' variable (in
+ 'gnun.conf'). The email messages contain the translated article
title as Subject, and the URL of the translation as its body. For
the official GNUN build, they are delivered to the
<address@hidden> mailing list and each language has its
own Mailman "topic". It is possible to subscribe to the list and
receive only traffic related to a specific language. *Note
- Mailing Lists: (web-trans)Mailing Lists.
+ (web-trans)Mailing Lists::.
The default behavior is not to send such announcements.
-`VERBOSE=yes'
- If defined, the value of the variables `templates-translated',
- `home-translated', `ALL_POTS', `articles-translated' and `gnunews'
- will be printed to the standard output. This is off by default,
- but recommended in general since it will show a bug in the
- computation of the basic variables.
+'VERBOSE=yes'
+ If defined, the value of the variables 'templates-translated',
+ 'ALL_POTS', 'articles-translated' and 'gnunews' will be printed to
+ the standard output. This is off by default, but recommended in
+ general since it will show a bug in the computation of the basic
+ variables.
-`GRACE=DAYS'
+'GRACE=DAYS'
If defined, ordinary articles that have fuzzy strings and are not
older than DAYS will not be regenerated. This functionality is
implemented specifically to prevent gratuitous replacement of
@@ -496,176 +481,177 @@
formatting changes in the original. The translator has time (the
"grace" period as defined in this variable) to review the changes
and unfuzzy the strings, while keeping the online translation
- intact. Note that this variable has no effect on the homepage,
- the server templates, gnunews and all articles defined in the
- variable `no-grace-articles'.
-
-`OUTDATED-GRACE=DAYS'
- Grace period for the out-of-date notice. When the variable
- `GRACE' is defined, `OUTDATED-GRACE' defaults to 60 days (*note
- grace period: GRACE.). The out-of-date notice is a special text
- (`server/outdated.html' in the `www' repository) that is inserted
+ intact. Note that this variable has no effect on the server
+ templates, gnunews and all articles defined in the variable
+ 'no-grace-articles'.
+
+'OUTDATED-GRACE=DAYS'
+ Grace period for the out-of-date notice. When the variable 'GRACE'
+ is defined, 'OUTDATED-GRACE' defaults to 60 days (*note grace
+ period: GRACE.). The out-of-date notice is a special text
+ ('server/outdated.html' in the 'www' repository) that is inserted
into every outdated translation when the period defined in this
variable is over; its purpose is to inform the reader that the
translation may not correspond to the original English article.
-`TEAM=LANG'
+'TEAM=LANG'
The translation team whose articles need to be checked for
- completeness. This variable is applicable only for the `report'
+ completeness. This variable is applicable only for the 'report'
target, and is mandatory for it. *Note report::.
-
- Note that `VCS=yes,always' is a valid combination: because POT files
-of the server templates are not handled by `always', running the build
+ Note that 'VCS=yes,always' is a valid combination: because POT files
+of the server templates are not handled by 'always', running the build
this way will commit any newly added files as specified in
-`TEMPLATE_LINGUAS' and will perform additional check at the end,
-`cvs|svn|bzr add'-ing all necessary files.
+'TEMPLATE_LINGUAS' and will perform additional check at the end,
+'cvs|svn|bzr add'-ing all necessary files.
- When validation is enabled (i.e. with `VALIDATE=yes'), the original
+ When validation is enabled (i.e. with 'VALIDATE=yes'), the original
English articles are validated first, before any commands that generate
-the other files, and `make' exits with an error on the first
-encountered article. This is done on purpose, to prevent the
-propagation of an eventual error in the markup of the original article
-to all translations.
+the other files, and 'make' exits with an error on the first encountered
+article. This is done on purpose, to prevent the propagation of an
+eventual error in the markup of the original article to all
+translations.
- Validation of the translated `.LANG.html' is performed after it is
+ Validation of the translated '.LANG.html' is performed after it is
preliminarily generated as a temporary file. When no errors are found,
the translation is updated; otherwise the real file is not changed (and
it is not added if absent)--the build will fail and further processing
of the remaining articles will not be performed. The translator has
time until the next run to fix the error--usually by modifying the
-corresponding `.LANG.po' file.
+corresponding '.LANG.po' file.
- If notification is enabled (`NOTIFY=yes'), and the build system
-encounters errors (mostly when validating articles), email messages
-will be sent to the party that is expected to fix the error. The
-subject of the messages always includes the problematic article, for
-example:
+ If notification is enabled ('NOTIFY=yes'), and the build system
+encounters errors (mostly when validating articles), email messages will
+be sent to the party that is expected to fix the error. The subject of
+the messages always includes the problematic article, for example:
Subject: [GNUN Error] gnu/gnu.fa.html is not valid HTML
---------- Footnotes ----------
(1) When GNU Bzr is used, files are added locally only; you need to
-take care to use `bzr push' manually (or via cron) to take care of
-effectively adding them to the public repository. *Note triggers::,
-for a short explanation.
+take care to use 'bzr push' manually (or via cron) to take care of
+effectively adding them to the public repository. *Note triggers::, for
+a short explanation.
2.1.2 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 or canned command sequences that are more complicated, and
-more importantly, whose arguments are variables computed at the time
-`make' reads the makefiles--the filesets they affect are specific and
-already defined, one way or another.
+under certain circumstances. Think of them like semi-automated commands
+or canned command sequences that are more complicated, and more
+importantly, whose arguments are variables computed at the time 'make'
+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.1.2.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 homepage, the server
-templates, gnunews, and all articles defined in the variable
-`no-grace-articles' (*note grace period: GRACE.).
+The 'no-grace-items' target regenerates a limited set of articles that
+are not affected by the grace period, namely, the server templates,
+gnunews, and all articles defined in the variable 'no-grace-articles'
+(*note grace period: GRACE.).
- This target can be rebuilt more often than `all'; it is invoked
-hourly by the official GNUN cron job.
+ This target can be rebuilt more often than 'all'; however, it is
+currently not used.
-2.1.2.2 The `update-localized-URLs' Target
+2.1.2.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
+The 'update-localized-URLs' target invokes a script that generates the
+'localized-urls.mk' file. This file includes the list of URLs that
should be localized, it is extracted from special comments in the HTML
source (*note Localized URLs::).
This target is meant to be rebuilt nightly.
-2.1.2.3 The `sync' Target
+2.1.2.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
+The 'sync' target has a simple task: synchronize the _original English_
+articles from a canonical repository, like 'www'. It is very important
that such synchronization happens, because it is desirable to develop
-the software and add more features in a testbed, while the `official
+the software and add more features in a testbed, while the 'official
instance' operates on the official repository in a predictable way.
- It is recommended that you `build' the `sync' target from a cron
-job, some time before the general build occurs. That way,
-prerequisites (e.g. original `.html' articles) will be updated from the
-canonical repository and the subsequent `make' invocation, possibly run
-by cron as well, will update all translations.
+ It is recommended that you 'build' the 'sync' target from a cron job,
+some time before the general build occurs. That way, prerequisites
+(e.g. original '.html' articles) will be updated from the canonical
+repository and the subsequent 'make' invocation, possibly run by cron as
+well, will update all translations.
- The `VCS' variable affects the behavior: if it is defined to `yes'
-then the synchronized files are committed to the `testing' repository,
+ The 'VCS' variable affects the behavior: if it is defined to 'yes'
+then the synchronized files are committed to the 'testing' repository,
i.e. the DESTINATION. In addition, if a file meant to be synchronized
disappeared from the SOURCE, a warning mail will be sent to the address
-defined in the `devel-addr' variable (defined in `gnun.conf'). The
+defined in the 'devel-addr' variable (defined in 'gnun.conf'). The
build will continue without failure, and will sync and commit all other
files, but will send the same email message again if the file is still
-present in the `files-to-sync' variable during a subsequent invocation.
+present in the 'files-to-sync' variable during a subsequent invocation.
- In addition, `sync' synchronizes all "verbatim" server templates
-that are not under GNUN's control, such as `server/header.html',
-`server/banner.html', `server/footer.html' and their translations, as
-defined in the `verbatim-templates' variable. This is important, as
-these files may change in the master repository, while the validation
-of the HTML files in the development repository will be performed with
-the old templates expanded, thus making this specific test more or less
+ In addition, 'sync' synchronizes all "verbatim" server templates that
+are not under GNUN's control, such as 'server/header.html',
+'server/banner.html', 'server/footer.html' and their translations, as
+defined in the 'verbatim-templates' variable. This is important, as
+these files may change in the master repository, while the validation of
+the HTML files in the development repository will be performed with the
+old templates expanded, thus making this specific test more or less
bogus.
- `VCS=always' has no effect on this target, as well as `VALIDATE'.
+ 'VCS=always' has no effect on this target, as well as 'VALIDATE'.
-2.1.2.4 The `report' Target
+2.1.2.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.
-The way to check this is by running `make report TEAM=LANG', where LANG
-is the language code, as usual. Thus, to check all French
-translations, one would run
+The way to check this is by running 'make report TEAM=LANG', where LANG
+is the language code, as usual. Thus, to check all French translations,
+one would run
make report TEAM=fr
This target checks only the PO files; the old translations that
haven't been converted to PO files are reported, but there is no
-reasonable way to check if they are up-to-date. In fact, this is one
-of the main reasons GNUN is being developed, if you recall.
+reasonable way to check if they are up-to-date. In fact, this is one of
+the main reasons GNUN is being developed, if you recall.
- When present, `priorities.mk' defines four classes of articles by
+ When present, 'priorities.mk' defines four classes of articles by
priority: PRIORITY-ARTICLES for the most important translations,
IMPORTANT-ARTICLES for the second priority level, IMPORTANT-DIRECTORIES
for the directories with important articles; all other translations are
reported as less important.
-2.1.2.5 The `triggers' Target
+ There is also a script, 'gnun-report', to generate HTML reports.
+*Note gnun-report::.
+
+2.1.2.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'.
+the main build and _after_ 'cvs|svn|bzr commit'.
- The `triggers' target currently executes the files named
-`ARTICLE.LANG.html.hook' in the `server/gnun' directory--these files
-are created during the main build and each of them contains the command
-to update the timestamp of the prerequisite based on the timestamp of
-the target that must be rebuilt. Finally, it deletes all those
-`*.hook' files.
+ The 'triggers' target currently executes the files named
+'ARTICLE.LANG.html.hook' in the 'server/gnun' directory--these files are
+created during the main build and each of them contains the command to
+update the timestamp of the prerequisite based on the timestamp of the
+target that must be rebuilt. Finally, it deletes all those '*.hook'
+files.
This is the rule that takes care of actually sending the
-announcements if `ANNOUNCE=yes'. Since it is a completely valid
+announcements if 'ANNOUNCE=yes'. Since it is a completely valid
scenario to have a new translation which is initially invalid HTML, the
-canned command sequence for announcements is recorded in `*.hook-ann'
-files, and they are treated by `triggers' in a different way. A newly
-added `.LANG.po' file may be invalid, in which case the HTML file is
-not added, and it is not appropriate to announce it as a new
-translation as it is completely useless for the general public. The
-`triggers' rule detects this case, and postpones the announcement to
-the next build attempt, when the generated HTML translation is supposed
-to be human-readable.
+canned command sequence for announcements is recorded in '*.hook-ann'
+files, and they are treated by 'triggers' in a different way. A newly
+added '.LANG.po' file may be invalid, in which case the HTML file is not
+added, and it is not appropriate to announce it as a new translation as
+it is completely useless for the general public. The 'triggers' rule
+detects this case, and postpones the announcement to the next build
+attempt, when the generated HTML translation is supposed to be
+human-readable.
To summarize, for effective operation GNUN should be invoked
-automatically as `make; cvs|svn|bzr commit -m ...; make triggers'. To
+automatically as 'make; cvs|svn|bzr commit -m ...; make triggers'. To
illustrate this, here is a concrete example showing the official job
running at fencepost.gnu.org:
@@ -678,29 +664,29 @@
The above example is for CVS; if the underlying repository is
Subversion, they need to be amended accordingly. If it is GNU Bzr,
-remember to add a `bzr push' after commit (in the usual scenario),
+remember to add a 'bzr push' after commit (in the usual scenario),
otherwise changes will be committed only locally. Since a distributed
Version Control System can be used in multiple (sometimes radically
-different) ways, this step cannot be anticipated and therefore cannot
-be automated. Adding the `push' command in the makefile rules would
-not work if a so called "bound branch" is used, for instance.
+different) ways, this step cannot be anticipated and therefore cannot be
+automated. Adding the 'push' command in the makefile rules would not
+work if a so called "bound branch" is used, for instance.
In the future, this target may be extended further to do other useful
things that should be "triggered" after the main build.
-2.1.2.6 The `validate-all' Target
+2.1.2.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 files, so errors in those included files could pass unnoticed.
+The 'validate-all' target validates all HTML pages under GNUN's control.
+It is needed because GNUN doesn't track dependencies on the included
+files, so errors in those included files could pass unnoticed.
This target is invoked once a day by the official GNUN cron job.
2.2 Defining Articles to be Built
=================================
-The file `gnun.mk' contains variable definitions, based on which almost
+The file 'gnun.mk' contains variable definitions, based on which almost
all other important variables are computed. In other words, the
variables defined in that file directly affect the overall behavior of
the build process.
@@ -708,90 +694,68 @@
There are two types of variables, which are specifically separated in
order to make translators' life easier: variables that translators are
free to modify and variables that are modified by the web-translators
-staff(1), ideally after performing some local tests. A translation
-team leader should update only `FUZZY_DIFF_LINGUAS', `TEMPLATE_LINGUAS'
-and `HOME_LINGUAS'; everything else is supposed to be built
-automagically, without manual intervention. If not, that is a bug that
-should be reported and fixed.
+staff(1), ideally after performing some local tests. A translation team
+leader should update only 'FUZZY_DIFF_LINGUAS', 'TEMPLATE_LINGUAS';
+everything else is supposed to be built automagically, without manual
+intervention. If not, that is a bug that should be reported and fixed.
-`TEMPLATE_LINGUAS'
+'TEMPLATE_LINGUAS'
A space-separated list with languages. Add here your language code
_if and only if_ you have all the SSI templates translated, and
- have already committed all template files:
-
- - `server/po/head-include-2.LANG.po'
-
- - `server/po/body-include-1.LANG.po'
-
- - `server/po/body-include-2.LANG.po'
-
- - `server/po/footer-text.LANG.po'
-
- - `server/po/outdated.LANG.po',
-
- as well as the templates that are not under GNUN's control and are
- translated manually, like
+ have already committed all template files listed in the
+ 'extra-templates' variable in 'server/gnun/gnun.mk', as well as the
+ templates that are not under GNUN's control and are translated
+ manually, like
+
+ - 'server/header.LANG.html'
+ - 'server/head-include-1.LANG.html'
+ - 'server/html5-header.LANG.html'
+ - 'server/html5-head-include-1.LANG.html'
+ - 'server/banner.LANG.html'
+ - 'server/footer.LANG.html'.
+
+'extra-templates'
+
+ The 'extra-templates' variable lists templates under GNUN control;
+ they are rebuilt from corresponding TEMPLATE.LANG.po files; when
+ the TEMPLATE.LANG.po file is absent, GNUN initializes and commits a
+ file with empty 'msgstr's.
- - `server/header.LANG.html'
+'optional-templates'
- - `server/head-include-1.LANG.html'
-
- - `server/html5-header.LANG.html'
-
- - `server/html5-head-include-1.LANG.html'
-
- - `server/banner.LANG.html'
-
- - `server/footer.LANG.html'.
-
-`extra-templates'
- The EXTRA-TEMPLATES variable lists additional templates under GNUN
- control; they are rebuilt from corresponding TEMPLATE.LANG.po
- files like those hardcoded in GNUmakefile (*note hardcoded
- templates::); when the TEMPLATE.LANG.po file is absent, GNUN
- initializes and commits a file with empty `msgstr's.
-
-`optional-templates'
- The OPTIONAL-TEMPLATES variable defines optional templates under
+ The 'optional-templates' variable defines optional templates under
GNUN control. Those are the templates of low priority items, like
news lines included in some pages. They are managed like the
additional templates listed in the EXTRA-TEMPLATES variable, except
- TEMPLATE.LANG.po is not added when absent, and
-
- - their POTs end in `.pot.opt' rather than `.pot'.
+ - their POTs end in '.pot.opt' rather than '.pot'.
This way, the scripts reporting outdated translations and
translations that hasn't been converted to PO files won't complain
about them unless the team decides to actually commit
TEMPLATE.LANG.po.
-`FUZZY_DIFF_LINGUAS'
+'FUZZY_DIFF_LINGUAS'
Add your language code here if you want GNUN to add differences to
- previous `msgid's in your PO files. The differences are shown in
- the default `wdiff' format. *Note wdiff: (wdiff)wdiff, for more
+ previous 'msgid's in your PO files. The differences are shown in
+ the default 'wdiff' format. *Note wdiff: (wdiff)wdiff, for more
information.
-`HOME_LINGUAS'
- Add your language code if you have already committed
- `po/home.LANG.po', that way the homepage for your language will be
- built. It is not acceptable to have your language code defined in
- this variable, but not in `TEMPLATE_LINGUAS'.
-
-`ROOT'
- Add here articles that are in the server root, like
- `keepingup.html' and `provide.html'. Always write only the
+'ROOT'
+ Add here articles that are in the server root, like 'home.html',
+ 'keepingup.html' and 'provide.html'. Always write only the
basename of the article, i.e. if you add these two articles, the
- value of `ROOT' should be `keepingup provide'. This is true for
+ value of 'ROOT' should be 'keepingup provide'. This is true for
all the variables that expect values in the form of article names.
-`ALL_DIRS'
- The list of directories containing articles, like `philosophy',
- `gnu', `licenses', etc.
-
-`gnu'
-`philosophy'
-`...directory...'
+'ALL_DIRS'
+ The list of directories containing articles, like 'philosophy',
+ 'gnu', 'licenses', etc.
+
+'gnu'
+'philosophy'
+'...directory...'
A space-separated list of basenames for articles residing in
DIRECTORY, for which POTs will be generated and updated when the
original article changes. If an article is missing here, there is
@@ -806,68 +770,66 @@
2.3 Working with PO Files
=========================
-We anticipate that some gnu.org translators will find this format odd
-or inconvenient, if they never happened to work with PO files before.
+We anticipate that some gnu.org translators will find this format odd or
+inconvenient, if they never happened to work with PO files before.
Don't worry, you will soon get accustomed to it. It is the established
format for translations in the Free World, and you should have no
problems if you have translated software before.
The most efficient way to edit a PO file is using a specialized PO
-editor, because each of them represents and treats gettext messages in
-a consistent and predictable way. It is possible to edit a PO file
-with an ordinary plain text editor, but extra effort would be necessary
-to make it valid. Here is a list of widely used PO editors:
+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
+ 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'.
+ '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/'.
+ <http://projects.gnome.org/gtranslator/>.
* Lokalize--the KDE 4 editor. See
- `http://userbase.kde.org/Lokalize'.
+ <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'.
+ * 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'.
+ <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'.
+ <http://www.vim.org/scripts/script.php?script_id=2530>.
- * Various web-based editors. *Note Savannah VCS:
- (web-trans)Savannah VCS.
+ * Various web-based editors. *Note (web-trans)Savannah VCS::.
2.3.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
+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
+<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 msginit Invocation: (gettext)msginit
-Invocation.
+ 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::.
@@ -895,43 +857,43 @@
conventions, and the rules for gnu.org translations. For reference,
here is a list with all fields explained:
-`Project-Id-Version'
+'Project-Id-Version'
Add here the filename of the original article, without the
sub-directory, like "body-include-1.html" or "free-sw.html".
-`POT-Creation-Date'
+'POT-Creation-Date'
Do not edit this field, it is already set when the POT is created.
-`PO-Revision-Date'
+'PO-Revision-Date'
Likewise, do not edit. This field is automatically filled in when
you save the file with any decent PO editor.
-`Last-Translator'
+'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
+ 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:
Elvis Parsley <address@hidden>
-`Language-Team'
+'Language-Team'
This field should contain the mailing list on which the translation
team can be reached--usually <address@hidden>. Example:
Czech <address@hidden>
-`MIME-Version'
+'MIME-Version'
Leave it like it is.
-`Content-Type'
- Usually this is `text/plain; charset=UTF-8'; change the charset
+'Content-Type'
+ Usually this is 'text/plain; charset=UTF-8'; change the charset
accordingly.
-`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.
+'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.
Here is an example of a properly edited header:
@@ -957,33 +919,33 @@
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
+and improves the performance of 'GNUmakefile.team''s 'publish' rule
(*note GNUmakefile.team Variables::).
There are some special messages that appear in the POT and PO:
-`*GNUN-SLOT: TRANSLATOR'S NOTES*'
+'*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, that is, <SPC>.
-`*GNUN-SLOT: TRANSLATOR'S CREDITS*'
+'*GNUN-SLOT: TRANSLATOR'S CREDITS*'
This is again optional, and should contain the name (and address)
- of the person who made the translation. "Translate" this string
- as a space (<SPC>) if you do not want your name to appear there.
+ of the person who made the translation. "Translate" this string as
+ a space (<SPC>) if you do not want your name to appear there.
*Note Credits Slot::.
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
+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
+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.
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
+in your '.emacs'; doing 'M-x po-wrap' while in PO mode will wrap all
long lines:
(defun po-wrap ()
@@ -1010,20 +972,20 @@
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
+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
+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.
+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
+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
+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:
@@ -1047,28 +1009,28 @@
"<li id=\"TransNote1\">Note clarifying the text.</li>\n"
"</ol>\n"
- Certainly, everything in the `msgstr's should be in your native
+ 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.
+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
+ 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
+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
+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.
@@ -1096,43 +1058,42 @@
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
+ 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.
+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
+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
+ 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
+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'"
+ 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"
+ You get 'foo.LANG.po' where all messages are marked as "fuzzy"
(unless you use a compendium); you still should make sure that the
translations correspond to the original and remove those "fuzzy" marks.
-The script adds differences against previous `msgid's to facilitate
+The script adds differences against previous 'msgid's to facilitate
checking.
There is no need to delete the existing HTML translation, GNUN will
@@ -1160,27 +1121,23 @@
-----------------------------------
*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.
+has been obsolete for some time now, as they are being fed automatically
+from Planet GNU (<http://planet.gnu.org>). Nevertheless, the
+information below is accurate to the extent that the support for the
+old-fashioned way is still available.
The GNU website has infrastructure for supporting "What's New", also
known as "GNU News". Entries are added in a special plain text file,
-`server/whatsnew.txt' and are used to build `server/whatsnew.include'
-and `gnusflashes.include'. The former is used by
-`server/whatsnew.html', while the latter is included in the homepage.
-
- GNUN has additional rules for building `whatsnew.pot', which
-contains a combination of all necessary strings for
-`server/whatsnew.LANG.html', `server/whatsnew.LANG.include' and
-`gnusflashes.LANG.include'. There is nothing unusual in this POT file,
-so it should be translated like any other. When you commit
-`whatsnew.LANG.po', it will be used to generate all three localized
-files. In addition, if there is a homepage for this language, it will
-be rebuilt when `gnusflashes.LANG.include' is generated for the first
-time in order the translated homepage to include it instead of
-`gnusflashes.include'.
+'server/whatsnew.txt' and are used to build 'server/whatsnew.include'
+and 'gnusflashes.include'. The former is used by
+'server/whatsnew.html', while the latter was included in the homepage.
+
+ GNUN has additional rules for building 'whatsnew.pot', which contains
+a combination of all necessary strings for 'server/whatsnew.LANG.html',
+'server/whatsnew.LANG.include' and 'gnusflashes.LANG.include'. There is
+nothing unusual in this POT file, so it should be translated like any
+other. When you commit 'whatsnew.LANG.po', it will be used to generate
+all three localized files.
Note that localized RSS feeds are not supported on purpose, as it
would be annoying for subscribers if new items appear in English and
@@ -1194,16 +1151,16 @@
files editing.
* When you install a new translation of an article (that is different
- from a server template or the homepage), all you need to do is to
- add your PO file in the appropriate `/po' sub-directory.
+ 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
+ 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.
+ * If you don't feel comfortable editing 'gnun.mk', do not worry.
Someone from the GNUN maintainers will notice and will amend
- `TEMPLATE_LINGUAS' or `HOME_LINGUAS' for you, as appropriate.
+ '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
@@ -1213,10 +1170,10 @@
"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.
+ 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
@@ -1224,14 +1181,14 @@
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,
+ 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
+ name to the '<address>'; otherwise it looks awkward in most
languages. Example:
# type: Content of: <div><address>
@@ -1244,44 +1201,44 @@
as a replacement for common non-ASCII characters. They are harder
to write and serve no purpose.
- * Wrapping of `msgstr' using `M-q' in Emacs (or other means) is
+ * 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.
+ will have predictable results. This will help tremendously for the
+ conversion to other formats, like Texinfo. Also, note that not all
+ elements are wrapped by default, so deliberately wrapping the text
+ inside the 'msgstr' could lead to an invalid page or a page that is
+ valid, but is rendered incorrectly by the web browser.
-2.3.5 The `generic.LANG.html' File
+2.3.5 The 'generic.LANG.html' File
----------------------------------
-The files `server/gnun/generic.LANG.html' are special: if no such 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
+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:
+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/www-foo";>the
+ 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
+ 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
+_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
+all '.LANG.html', including the homepage), will be modified to include
the contents of this special file.
-2.3.6 The `languages.txt' File
+2.3.6 The 'languages.txt' File
------------------------------
-The file `server/gnun/languages.txt' is used when generating lists of
+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
@@ -1313,19 +1270,19 @@
--------------------------------------------------------
GNUN operates on the "official" Web repository of the Savannah project
-`www', where normally only the coordinators of translation teams have
+'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
-original message. Mutual reviews and proof-reading of translations is
-a crucial part of the process. Furthermore, team work is great for 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.
- The file `GNUmakefile.team' in the `gnun' package is a template,
+ The file 'GNUmakefile.team' in the 'gnun' 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.
@@ -1344,20 +1301,20 @@
All members and the team leader commit in their project's
repository--when a translation is ready, the leader checks it in in the
-official `www' repository. If an original article changes, a build
+official 'www' repository. If an original article changes, a build
could be invoked to synchronize (i.e. merge) the changes and optionally
automatically commit them so that the draft PO files are updated. A
translator would then normally update the PO file, and commit it again
in the project's Sources repository, from where the coordinator will
-pick it up and install it in `www'.
+pick it up and install it in 'www'.
To take advantage of this semi-automation, rename this template
-`GNUmakefile.team' as `GNUmakefile' and install it in the root of your
+'GNUmakefile.team' as 'GNUmakefile' 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 `/po'
-sub-directories; they are redundant here. Instead, install the PO
-files in the normal locations where the corresponding `.LANG.html'
-resides in `www', for example:
+sub-directories exactly as they are in 'www'. Do not create the '/po'
+sub-directories; they are redundant here. Instead, install the PO files
+in the normal locations where the corresponding '.LANG.html' resides in
+'www', for example:
Root
|
@@ -1382,113 +1339,112 @@
|
+--...
- Add `priorities.mk' in order to make the `report' target sort the
+ Add 'priorities.mk' in order to make the 'report' target sort the
files by priority.
The next sections explain how to adopt the makefile for your team and
how to invoke a "build".
-2.3.7.1 Adopting `GNUmakefile.team' for a Specific Team
+2.3.7.1 Adopting 'GNUmakefile.team' for a Specific Team
.......................................................
To adjust the makefile for your team, you need to edit two variables.
-`TEAM'
- Set this to the language code, like `bg' or `pt-br'.
+'TEAM'
+ Set this to the language code, like 'bg' or 'pt-br'.
-`wwwdir'
+'wwwdir'
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 `~/projects/www-LANG' and the `www' Web
- repository at `~/projects/www', the value of `wwwdir' should be
- `../www/' or `/home/USER/projects/www/'. Note the slash at the
+ 'www' repository. So if you have checked out your project's
+ Sources repository at '~/projects/www-LANG' and the 'www' Web
+ repository at '~/projects/www', the value of 'wwwdir' should be
+ '../www/' or '/home/USER/projects/www/'. Note the slash at the
end, it is important.
If two variants of one language share the same project and repository
-(such as `zh-cn' and `zh-tw'), they should maintain two directories
-with two `GNUmakefile's and each directory having its own tree.
+(such as 'zh-cn' and 'zh-tw'), they should maintain two directories with
+two 'GNUmakefile's and each directory having its own tree.
Some variables are specified on the command line, and alter the
behavior of the build process.
-`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.
+'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
+'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
+ only those that resulted from running 'msgmerge'. Thus, it is
better to use a separate working copy dedicated solely for this
purpose.
-Targets in `GNUmakefile.team'
-.............................
+2.3.7.2 Targets in 'GNUmakefile.team'
+.....................................
-`update'
- Updates the repositories. Does nothing unless `VCS=yes'.
+'update'
+ Updates the repositories. Does nothing unless 'VCS=yes'.
-`sync'
+'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'
+'report'
Verifies which translations are complete, and prints a list (with
statistics) of those that need to be updated.
-`format'
+'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
+ 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.
+ 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
+ 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
+ '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
+'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
+ 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'
+ 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
+ sane to run 'sync' and correct any "fuzzy" messages and other
problems, if necessary.
- The `publish' rule does not depend on `sync' explicitly, because
+ 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
+ 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'.
+ a good practice to examine the output of 'cvs diff'.
- Invoking `make publish' prints warnings and does not actually copy
+ 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.
+ 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:
+ editing or just merging contributions from team members), one would
+ do:
$ make sync VCS=yes
$ make publish
@@ -1499,12 +1455,12 @@
$ cvs diff
$ cvs commit -m "Some descriptive message."
-`clean'
+'clean'
Deletes all backup and auto-generated files that some PO editors
- leave behind, namely--`FILE.po~', `FILE.po.bak' and `FILE.mo'.
+ leave behind, namely--'FILE.po~', 'FILE.po.bak' and 'FILE.mo'.
- `make VCS=yes' is the recommended command to be run periodically.
-To check the status of the translations, run `make report'.
+ '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
@@ -1514,9 +1470,9 @@
they were updated by the team members but not installed by the
coordinator). Either way, if you come up with something interesting, it
would be nice to send a message to <address@hidden>, so that
-`GNUmakefile.team' gets updated for all teams' benefit.
+'GNUmakefile.team' gets updated for all teams' benefit.
-2.3.7.2 Automatic Synchronization and Status Reports
+2.3.7.3 Automatic Synchronization and Status Reports
....................................................
It is convenient to invoke such synchronization automatically, for
@@ -1538,9 +1494,9 @@
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.
+ *Caution:* Most cron implementations do not allow the character '\'
+as a line continuation character--the example shown is made that way for
+better readability.
2.3.8 Using Compendia
---------------------
@@ -1552,33 +1508,33 @@
article, GNUN will use compendia to automatically fill the translations
for the new version of the strings.
- 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'.
+ 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'.
- The first kind, `master.LANG.po', can be used to simultaneously
+ 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
+'ARTICLE.LANG.po'. When 'master.LANG.po' is updated, the translations
will be rebuilt. GNUN doesn't modify this kind of compendia.
- The second kind, `compendium.LANG.po', is updated automatically.
+ 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
+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.
-
- 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
+'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.
+
+ 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'.
+specific file, 'exclude.pot', and when that file contains the string, it
+won't be added to 'compendium.pot'.
2.4 Tips and Hints for Webmasters
=================================
@@ -1595,13 +1551,13 @@
If you plan to edit a certain page extensively, please do so within
the period between two adjacent GNUN builds--i.e. within a day. That
way, the POT will be regenerated only once, and translators who are
-quick to update it immediately won't be disappointed if it changes
-again in the next run.
+quick to update it immediately won't be disappointed if it changes again
+in the next run.
2.4.1 Validation
----------------
-The script `gnun-validate-html' is useful for webmasters who want to
+The script 'gnun-validate-html' is useful for webmasters who want to
verify if their (potentially intrusive) changes result in a valid
markup. Before committing your changes, you can check whether the file
is valid by running
@@ -1629,47 +1585,47 @@
msgstr ""
As per the established convention, start the comment with
-`TRANSLATORS:' to catch their attention, and do not add a space after
-the beginning of the HTML comment (`<!--'), since this will
+'TRANSLATORS:' to catch their attention, and do not add a space after
+the beginning of the HTML comment ('<!--'), since this will
unnecessarily indent the comment in the POT.
2.4.3 Modifying Boilerplates
----------------------------
-*Warning:* Any significant structural diversion from `boilerplate.html'
+*Warning:* Any significant structural diversion from 'boilerplate.html'
in a specific article may result in errors from GNUN. Any untested
intrusive updates to the server templates (such as changing the entire
look & feel of the site) will probably break _all_ translations under
GNUN's control. Of course, this does not mean that no changes should
-happen--only that they must be applied in our sandbox first, to ensure
-a smooth transition.
+happen--only that they must be applied in our sandbox first, to ensure a
+smooth transition.
2.4.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
-versions appear in the respective translations, GNUN should be told
-what URLs need localization. It can be done with HTML comments like
+versions appear in the respective translations, GNUN should be told what
+URLs need localization. It can be done with HTML comments like
<!-- GNUN: localize URL /philosophy/category.png,
/licenses/template-diagram.png and /graphics/jesus-cartoon.jpg -->
The URLs are separated with spaces. One trailing comma at the end of
-every word is removed if present. Words without a dot, such as `and',
+every word is removed if present. Words without a dot, such as 'and',
do not count as URLs; they are ignored.
Such comments will be extracted nightly and compiled into per-article
-lists of URLs in `localized-urls.mk'.
+lists of URLs in 'localized-urls.mk'.
After every build GNUN will check if the respective
-`philosophy/category.LANG.png' and other files are present in the
+'philosophy/category.LANG.png' and other files are present in the
working copy and substitute the strings in the HTML file of the
translation.
- GNUN relies on URLs being absolute, starting from the root homepage
+ GNUN relies on URLs being absolute, starting from the root directory
as required in
-`http://www.gnu.org/server/fsf-html-style-sheet.html#FilenameAndURLGuidelines'.
+<http://www.gnu.org/server/fsf-html-style-sheet.html#FilenameAndURLGuidelines>.
And please don't forget to commit the image in its source form
(typically, in SVG format).
@@ -1685,7 +1641,7 @@
In order to make our translators' life easier, it is desirable to
keep the paragraphs short (no more than 350-700 characters). If
rearranging the paragraphs is not an option, you can use a conventional
-separator, `<span class="gnun-split"></span>':
+separator, '<span class="gnun-split"></span>':
<p>GNUN splits typical text by paragraphs, and translators write
the translations for the resulting parts of the text
@@ -1715,87 +1671,63 @@
mechanical actions, like initially filling the headers in the PO files.
They all can be invoked separately, as stand-alone programs.
-3.1.1 The `make-prototype' Script
----------------------------------
+3.1.1 The 'gnun-add-fuzzy-diff' Script
+--------------------------------------
-This is a Guile script which makes the "prototype" file,
-`foo.LANG.proto', from which the POT is generated. GNUN is designed in
-such a way, because it would be no big improvement if links to other
-translations ended up in the POT--it would mean that translators would
-have to manually update their PO file when a new translation is
-added.(1)
-
- In addition, `make-prototype' guards the timestamp (the $Date$ RCS
-keyword) in order the timestamp of the translation to be updated _only_
-when there are actual changes, being automatic or not.
-
- Finally, `make-prototype' "injects" the artificial elements
-`*GNUN-SLOT: TRANSLATOR'S NOTES*' and `*GNUN-SLOT: TRANSLATOR'S
-CREDITS*', thanks to which it is possible to insert the name of the
-translator and translator's notes, if necessary. *Note New
-Translation::.
-
- Here are the options that `make-prototype' accepts:
-
-`--article'
- Process the input file as an article. This is the default.(2)
-
-`--home'
- Process the input article as a homepage. Specify this when you
- want to create a `.proto' file for a homepage.
-
-`-i'
-`--input=FILE'
- Input file, which can be a common article (essay) or a homepage.
-
-`-g'
-`--generic=FILE'
- Common notes for a translation team; this is the
- `generic.LANG.html' file. *Note generic.LANG.html::.
-
-`-o'
-`--output=FILE'
- The file where to write the output of the script.
+This script adds comments with differences of current 'msgid's against
+previous ones to fuzzy translations in a PO file. To produce the
+differences 'wdiff' is used. This may be useful to figure out what has
+changed. In fact, it wraps around a 'sed' script used in GNUN
+internally.
-`--version'
- Print copyright and version information on the standard output.
+ gnun-add-fuzzy-diff [OPTION...] [FILE]
-`--help'
- Print usage information on stdout.
+'-i'
+'--in-place'
+ Edit the file in place.
- ---------- Footnotes ----------
+'--version'
+ Display copyright and version information and exit.
- (1) Since version 0.5, those links are maintained in a separate file
-included with SSI directives.
+'--help'
+ Display usage information and exit.
- (2) As of version 0.5, this option is considered obsolete because
-the lists of translations are implemented as an automatically generated
-file included via SSI directive just like the respective list is
-included in the homepage. *Note languages.txt::. In the future, both
-the `--article' and the `--home' option will be removed.
+3.1.2 The 'gnun-diff-po' Script
+-------------------------------
-3.1.2 The `gnun-add-fuzzy-diff' Script
---------------------------------------
+This script compares two versions of a PO file. It produces a HTML page
+with a table that contains original strings with highlighted differences
+of their translations.
-This script adds comments with differences of current `msgid's against
-previous ones to fuzzy translations in a PO file. To produce the
-differences `wdiff' is used. This may be useful to figure out what has
-changed. In fact, it wraps around a `sed' script used in GNUN
-internally.
+ If the sets of original strings in the input PO files differ, one of
+them will be merged with the other in order to eliminate the differences
+in the original strings.
- gnun-add-fuzzy-diff [OPTION...] [FILE]
+ The results are written to standard output. Example:
-`-i'
-`--in-place'
- Edit the file in place.
+ gnun-diff-po [OPTION...] PO_FILE1 PO_FILE2 > diff.html
+
+'-1'
+'--merge-against-first'
+ Adjust the original strings of PO_FILE2 against PO_FILE1 when their
+ sets differ. This is the default.
+
+'-2'
+'--merge-against-second'
+ Adjust the original strings of PO_FILE1 against PO_FILE2 when their
+ sets differ.
+
+'-t'
+'--title=TITLE'
+ Specify the title of the output HTML page.
-`--version'
+'--version'
Display copyright and version information and exit.
-`--help'
+'--help'
Display usage information and exit.
-3.1.3 The `gnun-init-po' Script
+3.1.3 The 'gnun-init-po' Script
-------------------------------
This script initializes a PO file using POT generated with GNUN, and
@@ -1804,91 +1736,129 @@
gnun-init-po [OPTION...] POT
-`-C'
-`--compendium=COMP'
+'-C'
+'--compendium=COMP'
Specify a compendium to use. You can issue this option many times
- to use multiple compendia simultaneously. The suffix of
- compendium is used when the language suffix is not specified with
- the `--language' option.
+ to use multiple compendia simultaneously. The suffix of compendium
+ is used when the language suffix is not specified with the
+ '--language' option.
-`-d'
-`--disable-diffs'
+'-d'
+'--disable-diffs'
Don't add diffs to previous messages.
-`-g'
-`--team="TEAM <LIST>"'
+'-g'
+'--team="TEAM <LIST>"'
Specify team's name and mailing list.
-`-l'
-`--language=LANG'
+'-l'
+'--language=LANG'
Specify language suffix, e.g "bg". The suffix also defines the
name of the language which is used in some fields of PO file
header.
-`-t'
-`--translator="FULL NAME <EMAIL>"'
+'-t'
+'--translator="FULL NAME <EMAIL>"'
Specify translator.
-`--version'
+'--version'
Display copyright and version information and exit.
-`--help'
+'--help'
Display usage information and exit.
- The PO file name is guessed from the name of POT and language
-suffix; the file is created in current working directory.
+ The PO file name is guessed from the name of POT and language suffix;
+the file is created in current working directory.
-3.1.4 The `gnun-preconvert' Script
+3.1.4 The 'gnun-preconvert' Script
----------------------------------
-This script uses `po4a-gettextize' to convert a translation from HTML
-to PO format (see
-`http://po4a.alioth.debian.org/man/man7/po4a.7.php#lbAO'). If the
+This script uses 'po4a-gettextize' to convert a translation from HTML to
+PO format (see
+<http://po4a.alioth.debian.org/man/man7/po4a.7.php#lbAO>). If the
conversion is successful, you can merge the result with the new POT
-using `gnun-merge-preconverted'.
+using 'gnun-merge-preconverted'.
gnun-preconvert [OPTION...] TRANSLATION MASTER
-`-e'
-`--encoding'
+'-e'
+'--encoding'
Specify the encoding of TRANSLATION (if other than UTF-8).
-`--version'
+'--version'
Display copyright and version information and exit.
-`--help'
+'--help'
Display usage information and exit.
-3.1.5 The `gnun-merge-preconverted' Script
+3.1.5 The 'gnun-merge-preconverted' Script
------------------------------------------
-This script takes `po4a-gettextize' output, adds current `msgid's as
+This script takes 'po4a-gettextize' output, adds current 'msgid's as
"previous" values, merges the file with the new POT, and adds
-differences against previous values like `gnun-add-fuzzy-diff' does.
+differences against previous values like 'gnun-add-fuzzy-diff' does.
gnun-merge-preconverted [OPTION...] PO POT
-`-C'
-`--compendium'
- Specify the compendium (if any). This option can be used more
- than once to specify multiple compendia.
+'-C'
+'--compendium'
+ Specify the compendium (if any). This option can be used more than
+ once to specify multiple compendia.
-`--version'
+'--version'
Display copyright and version information and exit.
-`--help'
+'--help'
Display usage information and exit.
-3.1.6 The `gnun-validate-html' Script
+3.1.6 The 'gnun-report' Script
+------------------------------
+
+This script generates HTML reports about translations of a given team.
+The HTML contains a set of tables sorted by priority and translation
+status (existing translations that need maintenance, untranslated files,
+complete translations).
+
+ The script depends on the presence of the 'priorities.mk' file in the
+'server/gnun' subdirectory of the working copy of 'www' repository.
+
+ The results are written to standard output. Example:
+
+ gnun-report --root=../www -t bg > report-bg.html
+
+'-t'
+'--team=LANG'
+ Specify the language code of the team, for example, 'ml'.
+
+'--root'
+ Specify the top directory of the working copy; the default is the
+ current directory.
+
+'-l'
+'--language=LANGUAGE'
+ Specify the language name, for example, 'Malayalam'. When this
+ option is missing, 'gnun-report' tries to figure out the language
+ name based on the language code provided with the "-t" option.
+
+'--version'
+ Display copyright and version information and exit.
+
+'--help'
+ Display usage information and exit.
+
+ There is also a target in 'GNUmakefile' to generate text reports
+intended for monthly messages sent to the teams. *Note report::.
+
+3.1.7 The 'gnun-validate-html' Script
-------------------------------------
This is a Bash script whose purpose is to "validate" both the original
-and translated articles to make sure that they conform to the
-respective W3C standard. Sometimes webmasters make mistakes, and
-translators too, so this tool is useful to catch errors of that kind.
+and translated articles to make sure that they conform to the respective
+W3C standard. Sometimes webmasters make mistakes, and translators too,
+so this tool is useful to catch errors of that kind.
GNUN enforces HTML validation at build time if invoked with
-`VALIDATE=yes'.
+'VALIDATE=yes'.
The script expects only one FILE as the last argument and will exit
with an error if it is not specified (which might be the case when an
@@ -1897,24 +1867,29 @@
gnun-validate-html --root . philosophy/free-sw.html
-`--root=DIRECTORY'
- Specify the top DIRECTORY of the working copy; the default value
- is `../..'.
+'--root=DIRECTORY'
+ Specify the top DIRECTORY of the working copy; the default value is
+ '../..'.
-`--expand-to=FILE'
+'--expand-to=FILE'
Save the expanded HTML as FILE.
-`--version'
+'-v, --verbose'
+ Produce more detailed output intended for automatic email reports;
+ essentially, it adds the expanded HTML to facilitate finding errors
+ by people who receive the report.
+
+'--version'
Display copyright and version information and exit.
-`--help'
+'--help'
Display usage information and exit.
-3.1.7 The `mailfail' Script
+3.1.8 The 'mailfail' Script
---------------------------
This is a helper script that runs a command, and mails the output of
-that command in case it exits with a non-zero exit status. `mailfail'
+that command in case it exits with a non-zero exit status. 'mailfail'
depends on GNU Mailutils, or a compatible implementation, such as BSD's
mailx.
@@ -1922,72 +1897,74 @@
mailfail [--dry-run] RCPT SUBJECT CMD [ARG ...]
- The `mailfail' script accepts the following options:
+ The 'mailfail' script accepts the following options:
-`--dry-run'
+'--dry-run'
Does not send the email message.
-`RCPT'
+'RCPT'
The recipient of the message in a valid format, like
- address@hidden'.
+ 'address@hidden'.
-`SUBJECT'
+'SUBJECT'
The subject of the message; if it is longer than a word you should
guard it with quotes.
-`CMD'
+'CMD'
The command you want to run and send a mail in case it fails.
-`ARG...'
- The arguments of `CMD', if any.
+'ARG...'
+ The arguments of 'CMD', if any.
Here is a typical example, similar to the way it is used in GNUN:
mailfail address@hidden "Bad PO" msgfmt -cv -o /dev/null bg.po
- This will check the validity of `bg.po' with the `msgfmt' program
-and in case there are errors, a message will be sent to the specified
-address with `Bad PO' as subject and the error output from `msgfmt' as
+ This will check the validity of 'bg.po' with the 'msgfmt' program and
+in case there are errors, a message will be sent to the specified
+address with 'Bad PO' as subject and the error output from 'msgfmt' as
body.
- `mailfail' inherits the exit status of the command being run. If an
+ 'mailfail' inherits the exit status of the command being run. If an
argument is missing, the usage information is printed to the standard
output and the exit code is 1.
-3.1.8 The `validate-html-notify' Script
+3.1.9 The 'validate-html-notify' Script
---------------------------------------
-This script is a wrapper around `gnun-validate-html' (*note
-gnun-validate-html::); it is necessary because it is hard to capture
-the output of the program from a program that itself captures the
-output of another program that it runs.
+This script is a wrapper around 'gnun-validate-html' (*note
+gnun-validate-html::); it is necessary because it is hard to capture the
+output of the program from a program that itself captures the output of
+another program that it runs.
Usage:
validate-html-notify [--dry-run] RCPT FILE
-`--dry-run'
- Does not actually send the message, just like `mailfail'.
+'--dry-run'
+ Does not actually send the message, just like 'mailfail'. In this
+ case it runs 'gnun-validate-html' without '--verbose' because it is
+ expected that the expanded file will be available locally.
-`RCPT'
+'RCPT'
The recipient of the message.
-`FILE'
+'FILE'
The HTML file that has to be validated for compliance with the W3C
standard.
The subject of the message is hardcoded in the script, since this
wrapper has a specific task and cannot be used to invoke an arbitrary
-command--use `mailfail' for that. *Note mailfail::.
+command--use 'mailfail' for that. *Note mailfail::.
-3.1.9 The `gnun-clear-previous' Script
---------------------------------------
+3.1.10 The 'gnun-clear-previous' Script
+---------------------------------------
This simple script is not used internally in GNUN. It is merely for
convenience only, for those who find it hard to remember the various
-`gettext' tools and their options.
+'gettext' tools and their options.
- `gnun-clear-previous' deletes the "previous" messages in a PO file,
+ 'gnun-clear-previous' deletes the "previous" messages in a PO file,
which is a good thing to do after the corresponding translation is
updated and the "fuzzy" marker removed. It can also be used to wrap
long lines in PO files.
@@ -1996,10 +1973,10 @@
gnun-clear-previous FILE
-`--version'
+'--version'
Print copyright and version information on the standard output.
-`--help'
+'--help'
Print usage information on stdout.
3.2 How The Recipes Work
@@ -2011,13 +1988,146 @@
****************
GNUnited Nations, like any other software, is not bug free. There are
-some known bugs and annoyances, which are listed in the `TODO' file,
-but it is absolutely certain that there are more which we know nothing
+some known bugs and annoyances, which are listed in the 'TODO' file, but
+it is absolutely certain that there are more which we know nothing
about.
If you encounter a bug, or if you have suggestions of any kind,
please do not hesitate to report them at <address@hidden> or
-`https://savannah.gnu.org/bugs/?group=gnun'.
+<https://savannah.gnu.org/bugs/?group=gnun>.
+
+Index
+*****
+
+* Menu:
+
+* ALL_DIRS: Main Variables. (line 751)
+* announce: Runtime Variables. (line 455)
+* articles in root directory, defining: Main Variables. (line 744)
+* Bazaar: Runtime Variables. (line 394)
+* boilerplates: Modifying Boilerplates.
+ (line 1594)
+* bugs, reporting: Bugs. (line 1989)
+* bzr: Runtime Variables. (line 394)
+* comments for translators: Comments for Translators.
+ (line 1571)
+* comparing, translations: gnun-diff-po. (line 1697)
+* compendia: Compendia. (line 1503)
+* compendium.pot: Compendia. (line 1503)
+* config.mk: Invoking GNUN. (line 359)
+* conventional separator for strings: Splitting Long Passages.
+ (line 1635)
+* conversion of existing translations: Migrating. (line 1054)
+* conversion of existing translations <1>: gnun-preconvert. (line 1775)
+* conversion of existing translations <2>: gnun-merge-preconverted.
+ (line 1796)
+* credits, translators: New Translation. (line 932)
+* credits, translators <1>: Credits Slot. (line 1031)
+* cron, team maintenance: GNUmakefile.team and Cron.
+ (line 1477)
+* CVS: Runtime Variables. (line 394)
+* deferred generation of articles: Runtime Variables. (line 475)
+* defining articles in the root dir: Main Variables. (line 744)
+* defining directories: Main Variables. (line 751)
+* defining templates: Main Variables. (line 701)
+* defining templates <1>: Main Variables. (line 716)
+* defining templates <2>: Main Variables. (line 723)
+* directories, defining: Main Variables. (line 751)
+* exclude.pot: Compendia. (line 1503)
+* extra-templates: Main Variables. (line 716)
+* fuzzy strings: Runtime Variables. (line 475)
+* FUZZY_DIFF_LINGUAS: Main Variables. (line 738)
+* generic notice, translations: generic.LANG.html. (line 1215)
+* GNUmakefile: Invoking GNUN. (line 344)
+* GNUmakefile.team: PO Files and Team. (line 1271)
+* gnun.mk: Invoking GNUN. (line 359)
+* gnun.mk <1>: Main Variables. (line 688)
+* gnunews: GNU News. (line 1122)
+* gnusflashes: GNU News. (line 1122)
+* GRACE: Runtime Variables. (line 475)
+* grace period: Runtime Variables. (line 475)
+* initializing, translations: gnun-init-po. (line 1732)
+* invocation: Invoking GNUN. (line 344)
+* invoking: Invoking GNUN. (line 344)
+* localized URLs: Localized URLs. (line 1605)
+* long lines, wrap: New Translation. (line 938)
+* long passages, avoiding: Splitting Long Passages.
+ (line 1635)
+* mail, notifications: Runtime Variables. (line 442)
+* mail, notifications <1>: mailfail. (line 1890)
+* migration, translations: Migrating. (line 1054)
+* migration, translations <1>: gnun-preconvert. (line 1775)
+* migration, translations <2>: gnun-merge-preconverted.
+ (line 1796)
+* new translation: New Translation. (line 818)
+* new translations, notifications/announcements: Runtime Variables.
+ (line 455)
+* notes, translators: New Translation. (line 926)
+* notes, translators <1>: Notes Slot. (line 984)
+* NOTIFY: Runtime Variables. (line 442)
+* optional-templates: Main Variables. (line 723)
+* OUTDATED-GRACE: Runtime Variables. (line 487)
+* output, detailed: Runtime Variables. (line 468)
+* PO editors: PO Files. (line 784)
+* PO headers: New Translation. (line 859)
+* PO, editing: PO Files. (line 772)
+* POT generation, articles: Main Variables. (line 755)
+* previous, diff: Main Variables. (line 738)
+* previous, diff <1>: gnun-add-fuzzy-diff.
+ (line 1676)
+* previous, manipulating PO files: gnun-clear-previous.
+ (line 1962)
+* priorities.mk: Invoking GNUN. (line 359)
+* priorities.mk <1>: report. (line 618)
+* priorities.mk <2>: PO Files and Team. (line 1341)
+* priorities.mk <3>: gnun-report. (line 1821)
+* project repository: PO Files and Team. (line 1271)
+* recommendations, PO files: PO Tips. (line 1148)
+* reporting: report. (line 605)
+* reporting <1>: gnun-report. (line 1816)
+* reporting bugs: Bugs. (line 1989)
+* repository, translation project: PO Files and Team. (line 1271)
+* ROOT: Main Variables. (line 744)
+* sanity checks: Runtime Variables. (line 421)
+* status, translations: report. (line 605)
+* status, translations <1>: gnun-report. (line 1816)
+* Subversion: Runtime Variables. (line 394)
+* SVN: Runtime Variables. (line 394)
+* synchronization, repository: sync. (line 570)
+* TEAM: Runtime Variables. (line 496)
+* team information: generic.LANG.html. (line 1215)
+* team maintenance: PO Files and Team. (line 1271)
+* team maintenance, cron: GNUmakefile.team and Cron.
+ (line 1477)
+* team workflow: PO Files and Team. (line 1289)
+* templates, additional: Main Variables. (line 716)
+* templates, defining: Main Variables. (line 701)
+* templates, optional: Main Variables. (line 723)
+* TEMPLATE_LINGUAS: Main Variables. (line 701)
+* tips, translators: PO Tips. (line 1148)
+* tips, webmasters: Webmaster Tips. (line 1541)
+* translation memory: Compendia. (line 1503)
+* translation, new: New Translation. (line 818)
+* translators' credits: New Translation. (line 932)
+* translators' credits <1>: Credits Slot. (line 1031)
+* translators' notes: New Translation. (line 926)
+* translators' notes <1>: Notes Slot. (line 984)
+* triggering, build: Invoking GNUN. (line 344)
+* VALIDATE: Runtime Variables. (line 421)
+* validation: Runtime Variables. (line 421)
+* validation <1>: Runtime Variables. (line 507)
+* validation <2>: validate-all. (line 679)
+* validation <3>: Validation. (line 1559)
+* validation, HTML, XHTML: gnun-validate-html. (line 1854)
+* variable, behavior: Runtime Variables. (line 387)
+* variable, team: Runtime Variables. (line 496)
+* variables: Runtime Variables. (line 387)
+* variables <1>: Main Variables. (line 688)
+* VCS: Runtime Variables. (line 394)
+* VERBOSE: Runtime Variables. (line 468)
+* webmaster tips: Webmaster Tips. (line 1541)
+* whatsnew: GNU News. (line 1122)
+* wrapping long lines: New Translation. (line 938)
Appendix A GNU Free Documentation License
*****************************************
@@ -2025,7 +2135,7 @@
Version 1.3, 3 November 2008
Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
- `http://fsf.org/'
+ <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@@ -2050,21 +2160,21 @@
free program should come with manuals providing the same freedoms
that the software does. But this License is not limited to
software manuals; it can be used for any textual work, regardless
- of subject matter or whether it is published as a printed book.
- We recommend this License principally for works whose purpose is
+ of subject matter or whether it is published as a printed book. We
+ recommend this License principally for works whose purpose is
instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium,
- that contains a notice placed by the copyright holder saying it
- can be distributed under the terms of this License. Such a notice
+ that contains a notice placed by the copyright holder saying it can
+ be distributed under the terms of this License. Such a notice
grants a world-wide, royalty-free license, unlimited in duration,
to use that work under the conditions stated herein. The
"Document", below, refers to any such manual or work. Any member
- of the public is a licensee, and is addressed as "you". You
- accept the license if you copy, modify or distribute the work in a
- way requiring permission under copyright law.
+ of the public is a licensee, and is addressed as "you". You accept
+ the license if you copy, modify or distribute the work in a way
+ requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
@@ -2082,12 +2192,12 @@
regarding them.
The "Invariant Sections" are certain Secondary Sections whose
- titles are designated, as being those of Invariant Sections, in
- the notice that says that the Document is released under this
- License. If a section does not fit the above definition of
- Secondary then it is not allowed to be designated as Invariant.
- The Document may contain zero Invariant Sections. If the Document
- does not identify any Invariant Sections then there are none.
+ titles are designated, as being those of Invariant Sections, in the
+ notice that says that the Document is released under this License.
+ If a section does not fit the above definition of Secondary then it
+ is not allowed to be designated as Invariant. The Document may
+ contain zero Invariant Sections. If the Document does not identify
+ any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
@@ -2098,27 +2208,27 @@
A "Transparent" copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
- straightforwardly with generic text editors or (for images
- composed of pixels) generic paint programs or (for drawings) some
- widely available drawing editor, and that is suitable for input to
- text formatters or for automatic translation to a variety of
- formats suitable for input to text formatters. A copy made in an
- otherwise Transparent file format whose markup, or absence of
- markup, has been arranged to thwart or discourage subsequent
- modification by readers is not Transparent. An image format is
- not Transparent if used for any substantial amount of text. A
- copy that is not "Transparent" is called "Opaque".
+ straightforwardly with generic text editors or (for images composed
+ of pixels) generic paint programs or (for drawings) some widely
+ available drawing editor, and that is suitable for input to text
+ formatters or for automatic translation to a variety of formats
+ suitable for input to text formatters. A copy made in an otherwise
+ Transparent file format whose markup, or absence of markup, has
+ been arranged to thwart or discourage subsequent modification by
+ readers is not Transparent. An image format is not Transparent if
+ used for any substantial amount of text. A copy that is not
+ "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format,
- SGML or XML using a publicly available DTD, and
- standard-conforming simple HTML, PostScript or PDF designed for
- human modification. Examples of transparent image formats include
- PNG, XCF and JPG. Opaque formats include proprietary formats that
- can be read and edited only by proprietary word processors, SGML or
- XML for which the DTD and/or processing tools are not generally
- available, and the machine-generated HTML, PostScript or PDF
- produced by some word processors for output purposes only.
+ SGML or XML using a publicly available DTD, and standard-conforming
+ simple HTML, PostScript or PDF designed for human modification.
+ Examples of transparent image formats include PNG, XCF and JPG.
+ Opaque formats include proprietary formats that can be read and
+ edited only by proprietary word processors, SGML or XML for which
+ the DTD and/or processing tools are not generally available, and
+ the machine-generated HTML, PostScript or PDF produced by some word
+ processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the
@@ -2156,8 +2266,8 @@
may not use technical measures to obstruct or control the reading
or further copying of the copies you make or distribute. However,
you may accept compensation in exchange for copies. If you
- distribute a large enough number of copies you must also follow
- the conditions in section 3.
+ distribute a large enough number of copies you must also follow the
+ conditions in section 3.
You may also lend copies, under the same conditions stated above,
and you may publicly display copies.
@@ -2171,12 +2281,11 @@
these Cover Texts: Front-Cover Texts on the front cover, and
Back-Cover Texts on the back cover. Both covers must also clearly
and legibly identify you as the publisher of these copies. The
- front cover must present the full title with all words of the
- title equally prominent and visible. You may add other material
- on the covers in addition. Copying with changes limited to the
- covers, as long as they preserve the title of the Document and
- satisfy these conditions, can be treated as verbatim copying in
- other respects.
+ front cover must present the full title with all words of the title
+ equally prominent and visible. You may add other material on the
+ covers in addition. Copying with changes limited to the covers, as
+ long as they preserve the title of the Document and satisfy these
+ conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
@@ -2184,40 +2293,39 @@
adjacent pages.
If you publish or distribute Opaque copies of the Document
- numbering more than 100, you must either include a
- machine-readable Transparent copy along with each Opaque copy, or
- state in or with each Opaque copy a computer-network location from
- which the general network-using public has access to download
- using public-standard network protocols a complete Transparent
- copy of the Document, free of added material. If you use the
- latter option, you must take reasonably prudent steps, when you
- begin distribution of Opaque copies in quantity, to ensure that
- this Transparent copy will remain thus accessible at the stated
- location until at least one year after the last time you
- distribute an Opaque copy (directly or through your agents or
- retailers) of that edition to the public.
+ numbering more than 100, you must either include a machine-readable
+ Transparent copy along with each Opaque copy, or state in or with
+ each Opaque copy a computer-network location from which the general
+ network-using public has access to download using public-standard
+ network protocols a complete Transparent copy of the Document, free
+ of added material. If you use the latter option, you must take
+ reasonably prudent steps, when you begin distribution of Opaque
+ copies in quantity, to ensure that this Transparent copy will
+ remain thus accessible at the stated location until at least one
+ year after the last time you distribute an Opaque copy (directly or
+ through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of
- the Document well before redistributing any large number of
- copies, to give them a chance to provide you with an updated
- version of the Document.
+ the Document well before redistributing any large number of copies,
+ to give them a chance to provide you with an updated version of the
+ Document.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you
- release the Modified Version under precisely this License, with
- the Modified Version filling the role of the Document, thus
- licensing distribution and modification of the Modified Version to
- whoever possesses a copy of it. In addition, you must do these
- things in the Modified Version:
+ release the Modified Version under precisely this License, with the
+ Modified Version filling the role of the Document, thus licensing
+ distribution and modification of the Modified Version to whoever
+ possesses a copy of it. In addition, you must do these things in
+ the Modified Version:
A. Use in the Title Page (and on the covers, if any) a title
- distinct from that of the Document, and from those of
- previous versions (which should, if there were any, be listed
- in the History section of the Document). You may use the
- same title as a previous version if the original publisher of
- that version gives permission.
+ distinct from that of the Document, and from those of previous
+ versions (which should, if there were any, be listed in the
+ History section of the Document). You may use the same title
+ as a previous version if the original publisher of that
+ version gives permission.
B. List on the Title Page, as authors, one or more persons or
entities responsible for authorship of the modifications in
@@ -2247,31 +2355,30 @@
I. Preserve the section Entitled "History", Preserve its Title,
and add to it an item stating at least the title, year, new
- authors, and publisher of the Modified Version as given on
- the Title Page. If there is no section Entitled "History" in
- the Document, create one stating the title, year, authors,
- and publisher of the Document as given on its Title Page,
- then add an item describing the Modified Version as stated in
- the previous sentence.
+ authors, and publisher of the Modified Version as given on the
+ Title Page. If there is no section Entitled "History" in the
+ Document, create one stating the title, year, authors, and
+ publisher of the Document as given on its Title Page, then add
+ an item describing the Modified Version as stated in the
+ previous sentence.
J. Preserve the network location, if any, given in the Document
for public access to a Transparent copy of the Document, and
likewise the network locations given in the Document for
- previous versions it was based on. These may be placed in
- the "History" section. You may omit a network location for a
- work that was published at least four years before the
- Document itself, or if the original publisher of the version
- it refers to gives permission.
+ previous versions it was based on. These may be placed in the
+ "History" section. You may omit a network location for a work
+ that was published at least four years before the Document
+ itself, or if the original publisher of the version it refers
+ to gives permission.
K. For any section Entitled "Acknowledgements" or "Dedications",
- Preserve the Title of the section, and preserve in the
- section all the substance and tone of each of the contributor
+ Preserve the Title of the section, and preserve in the section
+ all the substance and tone of each of the contributor
acknowledgements and/or dedications given therein.
- L. Preserve all the Invariant Sections of the Document,
- unaltered in their text and in their titles. Section numbers
- or the equivalent are not considered part of the section
- titles.
+ L. Preserve all the Invariant Sections of the Document, unaltered
+ in their text and in their titles. Section numbers or the
+ equivalent are not considered part of the section titles.
M. Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
@@ -2284,11 +2391,11 @@
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no
- material copied from the Document, you may at your option
- designate some or all of these sections as invariant. To do this,
- add their titles to the list of Invariant Sections in the Modified
- Version's license notice. These titles must be distinct from any
- other section titles.
+ material copied from the Document, you may at your option designate
+ some or all of these sections as invariant. To do this, add their
+ titles to the list of Invariant Sections in the Modified Version's
+ license notice. These titles must be distinct from any other
+ section titles.
You may add a section Entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
@@ -2297,15 +2404,15 @@
definition of a standard.
You may add a passage of up to five words as a Front-Cover Text,
- and a passage of up to 25 words as a Back-Cover Text, to the end
- of the list of Cover Texts in the Modified Version. Only one
- passage of Front-Cover Text and one of Back-Cover Text may be
- added by (or through arrangements made by) any one entity. If the
- Document already includes a cover text for the same cover,
- previously added by you or by arrangement made by the same entity
- you are acting on behalf of, you may not add another; but you may
- replace the old one, on explicit permission from the previous
- publisher that added the old one.
+ and a passage of up to 25 words as a Back-Cover Text, to the end of
+ the list of Cover Texts in the Modified Version. Only one passage
+ of Front-Cover Text and one of Back-Cover Text may be added by (or
+ through arrangements made by) any one entity. If the Document
+ already includes a cover text for the same cover, previously added
+ by you or by arrangement made by the same entity you are acting on
+ behalf of, you may not add another; but you may replace the old
+ one, on explicit permission from the previous publisher that added
+ the old one.
The author(s) and publisher(s) of the Document do not by this
License give permission to use their names for publicity for or to
@@ -2315,8 +2422,8 @@
You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for
- modified versions, provided that you include in the combination
- all of the Invariant Sections of all of the original documents,
+ modified versions, provided that you include in the combination all
+ of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your
combined work in its license notice, and that you preserve all
their Warranty Disclaimers.
@@ -2343,20 +2450,20 @@
documents released under this License, and replace the individual
copies of this License in the various documents with a single copy
that is included in the collection, provided that you follow the
- rules of this License for verbatim copying of each of the
- documents in all other respects.
+ rules of this License for verbatim copying of each of the documents
+ in all other respects.
You may extract a single document from such a collection, and
distribute it individually under this License, provided you insert
- a copy of this License into the extracted document, and follow
- this License in all other respects regarding verbatim copying of
- that document.
+ a copy of this License into the extracted document, and follow this
+ License in all other respects regarding verbatim copying of that
+ document.
7. AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Document or its derivatives with other
- separate and independent documents or works, in or on a volume of
- a storage or distribution medium, is called an "aggregate" if the
+ separate and independent documents or works, in or on a volume of a
+ storage or distribution medium, is called an "aggregate" if the
copyright resulting from the compilation is not used to limit the
legal rights of the compilation's users beyond what the individual
works permit. When the Document is included in an aggregate, this
@@ -2401,8 +2508,8 @@
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
- provisionally, unless and until the copyright holder explicitly
- and finally terminates your license, and (b) permanently, if the
+ provisionally, unless and until the copyright holder explicitly and
+ finally terminates your license, and (b) permanently, if the
copyright holder fails to notify you of the violation by some
reasonable means prior to 60 days after the cessation.
@@ -2414,10 +2521,10 @@
after your receipt of the notice.
Termination of your rights under this section does not terminate
- the licenses of parties who have received copies or rights from
- you under this License. If your rights have been terminated and
- not permanently reinstated, receipt of a copy of some or all of
- the same material does not give you any rights to use it.
+ the licenses of parties who have received copies or rights from you
+ under this License. If your rights have been terminated and not
+ permanently reinstated, receipt of a copy of some or all of the
+ same material does not give you any rights to use it.
10. FUTURE REVISIONS OF THIS LICENSE
@@ -2425,18 +2532,18 @@
the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
- `http://www.gnu.org/copyleft/'.
+ <http://www.gnu.org/copyleft/>.
Each version of the License is given a distinguishing version
number. If the Document specifies that a particular numbered
version of this License "or any later version" applies to it, you
have the option of following the terms and conditions either of
that specified version or of any later version that has been
- published (not as a draft) by the Free Software Foundation. If
- the Document does not specify a version number of this License,
- you may choose any version ever published (not as a draft) by the
- Free Software Foundation. If the Document specifies that a proxy
- can decide which future versions of this License can be used, that
+ published (not as a draft) by the Free Software Foundation. If the
+ Document does not specify a version number of this License, you may
+ choose any version ever published (not as a draft) by the Free
+ Software Foundation. If the Document specifies that a proxy can
+ decide which future versions of this License can be used, that
proxy's public statement of acceptance of a version permanently
authorizes you to choose that version for the Document.
@@ -2470,7 +2577,6 @@
site under CC-BY-SA on the same site at any time before August 1,
2009, provided the MMC is eligible for relicensing.
-
ADDENDUM: How to use this License for your documents
====================================================
@@ -2498,125 +2604,7 @@
situation.
If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of
-free software license, such as the GNU General Public License, to
-permit their use in free software.
-
-Index
-*****
+recommend releasing these examples in parallel under your choice of free
+software license, such as the GNU General Public License, to permit
+their use in free software.
-ALL_DIRS: See 2.2. (line 788)
-announce: See 2.1.1. (line 471)
-articles in root directory, defining: See 2.2. (line 781)
-Bazaar: See 2.1.1. (line 410)
-boilerplates: See 2.4.3. (line 1639)
-bugs, reporting: See 4. (line 2013)
-bzr: See 2.1.1. (line 410)
-comments for translators: See 2.4.2. (line 1616)
-compendia: See 2.3.8. (line 1548)
-compendium.pot: See 2.3.8. (line 1548)
-config.mk: See 2.1. (line 375)
-conventional separator for strings: See 2.4.5. (line 1680)
-conversion of existing translations <1>: See 3.1.5. (line 1865)
-conversion of existing translations <2>: See 3.1.4. (line 1844)
-conversion of existing translations: See 2.3.2. (line 1093)
-credits, translators <1>: See 2.3.1.2. (line 1070)
-credits, translators: See 2.3.1. (line 971)
-cron, team maintenance: See 2.3.7.2. (line 1522)
-CVS: See 2.1.1. (line 410)
-deferred generation of articles: See 2.1.1. (line 491)
-defining articles in the root dir: See 2.2. (line 781)
-defining directories: See 2.2. (line 788)
-defining homepage: See 2.2. (line 775)
-defining templates: See 2.2. (line 717)
-directories, defining: See 2.2. (line 788)
-exclude.pot: See 2.3.8. (line 1548)
-extra-templates: See 2.2. (line 747)
-fuzzy strings: See 2.1.1. (line 491)
-FUZZY_DIFF_LINGUAS: See 2.2. (line 769)
-generation, POT, .proto: See 3.1.1. (line 1721)
-generic notice, translations: See 2.3.5. (line 1259)
-GNUmakefile: See 2.1. (line 359)
-GNUmakefile.team: See 2.3.7. (line 1315)
-gnun.mk <1>: See 2.2. (line 703)
-gnun.mk: See 2.1. (line 375)
-gnunews: See 2.3.3. (line 1162)
-gnusflashes: See 2.3.3. (line 1162)
-GRACE: See 2.1.1. (line 491)
-grace period: See 2.1.1. (line 491)
-HOME_LINGUAS: See 2.2. (line 775)
-homepage, defining: See 2.2. (line 775)
-initializing, translations: See 3.1.3. (line 1801)
-invocation: See 2.1. (line 359)
-invoking: See 2.1. (line 359)
-localized URLs: See 2.4.4. (line 1650)
-long lines, wrap: See 2.3.1. (line 977)
-long passages, avoiding: See 2.4.5. (line 1680)
-mail, notifications <1>: See 3.1.7. (line 1916)
-mail, notifications: See 2.1.1. (line 458)
-migration, translations <1>: See 3.1.5. (line 1865)
-migration, translations <2>: See 3.1.4. (line 1844)
-migration, translations: See 2.3.2. (line 1093)
-new translation: See 2.3.1. (line 856)
-new translations, notifications/announcements: See 2.1.1. (line 471)
-notes, translators <1>: See 2.3.1.1. (line 1023)
-notes, translators: See 2.3.1. (line 965)
-NOTIFY: See 2.1.1. (line 458)
-optional-templates: See 2.2. (line 754)
-OUTDATED-GRACE: See 2.1.1. (line 503)
-output, detailed: See 2.1.1. (line 484)
-PO editors: See 2.3. (line 821)
-PO headers: See 2.3.1. (line 898)
-PO, editing: See 2.3. (line 809)
-POT generation: See 3.1.1. (line 1721)
-POT generation, articles: See 2.2. (line 792)
-previous, diff <1>: See 3.1.2. (line 1780)
-previous, diff: See 2.2. (line 769)
-previous, manipulating PO files: See 3.1.9. (line 1986)
-priorities.mk <1>: See 2.3.7. (line 1385)
-priorities.mk <2>: See 2.1.2.4. (line 636)
-priorities.mk: See 2.1. (line 375)
-project repository: See 2.3.7. (line 1315)
-prototype generation: See 3.1.1. (line 1721)
-recommendations, PO files: See 2.3.4. (line 1192)
-reporting: See 2.1.2.4. (line 623)
-reporting bugs: See 4. (line 2013)
-repository, translation project: See 2.3.7. (line 1315)
-ROOT: See 2.2. (line 781)
-sanity checks: See 2.1.1. (line 437)
-status, translations: See 2.1.2.4. (line 623)
-Subversion: See 2.1.1. (line 410)
-SVN: See 2.1.1. (line 410)
-synchronization, repository: See 2.1.2.3. (line 588)
-TEAM: See 2.1.1. (line 512)
-team information: See 2.3.5. (line 1259)
-team maintenance: See 2.3.7. (line 1315)
-team maintenance, cron: See 2.3.7.2. (line 1522)
-team workflow: See 2.3.7. (line 1333)
-TEMPLATE_LINGUAS: See 2.2. (line 717)
-templates, additional: See 2.2. (line 747)
-templates, defining: See 2.2. (line 717)
-templates, optional: See 2.2. (line 754)
-tips, translators: See 2.3.4. (line 1192)
-tips, webmasters: See 2.4. (line 1586)
-translation memory: See 2.3.8. (line 1548)
-translation, new: See 2.3.1. (line 856)
-translators' credits <1>: See 2.3.1.2. (line 1070)
-translators' credits: See 2.3.1. (line 971)
-translators' notes <1>: See 2.3.1.1. (line 1023)
-translators' notes: See 2.3.1. (line 965)
-triggering, build: See 2.1. (line 359)
-VALIDATE: See 2.1.1. (line 437)
-validation <1>: See 2.4.1. (line 1604)
-validation <2>: See 2.1.2.6. (line 694)
-validation: See 2.1.1. (line 437)
-validation, HTML, XHTML: See 3.1.6. (line 1885)
-variable, behavior: See 2.1.1. (line 403)
-variable, team: See 2.1.1. (line 512)
-variables <1>: See 2.2. (line 703)
-variables: See 2.1.1. (line 403)
-VCS: See 2.1.1. (line 410)
-VERBOSE: See 2.1.1. (line 484)
-webmaster tips: See 2.4. (line 1586)
-whatsnew: See 2.3.3. (line 1162)
-wrapping long lines: See 2.3.1. (line 977)
Index: gnun/gnun.txt.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/gnun.txt.gz,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
Binary files /tmp/cvsHO7vXv and /tmp/cvsCemmDw differ
Index: gnun/index.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/index.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- gnun/index.html 26 Sep 2012 14:49:38 -0000 1.17
+++ gnun/index.html 4 Dec 2012 16:24:20 -0000 1.18
@@ -4,33 +4,33 @@
<h2>GNU GNUN manual</h2>
<address>Free Software Foundation</address>
-<address>last updated September 26, 2012</address>
+<address>last updated December 04, 2012</address>
<p>This manual (gnun) is available in the following formats:</p>
<ul>
<li><a href="gnun.html">HTML
- (176K bytes)</a> - entirely on one web page.</li>
+ (196K bytes)</a> - entirely on one web page.</li>
<li><a href="html_node/index.html">HTML</a> - with one web page per
node.</li>
<li><a href="gnun.html.gz">HTML compressed
(48K gzipped characters)</a> - entirely on
one web page.</li>
<li><a href="gnun.html_node.tar.gz">HTML compressed
- (56K gzipped tar file)</a> -
+ (60K gzipped tar file)</a> -
with one web page per node.</li>
<li><a href="gnun.info.tar.gz">Info document
- (44K bytes gzipped tar file)</a>.</li>
+ (40K bytes gzipped tar file)</a>.</li>
<li><a href="gnun.txt">ASCII text
(120K bytes)</a>.</li>
<li><a href="gnun.txt.gz">ASCII text compressed
(40K bytes gzipped)</a>.</li>
<li><a href="gnun.dvi.gz">TeX dvi file
- (68K bytes gzipped)</a>.</li>
+ (64K bytes gzipped)</a>.</li>
<li><a href="gnun.ps.gz">PostScript file
(292K bytes gzipped)</a>.</li>
<li><a href="gnun.pdf">PDF file
- (404K bytes)</a>.</li>
+ (400K bytes)</a>.</li>
<li><a href="gnun.texi.tar.gz">Texinfo source
(68K bytes gzipped tar file).</a></li>
</ul>
Index: gnun/html_node/Advantages.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Advantages.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Advantages.html 26 Sep 2012 14:49:41 -0000 1.15
+++ gnun/html_node/Advantages.html 4 Dec 2012 16:24:21 -0000 1.16
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>Advantages - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Introduction.html#Introduction" title="Introduction">
-<link rel="prev" href="Concepts.html#Concepts" title="Concepts">
-<link rel="next" href="Disadvantages.html#Disadvantages" title="Disadvantages">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,52 +9,84 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Advantages</title>
+
+<meta name="description" content="GNUnited Nations: Advantages">
+<meta name="keywords" content="GNUnited Nations: Advantages">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Introduction.html#Introduction" rel="up" title="Introduction">
+<link href="Disadvantages.html#Disadvantages" rel="next" title="Disadvantages">
+<link href="Concepts.html#Concepts" rel="previous" title="Concepts">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Advantages"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Disadvantages.html#Disadvantages">Disadvantages</a>,
-Previous: <a rel="previous" accesskey="p"
href="Concepts.html#Concepts">Concepts</a>,
-Up: <a rel="up" accesskey="u"
href="Introduction.html#Introduction">Introduction</a>
-<hr>
+Next: <a href="Disadvantages.html#Disadvantages" accesskey="n"
rel="next">Disadvantages</a>, Previous: <a href="Concepts.html#Concepts"
accesskey="p" rel="previous">Concepts</a>, Up: <a
href="Introduction.html#Introduction" accesskey="u" rel="up">Introduction</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-
+<hr>
+<a name="Major-Advantages-of-GNUN"></a>
<h3 class="section">1.3 Major Advantages of GNUN</h3>
<p>Here is a simple list of situations where we hope this suite would
prove to be useful.
-
- <ul>
-<li>Automatic rebuild of all translations when the original article
+</p>
+<ul>
+<li> Automatic rebuild of all translations when the original article
changes. This is the most important feature, as it prevents
accumulation of seriously outdated translations.
- <li>Global update of the whole site. Apply the previous point to the web
-server templates (under <samp><span class="file">server/</span></samp> in the
`www' repository). A
+</li><li> Global update of the whole site. Apply the previous point to the web
+server templates (under <samp>server/</samp> in the ‘www’
repository). A
single change to such a file will affect literally <em>all</em>
articles, translated or not.
- <li>Urgent notices. Sometimes an “urgent” notice is added by
the
+</li><li> Urgent notices. Sometimes an “urgent” notice is added
by the
webmasters, which should appear on all pages. Typically this is about
an event where urgent action is needed, although often it is only
relevant to a single country or even a particular city. Such a notice
@@ -75,36 +98,44 @@
notice will appear in all translated pages and people who usually read
gnu.org pages in their native language will see it, so they can take
action as necessary. When the notice is removed, often in a week or
-two, it will disappear without translators' intervention, whether they
+two, it will disappear without translators’ intervention, whether they
translated it or not.
- <li>HTML validation. As a preliminary step, GNUN validates the English
+</li><li> HTML validation. As a preliminary step, GNUN validates the English
pages before updating the POT files, and the regenerated translations
before committing them. It often detects typos and other errors in
the markup.
- <li>Simplification of the translation process—lots of errors and
typos
+</li><li> Simplification of the translation process—lots of errors and
typos
come from the fact that translators basically have to duplicate the
whole HTML markup of the original. The PO files eliminate most of the
basic markup, which is where most of the validation errors come from.
- <li>Markup consistency site-wide—it would be substantially easier to
+</li><li> Markup consistency site-wide—it would be substantially easier
to
update the site to a future standard, because translations will
naturally follow the changes in the original articles. This also means
that translation teams do not have to undergo the boring process of
converting their articles to the new SSI-based layout; this will be done
automatically.
- <li>Easy updates by translators. Modified paragraphs, links, etc. will
+</li><li> Easy updates by translators. Modified paragraphs, links, etc. will
appear as “fuzzy” strings in the PO files, newly added ones will
appear as “untranslated”, and deleted will appear as
“obsolete”.
It is substantially easier to update a PO file, where a keystroke
takes you to the part that needs updating, whatever it may be.
- <li>Reporting and statistics. Since the basis is standard PO files, which
+</li><li> Reporting and statistics. Since the basis is standard PO files,
which
are the canonical source of the translations, it is easy to manipulate
them and extract useful information.
-</ul>
+</li></ul>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Disadvantages.html#Disadvantages" accesskey="n"
rel="next">Disadvantages</a>, Previous: <a href="Concepts.html#Concepts"
accesskey="p" rel="previous">Concepts</a>, Up: <a
href="Introduction.html#Introduction" accesskey="u" rel="up">Introduction</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
+
- </body></html>
+</body>
+</html>
Index: gnun/html_node/Bugs.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Bugs.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Bugs.html 26 Sep 2012 14:49:41 -0000 1.15
+++ gnun/html_node/Bugs.html 4 Dec 2012 16:24:21 -0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Bugs - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Internals.html#Internals" title="Internals">
-<link rel="next" href="Index.html#Index" title="Index">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,47 +9,83 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Bugs</title>
+
+<meta name="description" content="GNUnited Nations: Bugs">
+<meta name="keywords" content="GNUnited Nations: Bugs">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Index.html#Index" rel="next" title="Index">
+<link href="Rules.html#Rules" rel="previous" title="Rules">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Bugs"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="Index.html#Index">Index</a>,
-Previous: <a rel="previous" accesskey="p"
href="Internals.html#Internals">Internals</a>,
-Up: <a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Index.html#Index" accesskey="n" rel="next">Index</a>, Previous:
<a href="Internals.html#Internals" accesskey="p" rel="previous">Internals</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="Reporting-Bugs"></a>
<h2 class="chapter">4 Reporting Bugs</h2>
+<a name="index-bugs_002c-reporting"></a>
+<a name="index-reporting-bugs"></a>
-<p><a name="index-bugs_002c-reporting-117"></a><a
name="index-reporting-bugs-118"></a>
-GNUnited Nations, like any other software, is not bug free. There are
-some known bugs and annoyances, which are listed in the <samp><span
class="file">TODO</span></samp>
+<p>GNUnited Nations, like any other software, is not bug free. There are
+some known bugs and annoyances, which are listed in the <samp>TODO</samp>
file, but it is absolutely certain that there are more which we know
nothing about.
-
- <p>If you encounter a bug, or if you have suggestions of any kind, please
+</p>
+<p>If you encounter a bug, or if you have suggestions of any kind, please
do not hesitate to report them at <a
href="mailto:address@hidden";>address@hidden</a> or
<a
href="https://savannah.gnu.org/bugs/?group=gnun";>https://savannah.gnu.org/bugs/?group=gnun</a>.
+</p>
+
- </body></html>
+</body>
+</html>
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.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- gnun/html_node/Comments-for-Translators.html 26 Sep 2012 14:49:41
-0000 1.5
+++ gnun/html_node/Comments-for-Translators.html 4 Dec 2012 16:24:21
-0000 1.6
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>Comments for Translators - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Webmaster-Tips.html#Webmaster-Tips" title="Webmaster
Tips">
-<link rel="prev" href="Validation.html#Validation" title="Validation">
-<link rel="next" href="Modifying-Boilerplates.html#Modifying-Boilerplates"
title="Modifying Boilerplates">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,60 +9,98 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Comments for Translators</title>
+
+<meta name="description" content="GNUnited Nations: Comments for Translators">
+<meta name="keywords" content="GNUnited Nations: Comments for Translators">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Webmaster-Tips.html#Webmaster-Tips" rel="up" title="Webmaster
Tips">
+<link href="Modifying-Boilerplates.html#Modifying-Boilerplates" rel="next"
title="Modifying Boilerplates">
+<link href="Validation.html#Validation" rel="previous" title="Validation">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Comments-for-Translators"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Modifying-Boilerplates.html#Modifying-Boilerplates">Modifying
Boilerplates</a>,
-Previous: <a rel="previous" accesskey="p"
href="Validation.html#Validation">Validation</a>,
-Up: <a rel="up" accesskey="u"
href="Webmaster-Tips.html#Webmaster-Tips">Webmaster Tips</a>
-<hr>
+Next: <a href="Modifying-Boilerplates.html#Modifying-Boilerplates"
accesskey="n" rel="next">Modifying Boilerplates</a>, Previous: <a
href="Validation.html#Validation" accesskey="p" rel="previous">Validation</a>,
Up: <a href="Webmaster-Tips.html#Webmaster-Tips" accesskey="u"
rel="up">Webmaster Tips</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="Comments-for-Translators-1"></a>
<h4 class="subsection">2.4.2 Comments for Translators</h4>
+<a name="index-comments-for-translators"></a>
-<p><a name="index-comments-for-translators-100"></a>
-<!-- Emacs Lisp code goes here... -->
- <p>If you want a comment to be visible for translators, place it
+<p>If you want a comment to be visible for translators, place it
<em>inside</em> the element, for example:
+</p>
+<div class="example">
+<pre class="example"><p>
+<!--TRANSLATORS: Note that foo is bar in this context.-->
+The fooish bar mumbles bazzling.
+</p>
+</pre></div>
+
+<p>This will result in:
+</p>
+<div class="example">
+<pre class="example"># type: Content of: <p>
+#. TRANSLATORS: Note that foo is bar in this context.
+msgid "The fooish bar mumbles bazzling."
+msgstr ""
+</pre></div>
-<pre class="example"> <p>
- <!--TRANSLATORS: Note that foo is bar in this context.-->
- The fooish bar mumbles bazzling.
- </p>
-</pre>
- <p>This will result in:
-
-<pre class="example"> # type: Content of: <p>
- #. TRANSLATORS: Note that foo is bar in this context.
- msgid "The fooish bar mumbles bazzling."
- msgstr ""
-</pre>
- <p>As per the established convention, start the comment with
+<p>As per the established convention, start the comment with
<code>TRANSLATORS:</code> to catch their attention, and do not add a space
after the beginning of the HTML comment (<code><!--</code>), since this will
unnecessarily indent the comment in the POT.
+</p>
+
- </body></html>
+</body>
+</html>
Index: gnun/html_node/Compendia.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Compendia.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- gnun/html_node/Compendia.html 26 Sep 2012 14:49:41 -0000 1.4
+++ gnun/html_node/Compendia.html 4 Dec 2012 16:24:21 -0000 1.5
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Compendia - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="PO-Files.html#PO-Files" title="PO Files">
-<link rel="prev" href="PO-Files-and-Team.html#PO-Files-and-Team" title="PO
Files and Team">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,76 +9,121 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Compendia</title>
+
+<meta name="description" content="GNUnited Nations: Compendia">
+<meta name="keywords" content="GNUnited Nations: Compendia">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="PO-Files.html#PO-Files" rel="up" title="PO Files">
+<link href="Webmaster-Tips.html#Webmaster-Tips" rel="next" title="Webmaster
Tips">
+<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}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Compendia"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="PO-Files-and-Team.html#PO-Files-and-Team">PO Files and Team</a>,
-Up: <a rel="up" accesskey="u" href="PO-Files.html#PO-Files">PO Files</a>
-<hr>
+Previous: <a href="PO-Files-and-Team.html#PO-Files-and-Team" accesskey="p"
rel="previous">PO Files and Team</a>, Up: <a href="PO-Files.html#PO-Files"
accesskey="u" rel="up">PO Files</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-
+<hr>
+<a name="Using-Compendia"></a>
<h4 class="subsection">2.3.8 Using Compendia</h4>
-
-<p><a name="index-compendia-93"></a><a
name="index-translation-memory-94"></a><a
name="index-exclude_002epot-95"></a><a name="index-compendium_002epot-96"></a>
-Compendium is a PO file including translations for common strings; it is
-used to fill other PO files. See <a
href="../gettext/Compendium.html#Compendium">Compendium</a>. One example of
such
+<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/html_node/Compendium.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>GNUN uses compendia located in the <samp><span
class="file">server/gnun/compendia</span></samp>
-directory of the `www' web repository. There are two kinds of
-compendia: <samp><span class="file">master.</span><var>lang</var><span
class="file">.po</span></samp> and
-<samp><span class="file">compendium.</span><var>lang</var><span
class="file">.po</span></samp>.
-
- <p>The first kind, <samp><span
class="file">master.</span><var>lang</var><span class="file">.po</span></samp>,
can be used to
+</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><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>. When <samp><span
class="file">master.</span><var>lang</var><span class="file">.po</span></samp>
is
-updated, the translations will be rebuilt. GNUN doesn't modify this
+<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>The second kind, <samp><span
class="file">compendium.</span><var>lang</var><span
class="file">.po</span></samp>, is updated
+</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><span
class="file">compendium.pot</span></samp>. Then it checks
-all available <samp><var>article</var><span
class="file">.</span><var>lang</var><span class="file">.po</span></samp> files
for
+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><span class="file">compendium.</span><var>lang</var><span
class="file">.po</span></samp>. This file is also used to fill
-missing translations, but it doesn't override the translations from
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>, and the strings coming from
-<samp><span class="file">compendium.</span><var>lang</var><span
class="file">.po</span></samp> are always marked as “fuzzy” to
+<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>When updating <samp><span class="file">compendium.pot</span></samp>,
some strings should be excluded
+</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.html#Notes-Slot">Notes Slot</a>. They are not
+GNUN slots for translators’ notes. See <a
href="Notes-Slot.html#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><span
class="file">exclude.pot</span></samp>, and when that file
-contains the string, it won't be added to <samp><span
class="file">compendium.pot</span></samp>.
+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>
+<hr>
+<div class="header">
+<p>
+Previous: <a href="PO-Files-and-Team.html#PO-Files-and-Team" accesskey="p"
rel="previous">PO Files and Team</a>, Up: <a href="PO-Files.html#PO-Files"
accesskey="u" rel="up">PO Files</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+
- </body></html>
+</body>
+</html>
Index: gnun/html_node/Concepts.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Concepts.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Concepts.html 26 Sep 2012 14:49:41 -0000 1.15
+++ gnun/html_node/Concepts.html 4 Dec 2012 16:24:21 -0000 1.16
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>Concepts - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Introduction.html#Introduction" title="Introduction">
-<link rel="prev" href="Overview.html#Overview" title="Overview">
-<link rel="next" href="Advantages.html#Advantages" title="Advantages">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,40 +9,72 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Concepts</title>
+
+<meta name="description" content="GNUnited Nations: Concepts">
+<meta name="keywords" content="GNUnited Nations: Concepts">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Introduction.html#Introduction" rel="up" title="Introduction">
+<link href="Advantages.html#Advantages" rel="next" title="Advantages">
+<link href="Overview.html#Overview" rel="previous" title="Overview">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Concepts"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Advantages.html#Advantages">Advantages</a>,
-Previous: <a rel="previous" accesskey="p"
href="Overview.html#Overview">Overview</a>,
-Up: <a rel="up" accesskey="u"
href="Introduction.html#Introduction">Introduction</a>
-<hr>
+Next: <a href="Advantages.html#Advantages" accesskey="n"
rel="next">Advantages</a>, Previous: <a href="Overview.html#Overview"
accesskey="p" rel="previous">Overview</a>, Up: <a
href="Introduction.html#Introduction" accesskey="u" rel="up">Introduction</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-
+<hr>
+<a name="What-GNUnited-Nations-is-and-Should-be"></a>
<h3 class="section">1.2 What GNUnited Nations is and Should be</h3>
<p>The basic concept behind GNUN is that localization of HTML articles is
-similar to localization of computer programs<a rel="footnote" href="#fn-1"
name="fnd-1"><sup>1</sup></a>. In articles, like in programs, not every string
is considered
+similar to localization of computer programs<a name="DOCF1"
href="#FOOT1"><sup>1</sup></a>. In articles, like in programs, not every
string is considered
translatable, so translatable strings must be identified first, and then
collected in a file (called “PO template”) for translation.
Articles,
like programs, tend to change in time, but not every change in the
@@ -59,135 +82,138 @@
affect the translatable strings, but sometimes it does. So, translators
must have means to identify those changes and apply the appropriate
updates to the translation.
-
- <p>The GNU <code>gettext</code> package already provides the needed
-infrastructure for maintaining translations using PO files. See <a
href="../gettext/index.html#Top">Introduction</a>, for a basic overview.
+</p>
+<p>The GNU <code>gettext</code> package already provides the needed
+infrastructure for maintaining translations using PO files. See <a
href="http://www.gnu.org/software/gettext/manual/html_node/index.html#Top";>Introduction</a>
in <cite>GNU gettext tools</cite>, for a basic overview.
GNUnited Nations fills the gaps to apply this infrastructure to articles
-in <a href="http://gnu.org";>http://gnu.org</a> web site.<a rel="footnote"
href="#fn-2" name="fnd-2"><sup>2</sup></a>
-
- <p>The following diagram summarizes the relation between the files handled
+in <a href="http://gnu.org";>http://gnu.org</a> web site.<a name="DOCF2"
href="#FOOT2"><sup>2</sup></a>
+</p>
+<p>The following diagram summarizes the relation between the files handled
by GNUN. It is followed by somewhat detailed explanations, which you
should read while keeping an eye on the diagram. Having a clear
understanding of these interrelations will surely help translators and
web maintainers.
-
-<pre class="example"> .---<--- * Original ARTICLE.html
- |
- | .---> ARTICLE.pot ---> * ARTICLE.LANG.po --->---.
- `---+ |
+</p>
+<div class="example">
+<pre class="example">.---<--- * Original ARTICLE.html
+|
+| .---> ARTICLE.pot ---> * ARTICLE.LANG.po --->---.
+`---+ |
`--->---. .------<----------------------------'
| |
| `---.
| +---> Translated ARTICLE.LANG.html
`-------'
-</pre>
- <p>The indication ‘<samp><span class="samp">*</span></samp>’
appears in two places in this picture, and means
+</pre></div>
+
+<p>The indication ‘<samp>*</samp>’ appears in two places in this
picture, and means
that the corresponding file is intended to be edited by humans. The
-author or web maintainer edits the original <samp><var>article</var><span
class="file">.html</span></samp>,
-and translators edit <samp><var>article</var><span
class="file">.</span><var>lang</var><span class="file">.po</span></samp>. All
other
+author or web maintainer edits the original
<samp><var>article</var>.html</samp>,
+and translators edit <samp><var>article</var>.<var>lang</var>.po</samp>. All
other
files are regenerated by GNUN and any manual changes on them will be
lost on the next run.
-
- <p>Arrows denote dependency relation between files, where a change in one
+</p>
+<p>Arrows denote dependency relation between files, where a change in one
file will affect the other. Those automatic changes will be applied by
-running ‘<samp><span class="samp">make -C
server/gnun</span></samp>’. This is the primary way to invoke
+running ‘<samp>make -C server/gnun</samp>’. This is the primary
way to invoke
GNUN, since it is implemented as a set of recipes for GNU <code>make</code>.
-
- <p>First, GNUN extracts all translatable strings from the original English
-article <samp><var>article</var><span class="file">.html</span></samp> into
<samp><var>article</var><span class="file">.pot</span></samp>. The
+</p>
+<p>First, GNUN extracts all translatable strings from the original English
+article <samp><var>article</var>.html</samp> into
<samp><var>article</var>.pot</samp>. The
resulted file is suitable for manipulation with the various GNU
-‘<samp><span class="samp">gettext</span></samp>’ utilities. It
contains all original article strings and
-all translations are set to empty. The letter <code>t</code> in <samp><span
class="file">.pot</span></samp>
+‘<samp>gettext</samp>’ utilities. It contains all original
article strings and
+all translations are set to empty. The letter <code>t</code> in
<samp>.pot</samp>
marks this as a Template PO file, not yet oriented towards any
particular language.
-
- <p>The first time though, there is no <samp><var>article</var><span
class="file">.</span><var>lang</var><span class="file">.po</span></samp>
-yet, so a translator must manually copy <samp><var>article</var><span
class="file">.pot</span></samp> to
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>, where <var>lang</var> represents the
+</p>
+<p>The first time though, there is no
<samp><var>article</var>.<var>lang</var>.po</samp>
+yet, so a translator must manually copy <samp><var>article</var>.pot</samp> to
+<samp><var>article</var>.<var>lang</var>.po</samp>, where <var>lang</var>
represents the
target language. See <a href="New-Translation.html#New-Translation">New
Translation</a>, for details.
-
- <p>Then comes the initial translation of messages in
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>. Translation in itself is a whole
+</p>
+<p>Then comes the initial translation of messages in
+<samp><var>article</var>.<var>lang</var>.po</samp>. Translation in itself is
a whole
matter, whose complexity far overwhelms the level of this manual.
Nevertheless, a few hints are given in some other chapter of this
manual.
-
- <p>It is possible to make GNUN get translations for common strings from
+</p>
+<p>It is possible to make GNUN get translations for common strings from
dedicated PO files, so called compendia. See <a
href="Compendia.html#Compendia">Compendia</a>, for more
information.
+</p>
- <p>You may use any compatible PO editor to add translated messages into
-the PO file. See <a href="../gettext/Editing.html#Editing">Editing</a>,
+<p>You may use any compatible PO editor to add translated messages into
+the PO file. See <a
href="http://www.gnu.org/software/gettext/manual/html_node/Editing.html#Editing";>Editing</a>
in <cite>GNU gettext tools</cite>,
for more information.
-
- <p>When the PO file actually exists (hopefully populated with initial
-translations), GNUN generates <samp><var>article</var><span
class="file">.</span><var>lang</var><span class="file">.html</span></samp>
file.
-It takes its structure from the original <samp><var>article</var><span
class="file">.html</span></samp>, but
+</p>
+<p>When the PO file actually exists (hopefully populated with initial
+translations), GNUN generates
<samp><var>article</var>.<var>lang</var>.html</samp> file.
+It takes its structure from the original <samp><var>article</var>.html</samp>,
but
all translatable strings are replaced with their translations specified
-in <samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>.
-
- <p>Original articles sometimes change. A new paragraph is being added or a
+in <samp><var>article</var>.<var>lang</var>.po</samp>.
+</p>
+<p>Original articles sometimes change. A new paragraph is being added or a
tiny change in the wording is introduced. Also, some articles are
dynamic in nature, like ones containing news entries or a list of other
articles. If the original article changes, GNUN will automatically
-rebuild <samp><var>article</var><span class="file">.pot</span></samp>, and
will merge the changes to
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>. Any outdated translations will be
+rebuild <samp><var>article</var>.pot</samp>, and will merge the changes to
+<samp><var>article</var>.<var>lang</var>.po</samp>. Any outdated translations
will be
marked as fuzzy, any new strings will be added with empty translations,
waiting to be translated. In the same run
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.html</span></samp> will be rebuilt so the relevant
+<samp><var>article</var>.<var>lang</var>.html</samp> will be rebuilt so the
relevant
strings in the translation will be substituted with the original English
text, until the translation teams update them in
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>.
-
- <p>Those changes in the original article that do not affect the
+<samp><var>article</var>.<var>lang</var>.po</samp>.
+</p>
+<p>Those changes in the original article that do not affect the
translatable strings will not lead to changes in
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp>. Thus, no actions from translators
-will be needed. <samp><var>article</var><span
class="file">.</span><var>lang</var><span class="file">.html</span></samp> will
be
+<samp><var>article</var>.<var>lang</var>.po</samp>. Thus, no actions from
translators
+will be needed. <samp><var>article</var>.<var>lang</var>.html</samp> will be
automatically regenerated to reflect the changes.
+</p>
-<!-- FIXME: The following paragraphs should go to a separate section -->
-<!-- that explains those details like exact paths in www, diagram with -->
-<!-- the basic directory layout, additional files like .translinks, etc. -->
- <p>The POT for every article under GNUN's control is kept in the `www'
-repository under a special directory <samp><span
class="file">po/</span></samp>, which is a
-sub-directory of the relevant directory in the `www' tree. So, for
-<<code>http://www.gnu.org/philosophy/free-sw.html</code>> that is
-<samp><span class="file">philosophy/po/</span></samp>. Except <samp><span
class="file">free-sw.pot</span></samp>, this directory holds
-the canonical source of every translation, like <samp><span
class="file">free-sw.bg.po</span></samp>,
-<samp><span class="file">free-sw.ca.po</span></samp>, etc.
-
- <p>Several additional features are implemented, like automatic update of
+<p>The POT for every article under GNUN’s control is kept in the
‘www’
+repository under a special directory <samp>po/</samp>, which is a
+sub-directory of the relevant directory in the ‘www’ tree. So, for
+‘<code>http://www.gnu.org/philosophy/free-sw.html</code>’ that is
+<samp>philosophy/po/</samp>. Except <samp>free-sw.pot</samp>, this directory
holds
+the canonical source of every translation, like <samp>free-sw.bg.po</samp>,
+<samp>free-sw.ca.po</samp>, etc.
+</p>
+<p>Several additional features are implemented, like automatic update of
the list of the available translations. For example, if a new
-<samp><span class="file">free-sw.ja.po</span></samp> translation is added, the
list of translations
-included in <samp><span class="file">free-sw.html</span></samp> and all
translated
-<samp><span class="file">free-sw.</span><var>lang</var><span
class="file">.html</span></samp> is updated. This saves a lot of
+<samp>free-sw.ja.po</samp> translation is added, the list of translations
+included in <samp>free-sw.html</samp> and all translated
+<samp>free-sw.<var>lang</var>.html</samp> is updated. This saves a lot of
tedious, repetitive work and eliminates a source of mistakes. There
is a basic infrastructure to “inject” general information about a
translation team—like a note how to contact the team, or how to
-report a bug/suggestion for improvement. Translators' credits are
-also handled, as well as translators' notes, if any.
+report a bug/suggestion for improvement. Translators’ credits are
+also handled, as well as translators’ notes, if any.
+</p>
-<!-- ineiev: This passage carries no practically useful information -->
-<!-- for GNUN users; extensibility is a feature of any program, the plans -->
-<!-- seem too long-term. -->
-<!-- GNUN can be extended, and new features will certainly be added. The -->
-<!-- @file{TODO} file currently lists some of them, but new ideas pop up -->
-<!-- quite often. The plan is to make a solid foundation and develop -->
-<!-- front-ends-a web front-end, possibly based on Pootle, a statistics -->
-<!-- facility, probably a wiki compiler, and more. -->
- <div class="footnote">
+<div class="footnote">
<hr>
-<h4>Footnotes</h4><p class="footnote"><small>[<a name="fn-1"
href="#fnd-1">1</a>]</small> Actually, it is
+<h4 class="footnotes-heading">Footnotes</h4>
+
+<h3><a name="FOOT1" href="#DOCF1">(1)</a></h3>
+<p>Actually, it is
much more closer to localization of software documentation, where
-typically strings (also known as “messages” in gettext's context)
are
+typically strings (also known as “messages” in gettext’s
context) are
longer than strings in programs. Nevertheless, all points raised still
apply.</p>
-
- <p class="footnote"><small>[<a name="fn-2" href="#fnd-2">2</a>]</small> The
process of converting
+<h3><a name="FOOT2" href="#DOCF2">(2)</a></h3>
+<p>The process of converting
HTML to PO and the other way around is performed using po4a (“po for
anything”), see <a
href="http://po4a.alioth.debian.org";>http://po4a.alioth.debian.org</a>.</p>
+</div>
+<hr>
+<div class="header">
+<p>
+Next: <a href="Advantages.html#Advantages" accesskey="n"
rel="next">Advantages</a>, Previous: <a href="Overview.html#Overview"
accesskey="p" rel="previous">Overview</a>, Up: <a
href="Introduction.html#Introduction" accesskey="u" rel="up">Introduction</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
- <hr></div>
- </body></html>
+</body>
+</html>
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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Copying-This-Manual.html 26 Sep 2012 14:49:41 -0000
1.15
+++ gnun/html_node/Copying-This-Manual.html 4 Dec 2012 16:24:21 -0000
1.16
@@ -1,14 +1,7 @@
-<html lang="en">
-<head>
-<title>Copying This Manual - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Index.html#Index" title="Index">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -16,75 +9,107 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Copying This Manual</title>
+
+<meta name="description" content="GNUnited Nations: Copying This Manual">
+<meta name="keywords" content="GNUnited Nations: Copying This Manual">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Index.html#Index" rel="previous" title="Index">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Copying-This-Manual"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="Index.html#Index">Index</a>,
-Up: <a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Previous: <a href="Index.html#Index" accesskey="p" rel="previous">Index</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="GNU-Free-Documentation-License"></a>
<h2 class="appendix">Appendix A GNU Free Documentation License</h2>
-<!-- The GNU Free Documentation License. -->
-<div align="center">Version 1.3, 3 November 2008</div>
+<div align="center">Version 1.3, 3 November 2008
+</div>
+
+<div class="display">
+<pre class="display">Copyright © 2000, 2001, 2002, 2007, 2008 Free
Software Foundation, Inc.
+<a href="http://fsf.org/";>http://fsf.org/</a>
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+</pre></div>
-<!-- This file is intended to be included within another document, -->
-<!-- hence no sectioning command or @node. -->
-<pre class="display"> Copyright © 2000, 2001, 2002, 2007, 2008 Free
Software Foundation, Inc.
- <a href="http://fsf.org/";>http://fsf.org/</a>
-
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-</pre>
- <ol type=1 start=0>
-<li>PREAMBLE
+<ol>
+<li> PREAMBLE
- <p>The purpose of this License is to make a manual, textbook, or other
-functional and useful document <dfn>free</dfn> in the sense of freedom: to
+<p>The purpose of this License is to make a manual, textbook, or other
+functional and useful document <em>free</em> in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher a way
to get credit for their work, while not being considered responsible
for modifications made by others.
-
- <p>This License is a kind of “copyleft”, which means that
derivative
+</p>
+<p>This License is a kind of “copyleft”, which means that
derivative
works of the document must themselves be free in the same sense. It
complements the GNU General Public License, which is a copyleft
license designed for free software.
-
- <p>We have designed this License in order to use it for manuals for free
+</p>
+<p>We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free
program should come with manuals providing the same freedoms that the
software does. But this License is not limited to software manuals;
it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
+</p>
+</li><li> APPLICABILITY AND DEFINITIONS
- <li>APPLICABILITY AND DEFINITIONS
-
- <p>This License applies to any manual or other work, in any medium, that
+<p>This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
@@ -93,14 +118,14 @@
licensee, and is addressed as “you”. You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.
-
- <p>A “Modified Version” of the Document means any work
containing the
+</p>
+<p>A “Modified Version” of the Document means any work containing
the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
-
- <p>A “Secondary Section” is a named appendix or a
front-matter section
+</p>
+<p>A “Secondary Section” is a named appendix or a front-matter
section
of the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document's overall
+publishers or authors of the Document to the Document’s overall
subject (or to related matters) and contains nothing that could fall
directly within that overall subject. (Thus, if the Document is in
part a textbook of mathematics, a Secondary Section may not explain
@@ -108,21 +133,21 @@
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
-
- <p>The “Invariant Sections” are certain Secondary Sections
whose titles
+</p>
+<p>The “Invariant Sections” are certain Secondary Sections whose
titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.
-
- <p>The “Cover Texts” are certain short passages of text that
are listed,
+</p>
+<p>The “Cover Texts” are certain short passages of text that are
listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.
-
- <p>A “Transparent” copy of the Document means a
machine-readable copy,
+</p>
+<p>A “Transparent” copy of the Document means a machine-readable
copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
@@ -134,9 +159,9 @@
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
of text. A copy that is not “Transparent” is called
“Opaque”.
-
- <p>Examples of suitable formats for Transparent copies include plain
-<span class="sc">ascii</span> without markup, Texinfo input format, LaTeX input
+</p>
+<p>Examples of suitable formats for Transparent copies include plain
+<small>ASCII</small> without markup, Texinfo input format, LaTeX input
format, <acronym>SGML</acronym> or <acronym>XML</acronym> using a publicly
available
<acronym>DTD</acronym>, and standard-conforming simple <acronym>HTML</acronym>,
PostScript or <acronym>PDF</acronym> designed for human modification. Examples
@@ -147,35 +172,35 @@
not generally available, and the machine-generated <acronym>HTML</acronym>,
PostScript or <acronym>PDF</acronym> produced by some word processors for
output purposes only.
-
- <p>The “Title Page” means, for a printed book, the title page
itself,
+</p>
+<p>The “Title Page” means, for a printed book, the title page
itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, “Title Page”
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work’s title,
preceding the beginning of the body of the text.
-
- <p>The “publisher” means any person or entity that
distributes copies
+</p>
+<p>The “publisher” means any person or entity that distributes
copies
of the Document to the public.
-
- <p>A section “Entitled XYZ” means a named subunit of the
Document whose
+</p>
+<p>A section “Entitled XYZ” means a named subunit of the Document
whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
specific section name mentioned below, such as “Acknowledgements”,
“Dedications”, “Endorsements”, or
“History”.) To “Preserve the Title”
of such a section when you modify the Document means that it remains a
section “Entitled XYZ” according to this definition.
-
- <p>The Document may include Warranty Disclaimers next to the notice which
+</p>
+<p>The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document. These Warranty
Disclaimers are considered to be included by reference in this
License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
+</p>
+</li><li> VERBATIM COPYING
- <li>VERBATIM COPYING
-
- <p>You may copy and distribute the Document in any medium, either
+<p>You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies
to the Document are reproduced in all copies, and that you add no other
@@ -184,15 +209,15 @@
copying of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough
number of copies you must also follow the conditions in section 3.
-
- <p>You may also lend copies, under the same conditions stated above, and
+</p>
+<p>You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
+</p>
+</li><li> COPYING IN QUANTITY
- <li>COPYING IN QUANTITY
-
- <p>If you publish printed copies (or copies in media that commonly have
+<p>If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
-Document's license notice requires Cover Texts, you must enclose the
+Document’s license notice requires Cover Texts, you must enclose the
copies in covers that carry, clearly and legibly, all these Cover
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
the back cover. Both covers must also clearly and legibly identify
@@ -202,13 +227,13 @@
Copying with changes limited to the covers, as long as they preserve
the title of the Document and satisfy these conditions, can be treated
as verbatim copying in other respects.
-
- <p>If the required texts for either cover are too voluminous to fit
+</p>
+<p>If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto adjacent
pages.
-
- <p>If you publish or distribute Opaque copies of the Document numbering
+</p>
+<p>If you publish or distribute Opaque copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy
a computer-network location from which the general network-using
@@ -220,51 +245,51 @@
location until at least one year after the last time you distribute an
Opaque copy (directly or through your agents or retailers) of that
edition to the public.
-
- <p>It is requested, but not required, that you contact the authors of the
+</p>
+<p>It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
+</p>
+</li><li> MODIFICATIONS
- <li>MODIFICATIONS
-
- <p>You may copy and distribute a Modified Version of the Document under
+<p>You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
the Modified Version under precisely this License, with the Modified
Version filling the role of the Document, thus licensing distribution
and modification of the Modified Version to whoever possesses a copy
of it. In addition, you must do these things in the Modified Version:
-
- <ol type=A start=1>
-<li>Use in the Title Page (and on the covers, if any) a title distinct
+</p>
+<ol>
+<li> Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions
(which should, if there were any, be listed in the History section
of the Document). You may use the same title as a previous version
if the original publisher of that version gives permission.
- <li>List on the Title Page, as authors, one or more persons or
entities
+</li><li> List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.
- <li>State on the Title page the name of the publisher of the
+</li><li> State on the Title page the name of the publisher of the
Modified Version, as the publisher.
- <li>Preserve all the copyright notices of the Document.
+</li><li> Preserve all the copyright notices of the Document.
- <li>Add an appropriate copyright notice for your modifications
+</li><li> Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
- <li>Include, immediately after the copyright notices, a license
notice
+</li><li> Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.
- <li>Preserve in that license notice the full lists of Invariant
Sections
-and required Cover Texts given in the Document's license notice.
+</li><li> Preserve in that license notice the full lists of Invariant Sections
+and required Cover Texts given in the Document’s license notice.
- <li>Include an unaltered copy of this License.
+</li><li> Include an unaltered copy of this License.
- <li>Preserve the section Entitled “History”, Preserve
its Title, and add
+</li><li> Preserve the section Entitled “History”, Preserve its
Title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page. If
there is no section Entitled “History” in the Document, create one
@@ -272,7 +297,7 @@
given on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.
- <li>Preserve the network location, if any, given in the Document for
+</li><li> Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the “History” section.
@@ -280,38 +305,38 @@
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
- <li>For any section Entitled “Acknowledgements” or
“Dedications”, Preserve
+</li><li> For any section Entitled “Acknowledgements” or
“Dedications”, Preserve
the Title of the section, and preserve in the section all the
substance and tone of each of the contributor acknowledgements and/or
dedications given therein.
- <li>Preserve all the Invariant Sections of the Document,
+</li><li> Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles. Section numbers
or the equivalent are not considered part of the section titles.
- <li>Delete any section Entitled “Endorsements”. Such a
section
+</li><li> Delete any section Entitled “Endorsements”. Such a
section
may not be included in the Modified Version.
- <li>Do not retitle any existing section to be Entitled
“Endorsements” or
+</li><li> Do not retitle any existing section to be Entitled
“Endorsements” or
to conflict in title with any Invariant Section.
- <li>Preserve any Warranty Disclaimers.
- </ol>
+</li><li> Preserve any Warranty Disclaimers.
+</li></ol>
- <p>If the Modified Version includes new front-matter sections or
+<p>If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no material
copied from the Document, you may at your option designate some or all
of these sections as invariant. To do this, add their titles to the
-list of Invariant Sections in the Modified Version's license notice.
+list of Invariant Sections in the Modified Version’s license notice.
These titles must be distinct from any other section titles.
-
- <p>You may add a section Entitled “Endorsements”, provided it
contains
+</p>
+<p>You may add a section Entitled “Endorsements”, provided it
contains
nothing but endorsements of your Modified Version by various
parties—for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a
standard.
-
- <p>You may add a passage of up to five words as a Front-Cover Text, and a
+</p>
+<p>You may add a passage of up to five words as a Front-Cover Text, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version. Only one passage of
Front-Cover Text and one of Back-Cover Text may be added by (or
@@ -320,21 +345,21 @@
by arrangement made by the same entity you are acting on behalf of,
you may not add another; but you may replace the old one, on explicit
permission from the previous publisher that added the old one.
-
- <p>The author(s) and publisher(s) of the Document do not by this License
+</p>
+<p>The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
+</p>
+</li><li> COMBINING DOCUMENTS
- <li>COMBINING DOCUMENTS
-
- <p>You may combine the Document with other documents released under this
+<p>You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its
license notice, and that you preserve all their Warranty Disclaimers.
-
- <p>The combined work need only contain one copy of this License, and
+</p>
+<p>The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by
@@ -342,48 +367,48 @@
author or publisher of that section if known, or else a unique number.
Make the same adjustment to the section titles in the list of
Invariant Sections in the license notice of the combined work.
-
- <p>In the combination, you must combine any sections Entitled
“History”
+</p>
+<p>In the combination, you must combine any sections Entitled
“History”
in the various original documents, forming one section Entitled
“History”; likewise combine any sections Entitled
“Acknowledgements”,
and any sections Entitled “Dedications”. You must delete all
sections Entitled “Endorsements.”
+</p>
+</li><li> COLLECTIONS OF DOCUMENTS
- <li>COLLECTIONS OF DOCUMENTS
-
- <p>You may make a collection consisting of the Document and other
documents
+<p>You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
License in the various documents with a single copy that is included in
the collection, provided that you follow the rules of this License for
verbatim copying of each of the documents in all other respects.
-
- <p>You may extract a single document from such a collection, and
distribute
+</p>
+<p>You may extract a single document from such a collection, and distribute
it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
+</p>
+</li><li> AGGREGATION WITH INDEPENDENT WORKS
- <li>AGGREGATION WITH INDEPENDENT WORKS
-
- <p>A compilation of the Document or its derivatives with other separate
+<p>A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, is called an “aggregate” if the copyright
resulting from the compilation is not used to limit the legal rights
-of the compilation's users beyond what the individual works permit.
+of the compilation’s users beyond what the individual works permit.
When the Document is included in an aggregate, this License does not
apply to the other works in the aggregate which are not themselves
derivative works of the Document.
-
- <p>If the Cover Text requirement of section 3 is applicable to these
+</p>
+<p>If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half of
-the entire aggregate, the Document's Cover Texts may be placed on
+the entire aggregate, the Document’s Cover Texts may be placed on
covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.
+</p>
+</li><li> TRANSLATION
- <li>TRANSLATION
-
- <p>Translation is considered a kind of modification, so you may
+<p>Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
@@ -395,48 +420,48 @@
of those notices and disclaimers. In case of a disagreement between
the translation and the original version of this License or a notice
or disclaimer, the original version will prevail.
-
- <p>If a section in the Document is Entitled
“Acknowledgements”,
+</p>
+<p>If a section in the Document is Entitled “Acknowledgements”,
“Dedications”, or “History”, the requirement (section
4) to Preserve
its Title (section 1) will typically require changing the actual
title.
+</p>
+</li><li> TERMINATION
- <li>TERMINATION
-
- <p>You may not copy, modify, sublicense, or distribute the Document
+<p>You may not copy, modify, sublicense, or distribute the Document
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense, or distribute it is void, and
will automatically terminate your rights under this License.
-
- <p>However, if you cease all violation of this License, then your license
+</p>
+<p>However, if you cease all violation of this License, then your license
from a particular copyright holder is reinstated (a) provisionally,
unless and until the copyright holder explicitly and finally
terminates your license, and (b) permanently, if the copyright holder
fails to notify you of the violation by some reasonable means prior to
60 days after the cessation.
-
- <p>Moreover, your license from a particular copyright holder is
+</p>
+<p>Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
-
- <p>Termination of your rights under this section does not terminate the
+</p>
+<p>Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, receipt of a copy of some or all of the same material does
not give you any rights to use it.
+</p>
+</li><li> FUTURE REVISIONS OF THIS LICENSE
- <li>FUTURE REVISIONS OF THIS LICENSE
-
- <p>The Free Software Foundation may publish new, revised versions
+<p>The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
<a href="http://www.gnu.org/copyleft/";>http://www.gnu.org/copyleft/</a>.
-
- <p>Each version of the License is given a distinguishing version number.
+</p>
+<p>Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
License “or any later version” applies to it, you have the option
of
following the terms and conditions either of that specified version or
@@ -445,47 +470,49 @@
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation. If the Document
specifies that a proxy can decide which future versions of this
-License can be used, that proxy's public statement of acceptance of a
+License can be used, that proxy’s public statement of acceptance of a
version permanently authorizes you to choose that version for the
Document.
+</p>
+</li><li> RELICENSING
- <li>RELICENSING
-
- <p>“Massive Multiauthor Collaboration Site” (or “MMC
Site”) means any
+<p>“Massive Multiauthor Collaboration Site” (or “MMC
Site”) means any
World Wide Web server that publishes copyrightable works and also
provides prominent facilities for anybody to edit those works. A
public wiki that anybody can edit is an example of such a server. A
“Massive Multiauthor Collaboration” (or “MMC”)
contained in the
site means any set of copyrightable works thus published on the MMC
site.
-
- <p>“CC-BY-SA” means the Creative Commons Attribution-Share
Alike 3.0
+</p>
+<p>“CC-BY-SA” means the Creative Commons Attribution-Share Alike
3.0
license published by Creative Commons Corporation, a not-for-profit
corporation with a principal place of business in San Francisco,
California, as well as future copyleft versions of that license
published by that same organization.
-
- <p>“Incorporate” means to publish or republish a Document, in
whole or
+</p>
+<p>“Incorporate” means to publish or republish a Document, in
whole or
in part, as part of another Document.
-
- <p>An MMC is “eligible for relicensing” if it is licensed
under this
+</p>
+<p>An MMC is “eligible for relicensing” if it is licensed under
this
License, and if all works that were first published under this License
somewhere other than this MMC, and subsequently incorporated in whole
or in part into the MMC, (1) had no cover texts or invariant sections,
and (2) were thus incorporated prior to November 1, 2008.
-
- <p>The operator of an MMC Site may republish an MMC contained in the site
+</p>
+<p>The operator of an MMC Site may republish an MMC contained in the site
under CC-BY-SA on the same site at any time before August 1, 2009,
provided the MMC is eligible for relicensing.
+</p>
+</li></ol>
- </ol>
-
+<a name="ADDENDUM_003a-How-to-use-this-License-for-your-documents"></a>
<h3 class="heading">ADDENDUM: How to use this License for your documents</h3>
<p>To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
license notices just after the title page:
-
+</p>
+<div class="smallexample">
<pre class="smallexample"> Copyright (C) <var>year</var> <var>your
name</var>.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
@@ -493,25 +520,35 @@
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is included in the section entitled ``GNU
Free Documentation License''.
-</pre>
- <p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
-replace the “with<small class="dots">...</small>Texts.” line with
this:
+</pre></div>
+<p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the “with…Texts.” line with this:
+</p>
+<div class="smallexample">
<pre class="smallexample"> with the Invariant Sections being <var>list
their titles</var>, with
the Front-Cover Texts being <var>list</var>, and with the Back-Cover
Texts
being <var>list</var>.
-</pre>
- <p>If you have Invariant Sections without Cover Texts, or some other
+</pre></div>
+
+<p>If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.
-
- <p>If your document contains nontrivial examples of program code, we
+</p>
+<p>If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License,
to permit their use in free software.
+</p>
+
+
+<hr>
+<div class="header">
+<p>
+Previous: <a href="Index.html#Index" accesskey="p" rel="previous">Index</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>
+
-<!-- Local Variables: -->
-<!-- ispell-local-pdict: "ispell-dict" -->
-<!-- End: -->
- </body></html>
+</body>
+</html>
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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Credits-Slot.html 26 Sep 2012 14:49:41 -0000 1.15
+++ gnun/html_node/Credits-Slot.html 4 Dec 2012 16:24:21 -0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Credits Slot - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="New-Translation.html#New-Translation" title="New
Translation">
-<link rel="prev" href="Notes-Slot.html#Notes-Slot" title="Notes Slot">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,57 +9,96 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Credits Slot</title>
+
+<meta name="description" content="GNUnited Nations: Credits Slot">
+<meta name="keywords" content="GNUnited Nations: Credits Slot">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="New-Translation.html#New-Translation" rel="up" title="New
Translation">
+<link href="Migrating.html#Migrating" rel="next" title="Migrating">
+<link href="Notes-Slot.html#Notes-Slot" rel="previous" title="Notes Slot">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Credits-Slot"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="Notes-Slot.html#Notes-Slot">Notes Slot</a>,
-Up: <a rel="up" accesskey="u"
href="New-Translation.html#New-Translation">New Translation</a>
-<hr>
+Previous: <a href="Notes-Slot.html#Notes-Slot" accesskey="p"
rel="previous">Notes Slot</a>, Up: <a
href="New-Translation.html#New-Translation" accesskey="u" rel="up">New
Translation</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-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>
-<h5 class="subsubsection">2.3.1.2 The Special Slot for Translator's
Credits</h5>
-
-<p><a name="index-credits_002c-translators-74"></a><a
name="index-translators_0027-credits-75"></a>
-Most of the translators usually put their name under the translation,
+<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>Like the previous slot, you should “translate” it as a
<SPC> if
-you don't want your name to appear there.
-
- <p>Here is an example of the recommended way to specify credits:
-
-<pre class="example"> <b>Traduction</b>: Benjamin Drieu
- <a
href="mailto:address@hidden">&lt;address@hidden&gt;</a>,
- 2007, 2008.
-</pre>
- <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,
+<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>
+
- </body></html>
+</body>
+</html>
Index: gnun/html_node/Disadvantages.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/Disadvantages.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Disadvantages.html 26 Sep 2012 14:49:41 -0000 1.15
+++ gnun/html_node/Disadvantages.html 4 Dec 2012 16:24:21 -0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Disadvantages - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Introduction.html#Introduction" title="Introduction">
-<link rel="prev" href="Advantages.html#Advantages" title="Advantages">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,56 +9,83 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Disadvantages</title>
+
+<meta name="description" content="GNUnited Nations: Disadvantages">
+<meta name="keywords" content="GNUnited Nations: Disadvantages">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Introduction.html#Introduction" rel="up" title="Introduction">
+<link href="Usage.html#Usage" rel="next" title="Usage">
+<link href="Advantages.html#Advantages" rel="previous" title="Advantages">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Disadvantages"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="Advantages.html#Advantages">Advantages</a>,
-Up: <a rel="up" accesskey="u"
href="Introduction.html#Introduction">Introduction</a>
-<hr>
+Previous: <a href="Advantages.html#Advantages" accesskey="p"
rel="previous">Advantages</a>, Up: <a href="Introduction.html#Introduction"
accesskey="u" rel="up">Introduction</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-
+<hr>
+<a name="Known-Bugs-and-Limitations"></a>
<h3 class="section">1.4 Known Bugs and Limitations</h3>
-<p>As it happens in real life, we don't wear pink glasses and are aware
+<p>As it happens in real life, we don’t wear pink glasses and are aware
of certain limitations and annoyances of this semi-automatic system.
+</p>
+<ul>
+<li> There is no easy way to preview the translations. The official build
+is invoked twice an hour, because doing it much more often is not
+feasible with current build server hardware. Additionally, any errors
+interrupt the build so they have to be fixed before the next articles
+are processed.
+</li></ul>
- <ul>
-<li>The official build is invoked thrice daily<a rel="footnote" href="#fn-1"
name="fnd-1"><sup>1</sup></a>, because doing it more often
-will potentially generate more messages to the mailing list in the form
-of commit notifications. This has its drawback, since translators have
-to wait 8 hours until their PO files are updated, and another period
-for the <samp><span class="file">.</span><var>lang</var><span
class="file">.html</span></samp> articles to get generated, after they
-commit the updated POs. Additionally, any errors interrupt the build so
-they have to be fixed before the next articles are processed.
-</ul>
-
- <div class="footnote">
-<hr>
-<h4>Footnotes</h4><p class="footnote"><small>[<a name="fn-1"
href="#fnd-1">1</a>]</small> The “no-grace”
-items are rebuilt hourly.</p>
- <hr></div>
- </body></html>
+</body>
+</html>
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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/GNU-News.html 26 Sep 2012 14:49:42 -0000 1.15
+++ gnun/html_node/GNU-News.html 4 Dec 2012 16:24:21 -0000 1.16
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>GNU News - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="PO-Files.html#PO-Files" title="PO Files">
-<link rel="prev" href="Migrating.html#Migrating" title="Migrating">
-<link rel="next" href="PO-Tips.html#PO-Tips" title="PO Tips">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,67 +9,101 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: GNU News</title>
+
+<meta name="description" content="GNUnited Nations: GNU News">
+<meta name="keywords" content="GNUnited Nations: GNU News">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="PO-Files.html#PO-Files" rel="up" title="PO Files">
+<link href="PO-Tips.html#PO-Tips" rel="next" title="PO Tips">
+<link href="Migrating.html#Migrating" rel="previous" title="Migrating">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="GNU-News"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="PO-Tips.html#PO-Tips">PO Tips</a>,
-Previous: <a rel="previous" accesskey="p"
href="Migrating.html#Migrating">Migrating</a>,
-Up: <a rel="up" accesskey="u" href="PO-Files.html#PO-Files">PO Files</a>
-<hr>
+Next: <a href="PO-Tips.html#PO-Tips" accesskey="n" rel="next">PO Tips</a>,
Previous: <a href="Migrating.html#Migrating" accesskey="p"
rel="previous">Migrating</a>, Up: <a href="PO-Files.html#PO-Files"
accesskey="u" rel="up">PO Files</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-
+<hr>
+<a name="Special-Handling-for-GNU-News"></a>
<h4 class="subsection">2.3.3 Special Handling for GNU News</h4>
+<a name="index-gnunews"></a>
+<a name="index-whatsnew"></a>
+<a name="index-gnusflashes"></a>
-<p><a name="index-gnunews-78"></a><a name="index-whatsnew-79"></a><a
name="index-gnusflashes-80"></a>
-<strong>Pay attention:</strong> The practice of news handling that is
+<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>The GNU website has infrastructure for supporting “What's
New”, also
+</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><span class="file">server/whatsnew.txt</span></samp> and are used
to build
-<samp><span class="file">server/whatsnew.include</span></samp> and <samp><span
class="file">gnusflashes.include</span></samp>. The
-former is used by <samp><span class="file">server/whatsnew.html</span></samp>,
while the latter is
+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>GNUN has additional rules for building <samp><span
class="file">whatsnew.pot</span></samp>, which
+</p>
+<p>GNUN has additional rules for building <samp>whatsnew.pot</samp>, which
contains a combination of all necessary strings for
-<samp><span class="file">server/whatsnew.</span><var>lang</var><span
class="file">.html</span></samp>,
-<samp><span class="file">server/whatsnew.</span><var>lang</var><span
class="file">.include</span></samp> and
-<samp><span class="file">gnusflashes.</span><var>lang</var><span
class="file">.include</span></samp>. There is nothing unusual in this
+<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><span class="file">whatsnew.</span><var>lang</var><span
class="file">.po</span></samp>, it will be used to generate all three
-localized files. In addition, if there is a homepage for this language,
-it will be rebuilt when <samp><span
class="file">gnusflashes.</span><var>lang</var><span
class="file">.include</span></samp> is
-generated for the first time in order the translated homepage to include
-it instead of <samp><span class="file">gnusflashes.include</span></samp>.
-
- <p>Note that localized RSS feeds are not supported on purpose, as it would
+<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>
+
- </body></html>
+</body>
+</html>
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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/GNUmakefile_002eteam-Variables.html 26 Sep 2012 14:49:42
-0000 1.15
+++ gnun/html_node/GNUmakefile_002eteam-Variables.html 4 Dec 2012 16:24:22
-0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>GNUmakefile.team Variables - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="PO-Files-and-Team.html#PO-Files-and-Team" title="PO Files
and Team">
-<link rel="next"
href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron"
title="GNUmakefile.team and Cron">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,157 +9,118 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: GNUmakefile.team Variables</title>
+
+<meta name="description" content="GNUnited Nations: GNUmakefile.team
Variables">
+<meta name="keywords" content="GNUnited Nations: GNUmakefile.team Variables">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="PO-Files-and-Team.html#PO-Files-and-Team" rel="up" title="PO Files
and Team">
+<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">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
-<a name="GNUmakefile.team-Variables"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="GNUmakefile_002eteam-Variables"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron">GNUmakefile.team
and Cron</a>,
-Up: <a rel="up" accesskey="u"
href="PO-Files-and-Team.html#PO-Files-and-Team">PO Files and Team</a>
-<hr>
+Next: <a href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets"
accesskey="n" rel="next">GNUmakefile.team Targets</a>, Up: <a
href="PO-Files-and-Team.html#PO-Files-and-Team" accesskey="u" rel="up">PO Files
and Team</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-
-<h5 class="subsubsection">2.3.7.1 Adopting <samp><span
class="file">GNUmakefile.team</span></samp> for a Specific Team</h5>
+<hr>
+<a name="Adopting-GNUmakefile_002eteam-for-a-Specific-Team"></a>
+<h4 class="subsubsection">2.3.7.1 Adopting <samp>GNUmakefile.team</samp> for a
Specific Team</h4>
<p>To adjust the makefile for your team, you need to edit two variables.
-
- <dl>
-<dt>‘<samp><span class="samp">TEAM</span></samp>’<dd>Set this to
the language code, like <code>bg</code> or <code>pt-br</code>.
-
- <br><dt>‘<samp><span
class="samp">wwwdir</span></samp>’<dd>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><span
class="file">~/projects/www-</span><var>lang</var></samp> and the `www' Web
-repository at <samp><span class="file">~/projects/www</span></samp>, the value
of <code>wwwdir</code> should
-be <code>../www/</code> or <samp><span
class="file">/home/</span><var>user</var><span
class="file">/projects/www/</span></samp>. Note the
+</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>.
+</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>
</dl>
- <p>If two variants of one language share the same project and repository
+<p>If two variants of one language share the same project and repository
(such as <code>zh-cn</code> and <code>zh-tw</code>), they should maintain two
-directories with two <samp><span class="file">GNUmakefile</span></samp>s and
each directory having its
+directories with two <samp>GNUmakefile</samp>s and each directory having its
own tree.
-
- <p>Some variables are specified on the command line, and alter the behavior
+</p>
+<p>Some variables are specified on the command line, and alter the behavior
of the build process.
-
- <dl>
-<dt>‘<samp><span class="samp">VERBOSE=yes</span></samp>’<dd>Print
more information from <samp><span class="command">cvs</span></samp>,
<samp><span class="command">svn</span></samp> and
-<samp><span class="command">msgmerge</span></samp>; off by default. Note that
<code>VERBOSE</code> can be
+</p>
+<dl compact="compact">
+<dt>‘<samp>VERBOSE=yes</samp>’</dt>
+<dd><p>Print more information from <code>cvs</code>, <code>svn</code> and
+<code>msgmerge</code>; off by default. Note that <code>VERBOSE</code> can be
defined to any string, it will have the same effect.
-
- <br><dt>‘<samp><span
class="samp">VCS=yes</span></samp>’<dd>Update both ‘<samp><span
class="samp">www</span></samp>’ and ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’ repositories, then
+</p>
+</dd>
+<dt>‘<samp>VCS=yes</samp>’</dt>
+<dd><p>Update both ‘<samp>www</samp>’ and
‘<samp>www-<var>lang</var></samp>’ 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.
-
- <p><strong>Caution:</strong> The makefile rule will commit all local
changes, not
-only those that resulted from running <samp><span
class="command">msgmerge</span></samp>. Thus, it is
+</p>
+<p><strong>Caution:</strong> The makefile rule will commit all local changes,
not
+only those that resulted from running <code>msgmerge</code>. Thus, it is
better to use a separate working copy dedicated solely for this
purpose.
+</p></dd>
</dl>
-<h5 class="unnumberedsubsubsec">Targets in <samp><span
class="file">GNUmakefile.team</span></samp></h5>
-
- <dl>
-<dt><code>update</code><dd>Updates the repositories. Does nothing unless
<code>VCS=yes</code>.
-
- <br><dt><code>sync</code><dd>Merges all available PO files from the
corresponding POT in <dfn>www</dfn>.
-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.
-
- <br><dt><code>report</code><dd>Verifies which translations are complete,
and prints a list (with
-statistics) of those that need to be updated.
-
- <br><dt><code>format</code><dd>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>This rule checks for all translations that have lines longer than 80,
-and runs <samp><span class="command">msgcat</span></samp> 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 <samp><span class="command">msgcat</span></samp> for any
file that has a longer
-line, wherever it may occur.
-
- <br><dt><code>publish</code><dd>The <code>publish</code> rule's task is
to copy all modified files to the
-official <dfn>www</dfn> 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 <samp><span
class="command">cp</span></samp> invocations.
-As a rule of thumb, before running this rule it is sane to run
-<code>sync</code> and correct any <dfn>fuzzy</dfn> messages and other
problems, if
-necessary.
-
- <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>As usual, when committing to the official repository, it is always a
-good practice to examine the output of <samp><span class="command">cvs
diff</span></samp>.
-
- <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><span class="file">.pot</span></samp> is missing.
-
- <p>Typically, after an editing session (whether it involves actual editing
-or just merging contributions from team members), one would do:
-
- <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>
- <br><dt><code>clean</code><dd>Deletes all backup and auto-generated files
that some PO editors leave
-behind, namely—<samp><var>file</var><span
class="file">.po~</span></samp>, <samp><var>file</var><span
class="file">.po.bak</span></samp> and
-<samp><var>file</var><span class="file">.mo</span></samp>.
-</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>Feel free to replace all strings with equivalents in your native
-language and of course—do not hesitate to extend this file and modify
-it as much as you like. For example, useful extra functionality would
-be a target that will check which files have not yet been committed in
-the official repository, or which files have to be updated there
-(i.e. they were updated by the team members but not installed by the
-coordinator). Either way, if you come up with something interesting, it
-would be nice to send a message to <a
href="mailto:address@hidden";>address@hidden</a>, so that
-<samp><span class="file">GNUmakefile.team</span></samp> gets updated for all
teams' benefit.
- </body></html>
+</body>
+</html>
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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/GNUmakefile_002eteam-and-Cron.html 26 Sep 2012 14:49:42
-0000 1.15
+++ gnun/html_node/GNUmakefile_002eteam-and-Cron.html 4 Dec 2012 16:24:22
-0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>GNUmakefile.team and Cron - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="PO-Files-and-Team.html#PO-Files-and-Team" title="PO Files
and Team">
-<link rel="prev"
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables"
title="GNUmakefile.team Variables">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,61 +9,101 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: GNUmakefile.team and Cron</title>
+
+<meta name="description" content="GNUnited Nations: GNUmakefile.team and Cron">
+<meta name="keywords" content="GNUnited Nations: GNUmakefile.team and Cron">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="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="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets"
rel="previous" title="GNUmakefile.team Targets">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
-<a name="GNUmakefile.team-and-Cron"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="GNUmakefile_002eteam-and-Cron"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables">GNUmakefile.team
Variables</a>,
-Up: <a rel="up" accesskey="u"
href="PO-Files-and-Team.html#PO-Files-and-Team">PO Files and Team</a>
-<hr>
+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>
</div>
+<hr>
+<a name="Automatic-Synchronization-and-Status-Reports"></a>
+<h4 class="subsubsection">2.3.7.3 Automatic Synchronization and Status
Reports</h4>
+<a name="index-team-maintenance_002c-cron"></a>
+<a name="index-cron_002c-team-maintenance"></a>
-<h5 class="subsubsection">2.3.7.2 Automatic Synchronization and Status
Reports</h5>
-
-<p><a name="index-team-maintenance_002c-cron-91"></a><a
name="index-cron_002c-team-maintenance-92"></a>
-It is convenient to invoke such synchronization automatically, for
+<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
+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>
-<pre class="example"> # m h dom mon dow command
- @daily cd $HOME/projects/www-<var>lang</var>; make VCS=yes
-</pre>
- <p>It is not necessary the job to be run on the team leader's machine,
+<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>If desired, you could set up another job to report the status of the
+</p>
+<p>If desired, you could set up another job to report the status of the
translations weekly or fortnightly, for example:
-
-<pre class="example"> # m h dom mon dow command
- @weekly cd $HOME/projects/www-<var>lang</var>; \
- make report | mail -s "Weekly statistics" \
+</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>
- <p><strong>Caution:</strong> Most cron implementations do not allow the
character
-`\' as a line continuation character—the example shown is made that
+</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>
+
- </body></html>
+</body>
+</html>
Index: gnun/html_node/GRACE.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/GRACE.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- gnun/html_node/GRACE.html 30 Jan 2012 16:06:42 -0000 1.1
+++ gnun/html_node/GRACE.html 4 Dec 2012 16:24:22 -0000 1.2
@@ -1 +1,65 @@
-<meta http-equiv="refresh" content="0; url=Runtime-Variables.html#GRACE">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!--
+This manual (updated 3 December 2012) is for GNUnited Nations (version
+0.6), a suite for maintaining translations of www.gnu.org
+essays and other articles.
+
+
+Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- This file redirects to the location of a node or anchor -->
+<head>
+<title>GNUnited Nations: GRACE</title>
+
+<meta name="description" content="GNUnited Nations: GRACE">
+<meta name="keywords" content="GNUnited Nations: GRACE">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+<meta http-equiv="Refresh" content="0; url=Runtime-Variables.html#GRACE">
+
+</head>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+
+<p>The node you are looking for is at <a
href="Runtime-Variables.html#GRACE">GRACE</a>.</p>
+</body>
Index: gnun/html_node/Index.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Index.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Index.html 26 Sep 2012 14:49:42 -0000 1.15
+++ gnun/html_node/Index.html 4 Dec 2012 16:24:22 -0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Index - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Bugs.html#Bugs" title="Bugs">
-<link rel="next" href="Copying-This-Manual.html#Copying-This-Manual"
title="Copying This Manual">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,153 +9,308 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Index</title>
+
+<meta name="description" content="GNUnited Nations: Index">
+<meta name="keywords" content="GNUnited Nations: Index">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Copying-This-Manual.html#Copying-This-Manual" rel="next"
title="Copying This Manual">
+<link href="Bugs.html#Bugs" rel="previous" title="Bugs">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Index"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Copying-This-Manual.html#Copying-This-Manual">Copying This Manual</a>,
-Previous: <a rel="previous" accesskey="p" href="Bugs.html#Bugs">Bugs</a>,
-Up: <a rel="up" accesskey="u" href="index.html#Top">Top</a>
+Next: <a href="Copying-This-Manual.html#Copying-This-Manual" accesskey="n"
rel="next">Copying This Manual</a>, Previous: <a href="Bugs.html#Bugs"
accesskey="p" rel="previous">Bugs</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"
title="Index" rel="index">Index</a>]</p>
+</div>
<hr>
+<a name="Index-1"></a>
+<h2 class="unnumbered">Index</h2>
+
+<table><tr><th valign="top">Jump to: </th><td><a class="summary-letter"
href="#Index_cp_letter-A"><b>A</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-B"><b>B</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-C"><b>C</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-D"><b>D</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-E"><b>E</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-F"><b>F</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-G"><b>G</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-I"><b>I</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-L"><b>L</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-M"><b>M</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-N"><b>N</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-O"><b>O</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-P"><b>P</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-R"><b>R</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-S"><b>S</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-T"><b>T</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-V"><b>V</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-W"><b>W</b></a>
+
+</td></tr></table>
+<table class="index-cp" border="0">
+<tr><td></td><th align="left">Index Entry</th><td> </td><th align="left">
Section</th></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-A">A</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-ALL_005fDIRS">ALL_DIRS</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="Runtime-Variables.html#index-announce">announce</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="Main-Variables.html#index-articles-in-root-directory_002c-defining">articles
in root directory, defining</a>:</td><td> </td><td valign="top"><a
href="Main-Variables.html#Main-Variables">Main Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-B">B</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-Bazaar">Bazaar</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="Modifying-Boilerplates.html#index-boilerplates">boilerplates</a>:</td><td> </td><td
valign="top"><a
href="Modifying-Boilerplates.html#Modifying-Boilerplates">Modifying
Boilerplates</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Bugs.html#index-bugs_002c-reporting">bugs,
reporting</a>:</td><td> </td><td valign="top"><a
href="Bugs.html#Bugs">Bugs</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-bzr">bzr</a>:</td><td> </td><td
valign="top"><a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-C">C</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="Comments-for-Translators.html#index-comments-for-translators">comments
for translators</a>:</td><td> </td><td valign="top"><a
href="Comments-for-Translators.html#Comments-for-Translators">Comments for
Translators</a></td></tr>
+<tr><td></td><td valign="top"><a
href="gnun_002ddiff_002dpo.html#index-comparing_002c-translations">comparing,
translations</a>:</td><td> </td><td valign="top"><a
href="gnun_002ddiff_002dpo.html#gnun_002ddiff_002dpo">gnun-diff-po</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Compendia.html#index-compendia">compendia</a>:</td><td> </td><td
valign="top"><a href="Compendia.html#Compendia">Compendia</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Compendia.html#index-compendium_002epot">compendium.pot</a>:</td><td> </td><td
valign="top"><a href="Compendia.html#Compendia">Compendia</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Invoking-GNUN.html#index-config_002emk">config.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="Splitting-Long-Passages.html#index-conventional-separator-for-strings">conventional
separator for strings</a>:</td><td> </td><td valign="top"><a
href="Splitting-Long-Passages.html#Splitting-Long-Passages">Splitting Long
Passages</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Migrating.html#index-conversion-of-existing-translations">conversion of
existing translations</a>:</td><td> </td><td valign="top"><a
href="Migrating.html#Migrating">Migrating</a></td></tr>
+<tr><td></td><td valign="top"><a
href="gnun_002dpreconvert.html#index-conversion-of-existing-translations-1">conversion
of existing translations</a>:</td><td> </td><td valign="top"><a
href="gnun_002dpreconvert.html#gnun_002dpreconvert">gnun-preconvert</a></td></tr>
+<tr><td></td><td valign="top"><a
href="gnun_002dmerge_002dpreconverted.html#index-conversion-of-existing-translations-2">conversion
of existing translations</a>:</td><td> </td><td valign="top"><a
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a></td></tr>
+<tr><td></td><td valign="top"><a
href="New-Translation.html#index-credits_002c-translators">credits,
translators</a>:</td><td> </td><td valign="top"><a
href="New-Translation.html#New-Translation">New Translation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Credits-Slot.html#index-credits_002c-translators-1">credits,
translators</a>:</td><td> </td><td valign="top"><a
href="Credits-Slot.html#Credits-Slot">Credits Slot</a></td></tr>
+<tr><td></td><td valign="top"><a
href="GNUmakefile_002eteam-and-Cron.html#index-cron_002c-team-maintenance">cron,
team maintenance</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="Runtime-Variables.html#index-CVS">CVS</a>:</td><td> </td><td
valign="top"><a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-D">D</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-deferred-generation-of-articles">deferred
generation of articles</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="Main-Variables.html#index-defining-articles-in-the-root-dir">defining
articles in the root dir</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-defining-directories">defining
directories</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-defining-templates">defining
templates</a>:</td><td> </td><td valign="top"><a
href="Main-Variables.html#Main-Variables">Main Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-defining-templates-1">defining
templates</a>:</td><td> </td><td valign="top"><a
href="Main-Variables.html#Main-Variables">Main Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-defining-templates-2">defining
templates</a>:</td><td> </td><td valign="top"><a
href="Main-Variables.html#Main-Variables">Main Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-directories_002c-defining">directories,
defining</a>:</td><td> </td><td valign="top"><a
href="Main-Variables.html#Main-Variables">Main Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-E">E</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="Compendia.html#index-exclude_002epot">exclude.pot</a>:</td><td> </td><td
valign="top"><a href="Compendia.html#Compendia">Compendia</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-extra_002dtemplates">extra-templates</a>:</td><td> </td><td
valign="top"><a href="Main-Variables.html#Main-Variables">Main
Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-F">F</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-fuzzy-strings">fuzzy
strings</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="Main-Variables.html#index-FUZZY_005fDIFF_005fLINGUAS">FUZZY_DIFF_LINGUAS</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-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="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>
+<tr><td></td><td valign="top"><a
href="GNU-News.html#index-gnusflashes">gnusflashes</a>:</td><td> </td><td
valign="top"><a href="GNU-News.html#GNU-News">GNU News</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-GRACE">GRACE</a>:</td><td> </td><td
valign="top"><a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-grace-period">grace
period</a>:</td><td> </td><td valign="top"><a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-I">I</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="gnun_002dinit_002dpo.html#index-initializing_002c-translations">initializing,
translations</a>:</td><td> </td><td valign="top"><a
href="gnun_002dinit_002dpo.html#gnun_002dinit_002dpo">gnun-init-po</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Invoking-GNUN.html#index-invocation">invocation</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="Invoking-GNUN.html#index-invoking">invoking</a>:</td><td> </td><td
valign="top"><a href="Invoking-GNUN.html#Invoking-GNUN">Invoking
GNUN</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-L">L</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="Localized-URLs.html#index-localized-URLs">localized
URLs</a>:</td><td> </td><td valign="top"><a
href="Localized-URLs.html#Localized-URLs">Localized URLs</a></td></tr>
+<tr><td></td><td valign="top"><a
href="New-Translation.html#index-long-lines_002c-wrap">long lines,
wrap</a>:</td><td> </td><td valign="top"><a
href="New-Translation.html#New-Translation">New Translation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Splitting-Long-Passages.html#index-long-passages_002c-avoiding">long
passages, avoiding</a>:</td><td> </td><td valign="top"><a
href="Splitting-Long-Passages.html#Splitting-Long-Passages">Splitting Long
Passages</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-M">M</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-mail_002c-notifications">mail,
notifications</a>:</td><td> </td><td valign="top"><a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="mailfail.html#index-mail_002c-notifications-1">mail,
notifications</a>:</td><td> </td><td valign="top"><a
href="mailfail.html#mailfail">mailfail</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Migrating.html#index-migration_002c-translations">migration,
translations</a>:</td><td> </td><td valign="top"><a
href="Migrating.html#Migrating">Migrating</a></td></tr>
+<tr><td></td><td valign="top"><a
href="gnun_002dpreconvert.html#index-migration_002c-translations-1">migration,
translations</a>:</td><td> </td><td valign="top"><a
href="gnun_002dpreconvert.html#gnun_002dpreconvert">gnun-preconvert</a></td></tr>
+<tr><td></td><td valign="top"><a
href="gnun_002dmerge_002dpreconverted.html#index-migration_002c-translations-2">migration,
translations</a>:</td><td> </td><td valign="top"><a
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-N">N</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="New-Translation.html#index-new-translation">new
translation</a>:</td><td> </td><td valign="top"><a
href="New-Translation.html#New-Translation">New Translation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-new-translations_002c-notifications_002fannouncements">new
translations, notifications/announcements</a>:</td><td> </td><td
valign="top"><a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="New-Translation.html#index-notes_002c-translators">notes,
translators</a>:</td><td> </td><td valign="top"><a
href="New-Translation.html#New-Translation">New Translation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Notes-Slot.html#index-notes_002c-translators-1">notes,
translators</a>:</td><td> </td><td valign="top"><a
href="Notes-Slot.html#Notes-Slot">Notes Slot</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-NOTIFY">NOTIFY</a>:</td><td> </td><td
valign="top"><a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-O">O</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-optional_002dtemplates">optional-templates</a>:</td><td> </td><td
valign="top"><a href="Main-Variables.html#Main-Variables">Main
Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-OUTDATED_002dGRACE">OUTDATED-GRACE</a>:</td><td> </td><td
valign="top"><a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-output_002c-detailed">output,
detailed</a>:</td><td> </td><td valign="top"><a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-P">P</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="PO-Files.html#index-PO-editors">PO
editors</a>:</td><td> </td><td valign="top"><a
href="PO-Files.html#PO-Files">PO Files</a></td></tr>
+<tr><td></td><td valign="top"><a
href="New-Translation.html#index-PO-headers">PO
headers</a>:</td><td> </td><td valign="top"><a
href="New-Translation.html#New-Translation">New Translation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="PO-Files.html#index-PO_002c-editing">PO,
editing</a>:</td><td> </td><td valign="top"><a
href="PO-Files.html#PO-Files">PO Files</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-POT-generation_002c-articles">POT generation,
articles</a>:</td><td> </td><td valign="top"><a
href="Main-Variables.html#Main-Variables">Main Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-previous_002c-diff">previous,
diff</a>:</td><td> </td><td valign="top"><a
href="Main-Variables.html#Main-Variables">Main Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="gnun_002dadd_002dfuzzy_002ddiff.html#index-previous_002c-diff-1">previous,
diff</a>:</td><td> </td><td valign="top"><a
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff">gnun-add-fuzzy-diff</a></td></tr>
+<tr><td></td><td valign="top"><a
href="gnun_002dclear_002dprevious.html#index-previous_002c-manipulating-PO-files">previous,
manipulating PO files</a>:</td><td> </td><td valign="top"><a
href="gnun_002dclear_002dprevious.html#gnun_002dclear_002dprevious">gnun-clear-previous</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Invoking-GNUN.html#index-priorities_002emk">priorities.mk</a>:</td><td> </td><td
valign="top"><a href="Invoking-GNUN.html#Invoking-GNUN">Invoking
GNUN</a></td></tr>
+<tr><td></td><td valign="top"><a
href="report.html#index-priorities_002emk-1">priorities.mk</a>:</td><td> </td><td
valign="top"><a href="report.html#report">report</a></td></tr>
+<tr><td></td><td valign="top"><a
href="PO-Files-and-Team.html#index-priorities_002emk-2">priorities.mk</a>:</td><td> </td><td
valign="top"><a href="PO-Files-and-Team.html#PO-Files-and-Team">PO Files and
Team</a></td></tr>
+<tr><td></td><td valign="top"><a
href="gnun_002dreport.html#index-priorities_002emk-3">priorities.mk</a>:</td><td> </td><td
valign="top"><a
href="gnun_002dreport.html#gnun_002dreport">gnun-report</a></td></tr>
+<tr><td></td><td valign="top"><a
href="PO-Files-and-Team.html#index-project-repository">project
repository</a>:</td><td> </td><td valign="top"><a
href="PO-Files-and-Team.html#PO-Files-and-Team">PO Files and Team</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-R">R</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="PO-Tips.html#index-recommendations_002c-PO-files">recommendations, PO
files</a>:</td><td> </td><td valign="top"><a
href="PO-Tips.html#PO-Tips">PO Tips</a></td></tr>
+<tr><td></td><td valign="top"><a
href="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="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>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-sanity-checks">sanity
checks</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="report.html#index-status_002c-translations">status,
translations</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-status_002c-translations-1">status,
translations</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="Runtime-Variables.html#index-Subversion">Subversion</a>:</td><td> </td><td
valign="top"><a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-SVN">SVN</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="sync.html#index-synchronization_002c-repository">synchronization,
repository</a>:</td><td> </td><td valign="top"><a
href="sync.html#sync">sync</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<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="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="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>
+<tr><td></td><td valign="top"><a
href="Main-Variables.html#index-TEMPLATE_005fLINGUAS">TEMPLATE_LINGUAS</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="PO-Tips.html#index-tips_002c-translators">tips,
translators</a>:</td><td> </td><td valign="top"><a
href="PO-Tips.html#PO-Tips">PO Tips</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Webmaster-Tips.html#index-tips_002c-webmasters">tips,
webmasters</a>:</td><td> </td><td valign="top"><a
href="Webmaster-Tips.html#Webmaster-Tips">Webmaster Tips</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Compendia.html#index-translation-memory">translation
memory</a>:</td><td> </td><td valign="top"><a
href="Compendia.html#Compendia">Compendia</a></td></tr>
+<tr><td></td><td valign="top"><a
href="New-Translation.html#index-translation_002c-new">translation,
new</a>:</td><td> </td><td valign="top"><a
href="New-Translation.html#New-Translation">New Translation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="New-Translation.html#index-translators_0027-credits">translators’
credits</a>:</td><td> </td><td valign="top"><a
href="New-Translation.html#New-Translation">New Translation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Credits-Slot.html#index-translators_0027-credits-1">translators’
credits</a>:</td><td> </td><td valign="top"><a
href="Credits-Slot.html#Credits-Slot">Credits Slot</a></td></tr>
+<tr><td></td><td valign="top"><a
href="New-Translation.html#index-translators_0027-notes">translators’
notes</a>:</td><td> </td><td valign="top"><a
href="New-Translation.html#New-Translation">New Translation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Notes-Slot.html#index-translators_0027-notes-1">translators’
notes</a>:</td><td> </td><td valign="top"><a
href="Notes-Slot.html#Notes-Slot">Notes Slot</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Invoking-GNUN.html#index-triggering_002c-build">triggering,
build</a>:</td><td> </td><td valign="top"><a
href="Invoking-GNUN.html#Invoking-GNUN">Invoking GNUN</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-V">V</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-VALIDATE">VALIDATE</a>:</td><td> </td><td
valign="top"><a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-validation">validation</a>:</td><td> </td><td
valign="top"><a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-validation-1">validation</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="validate_002dall.html#index-validation-2">validation</a>:</td><td> </td><td
valign="top"><a
href="validate_002dall.html#validate_002dall">validate-all</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Validation.html#index-validation-3">validation</a>:</td><td> </td><td
valign="top"><a href="Validation.html#Validation">Validation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="gnun_002dvalidate_002dhtml.html#index-validation_002c-HTML_002c-XHTML">validation,
HTML, XHTML</a>:</td><td> </td><td valign="top"><a
href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml">gnun-validate-html</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-variable_002c-behavior">variable,
behavior</a>:</td><td> </td><td valign="top"><a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-variable_002c-team">variable,
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="Runtime-Variables.html#index-variables">variables</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="Main-Variables.html#index-variables-1">variables</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="Runtime-Variables.html#index-VCS">VCS</a>:</td><td> </td><td
valign="top"><a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></td></tr>
+<tr><td></td><td valign="top"><a
href="Runtime-Variables.html#index-VERBOSE">VERBOSE</a>:</td><td> </td><td
valign="top"><a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-W">W</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="Webmaster-Tips.html#index-webmaster-tips">webmaster
tips</a>:</td><td> </td><td valign="top"><a
href="Webmaster-Tips.html#Webmaster-Tips">Webmaster Tips</a></td></tr>
+<tr><td></td><td valign="top"><a
href="GNU-News.html#index-whatsnew">whatsnew</a>:</td><td> </td><td
valign="top"><a href="GNU-News.html#GNU-News">GNU News</a></td></tr>
+<tr><td></td><td valign="top"><a
href="New-Translation.html#index-wrapping-long-lines">wrapping long
lines</a>:</td><td> </td><td valign="top"><a
href="New-Translation.html#New-Translation">New Translation</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+</table>
+<table><tr><th valign="top">Jump to: </th><td><a class="summary-letter"
href="#Index_cp_letter-A"><b>A</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-B"><b>B</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-C"><b>C</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-D"><b>D</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-E"><b>E</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-F"><b>F</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-G"><b>G</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-I"><b>I</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-L"><b>L</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-M"><b>M</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-N"><b>N</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-O"><b>O</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-P"><b>P</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-R"><b>R</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-S"><b>S</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-T"><b>T</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-V"><b>V</b></a>
+
+<a class="summary-letter" href="#Index_cp_letter-W"><b>W</b></a>
+
+</td></tr></table>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Copying-This-Manual.html#Copying-This-Manual" accesskey="n"
rel="next">Copying This Manual</a>, Previous: <a href="Bugs.html#Bugs"
accesskey="p" rel="previous">Bugs</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"
title="Index" rel="index">Index</a>]</p>
</div>
-<h2 class="unnumbered">Index</h2>
-<ul class="index-cp" compact>
-<li><a href="Main-Variables.html#index-ALL_005fDIRS-57">ALL_DIRS</a>: <a
href="Main-Variables.html#Main-Variables">Main Variables</a></li>
-<li><a href="Runtime-Variables.html#index-announce-22">announce</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a
href="Main-Variables.html#index-articles-in-root-directory_002c-defining-55">articles
in root directory, defining</a>: <a
href="Main-Variables.html#Main-Variables">Main Variables</a></li>
-<li><a href="Runtime-Variables.html#index-Bazaar-14">Bazaar</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a
href="Modifying-Boilerplates.html#index-boilerplates-101">boilerplates</a>: <a
href="Modifying-Boilerplates.html#Modifying-Boilerplates">Modifying
Boilerplates</a></li>
-<li><a href="Bugs.html#index-bugs_002c-reporting-117">bugs, reporting</a>: <a
href="Bugs.html#Bugs">Bugs</a></li>
-<li><a href="Runtime-Variables.html#index-bzr-15">bzr</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a
href="Comments-for-Translators.html#index-comments-for-translators-100">comments
for translators</a>: <a
href="Comments-for-Translators.html#Comments-for-Translators">Comments for
Translators</a></li>
-<li><a href="Compendia.html#index-compendia-93">compendia</a>: <a
href="Compendia.html#Compendia">Compendia</a></li>
-<li><a href="Compendia.html#index-compendium_002epot-96">compendium.pot</a>:
<a href="Compendia.html#Compendia">Compendia</a></li>
-<li><a href="Invoking-GNUN.html#index-config_002emk-5">config.mk</a>: <a
href="Invoking-GNUN.html#Invoking-GNUN">Invoking GNUN</a></li>
-<li><a
href="Splitting-Long-Passages.html#index-conventional-separator-for-strings-104">conventional
separator for strings</a>: <a
href="Splitting-Long-Passages.html#Splitting-Long-Passages">Splitting Long
Passages</a></li>
-<li><a
href="gnun_002dmerge_002dpreconverted.html#index-conversion-of-existing-translations-113">conversion
of existing translations</a>: <a
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a></li>
-<li><a
href="gnun_002dpreconvert.html#index-conversion-of-existing-translations-111">conversion
of existing translations</a>: <a
href="gnun_002dpreconvert.html#gnun_002dpreconvert">gnun-preconvert</a></li>
-<li><a
href="Migrating.html#index-conversion-of-existing-translations-77">conversion
of existing translations</a>: <a
href="Migrating.html#Migrating">Migrating</a></li>
-<li><a href="Credits-Slot.html#index-credits_002c-translators-74">credits,
translators</a>: <a href="Credits-Slot.html#Credits-Slot">Credits Slot</a></li>
-<li><a href="New-Translation.html#index-credits_002c-translators-68">credits,
translators</a>: <a href="New-Translation.html#New-Translation">New
Translation</a></li>
-<li><a
href="GNUmakefile_002eteam-and-Cron.html#index-cron_002c-team-maintenance-92">cron,
team maintenance</a>: <a
href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron">GNUmakefile.team
and Cron</a></li>
-<li><a href="Runtime-Variables.html#index-CVS-11">CVS</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a
href="Runtime-Variables.html#index-deferred-generation-of-articles-28">deferred
generation of articles</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a
href="Main-Variables.html#index-defining-articles-in-the-root-dir-56">defining
articles in the root dir</a>: <a href="Main-Variables.html#Main-Variables">Main
Variables</a></li>
-<li><a href="Main-Variables.html#index-defining-directories-59">defining
directories</a>: <a href="Main-Variables.html#Main-Variables">Main
Variables</a></li>
-<li><a href="Main-Variables.html#index-defining-homepage-53">defining
homepage</a>: <a href="Main-Variables.html#Main-Variables">Main
Variables</a></li>
-<li><a href="Main-Variables.html#index-defining-templates-42">defining
templates</a>: <a href="Main-Variables.html#Main-Variables">Main
Variables</a></li>
-<li><a
href="Main-Variables.html#index-directories_002c-defining-58">directories,
defining</a>: <a href="Main-Variables.html#Main-Variables">Main
Variables</a></li>
-<li><a href="Compendia.html#index-exclude_002epot-95">exclude.pot</a>: <a
href="Compendia.html#Compendia">Compendia</a></li>
-<li><a
href="Main-Variables.html#index-extra_002dtemplates-43">extra-templates</a>: <a
href="Main-Variables.html#Main-Variables">Main Variables</a></li>
-<li><a href="Runtime-Variables.html#index-fuzzy-strings-26">fuzzy strings</a>:
<a href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a
href="Main-Variables.html#index-FUZZY_005fDIFF_005fLINGUAS-49">FUZZY_DIFF_LINGUAS</a>:
<a href="Main-Variables.html#Main-Variables">Main Variables</a></li>
-<li><a
href="make_002dprototype.html#index-generation_002c-POT_002c-_002eproto-107">generation,
POT, .proto</a>: <a
href="make_002dprototype.html#make_002dprototype">make-prototype</a></li>
-<li><a
href="generic_002eLANG_002ehtml.html#index-generic-notice_002c-translations-84">generic
notice, translations</a>: <a
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml">generic.LANG.html</a></li>
-<li><a href="Invoking-GNUN.html#index-GNUmakefile-4">GNUmakefile</a>: <a
href="Invoking-GNUN.html#Invoking-GNUN">Invoking GNUN</a></li>
-<li><a
href="PO-Files-and-Team.html#index-GNUmakefile_002eteam-88">GNUmakefile.team</a>:
<a href="PO-Files-and-Team.html#PO-Files-and-Team">PO Files and Team</a></li>
-<li><a href="Main-Variables.html#index-gnun_002emk-39">gnun.mk</a>: <a
href="Main-Variables.html#Main-Variables">Main Variables</a></li>
-<li><a href="Invoking-GNUN.html#index-gnun_002emk-6">gnun.mk</a>: <a
href="Invoking-GNUN.html#Invoking-GNUN">Invoking GNUN</a></li>
-<li><a href="GNU-News.html#index-gnunews-78">gnunews</a>: <a
href="GNU-News.html#GNU-News">GNU News</a></li>
-<li><a href="GNU-News.html#index-gnusflashes-80">gnusflashes</a>: <a
href="GNU-News.html#GNU-News">GNU News</a></li>
-<li><a href="Runtime-Variables.html#index-GRACE-25">GRACE</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="Runtime-Variables.html#index-grace-period-27">grace period</a>:
<a href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="Main-Variables.html#index-HOME_005fLINGUAS-51">HOME_LINGUAS</a>:
<a href="Main-Variables.html#Main-Variables">Main Variables</a></li>
-<li><a href="Main-Variables.html#index-homepage_002c-defining-52">homepage,
defining</a>: <a href="Main-Variables.html#Main-Variables">Main
Variables</a></li>
-<li><a
href="gnun_002dinit_002dpo.html#index-initializing_002c-translations-109">initializing,
translations</a>: <a
href="gnun_002dinit_002dpo.html#gnun_002dinit_002dpo">gnun-init-po</a></li>
-<li><a href="Invoking-GNUN.html#index-invocation-2">invocation</a>: <a
href="Invoking-GNUN.html#Invoking-GNUN">Invoking GNUN</a></li>
-<li><a href="Invoking-GNUN.html#index-invoking-1">invoking</a>: <a
href="Invoking-GNUN.html#Invoking-GNUN">Invoking GNUN</a></li>
-<li><a href="Localized-URLs.html#index-localized-URLs-102">localized URLs</a>:
<a href="Localized-URLs.html#Localized-URLs">Localized URLs</a></li>
-<li><a href="New-Translation.html#index-long-lines_002c-wrap-71">long lines,
wrap</a>: <a href="New-Translation.html#New-Translation">New
Translation</a></li>
-<li><a
href="Splitting-Long-Passages.html#index-long-passages_002c-avoiding-103">long
passages, avoiding</a>: <a
href="Splitting-Long-Passages.html#Splitting-Long-Passages">Splitting Long
Passages</a></li>
-<li><a href="mailfail.html#index-mail_002c-notifications-115">mail,
notifications</a>: <a href="mailfail.html#mailfail">mailfail</a></li>
-<li><a href="Runtime-Variables.html#index-mail_002c-notifications-20">mail,
notifications</a>: <a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></li>
-<li><a
href="gnun_002dmerge_002dpreconverted.html#index-migration_002c-translations-112">migration,
translations</a>: <a
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a></li>
-<li><a
href="gnun_002dpreconvert.html#index-migration_002c-translations-110">migration,
translations</a>: <a
href="gnun_002dpreconvert.html#gnun_002dpreconvert">gnun-preconvert</a></li>
-<li><a href="Migrating.html#index-migration_002c-translations-76">migration,
translations</a>: <a href="Migrating.html#Migrating">Migrating</a></li>
-<li><a href="New-Translation.html#index-new-translation-64">new
translation</a>: <a href="New-Translation.html#New-Translation">New
Translation</a></li>
-<li><a
href="Runtime-Variables.html#index-new-translations_002c-notifications_002fannouncements-21">new
translations, notifications/announcements</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="Notes-Slot.html#index-notes_002c-translators-72">notes,
translators</a>: <a href="Notes-Slot.html#Notes-Slot">Notes Slot</a></li>
-<li><a href="New-Translation.html#index-notes_002c-translators-66">notes,
translators</a>: <a href="New-Translation.html#New-Translation">New
Translation</a></li>
-<li><a href="Runtime-Variables.html#index-NOTIFY-19">NOTIFY</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a
href="Main-Variables.html#index-optional_002dtemplates-46">optional-templates</a>:
<a href="Main-Variables.html#Main-Variables">Main Variables</a></li>
-<li><a
href="Runtime-Variables.html#index-OUTDATED_002dGRACE-29">OUTDATED-GRACE</a>:
<a href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="Runtime-Variables.html#index-output_002c-detailed-24">output,
detailed</a>: <a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></li>
-<li><a href="PO-Files.html#index-PO-editors-62">PO editors</a>: <a
href="PO-Files.html#PO-Files">PO Files</a></li>
-<li><a href="New-Translation.html#index-PO-headers-65">PO headers</a>: <a
href="New-Translation.html#New-Translation">New Translation</a></li>
-<li><a href="PO-Files.html#index-PO_002c-editing-61">PO, editing</a>: <a
href="PO-Files.html#PO-Files">PO Files</a></li>
-<li><a href="make_002dprototype.html#index-POT-generation-105">POT
generation</a>: <a
href="make_002dprototype.html#make_002dprototype">make-prototype</a></li>
-<li><a href="Main-Variables.html#index-POT-generation_002c-articles-60">POT
generation, articles</a>: <a href="Main-Variables.html#Main-Variables">Main
Variables</a></li>
-<li><a
href="gnun_002dadd_002dfuzzy_002ddiff.html#index-previous_002c-diff-108">previous,
diff</a>: <a
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff">gnun-add-fuzzy-diff</a></li>
-<li><a href="Main-Variables.html#index-previous_002c-diff-50">previous,
diff</a>: <a href="Main-Variables.html#Main-Variables">Main Variables</a></li>
-<li><a
href="gnun_002dclear_002dprevious.html#index-previous_002c-manipulating-PO-files-116">previous,
manipulating PO files</a>: <a
href="gnun_002dclear_002dprevious.html#gnun_002dclear_002dprevious">gnun-clear-previous</a></li>
-<li><a
href="PO-Files-and-Team.html#index-priorities_002emk-90">priorities.mk</a>: <a
href="PO-Files-and-Team.html#PO-Files-and-Team">PO Files and Team</a></li>
-<li><a href="report.html#index-priorities_002emk-36">priorities.mk</a>: <a
href="report.html#report">report</a></li>
-<li><a href="Invoking-GNUN.html#index-priorities_002emk-7">priorities.mk</a>:
<a href="Invoking-GNUN.html#Invoking-GNUN">Invoking GNUN</a></li>
-<li><a href="PO-Files-and-Team.html#index-project-repository-85">project
repository</a>: <a href="PO-Files-and-Team.html#PO-Files-and-Team">PO Files and
Team</a></li>
-<li><a href="make_002dprototype.html#index-prototype-generation-106">prototype
generation</a>: <a
href="make_002dprototype.html#make_002dprototype">make-prototype</a></li>
-<li><a
href="PO-Tips.html#index-recommendations_002c-PO-files-82">recommendations, PO
files</a>: <a href="PO-Tips.html#PO-Tips">PO Tips</a></li>
-<li><a href="report.html#index-reporting-34">reporting</a>: <a
href="report.html#report">report</a></li>
-<li><a href="Bugs.html#index-reporting-bugs-118">reporting bugs</a>: <a
href="Bugs.html#Bugs">Bugs</a></li>
-<li><a
href="PO-Files-and-Team.html#index-repository_002c-translation-project-86">repository,
translation project</a>: <a href="PO-Files-and-Team.html#PO-Files-and-Team">PO
Files and Team</a></li>
-<li><a href="Main-Variables.html#index-ROOT-54">ROOT</a>: <a
href="Main-Variables.html#Main-Variables">Main Variables</a></li>
-<li><a href="Runtime-Variables.html#index-sanity-checks-18">sanity checks</a>:
<a href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="report.html#index-status_002c-translations-35">status,
translations</a>: <a href="report.html#report">report</a></li>
-<li><a href="Runtime-Variables.html#index-Subversion-12">Subversion</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="Runtime-Variables.html#index-SVN-13">SVN</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a
href="sync.html#index-synchronization_002c-repository-33">synchronization,
repository</a>: <a href="sync.html#sync">sync</a></li>
-<li><a href="Runtime-Variables.html#index-TEAM-30">TEAM</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="generic_002eLANG_002ehtml.html#index-team-information-83">team
information</a>: <a
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml">generic.LANG.html</a></li>
-<li><a href="PO-Files-and-Team.html#index-team-maintenance-87">team
maintenance</a>: <a href="PO-Files-and-Team.html#PO-Files-and-Team">PO Files
and Team</a></li>
-<li><a
href="GNUmakefile_002eteam-and-Cron.html#index-team-maintenance_002c-cron-91">team
maintenance, cron</a>: <a
href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron">GNUmakefile.team
and Cron</a></li>
-<li><a href="PO-Files-and-Team.html#index-team-workflow-89">team workflow</a>:
<a href="PO-Files-and-Team.html#PO-Files-and-Team">PO Files and Team</a></li>
-<li><a
href="Main-Variables.html#index-TEMPLATE_005fLINGUAS-40">TEMPLATE_LINGUAS</a>:
<a href="Main-Variables.html#Main-Variables">Main Variables</a></li>
-<li><a
href="Main-Variables.html#index-templates_002c-additional-44">templates,
additional</a>: <a href="Main-Variables.html#Main-Variables">Main
Variables</a></li>
-<li><a href="Main-Variables.html#index-templates_002c-defining-41">templates,
defining</a>: <a href="Main-Variables.html#Main-Variables">Main
Variables</a></li>
-<li><a href="Main-Variables.html#index-templates_002c-optional-47">templates,
optional</a>: <a href="Main-Variables.html#Main-Variables">Main
Variables</a></li>
-<li><a href="PO-Tips.html#index-tips_002c-translators-81">tips,
translators</a>: <a href="PO-Tips.html#PO-Tips">PO Tips</a></li>
-<li><a href="Webmaster-Tips.html#index-tips_002c-webmasters-97">tips,
webmasters</a>: <a href="Webmaster-Tips.html#Webmaster-Tips">Webmaster
Tips</a></li>
-<li><a href="Compendia.html#index-translation-memory-94">translation
memory</a>: <a href="Compendia.html#Compendia">Compendia</a></li>
-<li><a href="New-Translation.html#index-translation_002c-new-63">translation,
new</a>: <a href="New-Translation.html#New-Translation">New Translation</a></li>
-<li><a href="Credits-Slot.html#index-translators_0027-credits-75">translators'
credits</a>: <a href="Credits-Slot.html#Credits-Slot">Credits Slot</a></li>
-<li><a
href="New-Translation.html#index-translators_0027-credits-69">translators'
credits</a>: <a href="New-Translation.html#New-Translation">New
Translation</a></li>
-<li><a href="Notes-Slot.html#index-translators_0027-notes-73">translators'
notes</a>: <a href="Notes-Slot.html#Notes-Slot">Notes Slot</a></li>
-<li><a
href="New-Translation.html#index-translators_0027-notes-67">translators'
notes</a>: <a href="New-Translation.html#New-Translation">New
Translation</a></li>
-<li><a href="Invoking-GNUN.html#index-triggering_002c-build-3">triggering,
build</a>: <a href="Invoking-GNUN.html#Invoking-GNUN">Invoking GNUN</a></li>
-<li><a href="Runtime-Variables.html#index-VALIDATE-16">VALIDATE</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="Validation.html#index-validation-99">validation</a>: <a
href="Validation.html#Validation">Validation</a></li>
-<li><a href="validate_002dall.html#index-validation-37">validation</a>: <a
href="validate_002dall.html#validate_002dall">validate-all</a></li>
-<li><a href="Runtime-Variables.html#index-validation-17">validation</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a
href="gnun_002dvalidate_002dhtml.html#index-validation_002c-HTML_002c-XHTML-114">validation,
HTML, XHTML</a>: <a
href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml">gnun-validate-html</a></li>
-<li><a href="Runtime-Variables.html#index-variable_002c-behavior-9">variable,
behavior</a>: <a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></li>
-<li><a href="Runtime-Variables.html#index-variable_002c-team-31">variable,
team</a>: <a href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a></li>
-<li><a href="Main-Variables.html#index-variables-38">variables</a>: <a
href="Main-Variables.html#Main-Variables">Main Variables</a></li>
-<li><a href="Runtime-Variables.html#index-variables-8">variables</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="Runtime-Variables.html#index-VCS-10">VCS</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="Runtime-Variables.html#index-VERBOSE-23">VERBOSE</a>: <a
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a></li>
-<li><a href="Webmaster-Tips.html#index-webmaster-tips-98">webmaster tips</a>:
<a href="Webmaster-Tips.html#Webmaster-Tips">Webmaster Tips</a></li>
-<li><a href="GNU-News.html#index-whatsnew-79">whatsnew</a>: <a
href="GNU-News.html#GNU-News">GNU News</a></li>
-<li><a href="New-Translation.html#index-wrapping-long-lines-70">wrapping long
lines</a>: <a href="New-Translation.html#New-Translation">New
Translation</a></li>
- </ul></body></html>
+</body>
+</html>
Index: gnun/html_node/Internals.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Internals.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Internals.html 26 Sep 2012 14:49:42 -0000 1.15
+++ gnun/html_node/Internals.html 4 Dec 2012 16:24:22 -0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Internals - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Usage.html#Usage" title="Usage">
-<link rel="next" href="Bugs.html#Bugs" title="Bugs">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,47 +9,84 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Internals</title>
+
+<meta name="description" content="GNUnited Nations: Internals">
+<meta name="keywords" content="GNUnited Nations: Internals">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Scripts.html#Scripts" rel="next" title="Scripts">
+<link href="Splitting-Long-Passages.html#Splitting-Long-Passages"
rel="previous" title="Splitting Long Passages">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Internals"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="Bugs.html#Bugs">Bugs</a>,
-Previous: <a rel="previous" accesskey="p"
href="Usage.html#Usage">Usage</a>,
-Up: <a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+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>
</div>
-
-<h2 class="chapter">3 Unexciting Information for GNUN's Operation</h2>
+<hr>
+<a name="Unexciting-Information-for-GNUN_0027s-Operation"></a>
+<h2 class="chapter">3 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
front-end, except the section about scripts that includes descriptions
of programs that may also be useful for the translators.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="Scripts.html#Scripts"
accesskey="1">Scripts</a>:</td><td> </td><td align="left"
valign="top">Helper scripts.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="Rules.html#Rules"
accesskey="2">Rules</a>:</td><td> </td><td align="left"
valign="top">The knotty rules explained.
+</td></tr>
+</table>
+
-<ul class="menu">
-<li><a accesskey="1" href="Scripts.html#Scripts">Scripts</a>: Helper
scripts.
-<li><a accesskey="2" href="Rules.html#Rules">Rules</a>: The knotty
rules explained.
-</ul>
- </body></html>
+</body>
+</html>
Index: gnun/html_node/Introduction.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Introduction.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Introduction.html 26 Sep 2012 14:49:42 -0000 1.15
+++ gnun/html_node/Introduction.html 4 Dec 2012 16:24:22 -0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Introduction - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="index.html#Top" title="Top">
-<link rel="next" href="Usage.html#Usage" title="Usage">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,71 +9,115 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Introduction</title>
+
+<meta name="description" content="GNUnited Nations: Introduction">
+<meta name="keywords" content="GNUnited Nations: Introduction">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Overview.html#Overview" rel="next" title="Overview">
+<link href="index.html#Top" rel="previous" title="Top">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Introduction"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="Usage.html#Usage">Usage</a>,
-Previous: <a rel="previous" accesskey="p" href="index.html#Top">Top</a>,
-Up: <a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Usage.html#Usage" accesskey="n" rel="next">Usage</a>, Previous:
<a href="index.html#Top" accesskey="p" rel="previous">Top</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="Introduction-to-GNUnited-Nations"></a>
<h2 class="chapter">1 Introduction to GNUnited Nations</h2>
<p>GNUnited Nations (abbreviated GNUN) is a collection of makefiles and
scripts that are supposed to make the life of <a
href="http://gnu.org";>http://gnu.org</a>
translators easier. Although it is specifically developed for the GNU
-Project's website, it could be customized, at least in theory, to fit
+Project’s website, it could be customized, at least in theory, to fit
the needs of other internationalized sites. GNUN is in early stage of
development, but if it proves useful, and if there is sufficient
interest (and time), it is possible to develop a robust configuration
interface that would be appropriate for general usage.
-
- <p>It is vitally important to understand that GNUN is <em>not</em> a silver
+</p>
+<p>It is vitally important to understand that GNUN is <em>not</em> a silver
bullet that solves all problems. If we have to be honest, deploying
GNUN in fact even does create some (see <a
href="Disadvantages.html#Disadvantages">Disadvantages</a>).
-
- <p>GNUnited Nations is free software, available under the GNU General
+</p>
+<p>GNUnited Nations is free software, available under the GNU General
Public License.
-
- <p>This manual is organized in way that is suitable both for translators
+</p>
+<p>This manual is organized in way that is suitable both for translators
and GNU Web Translation managers (plus eventually interested GNU
Webmasters, if any). It may also serve as an introductory material and
reference for new GNUN developers and contributors. Hopefully, it might
be useful to people who customize and adopt the software for a third
party site or for their own needs. Feel free to skip sections or entire
chapters if they are irrelevant for your intended usage.
-
- <p>This manual is free documentation, and you can modify and redistribute
+</p>
+<p>This manual is free documentation, and you can modify and redistribute
it under the terms of the GNU Free Documentation License. See <a
href="Copying-This-Manual.html#Copying-This-Manual">GNU Free Documentation
License</a>.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="Overview.html#Overview"
accesskey="1">Overview</a>:</td><td> </td><td align="left"
valign="top">What is GNUN and why is necessary?
+</td></tr>
+<tr><td align="left" valign="top">• <a href="Concepts.html#Concepts"
accesskey="2">Concepts</a>:</td><td> </td><td align="left"
valign="top">Basic concepts and goals.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="Advantages.html#Advantages"
accesskey="3">Advantages</a>:</td><td> </td><td align="left"
valign="top">The goodness GNUN brings.
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Disadvantages.html#Disadvantages"
accesskey="4">Disadvantages</a>:</td><td> </td><td align="left"
valign="top">Staying on firm ground.
+</td></tr>
+</table>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Usage.html#Usage" accesskey="n" rel="next">Usage</a>, Previous:
<a href="index.html#Top" accesskey="p" rel="previous">Top</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>
-<ul class="menu">
-<li><a accesskey="1" href="Overview.html#Overview">Overview</a>:
What is GNUN and why is necessary?
-<li><a accesskey="2" href="Concepts.html#Concepts">Concepts</a>:
Basic concepts and goals.
-<li><a accesskey="3" href="Advantages.html#Advantages">Advantages</a>:
The goodness GNUN brings.
-<li><a accesskey="4"
href="Disadvantages.html#Disadvantages">Disadvantages</a>: Staying on
firm ground.
-</ul>
- </body></html>
+</body>
+</html>
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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Invoking-GNUN.html 26 Sep 2012 14:49:43 -0000 1.15
+++ gnun/html_node/Invoking-GNUN.html 4 Dec 2012 16:24:22 -0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Invoking GNUN - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Usage.html#Usage" title="Usage">
-<link rel="next" href="Main-Variables.html#Main-Variables" title="Main
Variables">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,86 +9,137 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Invoking GNUN</title>
+
+<meta name="description" content="GNUnited Nations: Invoking GNUN">
+<meta name="keywords" content="GNUnited Nations: Invoking GNUN">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Usage.html#Usage" rel="up" title="Usage">
+<link href="Runtime-Variables.html#Runtime-Variables" rel="next"
title="Runtime Variables">
+<link href="Usage.html#Usage" rel="previous" title="Usage">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Invoking-GNUN"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Main-Variables.html#Main-Variables">Main Variables</a>,
-Up: <a rel="up" accesskey="u" href="Usage.html#Usage">Usage</a>
-<hr>
+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>
</div>
-
+<hr>
+<a name="Invoking-GNUN-1"></a>
<h3 class="section">2.1 Invoking GNUN</h3>
+<a name="index-invoking"></a>
+<a name="index-invocation"></a>
+<a name="index-triggering_002c-build"></a>
+<a name="index-GNUmakefile"></a>
-<p><a name="index-invoking-1"></a><a name="index-invocation-2"></a><a
name="index-triggering_002c-build-3"></a><a name="index-GNUmakefile-4"></a>
-The central part of GNUnited Nations is a makefile; actually a
-<samp><span class="file">GNUmakefile</span></samp> since it heavily relies on
features and extensions
+<p>The central part of GNUnited Nations is a makefile; actually a
+<samp>GNUmakefile</samp> since it heavily relies on features and extensions
available in GNU Make. Thus, invoking a build consists of typing
-<samp><span class="command">make</span></samp> on the command line, or within
cron. If you are
+<code>make</code> on the command line, or within cron. If you are
deploying the software on a non-GNU machine, probably GNU Make is
-installed and available as <samp><span class="command">gmake</span></samp> or
<samp><span class="command">gnumake</span></samp>. If
+installed and available as <code>gmake</code> or <code>gnumake</code>. If
not, you should consider installing it, since the build will fail
otherwise. See <a
href="http://www.gnu.org/software/make";>http://www.gnu.org/software/make</a>
for information
how to download and install GNU Make.
-
- <p>If you don't specify a target, <samp><span
class="command">make</span></samp> by default builds the
+</p>
+<p>If you don’t specify a target, <code>make</code> by default builds the
target <code>all</code>, which in this case is to rebuild all translations
that are not up-to-date. However, there are special targets that do not
depend on the standard <code>all</code> target, which can be built by
-<code>make </code><var>target</var>. Some of the variables in the next section
+<code>make <var>target</var></code>. Some of the variables in the next section
apply to them, and some do not.
-
- <p><a name="index-config_002emk-5"></a><a name="index-gnun_002emk-6"></a><a
name="index-priorities_002emk-7"></a>Note that GNUN expects <samp><span
class="file">GNUmakefile</span></samp>, <samp><span
class="file">config.mk</span></samp> and
-<samp><span class="file">gnun.mk</span></samp> to be <em>present</em> under
<samp><span class="file">server/gnun</span></samp> of the
-`www' web repository, otherwise <samp><span class="command">make</span></samp>
has no way to know what
-and how should be built. Another file, <samp><span
class="file">priorities.mk</span></samp>, is
-expected to be present under <samp><span
class="file">server/gnun</span></samp> in order to define
+</p>
+<a name="index-config_002emk"></a>
+<a name="index-gnun_002emk"></a>
+<a name="index-priorities_002emk"></a>
+<p>Note that GNUN expects <samp>GNUmakefile</samp>, <samp>config.mk</samp> and
+<samp>gnun.mk</samp> to be <em>present</em> under <samp>server/gnun</samp> of
the
+‘www’ web repository, otherwise <code>make</code> has no way to
know what
+and how should be built. Another file, <samp>priorities.mk</samp>, is
+expected to be present under <samp>server/gnun</samp> in order to define
the priorities when reporting about the outdated translations. If
absent, the <code>report</code> target will not sort the translations by
priority. Since the location of the repository working
copy is strictly user-specific and cannot be determined in any way,
-<samp><span class="file">GNUmakefile</span></samp> and <samp><span
class="file">config.mk</span></samp> must be copied there manually
+<samp>GNUmakefile</samp> and <samp>config.mk</samp> must be copied there
manually
after the package installation. For convenience, these files are
-installed in ‘<samp><span
class="samp">$(pkgdatadadir)</span></samp>’ (<samp><span
class="file">/usr/local/share/gnun</span></samp> with
-the default ‘<samp><span class="samp">prefix</span></samp>’) so
you can just create symlinks pointing to
+installed in ‘<samp>$(pkgdatadadir)</samp>’
(<samp>/usr/local/share/gnun</samp> with
+the default ‘<samp>prefix</samp>’) so you can just create symlinks
pointing to
them, e.g.:
+</p>
+<div class="example">
+<pre class="example">ln -s /usr/local/share/gnun/config.mk
/path/to/www/server/gnun/
+ln -s /usr/local/share/gnun/GNUmakefile /path/to/www/server/gnun/
+</pre></div>
-<pre class="example"> ln -s /usr/local/share/gnun/config.mk
/path/to/www/server/gnun/
- ln -s /usr/local/share/gnun/GNUmakefile /path/to/www/server/gnun/
-</pre>
- <p>If next GNUN releases are installed with the same <samp><span
class="option">--prefix</span></samp>, you
+<p>If next GNUN releases are installed with the same <samp>--prefix</samp>, you
will always use the latest versions without the need for any manual
intervention.
-
- <p>If you are playing with non-gnu.org setup, you also have to take care of
-<samp><span class="file">gnun.mk</span></samp> and put a modified version
under <samp><span class="file">server/gnun</span></samp> of
+</p>
+<p>If you are playing with non-gnu.org setup, you also have to take care of
+<samp>gnun.mk</samp> and put a modified version under <samp>server/gnun</samp>
of
your hypothetical tree. (For gnu.org, that is not necessary since
-a proper <samp><span class="file">gnun.mk</span></samp> is maintained in
`www'.)
+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>
+</div>
-<ul class="menu">
-<li><a accesskey="1" href="Runtime-Variables.html#Runtime-Variables">Runtime
Variables</a>: Variables to control the build process.
-<li><a accesskey="2" href="Special-Targets.html#Special-Targets">Special
Targets</a>: Targets that are not built by default.
-</ul>
- </body></html>
+</body>
+</html>
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.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- gnun/html_node/Localized-URLs.html 26 Sep 2012 14:49:43 -0000 1.5
+++ gnun/html_node/Localized-URLs.html 4 Dec 2012 16:24:22 -0000 1.6
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>Localized URLs - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Webmaster-Tips.html#Webmaster-Tips" title="Webmaster
Tips">
-<link rel="prev" href="Modifying-Boilerplates.html#Modifying-Boilerplates"
title="Modifying Boilerplates">
-<link rel="next" href="Splitting-Long-Passages.html#Splitting-Long-Passages"
title="Splitting Long Passages">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,65 +9,102 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Localized URLs</title>
+
+<meta name="description" content="GNUnited Nations: Localized URLs">
+<meta name="keywords" content="GNUnited Nations: Localized URLs">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Webmaster-Tips.html#Webmaster-Tips" rel="up" title="Webmaster
Tips">
+<link href="Splitting-Long-Passages.html#Splitting-Long-Passages" rel="next"
title="Splitting Long Passages">
+<link href="Modifying-Boilerplates.html#Modifying-Boilerplates" rel="previous"
title="Modifying Boilerplates">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Localized-URLs"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Splitting-Long-Passages.html#Splitting-Long-Passages">Splitting Long
Passages</a>,
-Previous: <a rel="previous" accesskey="p"
href="Modifying-Boilerplates.html#Modifying-Boilerplates">Modifying
Boilerplates</a>,
-Up: <a rel="up" accesskey="u"
href="Webmaster-Tips.html#Webmaster-Tips">Webmaster Tips</a>
-<hr>
+Next: <a href="Splitting-Long-Passages.html#Splitting-Long-Passages"
accesskey="n" rel="next">Splitting Long Passages</a>, Previous: <a
href="Modifying-Boilerplates.html#Modifying-Boilerplates" accesskey="p"
rel="previous">Modifying Boilerplates</a>, Up: <a
href="Webmaster-Tips.html#Webmaster-Tips" accesskey="u" rel="up">Webmaster
Tips</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="Localized-URLs-1"></a>
<h4 class="subsection">2.4.4 Localized URLs</h4>
+<a name="index-localized-URLs"></a>
-<p><a name="index-localized-URLs-102"></a>
-Some articles may contain diagrams or other images with English text
+<p>Some articles may contain diagrams or other images with English text
that can and should be translated. In order to make the translated
versions appear in the respective translations, GNUN should be told
what URLs need localization. It can be done with HTML comments like
-
-<pre class="example"> <!-- GNUN: localize URL /philosophy/category.png,
+</p>
+<div class="example">
+<pre class="example"><!-- GNUN: localize URL /philosophy/category.png,
/licenses/template-diagram.png and /graphics/jesus-cartoon.jpg -->
-</pre>
- <p>The URLs are separated with spaces. One trailing comma at the end of
-every word is removed if present. Words without a dot, such as `and',
-do not count as URLs; they are ignored.
-
- <p>Such comments will be extracted nightly and compiled into per-article
-lists of URLs in <samp><span class="file">localized-urls.mk</span></samp>.
+</pre></div>
- <p>After every build GNUN will check if the respective
-<samp><span class="file">philosophy/category.</span><var>lang</var><span
class="file">.png</span></samp> and other files are present in
+<p>The URLs are separated with spaces. One trailing comma at the end of
+every word is removed if present. Words without a dot, such as
‘and’,
+do not count as URLs; they are ignored.
+</p>
+<p>Such comments will be extracted nightly and compiled into per-article
+lists of URLs in <samp>localized-urls.mk</samp>.
+</p>
+<p>After every build GNUN will check if the respective
+<samp>philosophy/category.<var>lang</var>.png</samp> and other files are
present in
the working copy and substitute the strings in the HTML file of the
translation.
-
- <p>GNUN relies on URLs being absolute, starting from the root homepage
+</p>
+<p>GNUN relies on URLs being absolute, starting from the root directory
as required in
<a
href="http://www.gnu.org/server/fsf-html-style-sheet.html#FilenameAndURLGuidelines";>http://www.gnu.org/server/fsf-html-style-sheet.html#FilenameAndURLGuidelines</a>.
-
- <p>And please don't forget to commit the image in its source form
+</p>
+<p>And please don’t forget to commit the image in its source form
(typically, in SVG format).
+</p>
+
- </body></html>
+</body>
+</html>
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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Main-Variables.html 26 Sep 2012 14:49:43 -0000 1.15
+++ gnun/html_node/Main-Variables.html 4 Dec 2012 16:24:22 -0000 1.16
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>Main Variables - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Usage.html#Usage" title="Usage">
-<link rel="prev" href="Invoking-GNUN.html#Invoking-GNUN" title="Invoking GNUN">
-<link rel="next" href="PO-Files.html#PO-Files" title="PO Files">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,136 +9,196 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Main Variables</title>
+
+<meta name="description" content="GNUnited Nations: Main Variables">
+<meta name="keywords" content="GNUnited Nations: Main Variables">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Usage.html#Usage" rel="up" title="Usage">
+<link href="PO-Files.html#PO-Files" rel="next" title="PO Files">
+<link href="validate_002dall.html#validate_002dall" rel="previous"
title="validate-all">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Main-Variables"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="PO-Files.html#PO-Files">PO
Files</a>,
-Previous: <a rel="previous" accesskey="p"
href="Invoking-GNUN.html#Invoking-GNUN">Invoking GNUN</a>,
-Up: <a rel="up" accesskey="u" href="Usage.html#Usage">Usage</a>
-<hr>
+Next: <a href="PO-Files.html#PO-Files" accesskey="n" rel="next">PO Files</a>,
Previous: <a href="Invoking-GNUN.html#Invoking-GNUN" accesskey="p"
rel="previous">Invoking GNUN</a>, Up: <a href="Usage.html#Usage" accesskey="u"
rel="up">Usage</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-
+<hr>
+<a name="Defining-Articles-to-be-Built"></a>
<h3 class="section">2.2 Defining Articles to be Built</h3>
+<a name="index-variables-1"></a>
+<a name="index-gnun_002emk-1"></a>
-<p><a name="index-variables-38"></a><a name="index-gnun_002emk-39"></a>
-The file <samp><span class="file">gnun.mk</span></samp> contains variable
definitions, based on which
+<p>The file <samp>gnun.mk</samp> contains variable definitions, based on which
almost all other important variables are computed. In other words,
the variables defined in that file directly affect the overall
behavior of the build process.
-
- <p>There are two types of variables, which are specifically separated in
-order to make translators' life easier: variables that translators are
+</p>
+<p>There are two types of variables, which are specifically separated in
+order to make translators’ life easier: variables that translators are
free to modify and variables that are modified by the web-translators
-staff<a rel="footnote" href="#fn-1" name="fnd-1"><sup>1</sup></a>, ideally
after performing some local tests. A
+staff<a name="DOCF4" href="#FOOT4"><sup>4</sup></a>, ideally after performing
some local tests. A
translation team leader should update only <code>FUZZY_DIFF_LINGUAS</code>,
-<code>TEMPLATE_LINGUAS</code> and
-<code>HOME_LINGUAS</code>; everything else is supposed to be built
+<code>TEMPLATE_LINGUAS</code>; everything else is supposed to be built
automagically, without manual intervention. If not, that is a bug that
should be reported and fixed.
-
-
-<a name="index-TEMPLATE_005fLINGUAS-40"></a>
-<a name="index-templates_002c-defining-41"></a>
-<a name="index-defining-templates-42"></a>
-<dl><dt>‘<samp><span
class="samp">TEMPLATE_LINGUAS</span></samp>’<dd>A space-separated list
with languages. Add here your language code
+</p>
+<dl compact="compact">
+<dd><a name="index-TEMPLATE_005fLINGUAS"></a>
+<a name="index-templates_002c-defining"></a>
+<a name="index-defining-templates"></a>
+</dd>
+<dt>‘<samp>TEMPLATE_LINGUAS</samp>’</dt>
+<dd><p>A space-separated list with languages. Add here your language code
<em>if and only if</em> you have all the SSI templates translated, and
-have already committed all <a name="hardcoded-templates"></a>template files:
-
- <ul>
-<li><samp><span
class="file">server/po/head-include-2.</span><var>lang</var><span
class="file">.po</span></samp>
-<li><samp><span
class="file">server/po/body-include-1.</span><var>lang</var><span
class="file">.po</span></samp>
-<li><samp><span
class="file">server/po/body-include-2.</span><var>lang</var><span
class="file">.po</span></samp>
-<li><samp><span class="file">server/po/footer-text.</span><var>lang</var><span
class="file">.po</span></samp>
-<li><samp><span class="file">server/po/outdated.</span><var>lang</var><span
class="file">.po</span></samp>,
-</ul>
-
- <p>as well as the templates that are not under GNUN's control and are
+have already committed all template files listed in
+the <code>extra-templates</code> variable in <samp>server/gnun/gnun.mk</samp>,
+as well as the templates that are not under GNUN’s control and are
translated manually, like
-
- <ul>
-<li><samp><span class="file">server/header.</span><var>lang</var><span
class="file">.html</span></samp>
-<li><samp><span class="file">server/head-include-1.</span><var>lang</var><span
class="file">.html</span></samp>
-<li><samp><span class="file">server/html5-header.</span><var>lang</var><span
class="file">.html</span></samp>
-<li><samp><span
class="file">server/html5-head-include-1.</span><var>lang</var><span
class="file">.html</span></samp>
-<li><samp><span class="file">server/banner.</span><var>lang</var><span
class="file">.html</span></samp>
-<li><samp><span class="file">server/footer.</span><var>lang</var><span
class="file">.html</span></samp>.
-</ul>
-
- <p><a name="index-extra_002dtemplates-43"></a><a
name="index-templates_002c-additional-44"></a><a
name="index-defining-templates-45"></a><a
name="extra_002dtemplates"></a><br><dt>‘<samp><span
class="samp">extra-templates</span></samp>’<dd>
-The <var>extra-templates</var> variable lists additional templates under GNUN
+</p>
+<ul class="no-bullet">
+<li>- <samp>server/header.<var>lang</var>.html</samp>
+</li><li>- <samp>server/head-include-1.<var>lang</var>.html</samp>
+</li><li>- <samp>server/html5-header.<var>lang</var>.html</samp>
+</li><li>- <samp>server/html5-head-include-1.<var>lang</var>.html</samp>
+</li><li>- <samp>server/banner.<var>lang</var>.html</samp>
+</li><li>- <samp>server/footer.<var>lang</var>.html</samp>.
+</li></ul>
+
+<a name="index-extra_002dtemplates"></a>
+<a name="index-templates_002c-additional"></a>
+<a name="index-defining-templates-1"></a>
+<a name="extra_002dtemplates"></a></dd>
+<dt>‘<samp>extra-templates</samp>’</dt>
+<dd>
+<p>The <code>extra-templates</code> variable lists templates under GNUN
control; they are rebuilt from corresponding
-<var>template</var>.<var>lang</var>.po files like those hardcoded in
GNUmakefile
-(see <a href="hardcoded-templates.html#hardcoded-templates">hardcoded
templates</a>);
+<var>template</var>.<var>lang</var>.po files;
when the <var>template</var>.<var>lang</var>.po file is absent, GNUN
initializes
and commits a file with empty <code>msgstr</code>s.
-
- <p><a name="index-optional_002dtemplates-46"></a><a
name="index-templates_002c-optional-47"></a><a
name="index-defining-templates-48"></a><a
name="optional_002dtemplates"></a><br><dt>‘<samp><span
class="samp">optional-templates</span></samp>’<dd>
-The <var>optional-templates</var> variable defines optional templates under
+</p>
+<a name="index-optional_002dtemplates"></a>
+<a name="index-templates_002c-optional"></a>
+<a name="index-defining-templates-2"></a>
+<a name="optional_002dtemplates"></a></dd>
+<dt>‘<samp>optional-templates</samp>’</dt>
+<dd>
+<p>The <code>optional-templates</code> variable defines optional templates
under
GNUN control. Those are the templates of low priority items, like news
lines included in some pages. They are managed like the additional
templates listed in the <var>extra-templates</var> variable, except
+</p>
+<ul class="no-bullet">
+<li>- <var>template</var>.<var>lang</var>.po is not added when absent, and
+</li><li>- their POTs end in <code>.pot.opt</code> rather than
<code>.pot</code>.
+</li></ul>
- <ul>
-<li><var>template</var>.<var>lang</var>.po is not added when absent, and
-<li>their POTs end in <code>.pot.opt</code> rather than <code>.pot</code>.
-</ul>
-
- <p>This way, the scripts reporting outdated translations and translations
-that hasn't been converted to PO files won't complain about them unless
+<p>This way, the scripts reporting outdated translations and translations
+that hasn’t been converted to PO files won’t complain about them
unless
the team decides to actually commit <var>template</var>.<var>lang</var>.po.
-
- <p><a name="index-FUZZY_005fDIFF_005fLINGUAS-49"></a><a
name="index-previous_002c-diff-50"></a><br><dt>‘<samp><span
class="samp">FUZZY_DIFF_LINGUAS</span></samp>’<dd>Add your language code
here if you want GNUN to add differences to
+</p>
+<a name="index-FUZZY_005fDIFF_005fLINGUAS"></a>
+<a name="index-previous_002c-diff"></a>
+</dd>
+<dt>‘<samp>FUZZY_DIFF_LINGUAS</samp>’</dt>
+<dd><p>Add your language code here if you want GNUN to add differences to
previous <code>msgid</code>s in your PO files. The differences are shown in
-the default <samp><span class="command">wdiff</span></samp> format. See <a
href="../wdiff/wdiff.html#wdiff">wdiff</a>, for more information.
-
- <p><a name="index-HOME_005fLINGUAS-51"></a><a
name="index-homepage_002c-defining-52"></a><a
name="index-defining-homepage-53"></a><br><dt>‘<samp><span
class="samp">HOME_LINGUAS</span></samp>’<dd>Add your language code if you
have already committed
-<samp><span class="file">po/home.</span><var>lang</var><span
class="file">.po</span></samp>, that way the homepage for your language
-will be built. It is not acceptable to have your language code
-defined in this variable, but not in <code>TEMPLATE_LINGUAS</code>.
-
- <p><a name="index-ROOT-54"></a><a
name="index-articles-in-root-directory_002c-defining-55"></a><a
name="index-defining-articles-in-the-root-dir-56"></a><br><dt>‘<samp><span
class="samp">ROOT</span></samp>’<dd>Add here articles that are in the
server root, like
-<samp><span class="file">keepingup.html</span></samp> and <samp><span
class="file">provide.html</span></samp>. Always write only the
+the default <code>wdiff</code> format. See <a
href="http://www.gnu.org/software/wdiff/manual/html_node/wdiff.html#wdiff";>The
word
+difference finder</a> in <cite>GNU wdiff</cite>, for more information.
+</p>
+<a name="index-ROOT"></a>
+<a name="index-articles-in-root-directory_002c-defining"></a>
+<a name="index-defining-articles-in-the-root-dir"></a>
+</dd>
+<dt>‘<samp>ROOT</samp>’</dt>
+<dd><p>Add here articles that are in the server root, like
<samp>home.html</samp>,
+<samp>keepingup.html</samp> and <samp>provide.html</samp>. Always write only
the
basename of the article, i.e. if you add these two articles, the value
of <code>ROOT</code> should be <code>keepingup provide</code>. This is true
for
all the variables that expect values in the form of article names.
-
- <p><a name="index-ALL_005fDIRS-57"></a><a
name="index-directories_002c-defining-58"></a><a
name="index-defining-directories-59"></a><br><dt>‘<samp><span
class="samp">ALL_DIRS</span></samp>’<dd>The list of directories
containing articles, like <samp><span class="file">philosophy</span></samp>,
-<samp><span class="file">gnu</span></samp>, <samp><span
class="file">licenses</span></samp>, etc.
-
- <p><a
name="index-POT-generation_002c-articles-60"></a><br><dt>‘<samp><span
class="samp">gnu</span></samp>’<dt>‘<samp><span
class="samp">philosophy</span></samp>’<dt>‘<samp><span
class="samp">...directory...</span></samp>’<dd>A space-separated list of
basenames for articles residing in
+</p>
+<a name="index-ALL_005fDIRS"></a>
+<a name="index-directories_002c-defining"></a>
+<a name="index-defining-directories"></a>
+</dd>
+<dt>‘<samp>ALL_DIRS</samp>’</dt>
+<dd><p>The list of directories containing articles, like
<samp>philosophy</samp>,
+<samp>gnu</samp>, <samp>licenses</samp>, etc.
+</p>
+<a name="index-POT-generation_002c-articles"></a>
+</dd>
+<dt>‘<samp>gnu</samp>’</dt>
+<dt>‘<samp>philosophy</samp>’</dt>
+<dt>‘<samp>…directory…</samp>’</dt>
+<dd><p>A space-separated list of basenames for articles residing in
<var>directory</var>, for which POTs will be generated and updated when the
original article changes. If an article is missing here, there is no
way its translations to be maintained via GNUN.
+</p></dd>
</dl>
- <div class="footnote">
+<div class="footnote">
<hr>
-<h4>Footnotes</h4><p class="footnote"><small>[<a name="fn-1"
href="#fnd-1">1</a>]</small> Only because presumably, they are more familiar
with
-GNUnited Nations' internals. From a purely technical point of view,
+<h4 class="footnotes-heading">Footnotes</h4>
+
+<h3><a name="FOOT4" href="#DOCF4">(4)</a></h3>
+<p>Only because presumably, they are more familiar with
+GNUnited Nations’ internals. From a purely technical point of view,
there is no difference.</p>
+</div>
+<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>
+</div>
- <hr></div>
- </body></html>
+</body>
+</html>
Index: gnun/html_node/Migrating.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Migrating.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnun/html_node/Migrating.html 26 Sep 2012 14:49:43 -0000 1.16
+++ gnun/html_node/Migrating.html 4 Dec 2012 16:24:22 -0000 1.17
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>Migrating - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="PO-Files.html#PO-Files" title="PO Files">
-<link rel="prev" href="New-Translation.html#New-Translation" title="New
Translation">
-<link rel="next" href="GNU-News.html#GNU-News" title="GNU News">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,47 +9,80 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Migrating</title>
+
+<meta name="description" content="GNUnited Nations: Migrating">
+<meta name="keywords" content="GNUnited Nations: Migrating">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="PO-Files.html#PO-Files" rel="up" title="PO Files">
+<link href="GNU-News.html#GNU-News" rel="next" title="GNU News">
+<link href="Credits-Slot.html#Credits-Slot" rel="previous" title="Credits
Slot">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Migrating"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="GNU-News.html#GNU-News">GNU
News</a>,
-Previous: <a rel="previous" accesskey="p"
href="New-Translation.html#New-Translation">New Translation</a>,
-Up: <a rel="up" accesskey="u" href="PO-Files.html#PO-Files">PO Files</a>
-<hr>
+Next: <a href="GNU-News.html#GNU-News" accesskey="n" rel="next">GNU News</a>,
Previous: <a href="New-Translation.html#New-Translation" accesskey="p"
rel="previous">New Translation</a>, Up: <a href="PO-Files.html#PO-Files"
accesskey="u" rel="up">PO Files</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-
+<hr>
+<a name="Transforming-Existing-Translation-in-PO-Format"></a>
<h4 class="subsection">2.3.2 Transforming Existing Translation in PO
Format</h4>
+<a name="index-migration_002c-translations"></a>
+<a name="index-conversion-of-existing-translations"></a>
-<p><a name="index-migration_002c-translations-76"></a><a
name="index-conversion-of-existing-translations-77"></a>
-Migrating an existing translation to a PO file format is basically
+<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>Typically, you will visit <samp><span
class="file">po/foo.</span><var>lang</var><span class="file">.po</span></samp>
(in PO mode) and
-<samp><span class="file">foo.</span><var>lang</var><span
class="file">.html</span></samp> (in HTML mode) in another buffer. Then you
+</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
@@ -70,52 +94,66 @@
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>There is also a semi-automatic way to produce an initial PO file. You
-checkout the revision of the English page, <samp><span
class="file">foo.html</span></samp>, that
+</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><span class="file">foo.</span><var>lang</var><span
class="file">.html</span></samp>. Then you run <samp><span
class="command">gnun-preconvert</span></samp>
-which invokes <samp><span class="command">po4a-gettextize</span></samp> (See
<a href="gnun_002dpreconvert.html#gnun_002dpreconvert">gnun-preconvert</a>.):
+<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.html#gnun_002dpreconvert">gnun-preconvert</a>.):
+</p>
+<div class="example">
+<pre class="example">gnun-preconvert foo.lang.html foo.html
+</pre></div>
-<pre class="example"> gnun-preconvert foo.lang.html foo.html
-</pre>
- <p>If some passages in <samp><span
class="file">foo.</span><var>lang</var><span class="file">.html</span></samp>
don't match the structure
-of <samp><span class="file">foo.html</span></samp>, error messages will be
displayed. Check them,
+<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
-<samp><span class="command">gnun-merge-preconverted</span></samp> (See <a
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a>.):
+<code>gnun-merge-preconverted</code> (See <a
href="gnun_002dmerge_002dpreconverted.html#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>
-<pre class="example"> gnun-merge-preconverted -C compendium.lang.po
foo.lang.po foo.pot
-</pre>
- <p>If you have no compendium, just omit the “<code>-C
+<p>If you have no compendium, just omit the “<code>-C
compendium.lang.po</code>” part.
-
- <p>You get <samp><span class="file">foo.</span><var>lang</var><span
class="file">.po</span></samp> where all messages are marked as
+</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>There is no need to delete the existing HTML translation, GNUN will
+</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>When an essay has been translated by several people through the years,
+</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>A recommended way to do this is as follows:
-
-<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>
- <p>In this example, it is clear that Cédric made the initial
+<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>
+<div class="header">
+<p>
+Next: <a href="GNU-News.html#GNU-News" accesskey="n" rel="next">GNU News</a>,
Previous: <a href="New-Translation.html#New-Translation" accesskey="p"
rel="previous">New Translation</a>, Up: <a href="PO-Files.html#PO-Files"
accesskey="u" rel="up">PO Files</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+
- </body></html>
+</body>
+</html>
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.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- gnun/html_node/Modifying-Boilerplates.html 26 Sep 2012 14:49:43 -0000
1.5
+++ gnun/html_node/Modifying-Boilerplates.html 4 Dec 2012 16:24:22 -0000
1.6
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>Modifying Boilerplates - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Webmaster-Tips.html#Webmaster-Tips" title="Webmaster
Tips">
-<link rel="prev" href="Comments-for-Translators.html#Comments-for-Translators"
title="Comments for Translators">
-<link rel="next" href="Localized-URLs.html#Localized-URLs" title="Localized
URLs">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,46 +9,81 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Modifying Boilerplates</title>
+
+<meta name="description" content="GNUnited Nations: Modifying Boilerplates">
+<meta name="keywords" content="GNUnited Nations: Modifying Boilerplates">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Webmaster-Tips.html#Webmaster-Tips" rel="up" title="Webmaster
Tips">
+<link href="Localized-URLs.html#Localized-URLs" rel="next" title="Localized
URLs">
+<link href="Comments-for-Translators.html#Comments-for-Translators"
rel="previous" title="Comments for Translators">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Modifying-Boilerplates"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Localized-URLs.html#Localized-URLs">Localized URLs</a>,
-Previous: <a rel="previous" accesskey="p"
href="Comments-for-Translators.html#Comments-for-Translators">Comments for
Translators</a>,
-Up: <a rel="up" accesskey="u"
href="Webmaster-Tips.html#Webmaster-Tips">Webmaster Tips</a>
-<hr>
+Next: <a href="Localized-URLs.html#Localized-URLs" accesskey="n"
rel="next">Localized URLs</a>, Previous: <a
href="Comments-for-Translators.html#Comments-for-Translators" accesskey="p"
rel="previous">Comments for Translators</a>, Up: <a
href="Webmaster-Tips.html#Webmaster-Tips" accesskey="u" rel="up">Webmaster
Tips</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="Modifying-Boilerplates-1"></a>
<h4 class="subsection">2.4.3 Modifying Boilerplates</h4>
+<a name="index-boilerplates"></a>
-<p><a name="index-boilerplates-101"></a>
-<strong>Warning:</strong> Any significant structural diversion from
-<samp><span class="file">boilerplate.html</span></samp> in a specific article
may result in errors from
+<p><strong>Warning:</strong> Any significant structural diversion from
+<samp>boilerplate.html</samp> in a specific article may result in errors from
GNUN. Any untested intrusive updates to the server templates (such as
changing the entire look & feel of the site) will probably break
-<em>all</em> translations under GNUN's control. Of course, this does not
+<em>all</em> translations under GNUN’s control. Of course, this does not
mean that no changes should happen—only that they must be applied in
our sandbox first, to ensure a smooth transition.
+</p>
+
- </body></html>
+</body>
+</html>
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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/New-Translation.html 26 Sep 2012 14:49:43 -0000 1.15
+++ gnun/html_node/New-Translation.html 4 Dec 2012 16:24:22 -0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>New Translation - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="PO-Files.html#PO-Files" title="PO Files">
-<link rel="next" href="Migrating.html#Migrating" title="Migrating">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,181 +9,249 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: New Translation</title>
+
+<meta name="description" content="GNUnited Nations: New Translation">
+<meta name="keywords" content="GNUnited Nations: New Translation">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="PO-Files.html#PO-Files" rel="up" title="PO Files">
+<link href="Notes-Slot.html#Notes-Slot" rel="next" title="Notes Slot">
+<link href="PO-Files.html#PO-Files" rel="previous" title="PO Files">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="New-Translation"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Migrating.html#Migrating">Migrating</a>,
-Up: <a rel="up" accesskey="u" href="PO-Files.html#PO-Files">PO Files</a>
-<hr>
+Next: <a href="Migrating.html#Migrating" accesskey="n"
rel="next">Migrating</a>, Up: <a href="PO-Files.html#PO-Files" accesskey="u"
rel="up">PO Files</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-
+<hr>
+<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>
-<p><a name="index-translation_002c-new-63"></a><a
name="index-new-translation-64"></a>
-To start a new translation, the most simple way is to copy the
-existing POT as <samp><span class="file">article.</span><var>lang</var><span
class="file">.po</span></samp>, where <var>lang</var> is your
+<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.</code><var>lang</var><code>.po</code> and then edit the latter. If
-<samp><span class="file">free-sw.pot</span></samp> does not exist it is
because either the article is
+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><span class="file">server/gnun/gnun.mk</span></samp>. In
that case, just ask them
+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>You could also use the <samp><span class="command">msginit</span></samp>
utility that would populate
+</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="../gettext/msginit-Invocation.html#msginit-Invocation">msginit
Invocation</a>.
-
- <p>GNUN also provides a customized script to automatically fill more
+environment is set up correctly. See <a
href="http://www.gnu.org/software/gettext/manual/html_node/msginit-Invocation.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.html#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>The PO file header as generated usually looks like this:
-
-<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>
- <p>You have to edit the header to match the already established
+<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-65"></a>
- <dl>
-<dt>‘<samp><span
class="samp">Project-Id-Version</span></samp>’<dd>Add here the filename
of the original article, without the
+</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”.
-
- <br><dt>‘<samp><span
class="samp">POT-Creation-Date</span></samp>’<dd>Do not edit this field,
it is already set when the POT is created.
-
- <br><dt>‘<samp><span
class="samp">PO-Revision-Date</span></samp>’<dd>Likewise, do not edit.
This field is automatically filled in when you
+</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.
-
- <br><dt>‘<samp><span
class="samp">Last-Translator</span></samp>’<dd>The name and email address
of the last translator who has edited the
+</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:
-
- <pre class="example"> Elvis Parsley <address@hidden>
-</pre>
- <br><dt>‘<samp><span
class="samp">Language-Team</span></samp>’<dd>This field should contain
the mailing list on which the translation
-team can be reached—usually <a
href="mailto:address@hidden";>www-LANG-<small
class="dots">...</small>@gnu.org</a>.
+</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:
-
- <pre class="example"> Czech <address@hidden>
-</pre>
- <br><dt>‘<samp><span
class="samp">MIME-Version</span></samp>’<dd>Leave it like it is.
-
- <br><dt>‘<samp><span
class="samp">Content-Type</span></samp>’<dd>Usually this is
<code>text/plain; charset=UTF-8</code>; change the charset
+</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.
-
- <br><dt>‘<samp><span
class="samp">Content-Transfer-Encoding</span></samp>’<dd>Set this to
<code>8bit</code>. Note that the PO file header ends with this
-field, and it should contain a newline (‘<samp><span
class="samp">\n</span></samp>’). Unfortunately, some
+</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.
+the file is automatically modified by GNUN’s rules.
+</p></dd>
</dl>
- <p>Here is an example of a properly edited header:
+<p>Here is an example of a properly edited header:
+</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>
-<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>
- <p>Notice the absence of the “fuzzy” marker; you should
“unfuzzy” the
+<p>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).
-
- <p>It is recommended that you wrap all lines in the comments to be less
+simply pressing <tt class="key">TAB</tt> in PO mode).
+</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><span
class="file">GNUmakefile.team</span></samp>'s <code>publish</code>
+and improves the performance of <samp>GNUmakefile.team</samp>’s
<code>publish</code>
rule (see <a
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables">GNUmakefile.team
Variables</a>).
-
- <p>There are some special messages that appear in the POT and PO:
-
-
-<a name="index-notes_002c-translators-66"></a>
-<a name="index-translators_0027-notes-67"></a>
-<dl><dt>‘<samp><span class="samp">*GNUN-SLOT: TRANSLATOR'S
NOTES*</span></samp>’<dd>This is for translator's notes that are injected
in the resulting
+</p>
+<p>There are some special messages that appear in the POT and PO:
+</p>
+<dl compact="compact">
+<dd><a name="index-notes_002c-translators"></a>
+<a name="index-translators_0027-notes"></a>
+</dd>
+<dt>‘<samp>*GNUN-SLOT: TRANSLATOR'S NOTES*</samp>’</dt>
+<dd><p>This is for translator’s notes that are injected in the resulting
translation. See <a href="Notes-Slot.html#Notes-Slot">Notes Slot</a>, for
more information. If your
translation does not have notes, you <em>must</em> translate this as a
-space, that is, <SPC>.
-
- <p><a name="index-credits_002c-translators-68"></a><a
name="index-translators_0027-credits-69"></a><br><dt>‘<samp><span
class="samp">*GNUN-SLOT: TRANSLATOR'S CREDITS*</span></samp>’<dd>This is
again optional, and should contain the name (and address) of
+space, that is, <tt class="key">SPC</tt>.
+</p>
+<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 (<SPC>) if you do not want your name to appear there.
+space (<tt class="key">SPC</tt>) if you do not want your name to appear there.
See <a href="Credits-Slot.html#Credits-Slot">Credits Slot</a>.
+</p></dd>
</dl>
- <p><a name="index-wrapping-long-lines-70"></a><a
name="index-long-lines_002c-wrap-71"></a>Most of the PO editors do not wrap
long lines that inevitably appear in
+<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
</code><var>file</var><code>.po
-</code><var>file</var><code>.po</code>, before installing it in the
repository. Either way, the
+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>For those lucky Emacs users, here is a code snippet that you can put
-in your <samp><span class="file">.emacs</span></samp>; doing <kbd>M-x
po-wrap</kbd> while in PO mode will
+</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:
-
-<pre class="lisp"> (defun po-wrap ()
- "Filter current po-mode buffer through `msgcat' tool to wrap all 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*")))
+ (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)))
+ "msgcat" nil tmp-buf t (shell-quote-argument
tmp-file)))
(let ((saved (point))
(inhibit-read-only t))
(delete-region (point-min) (point-max))
@@ -201,20 +261,31 @@
(error (buffer-string)))))
(kill-buffer tmp-buf)
(delete-file tmp-file)))))
-</pre>
- <p>It is highly desirable that you check if the PO file you finished
+</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 </code><var>file</var> or by simply
+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
+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.html#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.html#Credits-Slot" accesskey="2">Credits
Slot</a>:</td><td> </td><td align="left"
valign="top">Translator’s credits.
+</td></tr>
+</table>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Migrating.html#Migrating" accesskey="n"
rel="next">Migrating</a>, Up: <a href="PO-Files.html#PO-Files" accesskey="u"
rel="up">PO Files</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
-<ul class="menu">
-<li><a accesskey="1" href="Notes-Slot.html#Notes-Slot">Notes Slot</a>:
How to handle translator's notes.
-<li><a accesskey="2" href="Credits-Slot.html#Credits-Slot">Credits Slot</a>:
Translator's credits.
-</ul>
- </body></html>
+</body>
+</html>
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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Notes-Slot.html 26 Sep 2012 14:49:43 -0000 1.15
+++ gnun/html_node/Notes-Slot.html 4 Dec 2012 16:24:23 -0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Notes Slot - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="New-Translation.html#New-Translation" title="New
Translation">
-<link rel="next" href="Credits-Slot.html#Credits-Slot" title="Credits Slot">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,82 +9,126 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Notes Slot</title>
+
+<meta name="description" content="GNUnited Nations: Notes Slot">
+<meta name="keywords" content="GNUnited Nations: Notes Slot">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="New-Translation.html#New-Translation" rel="up" title="New
Translation">
+<link href="Credits-Slot.html#Credits-Slot" rel="next" title="Credits Slot">
+<link href="New-Translation.html#New-Translation" rel="previous" title="New
Translation">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Notes-Slot"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Credits-Slot.html#Credits-Slot">Credits Slot</a>,
-Up: <a rel="up" accesskey="u"
href="New-Translation.html#New-Translation">New Translation</a>
-<hr>
+Next: <a href="Credits-Slot.html#Credits-Slot" accesskey="n"
rel="next">Credits Slot</a>, Up: <a href="New-Translation.html#New-Translation"
accesskey="u" rel="up">New Translation</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-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>
-<h5 class="subsubsection">2.3.1.1 The Special Slot for Translator's Notes</h5>
-
-<p><a name="index-notes_002c-translators-72"></a><a
name="index-translators_0027-notes-73"></a>
-Sometimes it is necessary to complement the translation of an essay
-with translator's notes. The special message <code>*GNUN-SLOT:
+<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 (<SPC>)—otherwise the PO file will
be
+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:
+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>
-<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>
- <p>Certainly, everything in the <code>msgstr</code>s should be in your
native
+<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><span
class="samp">TransNote2</span></samp>’, ‘<samp><span
class="samp">TransNote3</span></samp>’, etc. and
+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>Do not worry about the <code>\n</code> character—it is inserted
-automatically when you press <RET>. It is not compulsory that
+</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>It is important to follow this specification, because notes will look
+</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
+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>
+<div class="header">
+<p>
+Next: <a href="Credits-Slot.html#Credits-Slot" accesskey="n"
rel="next">Credits Slot</a>, Up: <a href="New-Translation.html#New-Translation"
accesskey="u" rel="up">New Translation</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
+
- </body></html>
+</body>
+</html>
Index: gnun/html_node/Overview.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Overview.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Overview.html 26 Sep 2012 14:49:43 -0000 1.15
+++ gnun/html_node/Overview.html 4 Dec 2012 16:24:23 -0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Overview - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Introduction.html#Introduction" title="Introduction">
-<link rel="next" href="Concepts.html#Concepts" title="Concepts">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,58 +9,94 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Overview</title>
+
+<meta name="description" content="GNUnited Nations: Overview">
+<meta name="keywords" content="GNUnited Nations: Overview">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Introduction.html#Introduction" rel="up" title="Introduction">
+<link href="Concepts.html#Concepts" rel="next" title="Concepts">
+<link href="Introduction.html#Introduction" rel="previous"
title="Introduction">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Overview"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Concepts.html#Concepts">Concepts</a>,
-Up: <a rel="up" accesskey="u"
href="Introduction.html#Introduction">Introduction</a>
-<hr>
+Next: <a href="Concepts.html#Concepts" accesskey="n" rel="next">Concepts</a>,
Up: <a href="Introduction.html#Introduction" accesskey="u"
rel="up">Introduction</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-
+<hr>
+<a name="Why-GNUN-is-Being-Developed"></a>
<h3 class="section">1.1 Why GNUN is Being Developed</h3>
-<p>The GNU Project's website, <a
href="http://www.gnu.org";>http://www.gnu.org</a>, has become
+<p>The GNU Project’s website, <a
href="http://www.gnu.org";>http://www.gnu.org</a>, has become
considerably large over the years. Maintaining it requires significant
effort, and sometimes a new web standard is developed faster than the
time required to migrate all articles to the next widely adopted one.
-
- <p>When it comes to internationalization, the problems are so many that
+</p>
+<p>When it comes to internationalization, the problems are so many that
it is hard to enumerate them. It has become apparent that maintaining
translations up-to-date is a major undertaking, involving tedious
skimming through commit logs, reviewing diffs and other medieval
techniques to catch up. Some translation teams have developed their
own sets of scripts, but so far there has been no universal solution.
-
- <p>This unpleasant situation, combined with rapid and incompatible design
+</p>
+<p>This unpleasant situation, combined with rapid and incompatible design
changes, have lead some teams to neglect the important work of keeping
their translation in line with the changing original articles. As a
consequence, the GNU Project is facing the problem of maintaining them
in suboptimal ways, in order to keep the information updated.
-
- <p>The reasons for developing GNUnited Nations are very similar to those
+</p>
+<p>The reasons for developing GNUnited Nations are very similar to those
that lead to the inception of GNU gettext, or GNOME Documentation
Utilities (<code>gnome-doc-utils</code>) some years later.
+</p>
+
- </body></html>
+</body>
+</html>
Index: gnun/html_node/PO-Files-and-Team.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/gnun/html_node/PO-Files-and-Team.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/PO-Files-and-Team.html 26 Sep 2012 14:49:43 -0000
1.15
+++ gnun/html_node/PO-Files-and-Team.html 4 Dec 2012 16:24:23 -0000
1.16
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>PO Files and Team - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="PO-Files.html#PO-Files" title="PO Files">
-<link rel="prev" href="languages_002etxt.html#languages_002etxt"
title="languages.txt">
-<link rel="next" href="Compendia.html#Compendia" title="Compendia">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,97 +9,136 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: PO Files and Team</title>
+
+<meta name="description" content="GNUnited Nations: PO Files and Team">
+<meta name="keywords" content="GNUnited Nations: PO Files and Team">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#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="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables"
rel="next" title="GNUmakefile.team Variables">
+<link href="languages_002etxt.html#languages_002etxt" rel="previous"
title="languages.txt">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="PO-Files-and-Team"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Compendia.html#Compendia">Compendia</a>,
-Previous: <a rel="previous" accesskey="p"
href="languages_002etxt.html#languages_002etxt">languages.txt</a>,
-Up: <a rel="up" accesskey="u" href="PO-Files.html#PO-Files">PO Files</a>
-<hr>
+Next: <a href="Compendia.html#Compendia" accesskey="n"
rel="next">Compendia</a>, Previous: <a
href="languages_002etxt.html#languages_002etxt" accesskey="p"
rel="previous">languages.txt</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="Maintaining-Translations-in-Your-Team_0027s-Repository"></a>
+<h4 class="subsection">2.3.7 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>
-<h4 class="subsection">2.3.7 Maintaining Translations in Your Team's
Repository</h4>
-
-<p><a name="index-project-repository-85"></a><a
name="index-repository_002c-translation-project-86"></a><a
name="index-team-maintenance-87"></a><a
name="index-GNUmakefile_002eteam-88"></a>
-GNUN operates on the “official” Web repository of the Savannah
project
-`www', where normally only the coordinators of translation teams have
+<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>The PO files provide an excellent and natural way to review each other's
+</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>The file <samp><span class="file">GNUmakefile.team</span></samp> in the
‘<samp><span class="samp">gnun</span></samp>’ package is a
+</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
+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-89"></a>The following diagram illustrates a
typical workflow—it is applicable
+</p>
+<a name="index-team-workflow"></a>
+<p>The following diagram illustrates a typical workflow—it is applicable
for small, medium and large teams:
-
-<pre class="example"> +----------+ +-------------------+
- | ``www'' | | ``www-LANG'' |
- | Web |------>---->-------|Sources repository |
- |repository| automatic merge +-------------------+
- +----------+ | | |
+</p>
+<div class="example">
+<pre class="example">+----------+ +-------------------+
+| ``www'' | | ``www-LANG'' |
+| Web |------>---->-------|Sources repository |
+|repository| automatic merge +-------------------+
++----------+ | | |
| | | `-- Member A
+------------<----<-------------' |
Leader `---Member B
-</pre>
- <p>All members and the team leader commit in their project's
+</pre></div>
+
+<p>All members and the team leader commit in their project’s
repository—when a translation is ready, the leader checks it in in the
-official `www' repository. If an original article changes,
+official ‘www’ repository. If an original article changes,
a build could be invoked to synchronize (i.e. merge) the changes and
optionally automatically commit them so that the draft PO files are
updated. A translator would then normally update the PO file, and
-commit it again in the project's Sources repository, from where the
-coordinator will pick it up and install it in `www'.
-
- <p>To take advantage of this semi-automation, rename this template
-<samp><span class="file">GNUmakefile.team</span></samp> as <samp><span
class="file">GNUmakefile</span></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><span class="file">/po</span></samp> sub-directories; they are redundant
here. Instead, install
+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><span class="file">.</span><var>lang</var><span
class="file">.html</span></samp> resides in `www', for example:
-
-<pre class="example"> Root
+<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
@@ -117,20 +147,34 @@
| +--free-sw.<var>lang</var>.po
| +--not-ipr.<var>lang</var>.po
| +--open-source-misses-the-point.<var>lang</var>.po
- | +--...
+ | +--…
|
- +--...
-</pre>
- <p><a name="index-priorities_002emk-90"></a>Add <samp><span
class="file">priorities.mk</span></samp> in order to make the
<code>report</code> target sort
-the files by priority.
+ +--…
+</pre></div>
- <p>The next sections explain how to adopt the makefile for your team and
+<a name="index-priorities_002emk-2"></a>
+<p>Add <samp>priorities.mk</samp> in order to make the <code>report</code>
target sort
+the files by priority.
+</p>
+<p>The next sections explain how to adopt the makefile for your team and
how to invoke a “build”.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a
href="GNUmakefile_002eteam-Variables.html#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.html#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.html#GNUmakefile_002eteam-and-Cron"
accesskey="3">GNUmakefile.team and Cron</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+</table>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Compendia.html#Compendia" accesskey="n"
rel="next">Compendia</a>, Previous: <a
href="languages_002etxt.html#languages_002etxt" accesskey="p"
rel="previous">languages.txt</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>
-<ul class="menu">
-<li><a accesskey="1"
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables">GNUmakefile.team
Variables</a>
-<li><a accesskey="2"
href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron">GNUmakefile.team
and Cron</a>
-</ul>
- </body></html>
+</body>
+</html>
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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/PO-Files.html 26 Sep 2012 14:49:43 -0000 1.15
+++ gnun/html_node/PO-Files.html 4 Dec 2012 16:24:23 -0000 1.16
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>PO Files - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Usage.html#Usage" title="Usage">
-<link rel="prev" href="Main-Variables.html#Main-Variables" title="Main
Variables">
-<link rel="next" href="Webmaster-Tips.html#Webmaster-Tips" title="Webmaster
Tips">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,102 +9,148 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: PO Files</title>
+
+<meta name="description" content="GNUnited Nations: PO Files">
+<meta name="keywords" content="GNUnited Nations: PO Files">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#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="New-Translation.html#New-Translation" rel="next" title="New
Translation">
+<link href="Main-Variables.html#Main-Variables" rel="previous" title="Main
Variables">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="PO-Files"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Webmaster-Tips.html#Webmaster-Tips">Webmaster Tips</a>,
-Previous: <a rel="previous" accesskey="p"
href="Main-Variables.html#Main-Variables">Main Variables</a>,
-Up: <a rel="up" accesskey="u" href="Usage.html#Usage">Usage</a>
-<hr>
+Next: <a href="Webmaster-Tips.html#Webmaster-Tips" accesskey="n"
rel="next">Webmaster Tips</a>, Previous: <a
href="Main-Variables.html#Main-Variables" accesskey="p" rel="previous">Main
Variables</a>, Up: <a href="Usage.html#Usage" accesskey="u" rel="up">Usage</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-
+<hr>
+<a name="Working-with-PO-Files"></a>
<h3 class="section">2.3 Working with PO Files</h3>
+<a name="index-PO_002c-editing"></a>
-<p><a name="index-PO_002c-editing-61"></a>
-We anticipate that some gnu.org translators will find this format odd
+<p>We anticipate that some gnu.org translators will find this format odd
or inconvenient, if they never happened to work with PO files before.
-Don't worry, you will soon get accustomed to it. It is the
+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>The most efficient way to edit a PO file is using a specialized PO
+</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:
-
-
-<a name="index-PO-editors-62"></a>
-<ul><li>PO mode. We recommend using GNU Emacs in PO mode, because Emacs is
+</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><span class="file">.po</span></samp> file you
visit should automatically
+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
-<RET></code>. On some GNU/Linux distros such as gNewSense, PO mode is
+<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>Gtranslator—the GNOME PO editor. See
+</li><li> Gtranslator—the GNOME PO editor. See
<a
href="http://projects.gnome.org/gtranslator/";>http://projects.gnome.org/gtranslator/</a>.
- <li>Lokalize—the KDE 4 editor. See
+</li><li> Lokalize—the KDE 4 editor. See
<a
href="http://userbase.kde.org/Lokalize";>http://userbase.kde.org/Lokalize</a>.
- <li>KBabel—the KDE 3 editor. No longer supported, but might be
+</li><li> KBabel—the KDE 3 editor. No longer supported, but might be
available on some old systems.
- <li>Poedit—another popular editor that is based on the
<code>wxWidgets</code>
+</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>Virtaal—a relevantly new editor that supports also the XLIFF
format
+</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><!-- @heresy -->
-<!-- Please forgive them, they don't know what they are doing... -->
-po.vim—ftplugin for the Vim editor. The best option for people who
+</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>.
-<!-- @end heresy -->
-
- <li>Various web-based editors. See <a
href="../web-trans/Savannah-VCS.html#Savannah-VCS">Savannah VCS</a>.
-</ul>
-<ul class="menu">
-<li><a accesskey="1" href="New-Translation.html#New-Translation">New
Translation</a>: How to start a new translation.
-<li><a accesskey="2" href="Migrating.html#Migrating">Migrating</a>:
How to migrate an existing translation to a PO
- format under GNUN's control.
-<li><a accesskey="3" href="GNU-News.html#GNU-News">GNU News</a>:
How to handle ``whatsnew'' (a.k.a. ``gnunews'').
-<li><a accesskey="4" href="PO-Tips.html#PO-Tips">PO Tips</a>:
Tips and hints for translators.
-<li><a accesskey="5"
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml">generic.LANG.html</a>:
Specifying information that will propagate in
+</li><li> Various web-based editors. See <a
href="http://www.gnu.org/software/trans-coord/manual/web-trans/html_node/Savannah-VCS.html#Savannah-VCS";>Savannah
VCS</a> in <cite>GNU Web
+Translators Manual</cite>.
+</li></ul>
+
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a
href="New-Translation.html#New-Translation" accesskey="1">New
Translation</a>:</td><td> </td><td align="left" valign="top">How to
start a new translation.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="Migrating.html#Migrating"
accesskey="2">Migrating</a>:</td><td> </td><td align="left"
valign="top">How to migrate an existing translation to a PO
+ format under GNUN’s control.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="GNU-News.html#GNU-News"
accesskey="3">GNU News</a>:</td><td> </td><td align="left"
valign="top">How to handle “whatsnew” (a.k.a.
“gnunews”).
+</td></tr>
+<tr><td align="left" valign="top">• <a href="PO-Tips.html#PO-Tips"
accesskey="4">PO Tips</a>:</td><td> </td><td align="left"
valign="top">Tips and hints for translators.
+</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.
-<li><a accesskey="6"
href="languages_002etxt.html#languages_002etxt">languages.txt</a>:
Specifying canonical names for languages.
-<li><a accesskey="7" href="PO-Files-and-Team.html#PO-Files-and-Team">PO Files
and Team</a>: How to maintain translations in the team's
+</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="PO-Files-and-Team.html#PO-Files-and-Team" accesskey="7">PO Files and
Team</a>:</td><td> </td><td align="left" valign="top">How to
maintain translations in the team’s
repository.
-<li><a accesskey="8" href="Compendia.html#Compendia">Compendia</a>:
Using translation memory.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="Compendia.html#Compendia"
accesskey="8">Compendia</a>:</td><td> </td><td align="left"
valign="top">Using translation memory.
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+</pre></th></tr></table>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Webmaster-Tips.html#Webmaster-Tips" accesskey="n"
rel="next">Webmaster Tips</a>, Previous: <a
href="Main-Variables.html#Main-Variables" accesskey="p" rel="previous">Main
Variables</a>, Up: <a href="Usage.html#Usage" accesskey="u" rel="up">Usage</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
- </ul>
- </body></html>
+</body>
+</html>
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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/PO-Tips.html 26 Sep 2012 14:49:43 -0000 1.15
+++ gnun/html_node/PO-Tips.html 4 Dec 2012 16:24:23 -0000 1.16
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>PO Tips - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="PO-Files.html#PO-Files" title="PO Files">
-<link rel="prev" href="GNU-News.html#GNU-News" title="GNU News">
-<link rel="next"
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
title="generic.LANG.html">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,61 +9,94 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: PO Tips</title>
+
+<meta name="description" content="GNUnited Nations: PO Tips">
+<meta name="keywords" content="GNUnited Nations: PO Tips">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="PO-Files.html#PO-Files" rel="up" title="PO Files">
+<link href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
rel="next" title="generic.LANG.html">
+<link href="GNU-News.html#GNU-News" rel="previous" title="GNU News">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="PO-Tips"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml">generic.LANG.html</a>,
-Previous: <a rel="previous" accesskey="p"
href="GNU-News.html#GNU-News">GNU News</a>,
-Up: <a rel="up" accesskey="u" href="PO-Files.html#PO-Files">PO Files</a>
-<hr>
+Next: <a href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
accesskey="n" rel="next">generic.LANG.html</a>, Previous: <a
href="GNU-News.html#GNU-News" accesskey="p" rel="previous">GNU News</a>, Up: <a
href="PO-Files.html#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-
+<hr>
+<a name="Useful-Hints-for-Editing-PO-Files"></a>
<h4 class="subsection">2.3.4 Useful Hints for Editing PO Files</h4>
+<a name="index-tips_002c-translators"></a>
+<a name="index-recommendations_002c-PO-files"></a>
-<p><a name="index-tips_002c-translators-81"></a><a
name="index-recommendations_002c-PO-files-82"></a>
-This section contains additional explanations, some in the form of
+<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.
- <ul>
-<li>When you install a new translation of an article (that is different
-from a server template or the homepage), all you need to do is to add
-your PO file in the appropriate <samp><span class="file">/po</span></samp>
sub-directory.
-
- <p>In the next build, your <samp><var>article</var><span
class="file">.</span><var>lang</var><span class="file">.html</span></samp> will
be
+<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.
-
- <li>If you don't feel comfortable editing <samp><span
class="file">gnun.mk</span></samp>, do not worry.
+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> or <code>HOME_LINGUAS</code> for you, as
appropriate.
+<code>TEMPLATE_LINGUAS</code> for you, as appropriate.
- <li>Dealing with obsolete strings. Elements which are removed from the
+</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
+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
@@ -82,33 +106,35 @@
Failing that, you can still copy it and yank it at the appropriate
place.
- <li>You can add comments to every message in a PO file—for example
if
+</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>Sometimes, especially when the original message contains many links,
+</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>If you translate “Free Software Foundation, Inc.” in your
native
+</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:
- <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>
- <li>There is absolutely no reason to use HTML entities in translations as
a
+<div class="example">
+<pre class="example"># type: Content of: <div><address>
+msgid "51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA"
+msgstr ""
+"Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, "
+"Boston, MA 02110-1301, USA"
+</pre></div>
+
+</li><li> There is absolutely no reason to use HTML entities in translations
as a
replacement for common non-ASCII characters. They are harder to write
and serve no purpose.
- <li>Wrapping of <code>msgstr</code> using <kbd>M-q</kbd> in Emacs (or
other means) is
+</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
@@ -116,7 +142,15 @@
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.
-</ul>
+</li></ul>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
accesskey="n" rel="next">generic.LANG.html</a>, Previous: <a
href="GNU-News.html#GNU-News" accesskey="p" rel="previous">GNU News</a>, Up: <a
href="PO-Files.html#PO-Files" accesskey="u" rel="up">PO Files</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
+
- </body></html>
+</body>
+</html>
Index: gnun/html_node/Rules.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Rules.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Rules.html 26 Sep 2012 14:49:43 -0000 1.15
+++ gnun/html_node/Rules.html 4 Dec 2012 16:24:23 -0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Rules - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Internals.html#Internals" title="Internals">
-<link rel="prev" href="Scripts.html#Scripts" title="Scripts">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,38 +9,74 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Rules</title>
+
+<meta name="description" content="GNUnited Nations: Rules">
+<meta name="keywords" content="GNUnited Nations: Rules">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Internals.html#Internals" rel="up" title="Internals">
+<link href="Bugs.html#Bugs" rel="next" title="Bugs">
+<link href="gnun_002dclear_002dprevious.html#gnun_002dclear_002dprevious"
rel="previous" title="gnun-clear-previous">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Rules"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="Scripts.html#Scripts">Scripts</a>,
-Up: <a rel="up" accesskey="u"
href="Internals.html#Internals">Internals</a>
-<hr>
+Previous: <a href="Scripts.html#Scripts" accesskey="p"
rel="previous">Scripts</a>, Up: <a href="Internals.html#Internals"
accesskey="u" rel="up">Internals</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-
+<hr>
+<a name="How-The-Recipes-Work"></a>
<h3 class="section">3.2 How The Recipes Work</h3>
<p>Read the source code, then please tell us :-)
+</p>
+
- </body></html>
+</body>
+</html>
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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Runtime-Variables.html 26 Sep 2012 14:49:44 -0000
1.15
+++ gnun/html_node/Runtime-Variables.html 4 Dec 2012 16:24:23 -0000
1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Runtime Variables - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Invoking-GNUN.html#Invoking-GNUN" title="Invoking GNUN">
-<link rel="next" href="Special-Targets.html#Special-Targets" title="Special
Targets">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,180 +9,271 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Runtime Variables</title>
+
+<meta name="description" content="GNUnited Nations: Runtime Variables">
+<meta name="keywords" content="GNUnited Nations: Runtime Variables">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Invoking-GNUN.html#Invoking-GNUN" rel="up" title="Invoking GNUN">
+<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">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Runtime-Variables"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Special-Targets.html#Special-Targets">Special Targets</a>,
-Up: <a rel="up" accesskey="u"
href="Invoking-GNUN.html#Invoking-GNUN">Invoking GNUN</a>
-<hr>
+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>
</div>
-
+<hr>
+<a name="Variables-to-Control-the-Build-Process"></a>
<h4 class="subsection">2.1.1 Variables to Control the Build Process</h4>
+<a name="index-variables"></a>
+<a name="index-variable_002c-behavior"></a>
-<p><a name="index-variables-8"></a><a
name="index-variable_002c-behavior-9"></a>
-The build process has several modes of operation, and they all relate to
+<p>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
performing certain sanity checks at build time. The variables are
-specified on the command line, after <samp><span
class="command">make</span></samp>, in the form
+specified on the command line, after <code>make</code>, in the form
<code>VARIABLE=value</code>, e.g. <code>make VCS=yes</code>. In the future,
additional features will be implemented in a similar fashion.
-
-
-<a name="index-VCS-10"></a>
-<a name="index-CVS-11"></a>
-<a name="index-Subversion-12"></a>
-<a name="index-SVN-13"></a>
-<a name="index-Bazaar-14"></a>
-<a name="index-bzr-15"></a>
-<dl><dt>‘<samp><span
class="samp">VCS=no</span></samp>’<dt>‘<samp><span
class="samp">...</span></samp>’<dd>
-Do not add any files to the repository. This is the default. You may
+</p>
+<dl compact="compact">
+<dd><a name="index-VCS"></a>
+<a name="index-CVS"></a>
+<a name="index-Subversion"></a>
+<a name="index-SVN"></a>
+<a name="index-Bazaar"></a>
+<a name="index-bzr"></a>
+</dd>
+<dt>‘<samp>VCS=no</samp>’</dt>
+<dt>‘<samp>…</samp>’</dt>
+<dd>
+<p>Do not add any files to the repository. This is the default. You may
as well omit to define <code>VCS</code> entirely; there is no special code
-that expects assigning the value `no'.
-
- <br><dt>‘<samp><span
class="samp">VCS=yes</span></samp>’<dd>Automatically add any new files in
the repository (CVS, Subversion or
+that expects assigning the value ‘no’.
+</p>
+</dd>
+<dt>‘<samp>VCS=yes</samp>’</dt>
+<dd><p>Automatically add any new files in the repository (CVS, Subversion or
GNU Bazaar—the repository type is auto-determined at build time,
-<samp><span class="command">bzr</span></samp> being a fallback).<a
rel="footnote" href="#fn-1" name="fnd-1"><sup>1</sup></a> These are
+<code>bzr</code> being a fallback).<a name="DOCF3"
href="#FOOT3"><sup>3</sup></a> These are
any POT files, if they are generated for the first time, and the
-translated articles (<samp><span class="file">.</span><var>lang</var><span
class="file">.html</span></samp>) in HTML format. In
-addition, if there is no <samp><span
class="file">server/gnun/generic.</span><var>lang</var><span
class="file">.html</span></samp> file
+translated articles (<samp>.<var>lang</var>.html</samp>) in HTML format. In
+addition, if there is no <samp>server/gnun/generic.<var>lang</var>.html</samp>
file
for the specific language an article is being generated, an empty file
will be added. Finally, any missing PO and their HTML counterparts of
the server templates will be added, computed on the basis of the
-<code>template-files</code> variable.
-
- <br><dt>‘<samp><span
class="samp">VCS=always</span></samp>’<dd>Because GNU Make considers the
targets up-to-date after a successful
+<code>extra-templates</code> and <code>optional-templates</code> variables.
+</p>
+</dd>
+<dt>‘<samp>VCS=always</samp>’</dt>
+<dd><p>Because GNU Make considers the targets up-to-date after a successful
build, if it was performed with no VCS interaction, the important newly
created files will not be added (and committed when you do
<code>cvs|svn|bzr commit</code>) in the repository. Assigning this value
enables additional check and forcefully adds all files. Use it
sparingly, since it is very slow and generally less reliable.
-
- <p><a name="index-VALIDATE-16"></a><a name="index-validation-17"></a><a
name="index-sanity-checks-18"></a><br><dt>‘<samp><span
class="samp">VALIDATE=no</span></samp>’<dt>‘<samp><span
class="samp">...</span></samp>’<dd>Does not perform validation of the
HTML articles and PO files. This
+</p>
+<a name="index-VALIDATE"></a>
+<a name="index-validation"></a>
+<a name="index-sanity-checks"></a>
+</dd>
+<dt>‘<samp>VALIDATE=no</samp>’</dt>
+<dt>‘<samp>…</samp>’</dt>
+<dd><p>Does not perform validation of the HTML articles and PO files. This
is the default, and not defining this variable has the same effect.
-
- <br><dt>‘<samp><span
class="samp">VALIDATE=yes</span></samp>’<dd>Validates all original
articles before generating the POTs, to ensure
+</p>
+</dd>
+<dt>‘<samp>VALIDATE=yes</samp>’</dt>
+<dd><p>Validates all original articles before generating the POTs, to ensure
that the ultimate source is valid (X)HMTL. Also, validates all
generated translations in HTML format and all PO files. It is highly
recommended to run the build this way, even if it is a bit tedious to
fix the errors that are reported as a result of enforcing validation.
-
- <p>Articles defined in the variable <code>no-validate-articles</code> are
never
+</p>
+<p>Articles defined in the variable <code>no-validate-articles</code> are never
checked for HTML validity. Its purpose was to skip validation of HTML
5 articles, until the command-line validation tools are updated to
parse files that comply with this new standard. As of version 0.5
GNUN supports HTML 5, so resorting to <code>no-validate-articles</code>
should not be necessary.
-
- <p><a name="index-NOTIFY-19"></a><a
name="index-mail_002c-notifications-20"></a><br><dt>‘<samp><span
class="samp">NOTIFY=no</span></samp>’<dt>‘<samp><span
class="samp">...</span></samp>’<dd>Do not send email notifications about
errors. This is the default.
-
- <br><dt>‘<samp><span
class="samp">NOTIFY=yes</span></samp>’<dd>If an error occurs, send a mail
with a meaningful subject and the error
+</p>
+<a name="index-NOTIFY"></a>
+<a name="index-mail_002c-notifications"></a>
+</dd>
+<dt>‘<samp>NOTIFY=no</samp>’</dt>
+<dt>‘<samp>…</samp>’</dt>
+<dd><p>Do not send email notifications about errors. This is the default.
+</p>
+</dd>
+<dt>‘<samp>NOTIFY=yes</samp>’</dt>
+<dd><p>If an error occurs, send a mail with a meaningful subject and the error
message as body to the concerned party. The variables
<code>devel-addr</code>, <code>web-addr</code> and <code>transl-addr</code>
control the
recipients; normally they should be set to the GNUN maintainers,
webmasters and translators accordingly. These variables are defined in
-the configuration file <samp><span class="file">gnun.conf</span></samp> and by
default are set to
+the configuration file <samp>gnun.conf</samp> and by default are set to
<a href="mailto:address@hidden";>address@hidden</a>.
-
- <p><a
name="index-new-translations_002c-notifications_002fannouncements-21"></a><a
name="index-announce-22"></a><br><dt>‘<samp><span
class="samp">ANNOUNCE=yes</span></samp>’<dd>If defined, automatic
announcements for new translations will be sent to
+</p>
+<a name="index-new-translations_002c-notifications_002fannouncements"></a>
+<a name="index-announce"></a>
+</dd>
+<dt>‘<samp>ANNOUNCE=yes</samp>’</dt>
+<dd><p>If defined, automatic announcements for new translations will be sent to
the address defined in the <code>ann-addr</code> variable (in
-<samp><span class="file">gnun.conf</span></samp>). The email messages contain
the translated article
+<samp>gnun.conf</samp>). The email messages contain the translated article
title as Subject, and the URL of the translation as its body. For the
official GNUN build, they are delivered to the
<a href="mailto:address@hidden";>address@hidden</a> mailing list and each
language has its
-own Mailman <dfn>topic</dfn>. It is possible to subscribe to the list and
-receive only traffic related to a specific language. See <a
href="../web-trans/Mailing-Lists.html#Mailing-Lists">Mailing Lists</a>.
-
- <p>The default behavior is not to send such announcements.
-
- <p><a name="index-VERBOSE-23"></a><a
name="index-output_002c-detailed-24"></a><br><dt>‘<samp><span
class="samp">VERBOSE=yes</span></samp>’<dd>If defined, the value of the
variables <code>templates-translated</code>,
-<code>home-translated</code>, <code>ALL_POTS</code>,
<code>articles-translated</code> and
+own Mailman <em>topic</em>. It is possible to subscribe to the list and
+receive only traffic related to a specific language. See <a
href="http://www.gnu.org/software/trans-coord/manual/web-trans/html_node/Mailing-Lists.html#Mailing-Lists";>Mailing
+Lists</a> in <cite>GNU Web Translators Manual</cite>.
+</p>
+<p>The default behavior is not to send such announcements.
+</p>
+<a name="index-VERBOSE"></a>
+<a name="index-output_002c-detailed"></a>
+</dd>
+<dt>‘<samp>VERBOSE=yes</samp>’</dt>
+<dd><p>If defined, the value of the variables
<code>templates-translated</code>,
+<code>ALL_POTS</code>, <code>articles-translated</code> and
<code>gnunews</code> will be printed to the standard output. This is off by
default, but recommended in general since it will show a bug in the
computation of the basic variables.
-
- <p><a name="index-GRACE-25"></a><a name="index-fuzzy-strings-26"></a><a
name="index-grace-period-27"></a><a
name="index-deferred-generation-of-articles-28"></a><a
name="GRACE"></a><br><dt>‘<samp><span
class="samp">GRACE=</span><var>days</var></samp>’<dd>If defined, ordinary
articles that have fuzzy strings and are not older
+</p>
+<a name="index-GRACE"></a>
+<a name="index-fuzzy-strings"></a>
+<a name="index-grace-period"></a>
+<a name="index-deferred-generation-of-articles"></a>
+<a name="GRACE"></a></dd>
+<dt>‘<samp>GRACE=<var>days</var></samp>’</dt>
+<dd><p>If defined, ordinary articles that have fuzzy strings and are not older
than <var>days</var> will not be regenerated. This functionality is
implemented specifically to prevent gratuitous replacement of translated
strings with the English text when there are only minor formatting
changes in the original. The translator has time (the “grace”
period
as defined in this variable) to review the changes and unfuzzy the
strings, while keeping the online translation intact. Note that this
-variable has no effect on the homepage, the server templates, gnunews
+variable has no effect on the server templates, gnunews
and all articles defined in the variable <code>no-grace-articles</code>.
-
- <p><a name="index-OUTDATED_002dGRACE-29"></a><br><dt>‘<samp><span
class="samp">OUTDATED-GRACE=</span><var>days</var></samp>’<dd>Grace
period for the out-of-date notice. When the variable
+</p>
+<a name="index-OUTDATED_002dGRACE"></a>
+</dd>
+<dt>‘<samp>OUTDATED-GRACE=<var>days</var></samp>’</dt>
+<dd><p>Grace period for the out-of-date notice. When the variable
<code>GRACE</code> is defined, <code>OUTDATED-GRACE</code> defaults to 60 days
-(see <a href="GRACE.html#GRACE">grace period</a>). The out-of-date notice is
a special
-text (<samp><span class="file">server/outdated.html</span></samp> in the `www'
repository) that is
+(see <a href="#GRACE">grace period</a>). The out-of-date notice is a special
+text (<samp>server/outdated.html</samp> in the ‘www’ repository)
that is
inserted into every outdated translation when the period defined in
this variable is over; its purpose is to inform the reader that the
translation may not correspond to the original English article.
-
- <p><a name="index-TEAM-30"></a><a
name="index-variable_002c-team-31"></a><br><dt>‘<samp><span
class="samp">TEAM=</span><var>lang</var></samp>’<dd>The translation team
whose articles need to be checked for
+</p>
+<a name="index-TEAM"></a>
+<a name="index-variable_002c-team"></a>
+</dd>
+<dt>‘<samp>TEAM=<var>lang</var></samp>’</dt>
+<dd><p>The translation team whose articles need to be checked for
completeness. This variable is applicable only for the <code>report</code>
target, and is mandatory for it. See <a href="report.html#report">report</a>.
+</p>
+</dd>
+</dl>
- </dl>
-
- <p>Note that <code>VCS=yes,always</code> is a valid combination: because POT
+<p>Note that <code>VCS=yes,always</code> is a valid combination: because POT
files of the server templates are not handled by <code>always</code>, running
the build this way will commit any newly added files as specified in
<code>TEMPLATE_LINGUAS</code> and will perform additional check at the end,
<code>cvs|svn|bzr add</code>-ing all necessary files.
-
- <p><a name="index-validation-32"></a>When validation is enabled (i.e. with
<code>VALIDATE=yes</code>), the
+</p>
+<a name="index-validation-1"></a>
+<p>When validation is enabled (i.e. with <code>VALIDATE=yes</code>), the
original English articles are validated first, before any commands
-that generate the other files, and <samp><span
class="command">make</span></samp> exits with an error
+that generate the other files, and <code>make</code> exits with an error
on the first encountered article. This is done on purpose, to prevent
the propagation of an eventual error in the markup of the original
article to all translations.
-
- <p>Validation of the translated <samp><span
class="file">.</span><var>lang</var><span class="file">.html</span></samp> is
+</p>
+<p>Validation of the translated <samp>.<var>lang</var>.html</samp> is
performed after it is preliminarily generated as a temporary file.
When no errors are found, the translation is updated; otherwise
the real file is not changed (and it is not added if absent)—the build
will fail and further processing of the remaining articles will not be
performed. The translator has time
until the next run to fix the error—usually by modifying the
-corresponding <samp><span class="file">.</span><var>lang</var><span
class="file">.po</span></samp> file.
-
- <p>If notification is enabled (<code>NOTIFY=yes</code>), and the build
system
+corresponding <samp>.<var>lang</var>.po</samp> file.
+</p>
+<p>If notification is enabled (<code>NOTIFY=yes</code>), and the build system
encounters errors (mostly when validating articles), email messages
will be sent to the party that is expected to fix the error. The
subject of the messages always includes the problematic article, for
example:
+</p>
+<div class="example">
+<pre class="example">Subject: [GNUN Error] gnu/gnu.fa.html is not valid HTML
+</pre></div>
-<pre class="example"> Subject: [GNUN Error] gnu/gnu.fa.html is not valid
HTML
-</pre>
- <div class="footnote">
+<div class="footnote">
<hr>
-<h4>Footnotes</h4><p class="footnote"><small>[<a name="fn-1"
href="#fnd-1">1</a>]</small> When GNU Bzr is used, files
-are added locally only; you need to take care to use <samp><span
class="command">bzr push</span></samp>
+<h4 class="footnotes-heading">Footnotes</h4>
+
+<h3><a name="FOOT3" href="#DOCF3">(3)</a></h3>
+<p>When GNU Bzr is used, files
+are added locally only; you need to take care to use <code>bzr push</code>
manually (or via cron) to take care of effectively adding them to the
public repository. See <a href="triggers.html#triggers">triggers</a>, for a
short explanation.</p>
+</div>
+<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>
+</div>
- <hr></div>
- </body></html>
+</body>
+</html>
Index: gnun/html_node/Scripts.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Scripts.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Scripts.html 26 Sep 2012 14:49:44 -0000 1.15
+++ gnun/html_node/Scripts.html 4 Dec 2012 16:24:23 -0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Scripts - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Internals.html#Internals" title="Internals">
-<link rel="next" href="Rules.html#Rules" title="Rules">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,35 +9,68 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Scripts</title>
+
+<meta name="description" content="GNUnited Nations: Scripts">
+<meta name="keywords" content="GNUnited Nations: Scripts">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Internals.html#Internals" rel="up" title="Internals">
+<link
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff"
rel="next" title="gnun-add-fuzzy-diff">
+<link href="Internals.html#Internals" rel="previous" title="Internals">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Scripts"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="Rules.html#Rules">Rules</a>,
-Up: <a rel="up" accesskey="u"
href="Internals.html#Internals">Internals</a>
-<hr>
+Next: <a href="Rules.html#Rules" accesskey="n" rel="next">Rules</a>, Up: <a
href="Internals.html#Internals" accesskey="u" rel="up">Internals</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-
+<hr>
+<a name="GNUN-Scripts"></a>
<h3 class="section">3.1 GNUN Scripts</h3>
<p>For the time being there are several helper scripts. Some of them are
@@ -53,20 +78,34 @@
rules; other scripts were written specifically to facilitate some
mechanical actions, like initially filling the headers in the PO files.
They all can be invoked separately, as stand-alone programs.
-
-<ul class="menu">
-<li><a accesskey="1"
href="make_002dprototype.html#make_002dprototype">make-prototype</a>
-<li><a accesskey="2"
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff">gnun-add-fuzzy-diff</a>:
Add differences to previous
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff"
accesskey="1">gnun-add-fuzzy-diff</a>:</td><td> </td><td
align="left" valign="top">Add differences to previous
<code>msgid</code>s.
-<li><a accesskey="3"
href="gnun_002dinit_002dpo.html#gnun_002dinit_002dpo">gnun-init-po</a>:
Initialize a new translation.
-<li><a accesskey="4"
href="gnun_002dpreconvert.html#gnun_002dpreconvert">gnun-preconvert</a>:
Invoke the first step in converting
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="gnun_002ddiff_002dpo.html#gnun_002ddiff_002dpo"
accesskey="2">gnun-diff-po</a>:</td><td> </td><td align="left"
valign="top">Compare two revisions of a PO file.
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="gnun_002dinit_002dpo.html#gnun_002dinit_002dpo"
accesskey="3">gnun-init-po</a>:</td><td> </td><td align="left"
valign="top">Initialize a new translation.
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="gnun_002dpreconvert.html#gnun_002dpreconvert"
accesskey="4">gnun-preconvert</a>:</td><td> </td><td align="left"
valign="top">Invoke the first step in converting
HTML translation to PO format.
-<li><a accesskey="5"
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a>:
Run the second step of the conversion.
-<li><a accesskey="6"
href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml">gnun-validate-html</a>:
Validate HTML file.
-<li><a accesskey="7" href="mailfail.html#mailfail">mailfail</a>
-<li><a accesskey="8"
href="validate_002dhtml_002dnotify.html#validate_002dhtml_002dnotify">validate-html-notify</a>
-<li><a accesskey="9"
href="gnun_002dclear_002dprevious.html#gnun_002dclear_002dprevious">gnun-clear-previous</a>
-</ul>
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted"
accesskey="5">gnun-merge-preconverted</a>:</td><td> </td><td
align="left" valign="top">Run the second step of the conversion.
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="gnun_002dreport.html#gnun_002dreport"
accesskey="6">gnun-report</a>:</td><td> </td><td align="left"
valign="top">Generate report in HTML format.
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml"
accesskey="7">gnun-validate-html</a>:</td><td> </td><td align="left"
valign="top">Validate HTML file.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="mailfail.html#mailfail"
accesskey="8">mailfail</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="validate_002dhtml_002dnotify.html#validate_002dhtml_002dnotify"
accesskey="9">validate-html-notify</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="gnun_002dclear_002dprevious.html#gnun_002dclear_002dprevious">gnun-clear-previous</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+</table>
+
+
- </body></html>
+</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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Special-Targets.html 26 Sep 2012 14:49:44 -0000 1.15
+++ gnun/html_node/Special-Targets.html 4 Dec 2012 16:24:23 -0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Special Targets - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Invoking-GNUN.html#Invoking-GNUN" title="Invoking GNUN">
-<link rel="prev" href="Runtime-Variables.html#Runtime-Variables"
title="Runtime Variables">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,52 +9,94 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Special Targets</title>
+
+<meta name="description" content="GNUnited Nations: Special Targets">
+<meta name="keywords" content="GNUnited Nations: Special Targets">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Invoking-GNUN.html#Invoking-GNUN" rel="up" title="Invoking GNUN">
+<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">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Special-Targets"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="Runtime-Variables.html#Runtime-Variables">Runtime Variables</a>,
-Up: <a rel="up" accesskey="u"
href="Invoking-GNUN.html#Invoking-GNUN">Invoking GNUN</a>
-<hr>
+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>
</div>
-
+<hr>
+<a name="Targets-Specified-on-the-Command-Line"></a>
<h4 class="subsection">2.1.2 Targets Specified on the Command Line</h4>
<p>Some targets are not built by default, because they are only useful
under certain circumstances. Think of them like semi-automated
commands or canned command sequences that are more complicated, and
more importantly, whose arguments are variables computed at the time
-<samp><span class="command">make</span></samp> reads the makefiles—the
filesets they affect are
+<code>make</code> reads the makefiles—the filesets they affect are
specific and already defined, one way or another.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a
href="no_002dgrace_002ditems.html#no_002dgrace_002ditems"
accesskey="1">no-grace-items</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="update_002dlocalized_002dURLs.html#update_002dlocalized_002dURLs"
accesskey="2">update-localized-URLs</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="sync.html#sync"
accesskey="3">sync</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="report.html#report"
accesskey="4">report</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="triggers.html#triggers"
accesskey="5">triggers</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="validate_002dall.html#validate_002dall"
accesskey="6">validate-all</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+</table>
+
-<ul class="menu">
-<li><a accesskey="1"
href="no_002dgrace_002ditems.html#no_002dgrace_002ditems">no-grace-items</a>
-<li><a accesskey="2"
href="update_002dlocalized_002dURLs.html#update_002dlocalized_002dURLs">update-localized-URLs</a>
-<li><a accesskey="3" href="sync.html#sync">sync</a>
-<li><a accesskey="4" href="report.html#report">report</a>
-<li><a accesskey="5" href="triggers.html#triggers">triggers</a>
-<li><a accesskey="6"
href="validate_002dall.html#validate_002dall">validate-all</a>
-</ul>
- </body></html>
+</body>
+</html>
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.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- gnun/html_node/Splitting-Long-Passages.html 26 Sep 2012 14:49:44 -0000
1.1
+++ gnun/html_node/Splitting-Long-Passages.html 4 Dec 2012 16:24:23 -0000
1.2
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Splitting Long Passages - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Webmaster-Tips.html#Webmaster-Tips" title="Webmaster
Tips">
-<link rel="prev" href="Localized-URLs.html#Localized-URLs" title="Localized
URLs">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,58 +9,97 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Splitting Long Passages</title>
+
+<meta name="description" content="GNUnited Nations: Splitting Long Passages">
+<meta name="keywords" content="GNUnited Nations: Splitting Long Passages">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Webmaster-Tips.html#Webmaster-Tips" rel="up" title="Webmaster
Tips">
+<link href="Internals.html#Internals" rel="next" title="Internals">
+<link href="Localized-URLs.html#Localized-URLs" rel="previous"
title="Localized URLs">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Splitting-Long-Passages"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="Localized-URLs.html#Localized-URLs">Localized URLs</a>,
-Up: <a rel="up" accesskey="u"
href="Webmaster-Tips.html#Webmaster-Tips">Webmaster Tips</a>
-<hr>
+Previous: <a href="Localized-URLs.html#Localized-URLs" accesskey="p"
rel="previous">Localized URLs</a>, Up: <a
href="Webmaster-Tips.html#Webmaster-Tips" accesskey="u" rel="up">Webmaster
Tips</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="Splitting-Long-Passages-1"></a>
<h4 class="subsection">2.4.5 Splitting Long Passages</h4>
+<a name="index-long-passages_002c-avoiding"></a>
+<a name="index-conventional-separator-for-strings"></a>
-<p><a name="index-long-passages_002c-avoiding-103"></a><a
name="index-conventional-separator-for-strings-104"></a>
-GNUN splits typical text by paragraphs, and translators write the
+<p>GNUN splits typical text by paragraphs, and translators write the
translations for the resulting parts of the text one by one. When a
part is too long, it is hard to translate and proofread the translation;
the likelihood of skipping some phrases is relatively high.
-
- <p>In order to make our translators' life easier, it is desirable to keep
+</p>
+<p>In order to make our translators’ life easier, it is desirable to keep
the paragraphs short (no more than 350–700 characters). If rearranging
the paragraphs is not an option, you can use a conventional separator,
-<code><span class="gnun-split"></span></code>:
+<code><span class="gnun-split"></span></code>:
+</p>
+<div class="example">
+<pre class="example"><p>GNUN splits typical text by paragraphs, and
translators write
+the translations for the resulting parts of the text
+one by one. <span class="gnun-split"></span> When a part
+is too long, it is hard to translate and proofread the translation;
+the likelihood of skipping some phrases is relatively high.</p>
+</pre></div>
-<pre class="example"> <p>GNUN splits typical text by paragraphs, and
translators write
- the translations for the resulting parts of the text
- one by one. <span class="gnun-split"></span> When a part
- is too long, it is hard to translate and proofread the translation;
- the likelihood of skipping some phrases is relatively high.</p>
-</pre>
- <p>It is important that the separator be inserted between complete
+<p>It is important that the separator be inserted between complete
sentences, because different languages may require different orders
of parts of the sentence, and the translator has no control over
the sequence of the strings in the translation.
+</p>
+
- </body></html>
+</body>
+</html>
Index: gnun/html_node/Usage.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Usage.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Usage.html 26 Sep 2012 14:49:44 -0000 1.15
+++ gnun/html_node/Usage.html 4 Dec 2012 16:24:23 -0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Usage - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Introduction.html#Introduction" title="Introduction">
-<link rel="next" href="Internals.html#Internals" title="Internals">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,74 +9,109 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Usage</title>
+
+<meta name="description" content="GNUnited Nations: Usage">
+<meta name="keywords" content="GNUnited Nations: Usage">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Invoking-GNUN.html#Invoking-GNUN" rel="next" title="Invoking GNUN">
+<link href="Disadvantages.html#Disadvantages" rel="previous"
title="Disadvantages">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Usage"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Internals.html#Internals">Internals</a>,
-Previous: <a rel="previous" accesskey="p"
href="Introduction.html#Introduction">Introduction</a>,
-Up: <a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+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>
</div>
-
+<hr>
+<a name="General-Usage"></a>
<h2 class="chapter">2 General Usage</h2>
-<div align="right">If anything may go wrong, it will definitely go wrong.
- <p>—Murphy's Law
-
- <p>Murphy is an optimist.
- <p>—O'Rielly's Law
-</div>
-
- <pre class="sp">
-
-</pre>
+<p align="right">If anything may go wrong, it will definitely go wrong.
+—Murphy’s Law
+</p>
+<p align="right">Murphy is an optimist.
+—O’Rielly’s Law
+</p><br>
-GNUN currently consists of a few makefiles, scripts and optional
-<samp><span class="file">generic.</span><var>lang</var><span
class="file">.html</span></samp> files, intended to contain
+<p>GNUN currently consists of a few makefiles, scripts and optional
+<samp>generic.<var>lang</var>.html</samp> files, intended to contain
article-independent but team-specific information. They are designed
-to reside in the <samp><span class="file">server/gnun</span></samp> directory,
but this may change.
+to reside in the <samp>server/gnun</samp> directory, but this may change.
In all examples in this manual, “invoking” means executing on the
-command line <code>make -C server/gnun [</code><var>target</var><code>]
-[</code><var>variable</var><code>=</code><var>value</var><code> ...]</code>
while the working directory is
-the root in the `www' web repository. For the purpose of brevity, we
-will refer to the above command as simply <samp><span
class="command">make</span></samp>, which is
+command line <code>make -C server/gnun [<var>target</var>]
+[<var>variable</var>=<var>value</var> …]</code> while the working
directory is
+the root in the ‘www’ web repository. For the purpose of brevity,
we
+will refer to the above command as simply <code>make</code>, which is
equivalent to <code>cd server/gnun; make</code>. It is desirable never to
-invoke <samp><span class="command">make</span></samp> with the <samp><span
class="option">-k</span></samp> (<samp><span
class="option">--keep-going</span></samp>)
+invoke <code>make</code> with the <samp>-k</samp> (<samp>--keep-going</samp>)
option, because an eventual error in only one make recipe might create
a mess in many articles, both original and translated. Do this with
caution, and generally only when debugging in a safe environment.
-
- <p>The build process is intended to be invoked by a cron job, although
+</p>
+<p>The build process is intended to be invoked by a cron job, although
manual intervention to a certain degree is possible.
-
-<ul class="menu">
-<li><a accesskey="1" href="Invoking-GNUN.html#Invoking-GNUN">Invoking
GNUN</a>: How to trigger a (re)build.
-<li><a accesskey="2" href="Main-Variables.html#Main-Variables">Main
Variables</a>: Specifying what to build.
-<li><a accesskey="3" href="PO-Files.html#PO-Files">PO Files</a>:
The gentle art of editing PO files.
-<li><a accesskey="4" href="Webmaster-Tips.html#Webmaster-Tips">Webmaster
Tips</a>: The webmaster's guide to GNUnited Nations'
+</p>
+<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.
+</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.
+</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.
-</ul>
+</td></tr>
+</table>
+
+
- </body></html>
+</body>
+</html>
Index: gnun/html_node/Validation.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/Validation.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- gnun/html_node/Validation.html 26 Sep 2012 14:49:44 -0000 1.5
+++ gnun/html_node/Validation.html 4 Dec 2012 16:24:23 -0000 1.6
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Validation - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Webmaster-Tips.html#Webmaster-Tips" title="Webmaster
Tips">
-<link rel="next" href="Comments-for-Translators.html#Comments-for-Translators"
title="Comments for Translators">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,46 +9,84 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Validation</title>
+
+<meta name="description" content="GNUnited Nations: Validation">
+<meta name="keywords" content="GNUnited Nations: Validation">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Webmaster-Tips.html#Webmaster-Tips" rel="up" title="Webmaster
Tips">
+<link href="Comments-for-Translators.html#Comments-for-Translators" rel="next"
title="Comments for Translators">
+<link href="Webmaster-Tips.html#Webmaster-Tips" rel="previous"
title="Webmaster Tips">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Validation"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Comments-for-Translators.html#Comments-for-Translators">Comments for
Translators</a>,
-Up: <a rel="up" accesskey="u"
href="Webmaster-Tips.html#Webmaster-Tips">Webmaster Tips</a>
-<hr>
+Next: <a href="Comments-for-Translators.html#Comments-for-Translators"
accesskey="n" rel="next">Comments for Translators</a>, Up: <a
href="Webmaster-Tips.html#Webmaster-Tips" accesskey="u" rel="up">Webmaster
Tips</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="Validation-1"></a>
<h4 class="subsection">2.4.1 Validation</h4>
+<a name="index-validation-3"></a>
-<p><a name="index-validation-99"></a>
-The script <samp><span class="command">gnun-validate-html</span></samp> is
useful for webmasters who
+<p>The script <code>gnun-validate-html</code> is useful for webmasters who
want to verify if their (potentially intrusive) changes result in a
valid markup. Before committing your changes, you can check whether
the file is valid by running
+</p>
+<div class="example">
+<pre class="example">gnun-validate-html --root . philosophy/not-ipr.html
+</pre></div>
+
+<p>See <a
href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml">gnun-validate-html</a>,
for more information.
+</p>
-<pre class="example"> gnun-validate-html --root . philosophy/not-ipr.html
-</pre>
- <p>See <a
href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml">gnun-validate-html</a>,
for more information.
- </body></html>
+</body>
+</html>
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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/Webmaster-Tips.html 26 Sep 2012 14:49:44 -0000 1.15
+++ gnun/html_node/Webmaster-Tips.html 4 Dec 2012 16:24:23 -0000 1.16
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>Webmaster Tips - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Usage.html#Usage" title="Usage">
-<link rel="prev" href="PO-Files.html#PO-Files" title="PO Files">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,62 +9,104 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Webmaster Tips</title>
+
+<meta name="description" content="GNUnited Nations: Webmaster Tips">
+<meta name="keywords" content="GNUnited Nations: Webmaster Tips">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Usage.html#Usage" rel="up" title="Usage">
+<link href="Validation.html#Validation" rel="next" title="Validation">
+<link href="Compendia.html#Compendia" rel="previous" title="Compendia">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Webmaster-Tips"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="PO-Files.html#PO-Files">PO Files</a>,
-Up: <a rel="up" accesskey="u" href="Usage.html#Usage">Usage</a>
-<hr>
+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>
</div>
-
+<hr>
+<a name="Tips-and-Hints-for-Webmasters"></a>
<h3 class="section">2.4 Tips and Hints for Webmasters</h3>
+<a name="index-tips_002c-webmasters"></a>
+<a name="index-webmaster-tips"></a>
-<p><a name="index-tips_002c-webmasters-97"></a><a
name="index-webmaster-tips-98"></a>
-This section contains some tips and general recommendations for
+<p>This section contains some tips and general recommendations for
webmasters in no particular order—it is not mandatory to follow them,
-but doing so will make translators' lives substantially easier.
-
- <p>First and foremost, respect translators' work—it is ungrateful and
+but doing so will make translators’ lives substantially easier.
+</p>
+<p>First and foremost, respect translators’ work—it is ungrateful
and
hard, undoubtedly much harder than translation of programs. It is
important to have as many and as better as possible translations, and
-you don't have to make titanic efforts to help.
-
- <p>If you plan to edit a certain page extensively, please do so within the
+you don’t have to make titanic efforts to help.
+</p>
+<p>If you plan to edit a certain page extensively, please do so within the
period between two adjacent GNUN builds—i.e. within a day. That way,
the POT will be regenerated only once, and translators who are quick to
-update it immediately won't be disappointed if it changes again in the
+update it immediately won’t be disappointed if it changes again in the
next run.
-
-<ul class="menu">
-<li><a accesskey="1" href="Validation.html#Validation">Validation</a>:
How to verify the documents.
-<li><a accesskey="2"
href="Comments-for-Translators.html#Comments-for-Translators">Comments for
Translators</a>: Passing comments to translators.
-<li><a accesskey="3"
href="Modifying-Boilerplates.html#Modifying-Boilerplates">Modifying
Boilerplates</a>
-<li><a accesskey="4" href="Localized-URLs.html#Localized-URLs">Localized
URLs</a>: Specifying URLs of diagrams
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="Validation.html#Validation"
accesskey="1">Validation</a>:</td><td> </td><td align="left"
valign="top">How to verify the documents.
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Comments-for-Translators.html#Comments-for-Translators"
accesskey="2">Comments for Translators</a>:</td><td> </td><td
align="left" valign="top">Passing comments to translators.
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Modifying-Boilerplates.html#Modifying-Boilerplates"
accesskey="3">Modifying Boilerplates</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Localized-URLs.html#Localized-URLs" accesskey="4">Localized
URLs</a>:</td><td> </td><td align="left" valign="top">Specifying
URLs of diagrams
to be translated.
-<li><a accesskey="5"
href="Splitting-Long-Passages.html#Splitting-Long-Passages">Splitting Long
Passages</a>: How to avoid too long strings
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Splitting-Long-Passages.html#Splitting-Long-Passages"
accesskey="5">Splitting Long Passages</a>:</td><td> </td><td
align="left" valign="top">How to avoid too long strings
in PO files.
-</ul>
+</td></tr>
+</table>
+
+
- </body></html>
+</body>
+</html>
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.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- gnun/html_node/extra_002dtemplates.html 26 Sep 2012 14:49:44 -0000
1.1
+++ gnun/html_node/extra_002dtemplates.html 4 Dec 2012 16:24:23 -0000
1.2
@@ -1 +1,65 @@
-<meta http-equiv="refresh" content="0;
url=Main-Variables.html#extra%2dtemplates">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!--
+This manual (updated 3 December 2012) is for GNUnited Nations (version
+0.6), a suite for maintaining translations of www.gnu.org
+essays and other articles.
+
+
+Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- This file redirects to the location of a node or anchor -->
+<head>
+<title>GNUnited Nations: extra-templates</title>
+
+<meta name="description" content="GNUnited Nations: extra-templates">
+<meta name="keywords" content="GNUnited Nations: extra-templates">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+<meta http-equiv="Refresh" content="0;
url=Main-Variables.html#extra_002dtemplates">
+
+</head>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+
+<p>The node you are looking for is at <a
href="Main-Variables.html#extra_002dtemplates">extra-templates</a>.</p>
+</body>
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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/generic_002eLANG_002ehtml.html 26 Sep 2012 14:49:44
-0000 1.15
+++ gnun/html_node/generic_002eLANG_002ehtml.html 4 Dec 2012 16:24:23
-0000 1.16
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>generic.LANG.html - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="PO-Files.html#PO-Files" title="PO Files">
-<link rel="prev" href="PO-Tips.html#PO-Tips" title="PO Tips">
-<link rel="next" href="languages_002etxt.html#languages_002etxt"
title="languages.txt">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,62 +9,99 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: generic.LANG.html</title>
+
+<meta name="description" content="GNUnited Nations: generic.LANG.html">
+<meta name="keywords" content="GNUnited Nations: generic.LANG.html">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="PO-Files.html#PO-Files" rel="up" title="PO Files">
+<link href="languages_002etxt.html#languages_002etxt" rel="next"
title="languages.txt">
+<link href="PO-Tips.html#PO-Tips" rel="previous" title="PO Tips">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
-<a name="generic.LANG.html"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="generic_002eLANG_002ehtml"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="languages_002etxt.html#languages_002etxt">languages.txt</a>,
-Previous: <a rel="previous" accesskey="p" href="PO-Tips.html#PO-Tips">PO
Tips</a>,
-Up: <a rel="up" accesskey="u" href="PO-Files.html#PO-Files">PO Files</a>
-<hr>
+Next: <a href="languages_002etxt.html#languages_002etxt" accesskey="n"
rel="next">languages.txt</a>, Previous: <a href="PO-Tips.html#PO-Tips"
accesskey="p" rel="previous">PO Tips</a>, Up: <a href="PO-Files.html#PO-Files"
accesskey="u" rel="up">PO Files</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
+<hr>
+<a name="The-generic_002elang_002ehtml-File"></a>
+<h4 class="subsection">2.3.5 The <samp>generic.<var>lang</var>.html</samp>
File</h4>
+<a name="index-team-information"></a>
+<a name="index-generic-notice_002c-translations"></a>
-<h4 class="subsection">2.3.5 The <samp><span
class="file">generic.</span><var>lang</var><span
class="file">.html</span></samp> File</h4>
-
-<p><a name="index-team-information-83"></a><a
name="index-generic-notice_002c-translations-84"></a>
-The files <samp><span
class="file">server/gnun/generic.</span><var>lang</var><span
class="file">.html</span></samp> are special: if
+<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>
-<pre class="example"> <p>To join the Fooish translation team, see
<a
- href="http://gnu.org/server/standards/translations/www-foo">the
- Foo team homepage</a>.</p>
-</pre>
- <p>The contents of <samp><span
class="file">generic.</span><var>lang</var><span
class="file">.html</span></samp> is injected right after
-the translators' credits, if any, and before the timestamp. It should
+<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>When you modify this file, for example, adding a message to the
+</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><span class="file">generic.</span><var>lang</var><span
class="file">.html</span></samp>. The next time a build occurs, all
+<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><span class="file">.</span><var>lang</var><span
class="file">.html</span></samp>, including the homepage), will be modified to
+<samp>.<var>lang</var>.html</samp>, including the homepage), will be modified
to
include the contents of this special file.
+</p>
+
- </body></html>
+</body>
+</html>
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.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- gnun/html_node/gnun_002dadd_002dfuzzy_002ddiff.html 26 Sep 2012 14:49:44
-0000 1.5
+++ gnun/html_node/gnun_002dadd_002dfuzzy_002ddiff.html 4 Dec 2012 16:24:23
-0000 1.6
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>gnun-add-fuzzy-diff - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Scripts.html#Scripts" title="Scripts">
-<link rel="prev" href="make_002dprototype.html#make_002dprototype"
title="make-prototype">
-<link rel="next" href="gnun_002dinit_002dpo.html#gnun_002dinit_002dpo"
title="gnun-init-po">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,55 +9,98 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: gnun-add-fuzzy-diff</title>
+
+<meta name="description" content="GNUnited Nations: gnun-add-fuzzy-diff">
+<meta name="keywords" content="GNUnited Nations: gnun-add-fuzzy-diff">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Scripts.html#Scripts" rel="up" title="Scripts">
+<link href="gnun_002ddiff_002dpo.html#gnun_002ddiff_002dpo" rel="next"
title="gnun-diff-po">
+<link href="Scripts.html#Scripts" rel="previous" title="Scripts">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
-<a name="gnun-add-fuzzy-diff"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="gnun_002dadd_002dfuzzy_002ddiff"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="gnun_002dinit_002dpo.html#gnun_002dinit_002dpo">gnun-init-po</a>,
-Previous: <a rel="previous" accesskey="p"
href="make_002dprototype.html#make_002dprototype">make-prototype</a>,
-Up: <a rel="up" accesskey="u" href="Scripts.html#Scripts">Scripts</a>
-<hr>
+Next: <a href="gnun_002ddiff_002dpo.html#gnun_002ddiff_002dpo" accesskey="n"
rel="next">gnun-diff-po</a>, Up: <a href="Scripts.html#Scripts" accesskey="u"
rel="up">Scripts</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-gnun_002dadd_002dfuzzy_002ddiff-Script"></a>
+<h4 class="subsection">3.1.1 The <code>gnun-add-fuzzy-diff</code> Script</h4>
+<a name="index-previous_002c-diff-1"></a>
-<h4 class="subsection">3.1.2 The <samp><span
class="command">gnun-add-fuzzy-diff</span></samp> Script</h4>
-
-<p><a name="index-previous_002c-diff-108"></a>
-This script adds comments with differences of current <code>msgid</code>s
+<p>This script adds comments with differences of current <code>msgid</code>s
against previous ones to fuzzy translations in a PO file. To produce
-the differences <samp><span class="command">wdiff</span></samp> is used. This
may be useful to figure
-out what has changed. In fact, it wraps around a <samp><span
class="command">sed</span></samp> script
+the differences <code>wdiff</code> is used. This may be useful to figure
+out what has changed. In fact, it wraps around a <code>sed</code> script
used in GNUN internally.
+</p>
+<div class="example">
+<pre class="example">gnun-add-fuzzy-diff [OPTION...] [FILE]
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>-i</samp></dt>
+<dt><samp>--in-place</samp></dt>
+<dd><p>Edit the file in place.
+</p>
+</dd>
+<dt><samp>--version</samp></dt>
+<dd><p>Display copyright and version information and exit.
+</p>
+</dd>
+<dt><samp>--help</samp></dt>
+<dd><p>Display usage information and exit.
+</p></dd>
+</dl>
-<pre class="example"> gnun-add-fuzzy-diff [OPTION...] [FILE]
-</pre>
- <dl>
-<dt><samp><span class="option">-i</span></samp><dt><samp><span
class="option">--in-place</span></samp><dd>Edit the file in place.
-
- <br><dt><samp><span class="option">--version</span></samp><dd>Display
copyright and version information and exit.
- <br><dt><samp><span class="option">--help</span></samp><dd>Display usage
information and exit.
-</dl>
- </body></html>
+</body>
+</html>
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.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- gnun/html_node/gnun_002dclear_002dprevious.html 26 Sep 2012 14:49:44
-0000 1.7
+++ gnun/html_node/gnun_002dclear_002dprevious.html 4 Dec 2012 16:24:23
-0000 1.8
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>gnun-clear-previous - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Scripts.html#Scripts" title="Scripts">
-<link rel="prev"
href="validate_002dhtml_002dnotify.html#validate_002dhtml_002dnotify"
title="validate-html-notify">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,57 +9,98 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: gnun-clear-previous</title>
+
+<meta name="description" content="GNUnited Nations: gnun-clear-previous">
+<meta name="keywords" content="GNUnited Nations: gnun-clear-previous">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Scripts.html#Scripts" rel="up" title="Scripts">
+<link href="Rules.html#Rules" rel="next" title="Rules">
+<link href="validate_002dhtml_002dnotify.html#validate_002dhtml_002dnotify"
rel="previous" title="validate-html-notify">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
-<a name="gnun-clear-previous"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="gnun_002dclear_002dprevious"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="validate_002dhtml_002dnotify.html#validate_002dhtml_002dnotify">validate-html-notify</a>,
-Up: <a rel="up" accesskey="u" href="Scripts.html#Scripts">Scripts</a>
-<hr>
+Previous: <a
href="validate_002dhtml_002dnotify.html#validate_002dhtml_002dnotify"
accesskey="p" rel="previous">validate-html-notify</a>, Up: <a
href="Scripts.html#Scripts" accesskey="u" rel="up">Scripts</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-gnun_002dclear_002dprevious-Script"></a>
+<h4 class="subsection">3.1.10 The <code>gnun-clear-previous</code> Script</h4>
+<a name="index-previous_002c-manipulating-PO-files"></a>
-<h4 class="subsection">3.1.9 The <samp><span
class="command">gnun-clear-previous</span></samp> Script</h4>
-
-<p><a name="index-previous_002c-manipulating-PO-files-116"></a>
-This simple script is not used internally in GNUN. It is merely for
+<p>This simple script is not used internally in GNUN. It is merely for
convenience only, for those who find it hard to remember the various
-‘<samp><span class="samp">gettext</span></samp>’ tools and their
options.
-
- <p><samp><span class="command">gnun-clear-previous</span></samp> deletes
the <dfn>previous</dfn> messages in a
+‘<samp>gettext</samp>’ tools and their options.
+</p>
+<p><code>gnun-clear-previous</code> deletes the <em>previous</em> messages in a
PO file, which is a good thing to do after the corresponding translation
-is updated and the <dfn>fuzzy</dfn> marker removed. It can also be used to
+is updated and the <em>fuzzy</em> marker removed. It can also be used to
wrap long lines in PO files.
+</p>
+<p>Usage:
+</p>
+<div class="example">
+<pre class="example">gnun-clear-previous FILE
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>--version</samp></dt>
+<dd><p>Print copyright and version information on the standard output.
+</p>
+</dd>
+<dt><samp>--help</samp></dt>
+<dd><p>Print usage information on stdout.
+</p></dd>
+</dl>
- <p>Usage:
-
-<pre class="example"> gnun-clear-previous FILE
-</pre>
- <dl>
-<dt><samp><span class="option">--version</span></samp><dd>Print copyright and
version information on the standard output.
- <br><dt><samp><span class="option">--help</span></samp><dd>Print usage
information on stdout.
-</dl>
- </body></html>
+</body>
+</html>
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.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- gnun/html_node/gnun_002dinit_002dpo.html 26 Sep 2012 14:49:45 -0000
1.2
+++ gnun/html_node/gnun_002dinit_002dpo.html 4 Dec 2012 16:24:23 -0000
1.3
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>gnun-init-po - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Scripts.html#Scripts" title="Scripts">
-<link rel="prev"
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff"
title="gnun-add-fuzzy-diff">
-<link rel="next" href="gnun_002dpreconvert.html#gnun_002dpreconvert"
title="gnun-preconvert">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,68 +9,123 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: gnun-init-po</title>
+
+<meta name="description" content="GNUnited Nations: gnun-init-po">
+<meta name="keywords" content="GNUnited Nations: gnun-init-po">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Scripts.html#Scripts" rel="up" title="Scripts">
+<link href="gnun_002dpreconvert.html#gnun_002dpreconvert" rel="next"
title="gnun-preconvert">
+<link href="gnun_002ddiff_002dpo.html#gnun_002ddiff_002dpo" rel="previous"
title="gnun-diff-po">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
-<a name="gnun-init-po"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="gnun_002dinit_002dpo"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="gnun_002dpreconvert.html#gnun_002dpreconvert">gnun-preconvert</a>,
-Previous: <a rel="previous" accesskey="p"
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff">gnun-add-fuzzy-diff</a>,
-Up: <a rel="up" accesskey="u" href="Scripts.html#Scripts">Scripts</a>
-<hr>
+Next: <a href="gnun_002dpreconvert.html#gnun_002dpreconvert" accesskey="n"
rel="next">gnun-preconvert</a>, Previous: <a
href="gnun_002ddiff_002dpo.html#gnun_002ddiff_002dpo" accesskey="p"
rel="previous">gnun-diff-po</a>, Up: <a href="Scripts.html#Scripts"
accesskey="u" rel="up">Scripts</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-gnun_002dinit_002dpo-Script"></a>
+<h4 class="subsection">3.1.3 The <code>gnun-init-po</code> Script</h4>
+<a name="index-initializing_002c-translations"></a>
-<h4 class="subsection">3.1.3 The <samp><span
class="command">gnun-init-po</span></samp> Script</h4>
-
-<p><a name="index-initializing_002c-translations-109"></a>
-This script initializes a PO file using POT generated with GNUN,
+<p>This script initializes a PO file using POT generated with GNUN,
and fills some fields in the header. It also optionally uses
a compendium (or compendia) to fill translations.
-
-<pre class="example"> gnun-init-po [OPTION...] POT
-</pre>
- <dl>
-<dt><samp><span class="option">-C</span></samp><dt><samp><span
class="option">--compendium=</span><var>comp</var></samp><dd>Specify a
compendium to use. You can issue this option
+</p>
+<div class="example">
+<pre class="example">gnun-init-po [OPTION...] POT
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>-C</samp></dt>
+<dt><samp>--compendium=<var>comp</var></samp></dt>
+<dd><p>Specify a compendium to use. You can issue this option
many times to use multiple compendia simultaneously. The suffix
of compendium is used when the language suffix is not specified
with the <code>--language</code> option.
-
- <br><dt><samp><span class="option">-d</span></samp><dt><samp><span
class="option">--disable-diffs</span></samp><dd>Don't add diffs to previous
messages.
-
- <br><dt><samp><span class="option">-g</span></samp><dt><samp><span
class="option">--team="</span><var>team <list></var><span
class="option">"</span></samp><dd>Specify team's name and mailing list.
-
- <br><dt><samp><span class="option">-l</span></samp><dt><samp><span
class="option">--language=</span><var>lang</var></samp><dd>Specify language
suffix, e.g “bg”. The suffix also defines
+</p>
+</dd>
+<dt><samp>-d</samp></dt>
+<dt><samp>--disable-diffs</samp></dt>
+<dd><p>Don’t add diffs to previous messages.
+</p>
+</dd>
+<dt><samp>-g</samp></dt>
+<dt><samp>--team="<var>team <list></var>"</samp></dt>
+<dd><p>Specify team’s name and mailing list.
+</p>
+</dd>
+<dt><samp>-l</samp></dt>
+<dt><samp>--language=<var>lang</var></samp></dt>
+<dd><p>Specify language suffix, e.g “bg”. The suffix also defines
the name of the language which is used in some fields of PO file header.
-
- <br><dt><samp><span class="option">-t</span></samp><dt><samp><span
class="option">--translator="</span><var>full name <email></var><span
class="option">"</span></samp><dd>Specify translator.
-
- <br><dt><samp><span class="option">--version</span></samp><dd>Display
copyright and version information and exit.
-
- <br><dt><samp><span class="option">--help</span></samp><dd>Display usage
information and exit.
+</p>
+</dd>
+<dt><samp>-t</samp></dt>
+<dt><samp>--translator="<var>full name
<email></var>"</samp></dt>
+<dd><p>Specify translator.
+</p>
+</dd>
+<dt><samp>--version</samp></dt>
+<dd><p>Display copyright and version information and exit.
+</p>
+</dd>
+<dt><samp>--help</samp></dt>
+<dd><p>Display usage information and exit.
+</p></dd>
</dl>
- <p>The PO file name is guessed from the name of POT and language
+<p>The PO file name is guessed from the name of POT and language
suffix; the file is created in current working directory.
+</p>
+
- </body></html>
+</body>
+</html>
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.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- gnun/html_node/gnun_002dmerge_002dpreconverted.html 26 Sep 2012 14:49:45
-0000 1.3
+++ gnun/html_node/gnun_002dmerge_002dpreconverted.html 4 Dec 2012 16:24:23
-0000 1.4
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>gnun-merge-preconverted - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Scripts.html#Scripts" title="Scripts">
-<link rel="prev" href="gnun_002dpreconvert.html#gnun_002dpreconvert"
title="gnun-preconvert">
-<link rel="next"
href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml"
title="gnun-validate-html">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,55 +9,99 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: gnun-merge-preconverted</title>
+
+<meta name="description" content="GNUnited Nations: gnun-merge-preconverted">
+<meta name="keywords" content="GNUnited Nations: gnun-merge-preconverted">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Scripts.html#Scripts" rel="up" title="Scripts">
+<link href="gnun_002dreport.html#gnun_002dreport" rel="next"
title="gnun-report">
+<link href="gnun_002dpreconvert.html#gnun_002dpreconvert" rel="previous"
title="gnun-preconvert">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
-<a name="gnun-merge-preconverted"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="gnun_002dmerge_002dpreconverted"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml">gnun-validate-html</a>,
-Previous: <a rel="previous" accesskey="p"
href="gnun_002dpreconvert.html#gnun_002dpreconvert">gnun-preconvert</a>,
-Up: <a rel="up" accesskey="u" href="Scripts.html#Scripts">Scripts</a>
-<hr>
+Next: <a href="gnun_002dreport.html#gnun_002dreport" accesskey="n"
rel="next">gnun-report</a>, Previous: <a
href="gnun_002dpreconvert.html#gnun_002dpreconvert" accesskey="p"
rel="previous">gnun-preconvert</a>, Up: <a href="Scripts.html#Scripts"
accesskey="u" rel="up">Scripts</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-gnun_002dmerge_002dpreconverted-Script"></a>
+<h4 class="subsection">3.1.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>
-<h4 class="subsection">3.1.5 The <samp><span
class="command">gnun-merge-preconverted</span></samp> Script</h4>
-
-<p><a name="index-migration_002c-translations-112"></a><a
name="index-conversion-of-existing-translations-113"></a>
-This script takes <samp><span class="command">po4a-gettextize</span></samp>
output, adds current
+<p>This script takes <code>po4a-gettextize</code> output, adds current
<code>msgid</code>s as “previous” values, merges the file with the
new
POT, and adds differences against previous values like
-<samp><span class="command">gnun-add-fuzzy-diff</span></samp> does.
-
-<pre class="example"> gnun-merge-preconverted [OPTION...] PO POT
-</pre>
- <dl>
-<dt><samp><span class="option">-C</span></samp><dt><samp><span
class="option">--compendium</span></samp><dd>Specify the compendium (if any).
This option can be used
+<code>gnun-add-fuzzy-diff</code> does.
+</p>
+<div class="example">
+<pre class="example">gnun-merge-preconverted [OPTION...] PO POT
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>-C</samp></dt>
+<dt><samp>--compendium</samp></dt>
+<dd><p>Specify the compendium (if any). This option can be used
more than once to specify multiple compendia.
+</p>
+</dd>
+<dt><samp>--version</samp></dt>
+<dd><p>Display copyright and version information and exit.
+</p>
+</dd>
+<dt><samp>--help</samp></dt>
+<dd><p>Display usage information and exit.
+</p></dd>
+</dl>
- <br><dt><samp><span class="option">--version</span></samp><dd>Display
copyright and version information and exit.
- <br><dt><samp><span class="option">--help</span></samp><dd>Display usage
information and exit.
-</dl>
- </body></html>
+</body>
+</html>
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.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- gnun/html_node/gnun_002dpreconvert.html 26 Sep 2012 14:49:45 -0000
1.3
+++ gnun/html_node/gnun_002dpreconvert.html 4 Dec 2012 16:24:24 -0000
1.4
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>gnun-preconvert - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Scripts.html#Scripts" title="Scripts">
-<link rel="prev" href="gnun_002dinit_002dpo.html#gnun_002dinit_002dpo"
title="gnun-init-po">
-<link rel="next"
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted"
title="gnun-merge-preconverted">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,55 +9,99 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: gnun-preconvert</title>
+
+<meta name="description" content="GNUnited Nations: gnun-preconvert">
+<meta name="keywords" content="GNUnited Nations: gnun-preconvert">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Scripts.html#Scripts" rel="up" title="Scripts">
+<link
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted"
rel="next" title="gnun-merge-preconverted">
+<link href="gnun_002dinit_002dpo.html#gnun_002dinit_002dpo" rel="previous"
title="gnun-init-po">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
-<a name="gnun-preconvert"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="gnun_002dpreconvert"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a>,
-Previous: <a rel="previous" accesskey="p"
href="gnun_002dinit_002dpo.html#gnun_002dinit_002dpo">gnun-init-po</a>,
-Up: <a rel="up" accesskey="u" href="Scripts.html#Scripts">Scripts</a>
-<hr>
+Next: <a
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted"
accesskey="n" rel="next">gnun-merge-preconverted</a>, Previous: <a
href="gnun_002dinit_002dpo.html#gnun_002dinit_002dpo" accesskey="p"
rel="previous">gnun-init-po</a>, Up: <a href="Scripts.html#Scripts"
accesskey="u" rel="up">Scripts</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-gnun_002dpreconvert-Script"></a>
+<h4 class="subsection">3.1.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>
-<h4 class="subsection">3.1.4 The <samp><span
class="command">gnun-preconvert</span></samp> Script</h4>
-
-<p><a name="index-migration_002c-translations-110"></a><a
name="index-conversion-of-existing-translations-111"></a>
-This script uses <samp><span class="command">po4a-gettextize</span></samp> to
convert a translation
+<p>This script uses <code>po4a-gettextize</code> to convert a translation
from HTML to PO format (see
<a
href="http://po4a.alioth.debian.org/man/man7/po4a.7.php#lbAO";>http://po4a.alioth.debian.org/man/man7/po4a.7.php#lbAO</a>).
If
the conversion is successful, you can merge the result with the new
-POT using <samp><span class="command">gnun-merge-preconverted</span></samp>.
-
-<pre class="example"> gnun-preconvert [OPTION...] TRANSLATION MASTER
-</pre>
- <dl>
-<dt><samp><span class="option">-e</span></samp><dt><samp><span
class="option">--encoding</span></samp><dd>Specify the encoding of TRANSLATION
(if other than UTF-8).
+POT using <code>gnun-merge-preconverted</code>.
+</p>
+<div class="example">
+<pre class="example">gnun-preconvert [OPTION...] TRANSLATION MASTER
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>-e</samp></dt>
+<dt><samp>--encoding</samp></dt>
+<dd><p>Specify the encoding of TRANSLATION (if other than UTF-8).
+</p>
+</dd>
+<dt><samp>--version</samp></dt>
+<dd><p>Display copyright and version information and exit.
+</p>
+</dd>
+<dt><samp>--help</samp></dt>
+<dd><p>Display usage information and exit.
+</p></dd>
+</dl>
- <br><dt><samp><span class="option">--version</span></samp><dd>Display
copyright and version information and exit.
- <br><dt><samp><span class="option">--help</span></samp><dd>Display usage
information and exit.
-</dl>
- </body></html>
+</body>
+</html>
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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- gnun/html_node/gnun_002dvalidate_002dhtml.html 26 Sep 2012 14:49:45
-0000 1.11
+++ gnun/html_node/gnun_002dvalidate_002dhtml.html 4 Dec 2012 16:24:24
-0000 1.12
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>gnun-validate-html - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Scripts.html#Scripts" title="Scripts">
-<link rel="prev"
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted"
title="gnun-merge-preconverted">
-<link rel="next" href="mailfail.html#mailfail" title="mailfail">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,65 +9,115 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: gnun-validate-html</title>
+
+<meta name="description" content="GNUnited Nations: gnun-validate-html">
+<meta name="keywords" content="GNUnited Nations: gnun-validate-html">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Scripts.html#Scripts" rel="up" title="Scripts">
+<link href="mailfail.html#mailfail" rel="next" title="mailfail">
+<link href="gnun_002dreport.html#gnun_002dreport" rel="previous"
title="gnun-report">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
-<a name="gnun-validate-html"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="gnun_002dvalidate_002dhtml"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="mailfail.html#mailfail">mailfail</a>,
-Previous: <a rel="previous" accesskey="p"
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a>,
-Up: <a rel="up" accesskey="u" href="Scripts.html#Scripts">Scripts</a>
-<hr>
+Next: <a href="mailfail.html#mailfail" accesskey="n" rel="next">mailfail</a>,
Previous: <a href="gnun_002dreport.html#gnun_002dreport" accesskey="p"
rel="previous">gnun-report</a>, Up: <a href="Scripts.html#Scripts"
accesskey="u" rel="up">Scripts</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-gnun_002dvalidate_002dhtml-Script"></a>
+<h4 class="subsection">3.1.7 The <code>gnun-validate-html</code> Script</h4>
+<a name="index-validation_002c-HTML_002c-XHTML"></a>
-<h4 class="subsection">3.1.6 The <samp><span
class="command">gnun-validate-html</span></samp> Script</h4>
-
-<p><a name="index-validation_002c-HTML_002c-XHTML-114"></a>
-This is a Bash script whose purpose is to “validate” both the
+<p>This is a Bash script whose purpose is to “validate” both the
original and translated articles to make sure that they conform to the
respective W3C standard. Sometimes webmasters make mistakes, and
translators too, so this tool is useful to catch errors of that kind.
-
- <p>GNUN enforces HTML validation at build time if invoked with
+</p>
+<p>GNUN enforces HTML validation at build time if invoked with
<code>VALIDATE=yes</code>.
-
- <p>The script expects only one <var>file</var> as the last argument and
will exit
+</p>
+<p>The script expects only one <var>file</var> as the last argument and will
exit
with an error if it is not specified (which might be the case when an
automatic variable is not expanded properly due to a bug in the
makefile). Example:
+</p>
+<div class="example">
+<pre class="example">gnun-validate-html --root . philosophy/free-sw.html
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>--root=<var>directory</var></samp></dt>
+<dd><p>Specify the top <var>directory</var> of the working copy; the default
value
+is <samp>../..</samp>.
+</p>
+</dd>
+<dt><samp>--expand-to=<var>file</var></samp></dt>
+<dd><p>Save the expanded HTML as <var>file</var>.
+</p>
+</dd>
+<dt><samp>-v, --verbose</samp></dt>
+<dd><p>Produce more detailed output intended for automatic email reports;
+essentially, it adds the expanded HTML to facilitate finding errors
+by people who receive the report.
+</p>
+</dd>
+<dt><samp>--version</samp></dt>
+<dd><p>Display copyright and version information and exit.
+</p>
+</dd>
+<dt><samp>--help</samp></dt>
+<dd><p>Display usage information and exit.
+</p></dd>
+</dl>
-<pre class="example"> gnun-validate-html --root . philosophy/free-sw.html
-</pre>
- <dl>
-<dt><samp><span
class="option">--root=</span><var>directory</var></samp><dd>Specify the top
<var>directory</var> of the working copy; the default value
-is <samp><span class="file">../..</span></samp>.
-
- <br><dt><samp><span
class="option">--expand-to=</span><var>file</var></samp><dd>Save the expanded
HTML as <var>file</var>.
-
- <br><dt><samp><span class="option">--version</span></samp><dd>Display
copyright and version information and exit.
- <br><dt><samp><span class="option">--help</span></samp><dd>Display usage
information and exit.
-</dl>
- </body></html>
+</body>
+</html>
Index: gnun/html_node/index.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/index.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/index.html 26 Sep 2012 14:49:45 -0000 1.15
+++ gnun/html_node/index.html 4 Dec 2012 16:24:24 -0000 1.16
@@ -1,13 +1,7 @@
-<html lang="en">
-<head>
-<title>GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -15,144 +9,196 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled "GNU Free Documentation License."
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: Top</title>
+
+<meta name="description" content="GNUnited Nations: Top">
+<meta name="keywords" content="GNUnited Nations: Top">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="../dir/index.html" rel="up" title="(dir)">
+<link href="Introduction.html#Introduction" rel="next" title="Introduction">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<h1 class="settitle">GNUnited Nations</h1>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+<h1 class="settitle" align="center">GNUnited Nations</h1>
+
+
+
+
+<a name="SEC_Contents"></a>
+<h2 class="contents-heading">Table of Contents</h2>
+
<div class="contents">
-<h2>Table of Contents</h2>
-<ul>
-<li><a name="toc_Top" href="index.html#Top">GNUnited Nations</a>
-<li><a name="toc_Introduction" href="Introduction.html#Introduction">1
Introduction to GNUnited Nations</a>
-<ul>
-<li><a href="Overview.html#Overview">1.1 Why GNUN is Being Developed</a>
-<li><a href="Concepts.html#Concepts">1.2 What GNUnited Nations is and Should
be</a>
-<li><a href="Advantages.html#Advantages">1.3 Major Advantages of GNUN</a>
-<li><a href="Disadvantages.html#Disadvantages">1.4 Known Bugs and
Limitations</a>
-</li></ul>
-<li><a name="toc_Usage" href="Usage.html#Usage">2 General Usage</a>
-<ul>
-<li><a href="Invoking-GNUN.html#Invoking-GNUN">2.1 Invoking GNUN</a>
-<ul>
-<li><a href="Runtime-Variables.html#Runtime-Variables">2.1.1 Variables to
Control the Build Process</a>
-<li><a href="Special-Targets.html#Special-Targets">2.1.2 Targets Specified on
the Command Line</a>
-<ul>
-<li><a href="no_002dgrace_002ditems.html#no_002dgrace_002ditems">2.1.2.1 The
<code>no-grace-items</code> Target</a>
-<li><a
href="update_002dlocalized_002dURLs.html#update_002dlocalized_002dURLs">2.1.2.2
The <code>update-localized-URLs</code> Target</a>
-<li><a href="sync.html#sync">2.1.2.3 The <code>sync</code> Target</a>
-<li><a href="report.html#report">2.1.2.4 The <code>report</code> Target</a>
-<li><a href="triggers.html#triggers">2.1.2.5 The <code>triggers</code>
Target</a>
-<li><a href="validate_002dall.html#validate_002dall">2.1.2.6 The
<code>validate-all</code> Target</a>
-</li></ul>
-</li></ul>
-<li><a href="Main-Variables.html#Main-Variables">2.2 Defining Articles to be
Built</a>
-<li><a href="PO-Files.html#PO-Files">2.3 Working with PO Files</a>
-<ul>
-<li><a href="New-Translation.html#New-Translation">2.3.1 Starting a New
Translation</a>
-<ul>
-<li><a href="Notes-Slot.html#Notes-Slot">2.3.1.1 The Special Slot for
Translator's Notes</a>
-<li><a href="Credits-Slot.html#Credits-Slot">2.3.1.2 The Special Slot for
Translator's Credits</a>
-</li></ul>
-<li><a href="Migrating.html#Migrating">2.3.2 Transforming Existing Translation
in PO Format</a>
-<li><a href="GNU-News.html#GNU-News">2.3.3 Special Handling for GNU News</a>
-<li><a href="PO-Tips.html#PO-Tips">2.3.4 Useful Hints for Editing PO Files</a>
-<li><a href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml">2.3.5
The <samp><span class="file">generic.</span><var>lang</var><span
class="file">.html</span></samp> File</a>
-<li><a href="languages_002etxt.html#languages_002etxt">2.3.6 The <samp><span
class="file">languages.txt</span></samp> File</a>
-<li><a href="PO-Files-and-Team.html#PO-Files-and-Team">2.3.7 Maintaining
Translations in Your Team's Repository</a>
-<ul>
-<li><a
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables">2.3.7.1
Adopting <samp><span class="file">GNUmakefile.team</span></samp> for a
Specific Team</a>
-<li><a
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables">Targets
in <samp><span class="file">GNUmakefile.team</span></samp></a>
-<li><a
href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron">2.3.7.2
Automatic Synchronization and Status Reports</a>
-</li></ul>
-<li><a href="Compendia.html#Compendia">2.3.8 Using Compendia</a>
-</li></ul>
-<li><a href="Webmaster-Tips.html#Webmaster-Tips">2.4 Tips and Hints for
Webmasters</a>
-<ul>
-<li><a href="Validation.html#Validation">2.4.1 Validation</a>
-<li><a href="Comments-for-Translators.html#Comments-for-Translators">2.4.2
Comments for Translators</a>
-<li><a href="Modifying-Boilerplates.html#Modifying-Boilerplates">2.4.3
Modifying Boilerplates</a>
-<li><a href="Localized-URLs.html#Localized-URLs">2.4.4 Localized URLs</a>
-<li><a href="Splitting-Long-Passages.html#Splitting-Long-Passages">2.4.5
Splitting Long Passages</a>
-</li></ul>
-</li></ul>
-<li><a name="toc_Internals" href="Internals.html#Internals">3 Unexciting
Information for GNUN's Operation</a>
-<ul>
-<li><a href="Scripts.html#Scripts">3.1 GNUN Scripts</a>
-<ul>
-<li><a href="make_002dprototype.html#make_002dprototype">3.1.1 The <samp><span
class="command">make-prototype</span></samp> Script</a>
-<li><a
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff">3.1.2
The <samp><span class="command">gnun-add-fuzzy-diff</span></samp> Script</a>
-<li><a href="gnun_002dinit_002dpo.html#gnun_002dinit_002dpo">3.1.3 The
<samp><span class="command">gnun-init-po</span></samp> Script</a>
-<li><a href="gnun_002dpreconvert.html#gnun_002dpreconvert">3.1.4 The
<samp><span class="command">gnun-preconvert</span></samp> Script</a>
-<li><a
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted">3.1.5
The <samp><span class="command">gnun-merge-preconverted</span></samp>
Script</a>
-<li><a href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml">3.1.6
The <samp><span class="command">gnun-validate-html</span></samp> Script</a>
-<li><a href="mailfail.html#mailfail">3.1.7 The <samp><span
class="command">mailfail</span></samp> Script</a>
-<li><a
href="validate_002dhtml_002dnotify.html#validate_002dhtml_002dnotify">3.1.8 The
<samp><span class="command">validate-html-notify</span></samp> Script</a>
-<li><a
href="gnun_002dclear_002dprevious.html#gnun_002dclear_002dprevious">3.1.9 The
<samp><span class="command">gnun-clear-previous</span></samp> Script</a>
-</li></ul>
-<li><a href="Rules.html#Rules">3.2 How The Recipes Work</a>
-</li></ul>
-<li><a name="toc_Bugs" href="Bugs.html#Bugs">4 Reporting Bugs</a>
-<li><a name="toc_Copying-This-Manual"
href="Copying-This-Manual.html#Copying-This-Manual">Appendix A GNU Free
Documentation License</a>
-<li><a name="toc_Index" href="Index.html#Index">Index</a>
-</li></ul>
+
+<ul class="no-bullet">
+ <li><a name="toc-Introduction-to-GNUnited-Nations"
href="Introduction.html#Introduction">1 Introduction to GNUnited Nations</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Why-GNUN-is-Being-Developed"
href="Overview.html#Overview">1.1 Why GNUN is Being Developed</a></li>
+ <li><a name="toc-What-GNUnited-Nations-is-and-Should-be"
href="Concepts.html#Concepts">1.2 What GNUnited Nations is and Should
be</a></li>
+ <li><a name="toc-Major-Advantages-of-GNUN"
href="Advantages.html#Advantages">1.3 Major Advantages of GNUN</a></li>
+ <li><a name="toc-Known-Bugs-and-Limitations"
href="Disadvantages.html#Disadvantages">1.4 Known Bugs and Limitations</a></li>
+ </ul></li>
+ <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-Transforming-Existing-Translation-in-PO-Format"
href="Migrating.html#Migrating">2.3.2 Transforming Existing Translation in PO
Format</a></li>
+ <li><a name="toc-Special-Handling-for-GNU-News"
href="GNU-News.html#GNU-News">2.3.3 Special Handling for GNU News</a></li>
+ <li><a name="toc-Useful-Hints-for-Editing-PO-Files"
href="PO-Tips.html#PO-Tips">2.3.4 Useful Hints for Editing PO Files</a></li>
+ <li><a name="toc-The-generic_002elang_002ehtml-File"
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml">2.3.5 The
<samp>generic.<var>lang</var>.html</samp> File</a></li>
+ <li><a name="toc-The-languages_002etxt-File"
href="languages_002etxt.html#languages_002etxt">2.3.6 The
<samp>languages.txt</samp> File</a></li>
+ <li><a name="toc-Maintaining-Translations-in-Your-Team_0027s-Repository"
href="PO-Files-and-Team.html#PO-Files-and-Team">2.3.7 Maintaining Translations
in Your Team’s Repository</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Adopting-GNUmakefile_002eteam-for-a-Specific-Team"
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables">2.3.7.1
Adopting <samp>GNUmakefile.team</samp> for a Specific Team</a></li>
+ <li><a name="toc-Targets-in-GNUmakefile_002eteam"
href="GNUmakefile_002eteam-Targets.html#GNUmakefile_002eteam-Targets">2.3.7.2
Targets in <samp>GNUmakefile.team</samp></a></li>
+ <li><a name="toc-Automatic-Synchronization-and-Status-Reports"
href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron">2.3.7.3
Automatic Synchronization and Status Reports</a></li>
+ </ul></li>
+ <li><a name="toc-Using-Compendia" href="Compendia.html#Compendia">2.3.8
Using Compendia</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-GNUN-Scripts" href="Scripts.html#Scripts">3.1 GNUN
Scripts</a>
+ <ul class="no-bullet">
+ <li><a name="toc-The-gnun_002dadd_002dfuzzy_002ddiff-Script"
href="gnun_002dadd_002dfuzzy_002ddiff.html#gnun_002dadd_002dfuzzy_002ddiff">3.1.1
The <code>gnun-add-fuzzy-diff</code> Script</a></li>
+ <li><a name="toc-The-gnun_002ddiff_002dpo-Script"
href="gnun_002ddiff_002dpo.html#gnun_002ddiff_002dpo">3.1.2 The
<code>gnun-diff-po</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dinit_002dpo-Script"
href="gnun_002dinit_002dpo.html#gnun_002dinit_002dpo">3.1.3 The
<code>gnun-init-po</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dpreconvert-Script"
href="gnun_002dpreconvert.html#gnun_002dpreconvert">3.1.4 The
<code>gnun-preconvert</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dmerge_002dpreconverted-Script"
href="gnun_002dmerge_002dpreconverted.html#gnun_002dmerge_002dpreconverted">3.1.5
The <code>gnun-merge-preconverted</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dreport-Script"
href="gnun_002dreport.html#gnun_002dreport">3.1.6 The <code>gnun-report</code>
Script</a></li>
+ <li><a name="toc-The-gnun_002dvalidate_002dhtml-Script"
href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml">3.1.7 The
<code>gnun-validate-html</code> Script</a></li>
+ <li><a name="toc-The-mailfail-Script"
href="mailfail.html#mailfail">3.1.8 The <code>mailfail</code> Script</a></li>
+ <li><a name="toc-The-validate_002dhtml_002dnotify-Script"
href="validate_002dhtml_002dnotify.html#validate_002dhtml_002dnotify">3.1.9 The
<code>validate-html-notify</code> Script</a></li>
+ <li><a name="toc-The-gnun_002dclear_002dprevious-Script"
href="gnun_002dclear_002dprevious.html#gnun_002dclear_002dprevious">3.1.10 The
<code>gnun-clear-previous</code> Script</a></li>
+ </ul></li>
+ <li><a name="toc-How-The-Recipes-Work" href="Rules.html#Rules">3.2 How The
Recipes Work</a></li>
+ </ul></li>
+ <li><a name="toc-Reporting-Bugs" href="Bugs.html#Bugs">4 Reporting
Bugs</a></li>
+ <li><a name="toc-Index-1" href="Index.html#Index">Index</a></li>
+ <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>
</div>
-<div class="node">
<a name="Top"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Introduction.html#Introduction">Introduction</a>,
-Up: <a rel="up" accesskey="u" href="../index.html#dir">(dir)</a>
-<hr>
+Next: <a href="Introduction.html#Introduction" accesskey="n"
rel="next">Introduction</a>, Up: <a href="../dir/index.html" accesskey="u"
rel="up">(dir)</a> [<a href="#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="GNUnited-Nations"></a>
+<h1 class="top">GNUnited Nations</h1>
-<h2 class="unnumbered">GNUnited Nations</h2>
-
-<p>This manual (updated 26 September 2012) is for GNUnited Nations (version
+<p>This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.<br>
- <pre class="sp">
-
-</pre>
-Copyright © 2008, 2009, 2010, 2011, 2012 Free Software
+</p><br>
+<p>Copyright © 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
-
- <blockquote>
-Permission is granted to copy, distribute and/or modify this document
+</p>
+<blockquote>
+<p>Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled “GNU Free
Documentation License.”
-</blockquote>
+</p></blockquote>
+
+
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a
href="Introduction.html#Introduction"
accesskey="1">Introduction</a>:</td><td> </td><td align="left"
valign="top">Overview of GNUnited Nations.
+</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.
+</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.
+</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">
+</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.
+</td></tr>
+</table>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Introduction.html#Introduction" accesskey="n"
rel="next">Introduction</a>, Up: <a href="../dir/index.html" accesskey="u"
rel="up">(dir)</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
-<ul class="menu">
-<li><a accesskey="1" href="Introduction.html#Introduction">Introduction</a>:
Overview of GNUnited Nations.
-<li><a accesskey="2" href="Usage.html#Usage">Usage</a>: Basic
usage, invocation and tips.
-<li><a accesskey="3" href="Internals.html#Internals">Internals</a>:
Dive into GNUN.
-<li><a accesskey="4" href="Bugs.html#Bugs">Bugs</a>: How to
report bugs.
-<li><a accesskey="5" href="Index.html#Index">Index</a>
-<li><a accesskey="6"
href="Copying-This-Manual.html#Copying-This-Manual">Copying This Manual</a>:
The GNU Free Documentation License.
-</ul>
- </body></html>
+</body>
+</html>
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.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- gnun/html_node/languages_002etxt.html 26 Sep 2012 14:49:45 -0000
1.5
+++ gnun/html_node/languages_002etxt.html 4 Dec 2012 16:24:24 -0000
1.6
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>languages.txt - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="PO-Files.html#PO-Files" title="PO Files">
-<link rel="prev"
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
title="generic.LANG.html">
-<link rel="next" href="PO-Files-and-Team.html#PO-Files-and-Team" title="PO
Files and Team">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,66 +9,104 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: languages.txt</title>
+
+<meta name="description" content="GNUnited Nations: languages.txt">
+<meta name="keywords" content="GNUnited Nations: languages.txt">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="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="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml"
rel="previous" title="generic.LANG.html">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
-<a name="languages.txt"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="languages_002etxt"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="PO-Files-and-Team.html#PO-Files-and-Team">PO Files and Team</a>,
-Previous: <a rel="previous" accesskey="p"
href="generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml">generic.LANG.html</a>,
-Up: <a rel="up" accesskey="u" href="PO-Files.html#PO-Files">PO Files</a>
-<hr>
+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>
</div>
+<hr>
+<a name="The-languages_002etxt-File"></a>
+<h4 class="subsection">2.3.6 The <samp>languages.txt</samp> File</h4>
-<h4 class="subsection">2.3.6 The <samp><span
class="file">languages.txt</span></samp> File</h4>
-
-<p>The file <samp><span class="file">server/gnun/languages.txt</span></samp>
is used when generating
+<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 <TAB>-separated fields. The first field
+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>
+
+
-<pre class="example"> de German Deutsch
-</pre>
- <p>The generated list of translations may look like this:
-
-<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>
- </body></html>
+</body>
+</html>
Index: gnun/html_node/mailfail.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/mailfail.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/mailfail.html 26 Sep 2012 14:49:45 -0000 1.15
+++ gnun/html_node/mailfail.html 4 Dec 2012 16:24:24 -0000 1.16
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>mailfail - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Scripts.html#Scripts" title="Scripts">
-<link rel="prev"
href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml"
title="gnun-validate-html">
-<link rel="next"
href="validate_002dhtml_002dnotify.html#validate_002dhtml_002dnotify"
title="validate-html-notify">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,76 +9,125 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: mailfail</title>
+
+<meta name="description" content="GNUnited Nations: mailfail">
+<meta name="keywords" content="GNUnited Nations: mailfail">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Scripts.html#Scripts" rel="up" title="Scripts">
+<link href="validate_002dhtml_002dnotify.html#validate_002dhtml_002dnotify"
rel="next" title="validate-html-notify">
+<link href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml"
rel="previous" title="gnun-validate-html">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="mailfail"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="validate_002dhtml_002dnotify.html#validate_002dhtml_002dnotify">validate-html-notify</a>,
-Previous: <a rel="previous" accesskey="p"
href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml">gnun-validate-html</a>,
-Up: <a rel="up" accesskey="u" href="Scripts.html#Scripts">Scripts</a>
-<hr>
+Next: <a href="validate_002dhtml_002dnotify.html#validate_002dhtml_002dnotify"
accesskey="n" rel="next">validate-html-notify</a>, Previous: <a
href="gnun_002dvalidate_002dhtml.html#gnun_002dvalidate_002dhtml" accesskey="p"
rel="previous">gnun-validate-html</a>, Up: <a href="Scripts.html#Scripts"
accesskey="u" rel="up">Scripts</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-mailfail-Script"></a>
+<h4 class="subsection">3.1.8 The <code>mailfail</code> Script</h4>
+<a name="index-mail_002c-notifications-1"></a>
-<h4 class="subsection">3.1.7 The <samp><span
class="command">mailfail</span></samp> Script</h4>
-
-<p><a name="index-mail_002c-notifications-115"></a>
-This is a helper script that runs a command, and mails the output of
+<p>This is a helper script that runs a command, and mails the output of
that command in case it exits with a non-zero exit status.
-<samp><span class="command">mailfail</span></samp> depends on GNU Mailutils,
or a compatible
-implementation, such as BSD's mailx.
-
- <p>Usage:
-
-<pre class="example"> mailfail [--dry-run] RCPT SUBJECT CMD [ARG ...]
-</pre>
- <p>The <samp><span class="command">mailfail</span></samp> script accepts
the following options:
-
- <dl>
-<dt><samp><span class="option">--dry-run</span></samp><dd>Does not send the
email message.
-
- <br><dt><samp><span class="option">RCPT</span></samp><dd>The recipient of
the message in a valid format, like
+<code>mailfail</code> depends on GNU Mailutils, or a compatible
+implementation, such as BSD’s mailx.
+</p>
+<p>Usage:
+</p>
+<div class="example">
+<pre class="example">mailfail [--dry-run] RCPT SUBJECT CMD [ARG ...]
+</pre></div>
+
+<p>The <code>mailfail</code> script accepts the following options:
+</p>
+<dl compact="compact">
+<dt><samp>--dry-run</samp></dt>
+<dd><p>Does not send the email message.
+</p>
+</dd>
+<dt><samp>RCPT</samp></dt>
+<dd><p>The recipient of the message in a valid format, like
<code>address@hidden</code>.
-
- <br><dt><samp><span class="option">SUBJECT</span></samp><dd>The subject
of the message; if it is longer than a word you should
+</p>
+</dd>
+<dt><samp>SUBJECT</samp></dt>
+<dd><p>The subject of the message; if it is longer than a word you should
guard it with quotes.
-
- <br><dt><samp><span class="option">CMD</span></samp><dd>The command you
want to run and send a mail in case it fails.
-
- <br><dt><samp><span class="option">ARG...</span></samp><dd>The arguments
of <code>CMD</code>, if any.
+</p>
+</dd>
+<dt><samp>CMD</samp></dt>
+<dd><p>The command you want to run and send a mail in case it fails.
+</p>
+</dd>
+<dt><samp>ARG…</samp></dt>
+<dd><p>The arguments of <code>CMD</code>, if any.
+</p></dd>
</dl>
- <p>Here is a typical example, similar to the way it is used in GNUN:
+<p>Here is a typical example, similar to the way it is used in GNUN:
+</p>
+<div class="example">
+<pre class="example">mailfail address@hidden "Bad PO" msgfmt -cv -o
/dev/null bg.po
+</pre></div>
-<pre class="example"> mailfail address@hidden "Bad PO" msgfmt -cv -o
/dev/null bg.po
-</pre>
- <p>This will check the validity of <samp><span
class="file">bg.po</span></samp> with the <samp><span
class="command">msgfmt</span></samp>
+<p>This will check the validity of <samp>bg.po</samp> with the
<code>msgfmt</code>
program and in case there are errors, a message will be sent to the
-specified address with `Bad PO' as subject and the error output from
-<samp><span class="command">msgfmt</span></samp> as body.
-
- <p><samp><span class="command">mailfail</span></samp> inherits the exit
status of the command being run.
+specified address with ‘Bad PO’ as subject and the error output
from
+<code>msgfmt</code> as body.
+</p>
+<p><code>mailfail</code> inherits the exit status of the command being run.
If an argument is missing, the usage information is printed to the
standard output and the exit code is 1.
+</p>
+
- </body></html>
+</body>
+</html>
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.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- gnun/html_node/no_002dgrace_002ditems.html 26 Sep 2012 14:49:45 -0000
1.5
+++ gnun/html_node/no_002dgrace_002ditems.html 4 Dec 2012 16:24:24 -0000
1.6
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>no-grace-items - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Special-Targets.html#Special-Targets" title="Special
Targets">
-<link rel="next"
href="update_002dlocalized_002dURLs.html#update_002dlocalized_002dURLs"
title="update-localized-URLs">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,45 +9,80 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: no-grace-items</title>
+
+<meta name="description" content="GNUnited Nations: no-grace-items">
+<meta name="keywords" content="GNUnited Nations: no-grace-items">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Special-Targets.html#Special-Targets" rel="up" title="Special
Targets">
+<link href="update_002dlocalized_002dURLs.html#update_002dlocalized_002dURLs"
rel="next" title="update-localized-URLs">
+<link href="Special-Targets.html#Special-Targets" rel="previous"
title="Special Targets">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
-<a name="no-grace-items"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="no_002dgrace_002ditems"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="update_002dlocalized_002dURLs.html#update_002dlocalized_002dURLs">update-localized-URLs</a>,
-Up: <a rel="up" accesskey="u"
href="Special-Targets.html#Special-Targets">Special Targets</a>
-<hr>
+Next: <a
href="update_002dlocalized_002dURLs.html#update_002dlocalized_002dURLs"
accesskey="n" rel="next">update-localized-URLs</a>, Up: <a
href="Special-Targets.html#Special-Targets" accesskey="u" rel="up">Special
Targets</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>
-
-<h5 class="subsubsection">2.1.2.1 The <code>no-grace-items</code> Target</h5>
+<hr>
+<a name="The-no_002dgrace_002ditems-Target"></a>
+<h4 class="subsubsection">2.1.2.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 homepage, the
+that are not affected by the grace period, namely, the
server templates, gnunews, and all articles defined in the variable
-<code>no-grace-articles</code> (see <a href="GRACE.html#GRACE">grace
period</a>).
+<code>no-grace-articles</code> (see <a
href="Runtime-Variables.html#GRACE">grace period</a>).
+</p>
+<p>This target can be rebuilt more often than <code>all</code>; however, it is
+currently not used.
+</p>
- <p>This target can be rebuilt more often than <code>all</code>; it is
invoked
-hourly by the official GNUN cron job.
- </body></html>
+</body>
+</html>
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.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- gnun/html_node/optional_002dtemplates.html 26 Sep 2012 14:49:45 -0000
1.1
+++ gnun/html_node/optional_002dtemplates.html 4 Dec 2012 16:24:24 -0000
1.2
@@ -1 +1,65 @@
-<meta http-equiv="refresh" content="0;
url=Main-Variables.html#optional%2dtemplates">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!--
+This manual (updated 3 December 2012) is for GNUnited Nations (version
+0.6), a suite for maintaining translations of www.gnu.org
+essays and other articles.
+
+
+Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<!-- This file redirects to the location of a node or anchor -->
+<head>
+<title>GNUnited Nations: optional-templates</title>
+
+<meta name="description" content="GNUnited Nations: optional-templates">
+<meta name="keywords" content="GNUnited Nations: optional-templates">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+<meta http-equiv="Refresh" content="0;
url=Main-Variables.html#optional_002dtemplates">
+
+</head>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+
+<p>The node you are looking for is at <a
href="Main-Variables.html#optional_002dtemplates">optional-templates</a>.</p>
+</body>
Index: gnun/html_node/report.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/report.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/report.html 26 Sep 2012 14:49:45 -0000 1.15
+++ gnun/html_node/report.html 4 Dec 2012 16:24:24 -0000 1.16
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>report - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Special-Targets.html#Special-Targets" title="Special
Targets">
-<link rel="prev" href="sync.html#sync" title="sync">
-<link rel="next" href="triggers.html#triggers" title="triggers">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,57 +9,99 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: report</title>
+
+<meta name="description" content="GNUnited Nations: report">
+<meta name="keywords" content="GNUnited Nations: report">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Special-Targets.html#Special-Targets" rel="up" title="Special
Targets">
+<link href="triggers.html#triggers" rel="next" title="triggers">
+<link href="sync.html#sync" rel="previous" title="sync">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="report"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="triggers.html#triggers">triggers</a>,
-Previous: <a rel="previous" accesskey="p" href="sync.html#sync">sync</a>,
-Up: <a rel="up" accesskey="u"
href="Special-Targets.html#Special-Targets">Special Targets</a>
-<hr>
+Next: <a href="triggers.html#triggers" accesskey="n" rel="next">triggers</a>,
Previous: <a href="sync.html#sync" accesskey="p" rel="previous">sync</a>, Up:
<a href="Special-Targets.html#Special-Targets" accesskey="u" rel="up">Special
Targets</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-report-Target"></a>
+<h4 class="subsubsection">2.1.2.4 The <code>report</code> Target</h4>
+<a name="index-reporting"></a>
+<a name="index-status_002c-translations"></a>
-<h5 class="subsubsection">2.1.2.4 The <code>report</code> Target</h5>
-
-<p><a name="index-reporting-34"></a><a
name="index-status_002c-translations-35"></a>
-This target exists solely for convenience to translators, enabling them
+<p>This target exists solely for convenience to translators, enabling them
to check which articles are not 100% translated and have to be updated.
-The way to check this is by running <code>make report
TEAM=</code><var>lang</var>,
+The way to check this is by running <code>make report
TEAM=<var>lang</var></code>,
where <var>lang</var> is the language code, as usual. Thus, to check all
French translations, one would run
+</p>
+<div class="example">
+<pre class="example">make report TEAM=fr
+</pre></div>
-<pre class="example"> make report TEAM=fr
-</pre>
- <p>This target checks only the PO files; the old translations that haven't
+<p>This target checks only the PO files; the old translations that
haven’t
been converted to PO files are reported, but there is no reasonable way
to check if they are up-to-date. In fact, this is one of the main
reasons GNUN is being developed, if you recall.
-
- <p><a name="index-priorities_002emk-36"></a>When present, <samp><span
class="file">priorities.mk</span></samp> defines four classes of articles by
+</p>
+<a name="index-priorities_002emk-1"></a>
+<p>When present, <samp>priorities.mk</samp> defines four classes of articles by
priority: <var>priority-articles</var> for the most important translations,
<var>important-articles</var> for the second priority level,
<var>important-directories</var> for the directories with important articles;
all other translations are reported as less important.
+</p>
+<p>There is also a script, <code>gnun-report</code>, to generate HTML reports.
+See <a href="gnun_002dreport.html#gnun_002dreport">gnun-report</a>.
+</p>
+
- </body></html>
+</body>
+</html>
Index: gnun/html_node/sync.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/sync.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/sync.html 26 Sep 2012 14:49:46 -0000 1.15
+++ gnun/html_node/sync.html 4 Dec 2012 16:24:24 -0000 1.16
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>sync - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Special-Targets.html#Special-Targets" title="Special
Targets">
-<link rel="prev"
href="update_002dlocalized_002dURLs.html#update_002dlocalized_002dURLs"
title="update-localized-URLs">
-<link rel="next" href="report.html#report" title="report">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,74 +9,114 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: sync</title>
+
+<meta name="description" content="GNUnited Nations: sync">
+<meta name="keywords" content="GNUnited Nations: sync">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Special-Targets.html#Special-Targets" rel="up" title="Special
Targets">
+<link href="report.html#report" rel="next" title="report">
+<link href="update_002dlocalized_002dURLs.html#update_002dlocalized_002dURLs"
rel="previous" title="update-localized-URLs">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="sync"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="report.html#report">report</a>,
-Previous: <a rel="previous" accesskey="p"
href="update_002dlocalized_002dURLs.html#update_002dlocalized_002dURLs">update-localized-URLs</a>,
-Up: <a rel="up" accesskey="u"
href="Special-Targets.html#Special-Targets">Special Targets</a>
-<hr>
+Next: <a href="report.html#report" accesskey="n" rel="next">report</a>,
Previous: <a
href="update_002dlocalized_002dURLs.html#update_002dlocalized_002dURLs"
accesskey="p" rel="previous">update-localized-URLs</a>, Up: <a
href="Special-Targets.html#Special-Targets" accesskey="u" rel="up">Special
Targets</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-sync-Target"></a>
+<h4 class="subsubsection">2.1.2.3 The <code>sync</code> Target</h4>
+<a name="index-synchronization_002c-repository"></a>
-<h5 class="subsubsection">2.1.2.3 The <code>sync</code> Target</h5>
-
-<p><a name="index-synchronization_002c-repository-33"></a>
-The <code>sync</code> target has a simple task: synchronize the
+<p>The <code>sync</code> target has a simple task: synchronize the
<em>original English</em> articles from a canonical repository, like
-`www'. It is very important that such synchronization happens,
+‘www’. It is very important that such synchronization happens,
because it is desirable to develop the software and add more features
-in a testbed, while the `official instance' operates on the official
+in a testbed, while the ‘official instance’ operates on the
official
repository in a predictable way.
-
- <p>It is recommended that you `build' the <code>sync</code> target from a
cron
+</p>
+<p>It is recommended that you ‘build’ the <code>sync</code> target
from a cron
job, some time before the general build occurs. That way,
-prerequisites (e.g. original <samp><span class="file">.html</span></samp>
articles) will be updated
-from the canonical repository and the subsequent <samp><span
class="command">make</span></samp>
+prerequisites (e.g. original <samp>.html</samp> articles) will be updated
+from the canonical repository and the subsequent <code>make</code>
invocation, possibly run by cron as well, will update all
translations.
-
- <p>The <code>VCS</code> variable affects the behavior: if it is defined to
-`yes' then the synchronized files are committed to the `testing'
+</p>
+<p>The <code>VCS</code> variable affects the behavior: if it is defined to
+‘yes’ then the synchronized files are committed to the
‘testing’
repository, i.e. the <var>destination</var>. In addition, if a file meant
to be synchronized disappeared from the <var>source</var>, a warning mail
will be sent to the address defined in the <code>devel-addr</code> variable
-(defined in <samp><span class="file">gnun.conf</span></samp>). The build will
continue without
+(defined in <samp>gnun.conf</samp>). The build will continue without
failure, and will sync and commit all other files, but will send the
same email message again if the file is still present in the
<code>files-to-sync</code> variable during a subsequent invocation.
-
- <p>In addition, <code>sync</code> synchronizes all “verbatim”
server templates
-that are not under GNUN's control, such as <samp><span
class="file">server/header.html</span></samp>,
-<samp><span class="file">server/banner.html</span></samp>, <samp><span
class="file">server/footer.html</span></samp> and their
+</p>
+<p>In addition, <code>sync</code> synchronizes all “verbatim”
server templates
+that are not under GNUN’s control, such as
<samp>server/header.html</samp>,
+<samp>server/banner.html</samp>, <samp>server/footer.html</samp> and their
translations, as defined in the <code>verbatim-templates</code> variable.
This is important, as these files may change in the master repository,
while the validation of the HTML files in the development repository
will be performed with the old templates expanded, thus making this
specific test more or less bogus.
-
- <p><code>VCS=always</code> has no effect on this target, as well as
+</p>
+<p><code>VCS=always</code> has no effect on this target, as well as
<code>VALIDATE</code>.
+</p>
+<hr>
+<div class="header">
+<p>
+Next: <a href="report.html#report" accesskey="n" rel="next">report</a>,
Previous: <a
href="update_002dlocalized_002dURLs.html#update_002dlocalized_002dURLs"
accesskey="p" rel="previous">update-localized-URLs</a>, Up: <a
href="Special-Targets.html#Special-Targets" accesskey="u" rel="up">Special
Targets</a> [<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
+
- </body></html>
+</body>
+</html>
Index: gnun/html_node/triggers.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/gnun/html_node/triggers.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- gnun/html_node/triggers.html 26 Sep 2012 14:49:46 -0000 1.14
+++ gnun/html_node/triggers.html 4 Dec 2012 16:24:24 -0000 1.15
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>triggers - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Special-Targets.html#Special-Targets" title="Special
Targets">
-<link rel="prev" href="report.html#report" title="report">
-<link rel="next" href="validate_002dall.html#validate_002dall"
title="validate-all">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,98 +9,128 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: triggers</title>
+
+<meta name="description" content="GNUnited Nations: triggers">
+<meta name="keywords" content="GNUnited Nations: triggers">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Special-Targets.html#Special-Targets" rel="up" title="Special
Targets">
+<link href="validate_002dall.html#validate_002dall" rel="next"
title="validate-all">
+<link href="report.html#report" rel="previous" title="report">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="triggers"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="validate_002dall.html#validate_002dall">validate-all</a>,
-Previous: <a rel="previous" accesskey="p"
href="report.html#report">report</a>,
-Up: <a rel="up" accesskey="u"
href="Special-Targets.html#Special-Targets">Special Targets</a>
-<hr>
+Next: <a href="validate_002dall.html#validate_002dall" accesskey="n"
rel="next">validate-all</a>, Previous: <a href="report.html#report"
accesskey="p" rel="previous">report</a>, Up: <a
href="Special-Targets.html#Special-Targets" accesskey="u" rel="up">Special
Targets</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>
-
-<h5 class="subsubsection">2.1.2.5 The <code>triggers</code> Target</h5>
+<hr>
+<a name="The-triggers-Target"></a>
+<h4 class="subsubsection">2.1.2.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>.
+</p>
-<!-- FIXME: Check how Subversion behaves with keywords and update the -->
-<!-- paragraph below. -->
-<!-- ineiev: In fact, "the result" is _not_ "checked in" the repository. -->
-<!-- When a GNUN build completes and some translations fail at the HTML -->
-<!-- validation stage, the result is checked in the repository, as -->
-<!-- explained earlier (@pxref{Runtime Variables}). Thus, CVS updates the -->
-<!-- @w{$}Date$ RCS keyword (or any other keywords, for that matter) and -->
-<!-- resets the file(s) timestamp. Next time @command{make} is invoked, -->
-<!-- the target appears newer than the prerequisite so no rebuild is -->
-<!-- triggered. The purpose of the @code{triggers} target is to ``save'' -->
-<!-- the information of the faulty targets during the main build, and to -->
-<!-- touch their prerequisites in order such invalid articles not to remain -->
-<!-- online unnoticed. -->
- <p>The <code>triggers</code> target currently executes the files named
-<samp><var>article</var><span class="file">.</span><var>lang</var><span
class="file">.html.hook</span></samp> in the <samp><span
class="file">server/gnun</span></samp>
+<p>The <code>triggers</code> target currently executes the files named
+<samp><var>article</var>.<var>lang</var>.html.hook</samp> in the
<samp>server/gnun</samp>
directory—these files are created during the main build and each of
them contains the command to update the timestamp of the prerequisite
based on the timestamp of the target that must be rebuilt. Finally, it
-deletes all those <samp><span class="file">*.hook</span></samp> files.
-
- <p>This is the rule that takes care of actually sending the
+deletes all those <samp>*.hook</samp> files.
+</p>
+<p>This is the rule that takes care of actually sending the
announcements if <code>ANNOUNCE=yes</code>. Since it is a completely valid
scenario to have a new translation which is initially invalid HTML,
the canned command sequence for announcements is recorded in
-<samp><span class="file">*.hook-ann</span></samp> files, and they are treated
by <code>triggers</code> in a
-different way. A newly added <samp><span
class="file">.</span><var>lang</var><span class="file">.po</span></samp> file
may be
+<samp>*.hook-ann</samp> files, and they are treated by <code>triggers</code>
in a
+different way. A newly added <samp>.<var>lang</var>.po</samp> file may be
invalid, in which case the HTML file is not added, and it is not
appropriate to announce it as a new translation as it is completely
useless for the
general public. The <code>triggers</code> rule detects this case, and
postpones the announcement to the next build attempt, when the
generated HTML translation is supposed to be human-readable.
-
- <p>To summarize, for effective operation GNUN should be invoked
-automatically as <code>make; cvs|svn|bzr commit -m ...; make
+</p>
+<p>To summarize, for effective operation GNUN should be invoked
+automatically as <code>make; cvs|svn|bzr commit -m …; make
triggers</code>. To illustrate this, here is a concrete example showing the
official job running at fencepost.gnu.org:
-
-<pre class="example"> 25 4,12,20 * * * cd $HOME/projects/www; cvs -q
update &>/dev/null; \
+</p>
+<div class="example">
+<pre class="example">25 4,12,20 * * * cd $HOME/projects/www; cvs -q update
&>/dev/null; \
make -j1 -C server/gnun VCS=yes VALIDATE=yes; \
NOTIFY=yes VERBOSE=yes GRACE=5000; ANNOUNCE=yes; \
cvs commit -m \
- "Automatic update by GNUnited Nations."; \
+ "Automatic update by GNUnited Nations."; \
make -C server/gnun triggers
-</pre>
- <p>The above example is for CVS; if the underlying repository is
+</pre></div>
+
+<p>The above example is for CVS; if the underlying repository is
Subversion, they need to be amended accordingly. If it is GNU Bzr,
-remember to add a <samp><span class="command">bzr push</span></samp> after
commit (in the usual
+remember to add a <code>bzr push</code> after commit (in the usual
scenario), otherwise changes will be committed only locally. Since a
distributed Version Control System can be used in multiple (sometimes
radically different) ways, this step cannot be anticipated and therefore
-cannot be automated. Adding the <samp><span
class="command">push</span></samp> command in the makefile
+cannot be automated. Adding the <code>push</code> command in the makefile
rules would not work if a so called “bound branch” is used, for
instance.
-
- <p>In the future, this target may be extended further to do other useful
+</p>
+<p>In the future, this target may be extended further to do other useful
things that should be “triggered” after the main build.
+</p>
+<hr>
+<div class="header">
+<p>
+Next: <a href="validate_002dall.html#validate_002dall" accesskey="n"
rel="next">validate-all</a>, Previous: <a href="report.html#report"
accesskey="p" rel="previous">report</a>, Up: <a
href="Special-Targets.html#Special-Targets" accesskey="u" rel="up">Special
Targets</a> [<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
+</div>
+
- </body></html>
+</body>
+</html>
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.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- gnun/html_node/update_002dlocalized_002dURLs.html 26 Sep 2012 14:49:46
-0000 1.5
+++ gnun/html_node/update_002dlocalized_002dURLs.html 4 Dec 2012 16:24:24
-0000 1.6
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>update-localized-URLs - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Special-Targets.html#Special-Targets" title="Special
Targets">
-<link rel="prev" href="no_002dgrace_002ditems.html#no_002dgrace_002ditems"
title="no-grace-items">
-<link rel="next" href="sync.html#sync" title="sync">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,45 +9,79 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: update-localized-URLs</title>
+
+<meta name="description" content="GNUnited Nations: update-localized-URLs">
+<meta name="keywords" content="GNUnited Nations: update-localized-URLs">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Special-Targets.html#Special-Targets" rel="up" title="Special
Targets">
+<link href="sync.html#sync" rel="next" title="sync">
+<link href="no_002dgrace_002ditems.html#no_002dgrace_002ditems" rel="previous"
title="no-grace-items">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
-<a name="update-localized-URLs"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="update_002dlocalized_002dURLs"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="sync.html#sync">sync</a>,
-Previous: <a rel="previous" accesskey="p"
href="no_002dgrace_002ditems.html#no_002dgrace_002ditems">no-grace-items</a>,
-Up: <a rel="up" accesskey="u"
href="Special-Targets.html#Special-Targets">Special Targets</a>
-<hr>
+Next: <a href="sync.html#sync" accesskey="n" rel="next">sync</a>, Previous: <a
href="no_002dgrace_002ditems.html#no_002dgrace_002ditems" accesskey="p"
rel="previous">no-grace-items</a>, Up: <a
href="Special-Targets.html#Special-Targets" accesskey="u" rel="up">Special
Targets</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>
-
-<h5 class="subsubsection">2.1.2.2 The <code>update-localized-URLs</code>
Target</h5>
+<hr>
+<a name="The-update_002dlocalized_002dURLs-Target"></a>
+<h4 class="subsubsection">2.1.2.2 The <code>update-localized-URLs</code>
Target</h4>
<p>The <code>update-localized-URLs</code> target invokes a script that
-generates the <samp><span class="file">localized-urls.mk</span></samp> file.
This file includes the
+generates the <samp>localized-urls.mk</samp> file. This file includes the
list of URLs that should be localized, it is extracted from special
comments in the HTML source (see <a
href="Localized-URLs.html#Localized-URLs">Localized URLs</a>).
+</p>
+<p>This target is meant to be rebuilt nightly.
+</p>
- <p>This target is meant to be rebuilt nightly.
- </body></html>
+</body>
+</html>
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.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- gnun/html_node/validate_002dall.html 26 Sep 2012 14:49:46 -0000
1.2
+++ gnun/html_node/validate_002dall.html 4 Dec 2012 16:24:24 -0000
1.3
@@ -1,15 +1,7 @@
-<html lang="en">
-<head>
-<title>validate-all - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Special-Targets.html#Special-Targets" title="Special
Targets">
-<link rel="prev" href="triggers.html#triggers" title="triggers">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -17,44 +9,79 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: validate-all</title>
+
+<meta name="description" content="GNUnited Nations: validate-all">
+<meta name="keywords" content="GNUnited Nations: validate-all">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Special-Targets.html#Special-Targets" rel="up" title="Special
Targets">
+<link href="Main-Variables.html#Main-Variables" rel="next" title="Main
Variables">
+<link href="triggers.html#triggers" rel="previous" title="triggers">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
-<a name="validate-all"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="validate_002dall"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="triggers.html#triggers">triggers</a>,
-Up: <a rel="up" accesskey="u"
href="Special-Targets.html#Special-Targets">Special Targets</a>
-<hr>
+Previous: <a href="triggers.html#triggers" accesskey="p"
rel="previous">triggers</a>, Up: <a href="Special-Targets.html#Special-Targets"
accesskey="u" rel="up">Special Targets</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-validate_002dall-Target"></a>
+<h4 class="subsubsection">2.1.2.6 The <code>validate-all</code> Target</h4>
+<a name="index-validation-2"></a>
-<h5 class="subsubsection">2.1.2.6 The <code>validate-all</code> Target</h5>
-
-<p><a name="index-validation-37"></a>
-The <code>validate-all</code> target validates all HTML pages under GNUN's
-control. It is needed because GNUN doesn't track dependencies on the
+<p>The <code>validate-all</code> target validates all HTML pages under
GNUN’s
+control. It is needed because GNUN doesn’t track dependencies on the
included files, so errors in those included files could pass unnoticed.
+</p>
+<p>This target is invoked once a day by the official GNUN cron job.
+</p>
- <p>This target is invoked once a day by the official GNUN cron job.
- </body></html>
+</body>
+</html>
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.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnun/html_node/validate_002dhtml_002dnotify.html 26 Sep 2012 14:49:46
-0000 1.15
+++ gnun/html_node/validate_002dhtml_002dnotify.html 4 Dec 2012 16:24:24
-0000 1.16
@@ -1,16 +1,7 @@
-<html lang="en">
-<head>
-<title>validate-html-notify - GNUnited Nations</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNUnited Nations">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Scripts.html#Scripts" title="Scripts">
-<link rel="prev" href="mailfail.html#mailfail" title="mailfail">
-<link rel="next"
href="gnun_002dclear_002dprevious.html#gnun_002dclear_002dprevious"
title="gnun-clear-previous">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
-This manual (updated 26 September 2012) is for GNUnited Nations (version
+This manual (updated 3 December 2012) is for GNUnited Nations (version
0.6), a suite for maintaining translations of www.gnu.org
essays and other articles.
@@ -18,60 +9,105 @@
Copyright (C) 2008, 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNUnited Nations: validate-html-notify</title>
+
+<meta name="description" content="GNUnited Nations: validate-html-notify">
+<meta name="keywords" content="GNUnited Nations: validate-html-notify">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Scripts.html#Scripts" rel="up" title="Scripts">
+<link href="gnun_002dclear_002dprevious.html#gnun_002dclear_002dprevious"
rel="next" title="gnun-clear-previous">
+<link href="mailfail.html#mailfail" rel="previous" title="mailfail">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
-<a name="validate-html-notify"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="validate_002dhtml_002dnotify"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="gnun_002dclear_002dprevious.html#gnun_002dclear_002dprevious">gnun-clear-previous</a>,
-Previous: <a rel="previous" accesskey="p"
href="mailfail.html#mailfail">mailfail</a>,
-Up: <a rel="up" accesskey="u" href="Scripts.html#Scripts">Scripts</a>
-<hr>
+Next: <a href="gnun_002dclear_002dprevious.html#gnun_002dclear_002dprevious"
accesskey="n" rel="next">gnun-clear-previous</a>, Previous: <a
href="mailfail.html#mailfail" accesskey="p" rel="previous">mailfail</a>, Up: <a
href="Scripts.html#Scripts" accesskey="u" rel="up">Scripts</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-validate_002dhtml_002dnotify-Script"></a>
+<h4 class="subsection">3.1.9 The <code>validate-html-notify</code> Script</h4>
-<h4 class="subsection">3.1.8 The <samp><span
class="command">validate-html-notify</span></samp> Script</h4>
-
-<p>This script is a wrapper around <samp><span
class="command">gnun-validate-html</span></samp>
+<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
capture the output of the program from a program that itself captures
the output of another program that it runs.
-
- <p>Usage:
-
-<pre class="example"> validate-html-notify [--dry-run] RCPT FILE
-</pre>
- <dl>
-<dt><samp><span class="option">--dry-run</span></samp><dd>Does not actually
send the message, just like <samp><span class="command">mailfail</span></samp>.
-
- <br><dt><samp><span class="option">RCPT</span></samp><dd>The recipient of
the message.
-
- <br><dt><samp><span class="option">FILE</span></samp><dd>The HTML file
that has to be validated for compliance with the W3C
+</p>
+<p>Usage:
+</p>
+<div class="example">
+<pre class="example">validate-html-notify [--dry-run] RCPT FILE
+</pre></div>
+
+<dl compact="compact">
+<dt><samp>--dry-run</samp></dt>
+<dd><p>Does not actually send the message, just like <code>mailfail</code>.
+In this case it runs <code>gnun-validate-html</code> without
+<samp>--verbose</samp> because it is expected that the expanded file
+will be available locally.
+</p>
+</dd>
+<dt><samp>RCPT</samp></dt>
+<dd><p>The recipient of the message.
+</p>
+</dd>
+<dt><samp>FILE</samp></dt>
+<dd><p>The HTML file that has to be validated for compliance with the W3C
standard.
+</p></dd>
</dl>
- <p>The subject of the message is hardcoded in the script, since this
+<p>The subject of the message is hardcoded in the script, since this
wrapper has a specific task and cannot be used to invoke an arbitrary
-command—use <samp><span class="command">mailfail</span></samp> for that.
See <a href="mailfail.html#mailfail">mailfail</a>.
+command—use <code>mailfail</code> for that. See <a
href="mailfail.html#mailfail">mailfail</a>.
+</p>
+
- </body></html>
+</body>
+</html>
Index: web-trans/index.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/index.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- web-trans/index.html 29 Sep 2012 06:53:48 -0000 1.10
+++ web-trans/index.html 4 Dec 2012 16:24:25 -0000 1.11
@@ -4,31 +4,31 @@
<h2>GNU Web Translators Manual</h2>
<address>Free Software Foundation</address>
-<address>last updated September 29, 2012</address>
+<address>last updated December 04, 2012</address>
<p>This manual (web-trans) is available in the following formats:</p>
<ul>
<li><a href="web-trans.html">HTML
- (132K 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
- (44K 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>
<li><a href="web-trans.txt">ASCII text
(96K bytes)</a>.</li>
<li><a href="web-trans.txt.gz">ASCII text compressed
- (36K bytes gzipped)</a>.</li>
+ (32K bytes gzipped)</a>.</li>
<li><a href="web-trans.dvi.gz">TeX dvi file
(56K bytes gzipped)</a>.</li>
<li><a href="web-trans.ps.gz">PostScript file
- (260K bytes gzipped)</a>.</li>
+ (264K bytes gzipped)</a>.</li>
<li><a href="web-trans.pdf">PDF file
(348K bytes)</a>.</li>
<li><a href="web-trans.texi.tar.gz">Texinfo source
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.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
Binary files /tmp/cvsVYdtAZ and /tmp/cvsU1cdd1 differ
Index: web-trans/web-trans.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- web-trans/web-trans.html 29 Sep 2012 06:53:48 -0000 1.10
+++ web-trans/web-trans.html 4 Dec 2012 16:24:25 -0000 1.11
@@ -1,167 +1,198 @@
-<html lang="en">
-<head>
-<title>GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled "GNU Free Documentation License."
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual</title>
+
+<meta name="description" content="GNU Web Translators Manual">
+<meta name="keywords" content="GNU Web Translators Manual">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="#Top" rel="start" title="Top">
+<link href="#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="dir.html#Top" rel="up" title="(dir)">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<h1 class="settitle">GNU Web Translators Manual</h1>
- <div class="contents">
-<h2>Table of Contents</h2>
-<ul>
-<li><a name="toc_Top" href="#Top">GNU Web Translators Manual</a>
-<li><a name="toc_Introduction" href="#Introduction">1 Introduction</a>
-<li><a name="toc_Members" href="#Members">2 Team Members</a>
-<ul>
-<li><a href="#Joining">2.1 Joining A Team</a>
-<li><a href="#Submitting">2.2 How To Submit a Translation</a>
-<ul>
-<li><a href="#Submitting-as-PO">2.2.1 How To Submit a Translation in PO
Format</a>
-<li><a href="#Submitting-as-Plain-Text">2.2.2 How To Submit a Translation as
Plain Text</a>
-</li></ul>
-<li><a href="#Leaving-A-Team">2.3 Leaving A Team</a>
-</li></ul>
-<li><a name="toc_Leaders" href="#Leaders">3 Team Co-ordinators</a>
-<ul>
-<li><a href="#New-Team">3.1 How To Form A New Team</a>
-<li><a href="#Managing">3.2 The Gentle Art of Managing A Translation Team</a>
-<ul>
-<li><a href="#Review">3.2.1 Peer Review</a>
-<ul>
-<li><a href="#Tracking-Tasks">3.2.1.1 How To Track Tasks and Bugs Using
Savannah</a>
-<li><a href="#Unreviewed-Translations">3.2.1.2 How To Proceed With Unreviewed
Translations</a>
-</li></ul>
-<li><a href="#Commits">3.2.2 CVS Commits And Best Practices</a>
-<li><a href="#Savannah">3.2.3 Taking Advantage of Savannah</a>
-<ul>
-<li><a href="#Savannah-Members">3.2.3.1 Managing Members</a>
-<li><a href="#Savannah-Homepage">3.2.3.2 Homepage of The Team</a>
-<li><a href="#Savannah-Support">3.2.3.3 Support Tracker</a>
-<li><a href="#Savannah-Tasks">3.2.3.4 Tasks Tracker</a>
-<li><a href="#Savannah-Bugs">3.2.3.5 Bugs Tracker</a>
-<li><a href="#Savannah-Patch">3.2.3.6 Patch Tracker</a>
-<li><a href="#Savannah-News">3.2.3.7 News Tracker</a>
-<li><a href="#Savannah-Mailing-Lists">3.2.3.8 Managing Mailing Lists</a>
-<li><a href="#Savannah-VCS">3.2.3.9 Version Control Systems</a>
-</li></ul>
-<li><a href="#Co_002dleaders">3.2.4 Promoting Members As Co-leaders</a>
-</li></ul>
-<li><a href="#Reports">3.3 Reporting Team Status</a>
-<li><a href="#Stepping-Down">3.4 How To Retire Painlessly</a>
-</li></ul>
-<li><a name="toc_Translation-Managers" href="#Translation-Managers">4
‘<samp><span class="samp">trans-coord</span></samp>’ Admins</a>
-<li><a name="toc_Translation-Tips" href="#Translation-Tips">5 Details About
The Translation Process</a>
-<ul>
-<li><a href="#Migrating">5.1 Migration To The New Style</a>
-<li><a href="#SSI">5.2 Summary of SSI <code>#include</code>s</a>
-<li><a href="#CSS">5.3 How To Use Custom CSS</a>
-<ul>
-<li><a href="#topbanner">5.3.1 Localizing The <samp><span
class="file">topbanner</span></samp> Image</a>
-<li><a href="#RTL">5.3.2 Specific Issues Related to RTL</a>
-</li></ul>
-<li><a href="#Priorities">5.4 What To Translate</a>
-<li><a href="#Capitalization">5.5 When To CAPITALIZE</a>
-<li><a href="#Distribution-Terms">5.6 Distribution Terms</a>
-<li><a href="#Terminology">5.7 Language-specific Terminology</a>
-</li></ul>
-<li><a name="toc_Summary" href="#Summary">6 Overview Of The Translation
Process</a>
-<ul>
-<li><a href="#Mailing-Lists">6.1 Related Mailing Lists</a>
-<li><a href="#Savannah-Projects">6.2 Savannah Projects Membership</a>
-</li></ul>
-<li><a name="toc_Copying-This-Manual" href="#Copying-This-Manual">Appendix A
GNU Free Documentation License</a>
-</li></ul>
-</div>
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+<h1 class="settitle" align="center">GNU Web Translators Manual</h1>
-<div class="node">
-<a name="Top"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Introduction">Introduction</a>,
-Up: <a rel="up" accesskey="u" href="#dir">(dir)</a>
+<a name="SEC_Contents"></a>
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="no-bullet">
+ <li><a name="toc-Introduction-1" href="#Introduction">1 Introduction</a></li>
+ <li><a name="toc-Team-Members" href="#Members">2 Team Members</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Joining-A-Team" href="#Joining">2.1 Joining A
Team</a></li>
+ <li><a name="toc-How-To-Submit-a-Translation" href="#Submitting">2.2 How
To Submit a Translation</a>
+ <ul class="no-bullet">
+ <li><a name="toc-How-To-Submit-a-Translation-in-PO-Format"
href="#Submitting-as-PO">2.2.1 How To Submit a Translation in PO Format</a></li>
+ <li><a name="toc-How-To-Submit-a-Translation-as-Plain-Text"
href="#Submitting-as-Plain-Text">2.2.2 How To Submit a Translation as Plain
Text</a></li>
+ </ul></li>
+ <li><a name="toc-Leaving-A-Team-1" href="#Leaving-A-Team">2.3 Leaving A
Team</a></li>
+ </ul></li>
+ <li><a name="toc-Team-Co_002dordinators" href="#Leaders">3 Team
Co-ordinators</a>
+ <ul class="no-bullet">
+ <li><a name="toc-How-To-Form-A-New-Team" href="#New-Team">3.1 How To Form
A New Team</a></li>
+ <li><a name="toc-The-Gentle-Art-of-Managing-A-Translation-Team"
href="#Managing">3.2 The Gentle Art of Managing A Translation Team</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Peer-Review" href="#Review">3.2.1 Peer Review</a>
+ <ul class="no-bullet">
+ <li><a name="toc-How-To-Track-Tasks-and-Bugs-Using-Savannah"
href="#Tracking-Tasks">3.2.1.1 How To Track Tasks and Bugs Using
Savannah</a></li>
+ <li><a name="toc-How-To-Proceed-With-Unreviewed-Translations"
href="#Unreviewed-Translations">3.2.1.2 How To Proceed With Unreviewed
Translations</a></li>
+ </ul></li>
+ <li><a name="toc-CVS-Commits-And-Best-Practices" href="#Commits">3.2.2
CVS Commits And Best Practices</a></li>
+ <li><a name="toc-Taking-Advantage-of-Savannah" href="#Savannah">3.2.3
Taking Advantage of Savannah</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Managing-Members" href="#Savannah-Members">3.2.3.1
Managing Members</a></li>
+ <li><a name="toc-Homepage-of-The-Team"
href="#Savannah-Homepage">3.2.3.2 Homepage of The Team</a></li>
+ <li><a name="toc-Support-Tracker" href="#Savannah-Support">3.2.3.3
Support Tracker</a></li>
+ <li><a name="toc-Tasks-Tracker" href="#Savannah-Tasks">3.2.3.4 Tasks
Tracker</a></li>
+ <li><a name="toc-Bugs-Tracker" href="#Savannah-Bugs">3.2.3.5 Bugs
Tracker</a></li>
+ <li><a name="toc-Patch-Tracker" href="#Savannah-Patch">3.2.3.6 Patch
Tracker</a></li>
+ <li><a name="toc-News-Tracker" href="#Savannah-News">3.2.3.7 News
Tracker</a></li>
+ <li><a name="toc-Managing-Mailing-Lists"
href="#Savannah-Mailing-Lists">3.2.3.8 Managing Mailing Lists</a></li>
+ <li><a name="toc-Version-Control-Systems" href="#Savannah-VCS">3.2.3.9
Version Control Systems</a></li>
+ </ul></li>
+ <li><a name="toc-Promoting-Members-As-Co_002dleaders"
href="#Co_002dleaders">3.2.4 Promoting Members As Co-leaders</a></li>
+ </ul></li>
+ <li><a name="toc-Reporting-Team-Status" href="#Reports">3.3 Reporting Team
Status</a></li>
+ <li><a name="toc-How-To-Retire-Painlessly" href="#Stepping-Down">3.4 How
To Retire Painlessly</a></li>
+ </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>
+ <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>
+ <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>
+ </ul></li>
+ <li><a name="toc-What-To-Translate" href="#Priorities">5.4 What To
Translate</a></li>
+ <li><a name="toc-When-To-CAPITALIZE" href="#Capitalization">5.5 When To
CAPITALIZE</a></li>
+ <li><a name="toc-Distribution-Terms-1" href="#Distribution-Terms">5.6
Distribution Terms</a></li>
+ <li><a name="toc-Language_002dspecific-Terminology"
href="#Terminology">5.7 Language-specific Terminology</a></li>
+ </ul></li>
+ <li><a name="toc-Overview-Of-The-Translation-Process" href="#Summary">6
Overview Of The Translation Process</a>
+ <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>
+ </ul></li>
+ <li><a name="toc-GNU-Free-Documentation-License"
href="#Copying-This-Manual">Appendix A GNU Free Documentation License</a></li>
+</ul>
</div>
-<h2 class="unnumbered">GNU Web Translators Manual</h2>
+
+
+<a name="Top"></a>
+<div class="header">
+<p>
+Next: <a href="#Introduction" accesskey="n" rel="next">Introduction</a>, Up:
<a href="dir.html#Top" accesskey="u" rel="up">(dir)</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
+</div>
+<a name="GNU-Web-Translators-Manual"></a>
+<h1 class="top">GNU Web Translators Manual</h1>
<p>This manual is a guide for the GNU Web Translators.<br> Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- <pre class="sp">
-
-</pre>
-Copyright © 2009, 2010, 2011, 2012 Free Software
+</p><br>
+<p>Copyright © 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
-
- <blockquote>
-Permission is granted to copy, distribute and/or modify this document
+</p>
+<blockquote>
+<p>Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled “GNU Free
Documentation License.”
-</blockquote>
+</p></blockquote>
+
-<ul class="menu">
-<li><a accesskey="1" href="#Introduction">Introduction</a>: Begin of
the journey.
-<li><a accesskey="2" href="#Members">Members</a>: Information
for translation team members.
-<li><a accesskey="3" href="#Leaders">Leaders</a>: Guidelines and
procedures for team leaders.
-<li><a accesskey="4" href="#Translation-Managers">Translation Managers</a>:
Responsibilities of the GNU Web Translation
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#Introduction"
accesskey="1">Introduction</a>:</td><td> </td><td align="left"
valign="top">Begin of the journey.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Members"
accesskey="2">Members</a>:</td><td> </td><td align="left"
valign="top">Information for translation team members.
+</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.
-<li><a accesskey="5" href="#Translation-Tips">Translation Tips</a>:
Explanation of some non-obvious things.
-<li><a accesskey="6" href="#Summary">Summary</a>: Overview.
-<!-- * Index:: -->
-<li><a accesskey="7" href="#Copying-This-Manual">Copying This Manual</a>:
The GNU Free Documentation License.
-</ul>
+</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.
+</td></tr>
+</table>
-<div class="node">
+<hr>
<a name="Introduction"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Members">Members</a>,
-Previous: <a rel="previous" accesskey="p" href="#Top">Top</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Next: <a href="#Members" accesskey="n" rel="next">Members</a>, Previous: <a
href="#Top" accesskey="p" rel="previous">Top</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="Introduction-1"></a>
<h2 class="chapter">1 Introduction</h2>
<p>This manual is an attempt to describe in detail the process of
translating www.gnu.org articles—how to join a team, or start a new
one, the responsibilities of the team members and leaders, as well as
-some peculiarities of the GNU Project's website when it comes to
+some peculiarities of the GNU Project’s website when it comes to
localization.
-
- <p>The GNU website contains hundreds of documents, most of them
+</p>
+<p>The GNU website contains hundreds of documents, most of them
philosophical articles (essays) and technical documents which need to be
translated to make them available to a broader audience. This is
especially important for the philosophy-related materials, as many
@@ -170,14 +201,14 @@
translating a website this large is a hard job, and too often people
volunteering as translators get frustrated or lose interest in keeping
up with that work. Reading this manual, and the related GNUN manual
-(see <a href="gnun.html#Top">GNUnited Nations</a>), is
+(see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#Top";>GNUnited
Nations</a> in <cite>The GNUnited Nations Manual</cite>), is
just the tip of the iceberg. This is not meant to discourage any
potential volunteer; rather, we prefer to be honest and to give
preliminary estimation of the work/responsibility involved—if you feel
you are not in a position to help you may move on to a smaller project
before going through all procedures.
-
- <p>It is important to realize that being a GNU Web Translator is a hard job
+</p>
+<p>It is important to realize that being a GNU Web Translator is a hard job
at all levels, but your help is much appreciated and is invaluable
contribution to the society. While there are many people who contribute
to our community by writing free software (and their number is
@@ -186,150 +217,151 @@
rather unfortunately, there are not so many volunteers willing to
maintain on the long term translations of the various essays that
describe the fundamental values of the free software movement.
-
- <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, who are
+</p>
+<p>Translators of the <a href="http://gnu.org";>http://gnu.org</a> website are
organized in
+language teams. Each team has one or more co-ordinators (a.k.a
+leaders), who are
responsible for the respective team. The co-ordinators participate in
-the Savannah ‘<samp><span class="samp">trans-coord</span></samp>’
organizational project, which is managed
+the Savannah ‘<samp>trans-coord</samp>’ organizational project,
which is managed
by the GNU Web Translation Managers. The manual is organized in
chapters that follow the organizational structure of the whole
translation project.
-
- <p>If you wish to join a translation team or contribute a translation or
+</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><span
class="samp">trans-coord</span></samp>’
-administrators (a.k.a. <dfn>GNU Translation Managers</dfn>) describes all the
+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>.
-
-<div class="node">
+</p>
+<hr>
<a name="Members"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Leaders">Leaders</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Introduction">Introduction</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Next: <a href="#Leaders" accesskey="n" rel="next">Leaders</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>]</p>
</div>
-
+<a name="Team-Members"></a>
<h2 class="chapter">2 Team Members</h2>
<p>Being a team member means to co-operate with a group of other people,
working under the co-ordinatorship of the appointed team leader.
Usually, this involves translating articles and reviewing/proof-reading
-other people's translations, participating in discussions about
+other people’s translations, participating in discussions about
terminology issues, and sometimes performing clean-up tasks.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#Joining"
accesskey="1">Joining</a>:</td><td> </td><td align="left"
valign="top">How to join a translation team.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Submitting"
accesskey="2">Submitting</a>:</td><td> </td><td align="left"
valign="top">Submitting a translation when there is no team.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Leaving-A-Team"
accesskey="3">Leaving A Team</a>:</td><td> </td><td align="left"
valign="top">Leave when you have to.
+</td></tr>
+</table>
-<ul class="menu">
-<li><a accesskey="1" href="#Joining">Joining</a>: How to join a
translation team.
-<li><a accesskey="2" href="#Submitting">Submitting</a>: Submitting a
translation when there is no team.
-<li><a accesskey="3" href="#Leaving-A-Team">Leaving A Team</a>: Leave
when you have to.
-</ul>
-
-<div class="node">
+<hr>
<a name="Joining"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Submitting">Submitting</a>,
-Up: <a rel="up" accesskey="u" href="#Members">Members</a>
-
+<div class="header">
+<p>
+Next: <a href="#Submitting" accesskey="n" rel="next">Submitting</a>, Up: <a
href="#Members" accesskey="u" rel="up">Members</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<a name="Joining-A-Team"></a>
<h3 class="section">2.1 Joining A Team</h3>
<p>To join a team, please first look at the existing teams at
<a
href="http://www.gnu.org/server/standards/README.translations.html#TranslationsUnderway";>http://www.gnu.org/server/standards/README.translations.html#TranslationsUnderway</a>.
Chances are that there is already an established team. If there is no
team listed for your language, this means that:
-
- <ul>
-<li>There is no team established and there are no translations to this
+</p>
+<ul>
+<li> There is no team established and there are no translations to this
language.
- <li>Some translations were submitted by occasional contributors, but no
team
+</li><li> Some translations were submitted by occasional contributors, but no
team
has ever been formed.
- <li>The page is not updated to reflect the current situation (this
shouldn't
-happen, but it's a possibility anyway).
-</ul>
+</li><li> The page is not updated to reflect the current situation (this
shouldn’t
+happen, but it’s a possibility anyway).
+</li></ul>
- <p>If the team is marked as <dfn>orphaned</dfn>, there is no problem: you
can
+<p>If the team is marked as <em>orphaned</em>, there is no problem: you can
still submit your translation to <a
href="mailto:address@hidden";>address@hidden</a>
(see <a href="#Submitting">Submitting</a>). In case you want to establish a
new translation
team or become a co-ordinator of an existing one, please refer to the
next chapter, see <a href="#Leaders">Leaders</a>.
-
- <p>Contacting the team is best done via Savannah—each translation team
-has its own project, named ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’, with the project
+</p>
+<p>Contacting the team is best done via Savannah—each translation team
+has its own project, named ‘<samp>www-<var>lang</var></samp>’,
with the project
page being
-<<code>https://savannah.gnu.org/projects/www-</code><var>lang</var>>.
-Usually teams have mailing lists, typically in the form
-<a href="mailto:www-<var>lang</var>address@hidden">www-<var>lang</var>-<small
class="dots">...</small>@gnu.org</a>. Some teams have homepages,
-<<code>http://gnu.org/server/standards/translations/</code><var>lang</var>>
+‘<code>https://savannah.gnu.org/projects/www-<var>lang</var></code>’.
+All teams should have mailing lists, typically in the form
+<a
href="mailto:www-lang-…@gnu.org";>www-<var>lang</var>-…@gnu.org</a>.
Some teams have homepages,
+‘<code>http://gnu.org/server/standards/translations/<var>lang</var></code>’
with additional contact details and procedures for team members.
-
- <p>You could also write directly to the team leader via the Savannah
+</p>
+<p>You could also write directly to the team leader via the Savannah
interface—that way your request will be recorded by Savannah and can be
tracked or completed when the membership is approved.
-
- <p>The actual process of submitting translations for review varies from
+</p>
+<p>The actual process of submitting translations for review varies from
team to team, as teams have certain liberties to organize themselves as
they see fit. Thus, this manual does not make any attempt to cover that
aspect—please refer to the team-specific documentation (if any) or ask
the co-ordinator.
-
- <p>Certainly, it is not mandatory to be an active team member to contribute
-a translation or two. If you feel that you don't have the time to
+</p>
+<p>Certainly, it is not mandatory to be an active team member to contribute
+a translation or two. If you feel that you don’t have the time to
participate actively, that is fine; you can still send your translation
to the team. No contributions should be rejected.
-
- <p>If you do not hear from the team within a reasonable time frame (say,
+</p>
+<p>If you do not hear from the team within a reasonable time frame (say,
two weeks), please write to <a href="mailto:address@hidden";>address@hidden</a>.
-
- <p>For general information about the translation process,
+</p>
+<p>For general information about the translation process,
see <a href="#Translation-Tips">Translation Tips</a>.
-
-<div class="node">
+</p>
+<hr>
<a name="Submitting"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Leaving-A-Team">Leaving A
Team</a>,
-Previous: <a rel="previous" accesskey="p" href="#Joining">Joining</a>,
-Up: <a rel="up" accesskey="u" href="#Members">Members</a>
-
+<div class="header">
+<p>
+Next: <a href="#Leaving-A-Team" accesskey="n" rel="next">Leaving A Team</a>,
Previous: <a href="#Joining" accesskey="p" rel="previous">Joining</a>, Up: <a
href="#Members" accesskey="u" rel="up">Members</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<a name="How-To-Submit-a-Translation"></a>
<h3 class="section">2.2 How To Submit a Translation</h3>
<p>Everyone can still submit translations even if there is no translation
team formed. There are two ways to do that—following the existing
procedures, which is the preferred way, and sending it as plain text,
which means more work for a limited group of volunteers (the Translation
-Managers) to convert the translation in <samp><span
class="file">.po</span></samp> format.
+Managers) to convert the translation in <samp>.po</samp> format.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#Submitting-as-PO"
accesskey="1">Submitting as PO</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Submitting-as-Plain-Text"
accesskey="2">Submitting as Plain Text</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+</table>
-<ul class="menu">
-<li><a accesskey="1" href="#Submitting-as-PO">Submitting as PO</a>
-<li><a accesskey="2" href="#Submitting-as-Plain-Text">Submitting as Plain
Text</a>
-</ul>
-
-<div class="node">
+<hr>
<a name="Submitting-as-PO"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#Submitting-as-Plain-Text">Submitting as Plain Text</a>,
-Up: <a rel="up" accesskey="u" href="#Submitting">Submitting</a>
-
+<div class="header">
+<p>
+Next: <a href="#Submitting-as-Plain-Text" accesskey="n" rel="next">Submitting
as Plain Text</a>, Up: <a href="#Submitting" accesskey="u"
rel="up">Submitting</a> [<a href="#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
-
+<a name="How-To-Submit-a-Translation-in-PO-Format"></a>
<h4 class="subsection">2.2.1 How To Submit a Translation in PO Format</h4>
-<p>All translations<a rel="footnote" href="#fn-1"
name="fnd-1"><sup>1</sup></a> are maintained via GNUN (see
+<p>All translations<a name="DOCF1" href="#FOOT1"><sup>1</sup></a> are
maintained via GNUN (see
<a
href="http://www.gnu.org/software/gnun/";>http://www.gnu.org/software/gnun/</a>),
which significantly eases
maintenance and avoids the unpleasant situation where a translation is
-lagging behind the original. See <a
href="gnun.html#Advantages">Advantages</a>.
-
- <p>As of September 2008 all new translations at gnu.org are installed in
-<samp><span class="file">.po</span></samp> format, and the <samp><span
class="file">.html</span></samp> is generated automatically.
+lagging behind the original. See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#Advantages";>Advantages</a>
in <cite>The GNUnited
+Nations Manual</cite>.
+</p>
+<p>Since September 2008 all new translations at gnu.org are installed in
+<samp>.po</samp> format, and the <samp>.html</samp> is generated automatically.
Here are the steps to produce and submit such a translation:
-
- <ul>
-<li>Make a checkout of the CVS Web repository of the ‘<samp><span
class="samp">www</span></samp>’ Savannah
+</p>
+<ul>
+<li> Make a checkout of the CVS Web repository of the
‘<samp>www</samp>’ Savannah
project. You can find generic instructions at
<a
href="https://savannah.gnu.org/cvs/?group=www";>https://savannah.gnu.org/cvs/?group=www</a>.
All updates to the
website are done as commits in the repository, so you would need an
@@ -338,58 +370,65 @@
Savannah to use it. You can also check out only a specific directory,
for example:
- <pre class="example"> cvs -z3 -d:pserver:address@hidden:/web/www
co www/gnu
-</pre>
- <p>This command will fetch only the <samp><span
class="file">/gnu</span></samp> directory—in other words,
-all articles at <a href="http://gnu.org/gnu";>http://gnu.org/gnu</a>.
+<div class="example">
+<pre class="example">cvs -z3 -d:pserver:address@hidden:/web/www co www/gnu
+</pre></div>
- <li>Assuming you already know the article you want to translate, you have
to
-create an empty <samp><var>article</var><span
class="file">.</span><var>lang</var><span class="file">.po</span></samp> file
and then
-translate all messages with a PO editor. See <a
href="gnun.html#New-Translation">New Translation</a>. For an almost complete
list of PO
-editors, see <a href="gnun.html#PO-Files">PO Files</a>.
+<p>This command will fetch only the <samp>/gnu</samp> directory—in other
words,
+all articles at <a href="http://gnu.org/gnu";>http://gnu.org/gnu</a>.
+</p>
+<p>You can also fetch single files by their respective URLs. For example,
+the URL for the template file of
+<a
href="http://www.gnu.org/philosophy/free-sw.html";>http://www.gnu.org/philosophy/free-sw.html</a>
is
+<a
href="http://www.gnu.org/philosophy/po/free-sw.pot";>http://www.gnu.org/philosophy/po/free-sw.pot</a>;
the URL for
+its <var>lang</var> PO file (when available) is
+<a
href="http://www.gnu.org/philosophy/po/free-sw.lang.po";>http://www.gnu.org/philosophy/po/free-sw.lang.po</a>:
+</p>
+<div class="example">
+<pre class="example">wget http://www.gnu.org/philosophy/po/free-sw.pot
+</pre></div>
+
+</li><li> Assuming you already know the article you want to translate, you
have to
+create an empty <samp><var>article</var>.<var>lang</var>.po</samp> file and
then
+translate all messages with a PO editor. See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#New-Translation";>New
Translation</a> in <cite>The GNUnited Nations Manual</cite>. For an almost
complete list of PO
+editors, see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#PO-Files";>PO
Files</a> in <cite>The GNUnited Nations Manual</cite>.
- <li>When you are pleased with the translation, check that the PO file is
+</li><li> When you are pleased with the translation, check that the PO file is
valid and submit it to <a href="mailto:address@hidden";>address@hidden</a>,
attached to
your message. The web-translators will review (to the best of their
ability) the translation and will install it in the repository.
- <li>In order GNUN to be able to generate (and subsequently update) a
-gettextized translation, the language should have the server templates
+</li><li> In order GNUN to be able to generate (and subsequently update) a
fully
+translated page, the language should have the server templates
available as PO files. These templates are short, and translating them
-shouldn't take much time. If the language code is present in the
-<code>TEMPLATE_LINGUAS</code> variable at <samp><span
class="file">server/gnun/gnun.mk</span></samp>, then you
-don't have to do anything. If it is not, the required files are
-<samp><span class="file">server/po/head-include-2.</span><var>lang</var><span
class="file">.po</span></samp>,
-<samp><span class="file">server/po/body-include-1.</span><var>lang</var><span
class="file">.po</span></samp>,
-<samp><span class="file">server/po/body-include-2.</span><var>lang</var><span
class="file">.po</span></samp> and
-<samp><span class="file">server/po/footer-text.</span><var>lang</var><span
class="file">.po</span></samp>—you can translate and
+shouldn’t take much time. If the language code is present in the
+<code>TEMPLATE_LINGUAS</code> variable at <samp>server/gnun/gnun.mk</samp>,
then you
+don’t have to do anything. If it is not, the required files
+are defined via the <code>extra-templates</code> variable
+in <samp>server/gnun/gnun.mk</samp>—you can translate and
submit them in the usual way, together with the translation of the
essay.
- <p>Additional templates are defined via the <var>extra-templates</var>
variable
-in <samp><span class="file">server/gnun/gnun.mk</span></samp>.
-
- <p>If you don't want to translate the templates for whatever
reason—do
+<p>If you don’t want to translate the templates for whatever
reason—do
not worry, the web-translators will install empty templates (which means
the English strings will be used).
-</ul>
+</p></li></ul>
- <p>It is quite possible that there will be errors or typos, so once you are
+<p>It is quite possible that there will be errors or typos, so once you are
informed that the translation is online, check it carefully and if
necessary, resubmit the PO file with corrections. Do not forget to run
-<code>cvs update</code> first and edit the updated <samp><span
class="file">.po</span></samp> file from the
+<code>cvs update</code> first and edit the updated <samp>.po</samp> file from
the
repository—most probably the Translation Managers have already made
some modifications to it, usually to fix validation errors and to
complete the PO file header.
-
-<div class="node">
+</p>
+<hr>
<a name="Submitting-as-Plain-Text"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p"
href="#Submitting-as-PO">Submitting as PO</a>,
-Up: <a rel="up" accesskey="u" href="#Submitting">Submitting</a>
-
+<div class="header">
+<p>
+Previous: <a href="#Submitting-as-PO" accesskey="p" rel="previous">Submitting
as PO</a>, Up: <a href="#Submitting" accesskey="u" rel="up">Submitting</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-
+<a name="How-To-Submit-a-Translation-as-Plain-Text"></a>
<h4 class="subsection">2.2.2 How To Submit a Translation as Plain Text</h4>
<p>If you feel the procedure described in the previous section is too
@@ -398,29 +437,35 @@
the GNU Web Translation Managers, which can be tricky sometimes, and
naturally, means more work for them and slower processing of your
request.
-
- <p>You should <em>never</em> translate the HTML markup—i.e. <em>do
not</em>
+</p>
+<p>You should <em>never</em> translate the HTML markup—i.e. <em>do
not</em>
use the “View Source” functionality of your browser to translate
the
raw HTML. Most of it is irrelevant, and automatically inherited from
the markup of the original article. Simply save your translation in a
-plain text file (<samp><span class="file">.txt</span></samp>), preferably in
UTF-8 encoding. You can
+plain text file (<samp>.txt</samp>), preferably in UTF-8 encoding. You can
use any decent text editor for that—Emacs, Vim, gEdit, Kate,
-OpenOffice.org (the file should be saved as <samp><span
class="file">.txt</span></samp>, not
-<samp><span class="file">.odt</span></samp>), etc.
-
- <p>Translate the title, the blue heading (if it differs slightly from the
-title) and the body of the article upto the link ‘<samp><span
class="samp">back to top</span></samp>’.
+OpenOffice.org (the file should be saved as <samp>.txt</samp>, not
+<samp>.odt</samp>), etc.
+</p>
+<p>Translate the title, the blue heading (if it differs slightly from the
+title) and the body of the article upto the link ‘<samp>back to
top</samp>’.
For example, for <a
href="http://www.gnu.org/philosophy/free-sw.html";>http://www.gnu.org/philosophy/free-sw.html</a>
that would be:
+</p>
+<div class="example">
+<pre class="example">What is free software? - GNU Project - Free Software
Foundation (FSF)
-<pre class="example"> The Free Software Definition - GNU Project - Free
Software Foundation (FSF)
+What is free software?
- We maintain this free software definition...
- ...
- ...If you would like to review the complete list of changes, you can
- do so on our cvsweb interface.
-</pre>
- <p>Since web-translators do not speak all languages, it is essential to
+The Free Software Definition
+
+The free software definition presents…
+…
+…You can review the complete list of changes to the page through
+the cvsweb interface.
+</pre></div>
+
+<p>Since web-translators do not speak all languages, it is essential to
mark somehow any inner markup, because very often it is hard to figure
out what translated text should be enclosed inside <code><em></code> or
<code><a></code> elements, to name a few. The easiest way to do this is
just
@@ -428,85 +473,87 @@
suitable. For example, here is how to indicate that the link “History
section” at the first paragraph of the same article should correspond
to “sección historial” in the translation:
+</p>
+<div class="example">
+<pre class="example">Si quisiera revisar los cambios que hemos hecho, por
favor vea la
+{sección historial} más abajo para más información.
+</pre></div>
-<pre class="example"> Si quisiera revisar los cambios que hemos hecho, por
favor vea la
- {sección historial} más abajo para más
información.
-</pre>
- <p>It is not necessary to include the value of the <code>href</code>
attribute,
+<p>It is not necessary to include the value of the <code>href</code> attribute,
as it is already known.
-
- <p>If you wish your name to appear in the footer as a translator of the
-article, please also provide a translation of ‘<samp><span
class="samp">Translation:
-</span><var>your name in your native language</var></samp>’ or
‘<samp><span class="samp">Translated by:
-</span><var>your name in your native language</var></samp>’, as you
prefer. Please also
+</p>
+<p>If you wish your name to appear in the footer as a translator of the
+article, please also provide a translation of ‘<samp>Translation:
+<var>your name in your native language</var></samp>’ or
‘<samp>Translated by:
+<var>your name in your native language</var></samp>’, as you prefer.
Please also
state if you wish your email address to be published (some readers
prefer to send suggestions directly to the translator, but we certainly
do not require that translators must publish their address).
-
- <p>Finally, send the translation to <a
href="mailto:address@hidden";>address@hidden</a>,
+</p>
+<p>Finally, send the translation to <a
href="mailto:address@hidden";>address@hidden</a>,
either inline or as an attachment to your message. Once online, please
check for any errors or omissions that may have resulted from the
conversion process, and report them back.
-
-<div class="node">
+</p>
+<hr>
<a name="Leaving-A-Team"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p"
href="#Submitting">Submitting</a>,
-Up: <a rel="up" accesskey="u" href="#Members">Members</a>
-
+<div class="header">
+<p>
+Previous: <a href="#Submitting" accesskey="p" rel="previous">Submitting</a>,
Up: <a href="#Members" accesskey="u" rel="up">Members</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<a name="Leaving-A-Team-1"></a>
<h3 class="section">2.3 Leaving A Team</h3>
-<p>When you realize that you don't have time or can't devote sufficient
+<p>When you realize that you don’t have time or can’t devote
sufficient
resources to perform the tasks anymore, it is prudent to inform the
translation team co-ordinator and possibly all the rest of the
team-mates. The team leader should always have a rough estimation about
the available translators, even though there are no reliable means to
establish that. Your announcement that you are stepping down
(temporarily or permanently) may help her in this regard.
-
-<div class="node">
+</p>
+<hr>
<a name="Leaders"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#Translation-Managers">Translation Managers</a>,
-Previous: <a rel="previous" accesskey="p" href="#Members">Members</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</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>
</div>
-
+<a name="Team-Co_002dordinators"></a>
<h2 class="chapter">3 Team Co-ordinators</h2>
<p>A gnu.org translation team leader is the person who is ultimately
responsible for organizing and managing the team, including, but not
limited to, having the final say on contributed translations and
exercising levels of control as she sees fit.
-
- <p>A prospective team co-ordinator should have perfect understanding of the
+</p>
+<p>A prospective team co-ordinator should have perfect understanding of the
GNU Philosophy and the various issues the free software movement set out
to solve. Energy and time are always needed, as well as certain
communication skills.
-
- <p>However, a team leader is not a dictator (for life); every action and/or
+</p>
+<p>However, a team leader is not a dictator (for life); every action and/or
decision taken should have its justification and should stem from the
goals of the project at large. Inefficient or inoperative leaders are
replaced, if necessary.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#New-Team" accesskey="1">New
Team</a>:</td><td> </td><td align="left" valign="top">Procedures to
establish a new team.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Managing"
accesskey="2">Managing</a>:</td><td> </td><td align="left"
valign="top">General guidelines how to manage a team.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Reports"
accesskey="3">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="4">Stepping Down</a>:</td><td> </td><td align="left"
valign="top">Orphaning the team and finding a replacement.
+</td></tr>
+</table>
-<ul class="menu">
-<li><a accesskey="1" href="#New-Team">New Team</a>: Procedures to
establish a new team.
-<li><a accesskey="2" href="#Managing">Managing</a>: General
guidelines how to manage a team.
-<li><a accesskey="3" href="#Reports">Reports</a>: Reporting team
status and activity.
-<li><a accesskey="4" href="#Stepping-Down">Stepping Down</a>: Orphaning
the team and finding a replacement.
-</ul>
-
-<div class="node">
+<hr>
<a name="New-Team"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Managing">Managing</a>,
-Up: <a rel="up" accesskey="u" href="#Leaders">Leaders</a>
-
+<div class="header">
+<p>
+Next: <a href="#Managing" accesskey="n" rel="next">Managing</a>, Up: <a
href="#Leaders" accesskey="u" rel="up">Leaders</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<a name="How-To-Form-A-New-Team"></a>
<h3 class="section">3.1 How To Form A New Team</h3>
<p>Establishing a new team is not hard, but a certain procedure ought to be
@@ -514,10 +561,10 @@
a long-term engagement that requires a lot of spare time, communication
and technical skills, and devotion. The only “bonus” team leaders
have is more work and more responsibilities.
-
- <p>You should read and <em>all</em> the documentation related to the
-translation process at the very least all important philosophy-related
-articles listed on
+</p>
+<p>You should read <em>all</em> the documentation related to the
+translation process and at the very least all important
+philosophy-related articles listed on
<a
href="http://gnu.org/server/standards/README.translations.html";>http://gnu.org/server/standards/README.translations.html</a>
and
<a
href="http://gnu.org/server/standards/translations/priorities.html";>http://gnu.org/server/standards/translations/priorities.html</a>
@@ -525,169 +572,167 @@
Once you have the internal feeling that having a gnu.org translation
team for your language is a must, and you are the one for this job,
follow these steps:
-
- <ol type=1 start=1>
-<li>If you do not have a Savannah account, register at
+</p>
+<ol>
+<li> If you do not have a Savannah account, register at
<a
href="https://savannah.gnu.org/account/register.php";>https://savannah.gnu.org/account/register.php</a>.
Write access
to the repository and project membership is handled via Savannah, so you
would need an account in any case.
- <li>Checkout a complete working copy of the CVS Web repository as
described
+</li><li> Checkout a complete working copy of the CVS Web repository as
described
at <a
href="https://savannah.gnu.org/cvs/?group=www";>https://savannah.gnu.org/cvs/?group=www</a>.
If you still
-don't have a Savannah account or if you have registered one, but are not
+don’t have a Savannah account or if you have registered one, but are not
yet member of any Savannah project, refer to the instructions under
“Anonymous CVS Access”. If you are already a member of (any)
Savannah
project, you can proceed with “Project Member CVS Access via SSH”,
although you will still lack permission to commit (later, when it is
granted, you can use the same working copy).
- <p>Examine the layout and structure of the repository. Basically, it is
+<p>Examine the layout and structure of the repository. Basically, it is
mapped to the URL locations, more or less. Take a look at the most
-important materials to translate under <samp><span
class="file">/philosophy</span></samp>, <samp><span
class="file">/gnu</span></samp>,
-<samp><span class="file">/distros</span></samp>, <samp><span
class="file">/copyleft</span></samp> and <samp><span
class="file">/licenses</span></samp> directories just
-to get a rough estimate about the amount of work involved. If you are
+important materials to translate under <samp>/philosophy</samp>,
<samp>/gnu</samp>,
+<samp>/distros</samp>, <samp>/copyleft</samp> and <samp>/licenses</samp>
directories just
+to get a rough estimate about the amount of work involved<a name="DOCF2"
href="#FOOT2"><sup>2</sup></a>. If you are
still not scared and determined to go on further, excellent.
-
- <p>As you have probably observed, every directory that contains
-translatable articles has a <samp><span class="file">/po</span></samp>
sub-directory, which is where the
+</p>
+<p>As you have probably observed, every directory that contains
+translatable articles has a <samp>/po</samp> sub-directory, which is where the
canonical source format of the translations is stored.
-
- <li>Submit your first message stating that you would like to establish a
new
+</p>
+</li><li> Submit your first message stating that you would like to establish a
new
team to <a href="mailto:address@hidden";>address@hidden</a>; please mention
that you have
read all the documentation and list the issues that remain unclear for
you. The Translation Managers will answer your questions and send you
the standard questionnaire for new team leaders. It is short and
-shouldn't take more than 10–30 minutes to complete. This questionnaire
+shouldn’t take more than 10–30 minutes to complete. This
questionnaire
is important, as we consider it crucial for any translation team
co-ordinator to have a good understanding of the philosophy of the free
software movement.
- <li>Check if your language code is
+</li><li> Check if your language code is
present in the variable <code>TEMPLATE_LINGUAS</code> at
-<samp><span class="file">server/gnun/gnun.mk</span></samp>. If it is not, the
first thing to do is to
+<samp>server/gnun/gnun.mk</samp>. If it is not, the first thing to do is to
translate and submit to <a href="mailto:address@hidden";>address@hidden</a> the
following
-files (all in the <samp><span class="file">server/po/</span></samp> directory):
-<samp><span class="file">head-include-2.</span><var>lang</var><span
class="file">.po</span></samp>,
-<samp><span class="file">body-include-1.</span><var>lang</var><span
class="file">.po</span></samp>,
-<samp><span class="file">body-include-2.</span><var>lang</var><span
class="file">.po</span></samp>
-<samp><span class="file">footer-text.</span><var>lang</var><span
class="file">.po</span></samp>,
-<samp><span class="file">outdated.</span><var>lang</var><span
class="file">.po</span></samp>,
-<samp><span class="file">skip-translations.</span><var>lang</var><span
class="file">.po</span></samp>,
-and <samp><span class="file">top-addendum.</span><var>lang</var><span
class="file">.po</span></samp>.
-See <a href="gnun.html#New-Translation">New Translation</a>.
-
- <ul>
-<li>The language code (<var>lang</var>) should be the ISO 639-1 code of the
-language, for example ‘<samp><span class="samp">hy</span></samp>’
for Armenian or ‘<samp><span class="samp">el</span></samp>’ for
Greek. If
-there is no such code, use the ISO 639-2 one—e.g. ‘<samp><span
class="samp">mai</span></samp>’ for
-Maithili. If the language is a variant such as Brazilian Portuguese or
-Simplified Chinese, use small caps and a dash—‘<samp><span
class="samp">pt-br</span></samp>’ and
-‘<samp><span class="samp">zh-cn</span></samp>’ instead of
‘<samp><span class="samp">pt_BR</span></samp>’ and
‘<samp><span class="samp">zh_CN</span></samp>’.
+files (all in the <samp>server/po/</samp> directory):
+<samp>head-include-2.<var>lang</var>.po</samp>,
+<samp>body-include-1.<var>lang</var>.po</samp>,
+<samp>body-include-2.<var>lang</var>.po</samp>
+<samp>footer-text.<var>lang</var>.po</samp>,
+<samp>outdated.<var>lang</var>.po</samp>,
+<samp>skip-translations.<var>lang</var>.po</samp>,
+and <samp>top-addendum.<var>lang</var>.po</samp>.
+See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#New-Translation";>New
Translation</a> in <cite>The GNUnited Nations Manual</cite>.
+
+<ul class="no-bullet">
+<li>- The language code (<var>lang</var>) should be the ISO 639-1 code of the
+language, for example ‘<samp>hy</samp>’ for Armenian or
‘<samp>el</samp>’ for Greek. If
+the language is a variant such as Brazilian Portuguese or
+Simplified Chinese, use small caps and a
dash—‘<samp>pt-br</samp>’ and
+‘<samp>zh-cn</samp>’ instead of ‘<samp>pt_BR</samp>’
and ‘<samp>zh_CN</samp>’.
- <li>The PO file header and initial comments should be completed as
+</li><li>- The PO file header and initial comments should be completed as
documented.
- <li>Do not use HTML entities for non-ASCII characters as in the
English
+</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><span class="samp">&uuml;</span></samp>’ and this is a
character from the alphabet of your
-language, just write it as ‘<samp><span
class="samp">ü</span></samp>’ directly.
-</ul>
+‘<samp>&uuml;</samp>’ and this is a character from the
alphabet of your
+language, just write it as ‘<samp>ü</samp>’ directly.
+</li></ul>
- <li>Any prospective team leader should submit a few translations first.
+</li><li> Any prospective team leader should submit a few translations first.
This is a process of pointing errors and omissions (which are expected
-and natural); it's an important thing to do as the leader is going to
+and natural); it’s an important thing to do as the leader is going to
carry out these checks on her own, once the team is approved. If there
are existing translations that are not yet in PO format, the best thing
-to do is to migrate one or two. You can use <samp><span
class="command">find</span></samp> to find out
-what's already in the repository, for example:
+to do is to migrate one or two. You can use <code>find</code> to find out
+what’s already in the repository, for example:
- <pre class="example"> find -name \*.<var>lang</var>.html
-</pre>
- <li>Submit at least two translations of your own. We maintain a list with
+<div class="example">
+<pre class="example">find -name \*.<var>lang</var>.html
+</pre></div>
+
+</li><li> Submit at least two translations of your own. We maintain a list
with
priority articles at
<a
href="http://www.gnu.org/server/standards/translations/priorities.html";>http://www.gnu.org/server/standards/translations/priorities.html</a>,
although it is probably hard to start with one of them. Choose whatever
you wish, provided it is an essay and not an auxiliary page. Avoid
-translating the homepage or <samp><span
class="file">whatsnew.html</span></samp>—they are moving
+translating the homepage or <samp>planetfeeds.html</samp>—they are moving
targets and keeping up would be only a distraction for both parties in
the process. As usual, send the completed translation to
<a href="mailto:address@hidden";>address@hidden</a>.
- <li>The Translation Managers will review your translations, and eventually
+</li><li> The Translation Managers will review your translations, and
eventually
comment on them (mostly technical details if there is no one among them
speaking your language). Depending on the case, it might be required to
submit a corrected file. In any event, please take into account the
remarks in future work.
- <li>If all goes well, you will receive a response inviting you to apply
for
+</li><li> If all goes well, you will receive a response inviting you to apply
for
a new translation project at Savannah. The project name should be
-‘<samp><span class="samp">www-</span><var>lang</var></samp>’ where
<var>lang</var> is, unsurprisingly, the language
+‘<samp>www-<var>lang</var></samp>’ where <var>lang</var> is,
unsurprisingly, the language
code. If such a project already exists, this step will be skipped and
-you'll be made an administrator of the project. To register the
+you’ll be made an administrator of the project and its mailing lists.
+To register the
project, go to <a
href="https://savannah.gnu.org/register/";>https://savannah.gnu.org/register/</a>
and make sure
you fill in the required fields. The “Group type” should be
-‘<samp><span class="samp">www.gnu.org translation
team</span></samp>’, and “Project
-license”—‘<samp><span class="samp">WebSite
Only</span></samp>’. In the “Tarball URL” field enter a
-bogus URL such as ‘<samp><span
class="samp">http://gnu.org</span></samp>’.
+‘<samp>www.gnu.org translation team</samp>’, and “Project
+license”—‘<samp>WebSite Only</samp>’. In the
“Tarball URL” field enter a
+bogus URL such as ‘<samp>http://gnu.org</samp>’.
- <p><strong>Pay attention:</strong> This step is a formality. You should
proceed
+<p><strong>Pay attention:</strong> This step is a formality. You should
proceed
with the project registration only when you have been asked by
<a href="mailto:address@hidden";>address@hidden</a> to do so. Otherwise, the
submission
may appear in the task list of the Savannah Hackers for a fairly long
time, which is troublesome.
-
- <li>When the project is approved, the team information will be added to
the
-list at <samp><span class="file">README.translations.html</span></samp>, you
will become a member of the
-‘<samp><span class="samp">www</span></samp>’ project (thus
granting you CVS write access to the whole
-repository—so be careful) and the ‘<samp><span
class="samp">trans-coord</span></samp>’ project. You'll
+</p>
+</li><li> When the project is approved, the team information will be added to
the
+list at <samp>README.translations.html</samp>, you will become a member of the
+‘<samp>www</samp>’ project (thus granting you CVS write access to
the whole
+repository—so be careful) and the ‘<samp>trans-coord</samp>’
project. You’ll
also be subscribed to the following mailing lists:
- <ul>
-<li>www-commits
+<ul class="no-bullet">
+<li>- www-commits
- <li>trans-coord-discuss
-</ul>
+</li><li>- trans-coord-discuss
+
+</li><li>- www-discuss
+</li></ul>
- <p>You'll have to request subscription to ‘<samp><span
class="samp">www-discuss</span></samp>’
-yourself—this list is managed by the GNU Webmasters, but all team
-leaders are required to subscribe in order to receive important
-site-wide announcements.
- </ol>
+</li></ol>
- <p>The whole process should not take more than two weeks or maximum a
+<p>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
web-translators are badly lagging behind and do not process the requests
with the expected pace.
-
- <p>Applications for new teams are sometimes processed in
-parallel<a rel="footnote" href="#fn-2" name="fnd-2"><sup>2</sup></a>—the
+</p>
+<p>Applications for new teams are sometimes processed in
+parallel<a name="DOCF3" href="#FOOT3"><sup>3</sup></a>—the
most suitable candidate is chosen in this case. This is, undoubtedly,
based on a subjective judgment made by the Translation Managers, and
many factors are important.
-
- <p>The procedure for taking over an orphaned team is the same. Once
+</p>
+<p>The procedure for taking over an orphaned team is the same. Once
completed, you will be made an admin of the respective
-‘<samp><span class="samp">www-</span><var>lang</var></samp>’
Savannah project, or if it doesn't exist, invited
+‘<samp>www-<var>lang</var></samp>’ Savannah project, or if it
doesn’t exist, invited
to apply for registration. Do not automatically remove old members just
because you are starting “afresh”—some of them might want to
-continue to contribute. Contact them privately, explaining that you're
+continue to contribute. Contact them privately, explaining that you’re
the new appointed team co-ordinator, and ask them if they would be
willing to continue their involvement in the team.
-
-<div class="node">
+</p>
+<hr>
<a name="Managing"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Reports">Reports</a>,
-Previous: <a rel="previous" accesskey="p" href="#New-Team">New Team</a>,
-Up: <a rel="up" accesskey="u" href="#Leaders">Leaders</a>
-
+<div class="header">
+<p>
+Next: <a href="#Reports" accesskey="n" rel="next">Reports</a>, Previous: <a
href="#New-Team" accesskey="p" rel="previous">New Team</a>, Up: <a
href="#Leaders" accesskey="u" rel="up">Leaders</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<a name="The-Gentle-Art-of-Managing-A-Translation-Team"></a>
<h3 class="section">3.2 The Gentle Art of Managing A Translation Team</h3>
<p>It is not our ambition to describe all activities involved in managing a
-team—it's very likely that you will encounter new problems, take care
+team—it’s very likely that you will encounter new problems, take
care
of tasks nobody else is aware of, or invent new techniques and
approaches in your quest to keep things running. Managing a team is a
hard task on all counts: communication with others, recruiting
@@ -695,31 +740,34 @@
decisions, leading discussions about terminology issues, handling
personal conflicts within the team, technical skills when
reviewing/merging/syncing translations, etc. The list goes on and on.
-
- <p>This manual can only summarize some of the most common issues and
+</p>
+<p>This manual can only summarize some of the most common issues and
<em>suggest</em> ways to deal with them. It is up to the team leader to
establish the precise team procedures and practices.
-
- <p>The <a href="mailto:address@hidden";>address@hidden</a> mailing list was
specifically
+</p>
+<p>The <a href="mailto:address@hidden";>address@hidden</a> mailing list was
specifically
created to discuss issues that leaders encounter while managing the
teams, and for general organizational work. Feel free to discuss
anything related to the translation process there.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#Review"
accesskey="1">Review</a>:</td><td> </td><td align="left"
valign="top">The importance of peer review.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Commits"
accesskey="2">Commits</a>:</td><td> </td><td align="left"
valign="top">What to modify, and how.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Savannah"
accesskey="3">Savannah</a>:</td><td> </td><td align="left"
valign="top">Using Savannah resources.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Co_002dleaders"
accesskey="4">Co-leaders</a>:</td><td> </td><td align="left"
valign="top">Promoting co-leaders, when necessary.
+</td></tr>
+</table>
-<ul class="menu">
-<li><a accesskey="1" href="#Review">Review</a>: The importance
of peer review.
-<li><a accesskey="2" href="#Commits">Commits</a>: What to modify,
and how.
-<li><a accesskey="3" href="#Savannah">Savannah</a>: Using Savannah
resources.
-<li><a accesskey="4" href="#Co_002dleaders">Co-leaders</a>:
Promoting co-leaders, when necessary.
-</ul>
-
-<div class="node">
+<hr>
<a name="Review"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Commits">Commits</a>,
-Up: <a rel="up" accesskey="u" href="#Managing">Managing</a>
-
+<div class="header">
+<p>
+Next: <a href="#Commits" accesskey="n" rel="next">Commits</a>, Up: <a
href="#Managing" accesskey="u" rel="up">Managing</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<a name="Peer-Review"></a>
<h4 class="subsection">3.2.1 Peer Review</h4>
<p>First and foremost, find at least one person for peer review. You will
@@ -729,43 +777,44 @@
larger group) is crucial for the quality of the translation process.
Too many errors are just missed (especially if they are obvious) when
the translator does a final review of her own translation.
-
- <p>It is good to establish a practice: Do not commit officially (i.e. in
-‘<samp><span class="samp">www</span></samp>’, which will appear
online at <a href="http://gnu.org";>http://gnu.org</a>
+</p>
+<p>It is good to establish a practice: Do not commit officially (i.e. in
+‘<samp>www</samp>’, which will appear online at <a
href="http://gnu.org";>http://gnu.org</a>
immediately) a translation that is not yet reviewed by someone else who
is not the translator. Always perform a final review yourself even if
the translation has been checked by another member of the team. In
other words, every translation installed at gnu.org should pass through
your hands (read: eyes).
-
- <p>One common technique for performing such reviews is to use a mailing
+</p>
+<p>One common technique for performing such reviews is to use a mailing
list—the translator sends the new translation and participants comment
on specific parts, quoting them appropriately. The benefit of this
approach is that it is straightforward, but the drawback is that there
is no automatic “record” about the conclusion of the specific
discussion (or sub-thread) and sometimes such discussions easily
digress, making it even harder to come up with a solution.
-
- <p>Another way is to use Savannah's built-in trackers (the
‘<samp><span class="samp">Tasks</span></samp>’ and
-‘<samp><span class="samp">Bugs</span></samp>’ trackers,
specifically). This is further explained in the
+</p>
+<p>Another way is to use Savannah’s built-in trackers (the
‘<samp>Tasks</samp>’ and
+‘<samp>Bugs</samp>’ trackers, specifically). This is further
explained in the
next section, see <a href="#Tracking-Tasks">Tracking Tasks</a>. One way or
another, you should
create some kind of review process.
-
-<ul class="menu">
-<li><a accesskey="1" href="#Tracking-Tasks">Tracking Tasks</a>:
Using Savannah to track tasks and bugs.
-<li><a accesskey="2" href="#Unreviewed-Translations">Unreviewed
Translations</a>: What to do with translations that are
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#Tracking-Tasks"
accesskey="1">Tracking Tasks</a>:</td><td> </td><td align="left"
valign="top">Using Savannah to track tasks and bugs.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Unreviewed-Translations"
accesskey="2">Unreviewed Translations</a>:</td><td> </td><td
align="left" valign="top">What to do with translations that are
not reviewed.
-</ul>
+</td></tr>
+</table>
-<div class="node">
+<hr>
<a name="Tracking-Tasks"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#Unreviewed-Translations">Unreviewed Translations</a>,
-Up: <a rel="up" accesskey="u" href="#Review">Review</a>
-
+<div class="header">
+<p>
+Next: <a href="#Unreviewed-Translations" accesskey="n" rel="next">Unreviewed
Translations</a>, Up: <a href="#Review" accesskey="u" rel="up">Review</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-
-<h5 class="subsubsection">3.2.1.1 How To Track Tasks and Bugs Using
Savannah</h5>
+<a name="How-To-Track-Tasks-and-Bugs-Using-Savannah"></a>
+<h4 class="subsubsection">3.2.1.1 How To Track Tasks and Bugs Using
Savannah</h4>
<p>The team leader has to make sure that prospective translations are
reviewed, that they do not contain obvious errors and/or confusing
@@ -778,13 +827,13 @@
such tasks. Team co-ordinators often do not manage to make such reviews
in time, resulting in frustration among the team members and generally
slowing the translation process.
-
- <p>A solution to this specific problem is to distribute the load among more
-people. For example: Member D makes a translation of <samp><span
class="file">foo.html</span></samp>
-and uploads <samp><span class="file">foo.</span><var>lang</var><span
class="file">.po</span></samp> in the translation project's
+</p>
+<p>A solution to this specific problem is to distribute the load among more
+people. For example: Member D makes a translation of <samp>foo.html</samp>
+and uploads <samp>foo.<var>lang</var>.po</samp> in the translation
project’s
repository at Savannah, marking the relevant task as “Ready for
Test”
(of course, the equivalent is sending a message with the attached
-translation to the team's mailing list, or similar). Then Member A, B
+translation to the team’s mailing list, or similar). Then Member A, B
and C (or only A and B if C is currently busy) review it independently
and post comments/suggestions/errors in the bug tracker. Discussion
goes on between them and D, problems are rectified and finally the
@@ -796,186 +845,187 @@
shoulders of the leader. You can also set up an internal formal rule:
If a member makes a translation, he has to review another one (or two)
as well.
-
- <p>Some translations can take a fairly long time—the typical example
is a
+</p>
+<p>Some translations can take a fairly long time—the typical example is a
complicated essay or a transcript of a speech. It is best to avoid
duplicate work by indicating, or better—recording, that someone is
-working on this specific article. The ‘<samp><span
class="samp">Tasks</span></samp>’ tracker is suitable
+working on this specific article. The ‘<samp>Tasks</samp>’
tracker is suitable
for this purpose.
-
- <p>It is prudent to discuss the most convenient naming scheme and practice
+</p>
+<p>It is prudent to discuss the most convenient naming scheme and practice
among team members, and publish the convention and/or rules at the
-team's homepage. Note that you can create <dfn>Custom Fields</dfn> in the
+team’s homepage. Note that you can create <em>Custom Fields</em> in the
trackers, and resolved bugs can be searched based on these custom
values.
+</p>
+<p>Thus, a possible straightforward way to manage these tasks is:
+</p>
+<ul>
+<li> If someone starts working on a new translation, she creates a new task
+with a ‘<samp>Subject</samp>’ indicating the article, for example
simply
+‘<samp>philosophy/bsd.html</samp>’ and assigns it to herself.
- <p>Thus, a possible straightforward way to manage these tasks is:
-
- <ul>
-<li>If someone starts working on a new translation, she creates a new task
-with a ‘<samp><span class="samp">Subject</span></samp>’ indicating
the article, for example simply
-‘<samp><span class="samp">philosophy/bsd.html</span></samp>’ and
assigns it to herself.
-
- <li>When the translation is finished and ready for review, the translator
-changes the ‘<samp><span class="samp">Status</span></samp>’ to
“Ready For Test”.
+</li><li> When the translation is finished and ready for review, the translator
+changes the ‘<samp>Status</samp>’ to “Ready For Test”.
- <li>Other members review it, and open bugs relevant to one specific
problem.
+</li><li> Other members review it, and open bugs relevant to one specific
problem.
It is usually better not to conflate two different issues together—it
makes them harder to discuss, and hard to track them by severity. Some
are grammatical errors, some are fundamental ones that change the whole
meaning, some are simply suggestions for improvement. It helps if the
project admin creates new Category fields for every article, for
-instance ‘<samp><span
class="samp">gnu/gnu-history.</span><var>lang</var><span
class="samp">.html</span></samp>’,
-‘<samp><span
class="samp">philosophy/microsoft.</span><var>lang</var><span
class="samp">.html</span></samp>’—it would enable
+instance ‘<samp>gnu/gnu-history.<var>lang</var>.html</samp>’,
+‘<samp>philosophy/microsoft.<var>lang</var>.html</samp>’—it
would enable
functionality like “Show me all bugs ever reported against this
translation”, which is useful.
- <li>Once the bugs (or at least the important bugs) are fixed, the team
+</li><li> Once the bugs (or at least the important bugs) are fixed, the team
leader can make the final review and install the translation in the
-official repository, marking the task as ‘<samp><span
class="samp">Done</span></samp>’. Bugs that are not
-resolved should remain opened, naturally.
-</ul>
+official repository, marking the task as ‘<samp>Done</samp>’.
Bugs that are not
+resolved should remain open, naturally.
+</li></ul>
- <p>Of course, teams can choose to manage these things using external
+<p>Of course, teams can choose to manage these things using external
resources and eventually other bug (or issue) tracking systems.
Whatever you decide, please make sure that bugs can be reported using
free software only, and that the software providing that service is
free. It makes an extremely bad impression if a reader has to report a
-problem about a gnu.org translation via non-free hosting platforms like
+problem about a gnu.org translation via nonfree hosting platforms like
SourceForge.
-
- <p>If you use a certain facility (i.e. a bug tracking system) to manage
+</p>
+<p>If you use a certain facility (i.e. a bug tracking system) to manage
bugs in translations, it is best to take advantage of
-<samp><span class="file">generic.</span><var>lang</var><span
class="file">.html</span></samp> and advertise it on every page.
-See <a href="gnun.html#generic_002eLANG_002ehtml">generic.LANG.html</a>, for
+<samp>generic.<var>lang</var>.html</samp> and advertise it on every page.
+See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#generic_002eLANG_002ehtml";>generic.LANG.html</a>
in <cite>The GNUnited Nations Manual</cite>, for
details.
-
-<div class="node">
+</p>
+<hr>
<a name="Unreviewed-Translations"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Tracking-Tasks">Tracking
Tasks</a>,
-Up: <a rel="up" accesskey="u" href="#Review">Review</a>
-
+<div class="header">
+<p>
+Previous: <a href="#Tracking-Tasks" accesskey="p" rel="previous">Tracking
Tasks</a>, Up: <a href="#Review" accesskey="u" rel="up">Review</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
-<h5 class="subsubsection">3.2.1.2 How To Proceed With Unreviewed
Translations</h5>
+<a name="How-To-Proceed-With-Unreviewed-Translations"></a>
+<h4 class="subsubsection">3.2.1.2 How To Proceed With Unreviewed
Translations</h4>
<p>Sometimes a translation (typically your own) is not reviewed by anyone
else for a fairly long time. This is unfortunate, but there is no
reason to keep it in draft state forever. If nobody reviewed it for a
substantially long period (like 3 or 4 months), commit it as it is.
Readers may report bugs as well (and they do!).
-
- <p>It is important to record somehow that this published translation still
+</p>
+<p>It is important to record somehow that this published translation still
lacks appropriate review. If the suggestion in the previous section is
-implemented, it would mean leaving the relevant task ‘<samp><span
class="samp">Open</span></samp>’ and
-‘<samp><span class="samp">Ready For Test</span></samp>’ despite
the translation being officially online.
+implemented, it would mean leaving the relevant task
‘<samp>Open</samp>’ and
+‘<samp>Ready For Test</samp>’ despite the translation being
officially online.
You may also add a comment to the PO file.
-
-<div class="node">
+</p>
+<hr>
<a name="Commits"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Savannah">Savannah</a>,
-Previous: <a rel="previous" accesskey="p" href="#Review">Review</a>,
-Up: <a rel="up" accesskey="u" href="#Managing">Managing</a>
-
+<div class="header">
+<p>
+Next: <a href="#Savannah" accesskey="n" rel="next">Savannah</a>, Previous: <a
href="#Review" accesskey="p" rel="previous">Review</a>, Up: <a href="#Managing"
accesskey="u" rel="up">Managing</a> [<a href="#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<a name="CVS-Commits-And-Best-Practices"></a>
<h4 class="subsection">3.2.2 CVS Commits And Best Practices</h4>
<p>As all team leaders have write access to the CVS repository of the
-‘<samp><span class="samp">www</span></samp>’ project, this
technically means that they are able to modify
-every single file in it, and also those of the Web CVS repositories of
-other projects at Savannah. This vote of confidence should never be
+‘<samp>www</samp>’ project, this technically means that they are
able to modify
+every single file in it. This vote of confidence should never be
abused—the only files team co-ordinators should add/update are those
relevant to their translation work. It is OK to fix an obvious typo in
an original article; for anything else please report to
<a href="mailto:address@hidden";>address@hidden</a>.
-
- <p>If you wish to volunteer as webmaster and help with generic webmaster
+</p>
+<p>If you wish to volunteer as webmaster and help with generic webmaster
work and RT tickets, that is perfectly fine—please follow the
established (by the GNU Webmasters) procedure. If you are approved, you
-can modify such pages wearing your “webmaster's hat”.
-
- <p>If a particular page has issues with the markup which create problems
+can modify such pages wearing your “webmaster’s hat”.
+</p>
+<p>If a particular page has issues with the markup which create problems
for your language, please inform <a
href="mailto:address@hidden";>address@hidden</a>.
For general issues that affect more articles, or for severe problems,
please write to <a href="mailto:address@hidden";>address@hidden</a>.
-
- <p>It is recommended to read the entire CVS manual at least once, for a
-basic understanding of how this VCS works. See <a
href="cvs.html#Top">Concurrent Versions System</a>. It is not
-necessary to become an expert—the ‘<samp><span
class="samp">www</span></samp>’ project does not use
+</p>
+<p>It is recommended to read the entire CVS manual at least once, for a
+basic understanding of how this VCS works. See <a
href="cvs.html#Top">Concurrent
+Versions System</a> in <cite>Version Management with CVS</cite>. It is not
+necessary to become an expert—the ‘<samp>www</samp>’ project
does not use
complex features like tags, vendor branches, merging, etc. as they are
not very useful for a live website.
-
- <p>However, you'd probably have to learn how to use CVS for effective
+</p>
+<p>However, you’d probably have to learn how to use CVS for effective
work—to extract information from the history, review diffs and
specific changes, synchronize with the working repository of the team
(if any), adding/removing files, etc.
-
- <p>If you make changes that affect more than one file but the change is
+</p>
+<p>If you make changes that affect more than one file but the change is
coherent, please do it as a single commit. This will generate only one
message to <a href="mailto:address@hidden";>address@hidden</a>, which is better
than 5 messages
for 5 files about semantically the same change. Always write commit
-logs in English<a rel="footnote" href="#fn-3" name="fnd-3"><sup>3</sup></a>,
providing a short
+logs in English<a name="DOCF4" href="#FOOT4"><sup>4</sup></a>, providing a
short
description of the change. If you modify a file that is not an article
-but a script or part of software (such as <samp><span
class="file">server/gnun/gnun.mk</span></samp>),
+but a script or part of software (such as <samp>server/gnun/gnun.mk</samp>),
it would be nice to follow the GNU Coding Standards and describe the
-change precisely. For example, do not write:
+change precisely. See <a
href="http://www.gnu.org/prep/standards/standards.html#Change-Logs";>Change
Logs</a> in <cite>The GNU Coding Standards</cite>. For example, do not write:
+</p>
+<div class="example">
+<pre class="example">Added support for Nepali.
+</pre></div>
+
+<p>or
+</p>
+<div class="example">
+<pre class="example">Yay! First commit of the Panjabi homepage!
+</pre></div>
+
+<p>Instead, write the log as follows:
+</p>
+<div class="example">
+<pre class="example">(TEMPLATE_LINGUAS): Add `ne'.
+</pre></div>
+
+<p>and
+</p>
+<div class="example">
+<pre class="example">(FUZZY_DIFF_LINGUAS): Add `pa'.
+</pre></div>
-<pre class="example"> Added support for Nepali.
-</pre>
- <p>or
-
-<pre class="example"> Yay! First commit of the Panjabi homepage!
-</pre>
- <p>Instead, write the log as follows:
-
-<pre class="example"> (TEMPLATE_LINGUAS): Add `ne'.
-</pre>
- <p>and
-
-<pre class="example"> (HOME_LINGUAS): Add `pa'.
-</pre>
- <p>This makes it easier for others to search for a particular change in the
+<p>This makes it easier for others to search for a particular change in the
history.
-
- <p>If you add a binary file (for example, <samp><span
class="file">.png</span></samp>), do it with
-<code>cvs commit -kb </code><var>file</var>. This turns off keyword
substitution,
-which prevents RCS keywords like ‘<samp><span class="samp">$<!-- /@w
-->Id$</span></samp>’ to get expanded,
-subsequently corrupting the file. See <a
href="cvs.html#Substitution-Modes">Substitution Modes</a>. More importantly,
using <samp><span class="option">-kb</span></samp>
+</p>
+<p>If you add a binary file (for example, <samp>.png</samp>), do it with
+<code>cvs commit -kb <var>file</var></code>. This turns off keyword
substitution,
+which prevents RCS keywords like ‘<samp>$<!-- /@w -->Id$</samp>’
to get expanded,
+subsequently corrupting the file. See <a
href="cvs.html#Substitution-Modes">Substitution Modes</a> in <cite>Version
Management with CVS</cite>. More importantly, using <samp>-kb</samp>
prevents corruption of the binary when people using CVS clients under
-Windoze checkout, modify the file, and then commit it with messed EOLs.
-(Unfortunately there are still committers using non-free operating
-systems—we cannot dictate what OS people use, but we can at least try
-to prevent damage.)
-
- <p>Although not absolutely compulsory, it is recommended that every team
+infamous OS checkout, modify the file, and then commit it with
+messed ends of lines.<a name="DOCF5" href="#FOOT5"><sup>5</sup></a>
+</p>
+<p>Although not absolutely compulsory, it is recommended that every team
leader subscribes to <a href="mailto:address@hidden";>address@hidden</a>. It
is useful to
examine the diffs of your own messages, if you miss something while
inspecting the diff before the commit. In any case, a team leader
should be subscribed to that list to avoid his own commit messages to be
moderated. If you absolutely do not desire receiving all traffic, just
-disable mail delivery in Mailman's user interface.
-
-<div class="node">
+disable mail delivery in Mailman’s user interface.
+</p>
+<hr>
<a name="Savannah"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Co_002dleaders">Co-leaders</a>,
-Previous: <a rel="previous" accesskey="p" href="#Commits">Commits</a>,
-Up: <a rel="up" accesskey="u" href="#Managing">Managing</a>
-
+<div class="header">
+<p>
+Next: <a href="#Co_002dleaders" accesskey="n" rel="next">Co-leaders</a>,
Previous: <a href="#Commits" accesskey="p" rel="previous">Commits</a>, Up: <a
href="#Managing" accesskey="u" rel="up">Managing</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<a name="Taking-Advantage-of-Savannah"></a>
<h4 class="subsection">3.2.3 Taking Advantage of Savannah</h4>
<p>Every translation team should have a project in Savannah. There are
some teams that use their own resources outside from Savannah; although
-there's no obligation to use Savannah for team work, the need for a
-Savannah project for each language is obvious: it's a standard way to
+there’s no obligation to use Savannah for team work, the need for a
+Savannah project for each language is obvious: it’s a standard way to
find information for translation teams and their contacts.
-
- <p>Using external hosting facilities may seem justified sometimes. Some
+</p>
+<p>Using external hosting facilities may seem justified sometimes. Some
teams may have already established repositories and/or bug tracking
systems where usual contributors already have access. Some team
members prefer to work within the established infrastructure of a
@@ -984,542 +1034,551 @@
(see <a href="#Savannah-Mailing-Lists">Savannah Mailing Lists</a>), because it
is easier to pass its
management to the new co-ordinator when the old one steps down, and it
helps to keep the archives at one place for future members of the
-team. Likewise, it is better to use Savannah for the team's
+team. Likewise, it is better to use Savannah for the team’s
repository and bugs/tasks, but this is not mandatory.
-
- <p>However, it is important to remember that regardless of the technical
+</p>
+<p>However, it is important to remember that regardless of the technical
resources which a team decides to use, the responsibility of the team
co-ordinator remains the same.
-
- <p>Those teams that are using Savannah have a broad variety of tools at
+</p>
+<p>Those teams that are using Savannah have a broad variety of tools at
hand: team membership management, documents, trackers (bugs, tasks and
support), alerts, CVS (and any other VCS that Savannah supports), home
pages, etc. How each team uses these resources is up to the team
itself, but it often turns out to choose Savannah for nearly all of
the team activities, as it requires almost zero work; the Savannah
Hackers are happy to support us.
-
- <p>Whatever you (in your capacity as a team leader) decide, please do it
+</p>
+<p>Whatever you (in your capacity as a team leader) decide, please do it
with caution: some organizational decisions may become ineffective as
time goes by, and some may not scale well when the team grows. If the
team is young and has a couple of members, it is better to refrain from
such decision and discuss them with all the members when their number
grows. Two or three people do not need a rocket platform or complex
wizardry to do their work.
-
- <p>The next sections contain suggestions about how a team can use the
+</p>
+<p>The next sections contain suggestions about how a team can use the
facilities provided by Savannah. It is not mandatory to follow them,
they are just suggestions.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#Savannah-Members"
accesskey="1">Savannah Members</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Savannah-Homepage"
accesskey="2">Savannah Homepage</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Savannah-Support"
accesskey="3">Savannah Support</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Savannah-Tasks"
accesskey="4">Savannah Tasks</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Savannah-Bugs"
accesskey="5">Savannah Bugs</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Savannah-Patch"
accesskey="6">Savannah Patch</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Savannah-News"
accesskey="7">Savannah News</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Savannah-Mailing-Lists"
accesskey="8">Savannah Mailing Lists</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Savannah-VCS"
accesskey="9">Savannah VCS</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+</table>
-<ul class="menu">
-<li><a accesskey="1" href="#Savannah-Members">Savannah Members</a>
-<li><a accesskey="2" href="#Savannah-Homepage">Savannah Homepage</a>
-<li><a accesskey="3" href="#Savannah-Support">Savannah Support</a>
-<li><a accesskey="4" href="#Savannah-Tasks">Savannah Tasks</a>
-<li><a accesskey="5" href="#Savannah-Bugs">Savannah Bugs</a>
-<li><a accesskey="6" href="#Savannah-Patch">Savannah Patch</a>
-<li><a accesskey="7" href="#Savannah-News">Savannah News</a>
-<li><a accesskey="8" href="#Savannah-Mailing-Lists">Savannah Mailing Lists</a>
-<li><a accesskey="9" href="#Savannah-VCS">Savannah VCS</a>
-</ul>
-
-<div class="node">
+<hr>
<a name="Savannah-Members"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Savannah-Homepage">Savannah
Homepage</a>,
-Up: <a rel="up" accesskey="u" href="#Savannah">Savannah</a>
-
+<div class="header">
+<p>
+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>
-
-<h5 class="subsubsection">3.2.3.1 Managing Members</h5>
+<a name="Managing-Members"></a>
+<h4 class="subsubsection">3.2.3.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
-of the project's resources, and tracking their number is one of the ways
+of the project’s resources, and tracking their number is one of the ways
for web-translators to determine the status of the team.
-
- <p>It is OK if a particular contributor wants to translate an article or
+</p>
+<p>It is OK if a particular contributor wants to translate an article or
two and does not want to be engaged with the team on a long-term basis.
In such situations, there is no need to add her as a member.
-
- <p>It is a good idea to mark inactive members, for example if there is no
+</p>
+<p>It is a good idea to mark inactive members, for example if there is no
interaction (bug reports, new translations, updates to existing
translations, proof-reading) for at least six months. You can do that
-by unmarking the ‘<samp><span class="samp">On Duty</span></samp>’
checkbox for the respective project
-member under ‘<samp><span class="samp">Set
Permissions</span></samp>’. Inactive members have absolutely
-the same rights as active ones—the only exception is that they don't
+by unmarking the ‘<samp>On Duty</samp>’ checkbox for the
respective project
+member under ‘<samp>Set Permissions</samp>’. Inactive members
have absolutely
+the same rights as active ones—the only exception is that they
don’t
count for the total number of members, and they appear separately on
-‘<samp><span class="samp">View Members</span></samp>’.
-
-<div class="node">
+‘<samp>View Members</samp>’.
+</p>
+<hr>
<a name="Savannah-Homepage"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Savannah-Support">Savannah
Support</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Savannah-Members">Savannah Members</a>,
-Up: <a rel="up" accesskey="u" href="#Savannah">Savannah</a>
-
+<div class="header">
+<p>
+Next: <a href="#Savannah-Support" accesskey="n" rel="next">Savannah
Support</a>, Previous: <a href="#Savannah-Members" accesskey="p"
rel="previous">Savannah Members</a>, Up: <a href="#Savannah" accesskey="u"
rel="up">Savannah</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-
-<h5 class="subsubsection">3.2.3.2 Homepage of The Team</h5>
+<a name="Homepage-of-The-Team"></a>
+<h4 class="subsubsection">3.2.3.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
-<<code>http://www.gnu.org/server/standards/translations/</code><var>lang</var>>;
+‘<code>http://www.gnu.org/server/standards/translations/<var>lang</var></code>’;
to add files to it first make a checkout, following the instructions at
-<<code>https://savannah.gnu.org/cvs/?group=www-</code><var>lang</var>>.
-
- <p>It is recommended to describe all team-specific procedures, if there are
+‘<code>https://savannah.gnu.org/cvs/?group=www-<var>lang</var></code>’.
+</p>
+<p>It is recommended to describe all team-specific procedures, if there are
any. That way, you can point potential team members to the
corresponding page containing these instructions, instead of repeatedly
explaining every volunteer separately.
-
- <p>All team-specific pages should follow the usual linking criteria (see
+</p>
+<p>All team-specific pages should follow the usual linking criteria (see
<a
href="http://gnu.org/server/standards/README.webmastering.html#pollinking";>http://gnu.org/server/standards/README.webmastering.html#pollinking</a>
and the FSF HTML Style Sheet
Guidelines—<a
href="http://gnu.org/server/fsf-html-style-sheet.html";>http://gnu.org/server/fsf-html-style-sheet.html</a>).
-
- <p>For historical reasons, team-specific materials were available in the
-‘<samp><span class="samp">www</span></samp>’ repository, under
ad-hoc locations as <samp><span class="file">/spanish</span></samp>,
-<samp><span class="file">/wwwsr</span></samp>, etc. These locations are
deprecated, and the contents
-will be moved without warning to <samp><span
class="file">/graveyard</span></samp> in the
-‘<samp><span class="samp">trans-coord</span></samp>’
<em>Sources</em> repository, following the original
-‘<samp><span class="samp">www</span></samp>’ layout (that is, if
there were any sub-directories, they will
-be retained).
-
-<div class="node">
+</p>
+<p>For historical reasons, team-specific materials were available in the
+‘<samp>www</samp>’ repository, under ad-hoc locations as
<samp>/spanish</samp>,
+<samp>/wwwsr</samp>, etc. These locations are deprecated, and the contents
+will be removed without warning.
+</p>
+<hr>
<a name="Savannah-Support"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Savannah-Tasks">Savannah
Tasks</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Savannah-Homepage">Savannah Homepage</a>,
-Up: <a rel="up" accesskey="u" href="#Savannah">Savannah</a>
-
+<div class="header">
+<p>
+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>
-
-<h5 class="subsubsection">3.2.3.3 Support Tracker</h5>
+<a name="Support-Tracker"></a>
+<h4 class="subsubsection">3.2.3.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
-functionality and/or features that requires the project admin(s)'s
+functionality and/or features that requires the project admin’s
action. Do not use it for anything else as it quickly becomes
confusing. It is OK to disable it if the team is small.
-
-<div class="node">
+</p>
+<hr>
<a name="Savannah-Tasks"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Savannah-Bugs">Savannah Bugs</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Savannah-Support">Savannah Support</a>,
-Up: <a rel="up" accesskey="u" href="#Savannah">Savannah</a>
-
+<div class="header">
+<p>
+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>
-
-<h5 class="subsubsection">3.2.3.4 Tasks Tracker</h5>
+<a name="Tasks-Tracker"></a>
+<h4 class="subsubsection">3.2.3.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
is possible to use this tracker to “announce” to the team members
that
a specific article should be translated. The one who volunteers may
assign the task to herself.
-
- <p>Teams may use this tracker to avoid duplicate work, by declaring that
+</p>
+<p>Teams may use this tracker to avoid duplicate work, by declaring that
they intend to work on a specific translation.
-
- <p>Feel free to organize the ‘<samp><span
class="samp">Tasks</span></samp>’ management as you see fit.
-
-<div class="node">
+</p>
+<p>Feel free to organize the ‘<samp>Tasks</samp>’ management as
you see fit.
+</p>
+<hr>
<a name="Savannah-Bugs"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Savannah-Patch">Savannah
Patch</a>,
-Previous: <a rel="previous" accesskey="p" href="#Savannah-Tasks">Savannah
Tasks</a>,
-Up: <a rel="up" accesskey="u" href="#Savannah">Savannah</a>
-
+<div class="header">
+<p>
+Next: <a href="#Savannah-Patch" accesskey="n" rel="next">Savannah Patch</a>,
Previous: <a href="#Savannah-Tasks" accesskey="p" rel="previous">Savannah
Tasks</a>, Up: <a href="#Savannah" accesskey="u" rel="up">Savannah</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
+<a name="Bugs-Tracker"></a>
+<h4 class="subsubsection">3.2.3.5 Bugs Tracker</h4>
-<h5 class="subsubsection">3.2.3.5 Bugs Tracker</h5>
-
-<p>The ‘<samp><span class="samp">Bugs</span></samp>’ tracker is
designed for tracking bugs. You can use for
+<p>The ‘<samp>Bugs</samp>’ tracker is designed for tracking bugs.
You can use for
several purposes:
+</p>
+<ul>
+<li> Suggest readers to report bugs there.
- <ul>
-<li>Suggest readers to report bugs there.
-
- <li>Use it for all kinds of internal team tasks.
+</li><li> Use it for all kinds of internal team tasks.
- <li>Forward bugs reported against <var>lang</var> translations in the
-‘<samp><span class="samp">trans-coord</span></samp>’ project and
assign them to the specific maintainer
-(who is supposed to be a ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’ project member), if you
+</li><li> Forward bugs reported against <var>lang</var> translations in the
+‘<samp>trans-coord</samp>’ project and assign them to the specific
maintainer
+(who is supposed to be a ‘<samp>www-<var>lang</var></samp>’
project member), if you
have such policy.
-</ul>
+</li></ul>
-<div class="node">
+<hr>
<a name="Savannah-Patch"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Savannah-News">Savannah News</a>,
-Previous: <a rel="previous" accesskey="p" href="#Savannah-Bugs">Savannah
Bugs</a>,
-Up: <a rel="up" accesskey="u" href="#Savannah">Savannah</a>
-
+<div class="header">
+<p>
+Next: <a href="#Savannah-News" accesskey="n" rel="next">Savannah News</a>,
Previous: <a href="#Savannah-Bugs" accesskey="p" rel="previous">Savannah
Bugs</a>, Up: <a href="#Savannah" accesskey="u" rel="up">Savannah</a>
[<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
+<a name="Patch-Tracker"></a>
+<h4 class="subsubsection">3.2.3.6 Patch Tracker</h4>
-<h5 class="subsubsection">3.2.3.6 Patch Tracker</h5>
-
-<p>This tracker doesn't make much sense for translation projects, as the
+<p>This tracker doesn’t make much sense for translation projects, as the
original on which the translation is based is volatile and the
-translation <dfn>patch</dfn> is 100% guaranteed not to apply cleanly very
+translation <em>patch</em> is 100% guaranteed not to apply cleanly very
soon after it is submitted. Even ignoring this detail, this specific
feature is slowly marching towards complete deprecation, as there are
much better ways to submit patches nowadays.
-
- <p>You should disable this feature, as it causes only confusion.
-
-<div class="node">
+</p>
+<p>You should disable this feature, as it causes only confusion.
+</p>
+<hr>
<a name="Savannah-News"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Savannah-Mailing-Lists">Savannah
Mailing Lists</a>,
-Previous: <a rel="previous" accesskey="p" href="#Savannah-Patch">Savannah
Patch</a>,
-Up: <a rel="up" accesskey="u" href="#Savannah">Savannah</a>
-
+<div class="header">
+<p>
+Next: <a href="#Savannah-Mailing-Lists" accesskey="n" rel="next">Savannah
Mailing Lists</a>, Previous: <a href="#Savannah-Patch" accesskey="p"
rel="previous">Savannah Patch</a>, Up: <a href="#Savannah" accesskey="u"
rel="up">Savannah</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-
-<h5 class="subsubsection">3.2.3.7 News Tracker</h5>
+<a name="News-Tracker"></a>
+<h4 class="subsubsection">3.2.3.7 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><span
class="samp">News</span></samp>’ RSS
+project page from time to time, or subscribe to the
‘<samp>News</samp>’ RSS
feed) about a major change or event within the project.
-
- <p>You can also setup news entries to be sent to a mailing list (that's
+</p>
+<p>You can also setup news entries to be sent to a mailing list (that’s
possible for the other trackers as well).
-
- <p>The purpose of this feature is informational—if members need to
know
+</p>
+<p>The purpose of this feature is informational—if members need to know
about an important change (in practices, procedures, etc.), it is
perfectly OK to announce it here. Some teams use it to announce new
translations, which is also fine.
-
-<div class="node">
+</p>
+<hr>
<a name="Savannah-Mailing-Lists"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Savannah-VCS">Savannah VCS</a>,
-Previous: <a rel="previous" accesskey="p" href="#Savannah-News">Savannah
News</a>,
-Up: <a rel="up" accesskey="u" href="#Savannah">Savannah</a>
-
+<div class="header">
+<p>
+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>
-
-<h5 class="subsubsection">3.2.3.8 Managing Mailing Lists</h5>
+<a name="Managing-Mailing-Lists"></a>
+<h4 class="subsubsection">3.2.3.8 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><span
class="samp">www-</span><var>lang</var><span
class="samp">-</span></samp>’.
-
- <p>The list will make it possible for the GNU project to contact the team
+name of the list should begin with
‘<samp>www-<var>lang</var>-</samp>’.
+</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
the history for new translators.
-
- <p>You can create new mailing lists via the Savannah interface. However,
+</p>
+<p>You can create new mailing lists via the Savannah interface. However,
this should be done after some thought. If the project membership is
low (<= 10 members), there is no need to create more than one mailing
list.
-
- <p>You can redirect all messages generated by the trackers to any list.
-
-<div class="node">
+</p>
+<p>You can redirect all messages generated by the trackers to any list.
+</p>
+<hr>
<a name="Savannah-VCS"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p"
href="#Savannah-Mailing-Lists">Savannah Mailing Lists</a>,
-Up: <a rel="up" accesskey="u" href="#Savannah">Savannah</a>
-
+<div class="header">
+<p>
+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>
-
-<h5 class="subsubsection">3.2.3.9 Version Control Systems</h5>
+<a name="Version-Control-Systems"></a>
+<h4 class="subsubsection">3.2.3.9 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
-translation project's Sources repository. That way, it is easy to edit
-draft translations and install them in ‘<samp><span
class="samp">www</span></samp>’ only when they're
+translation project’s Sources repository. That way, it is easy to edit
+draft translations and install them in ‘<samp>www</samp>’ only
when they’re
ready. It is also convenient to update the translation (merge any
changes from the original) while it is still under review.
-
- <p>See <a href="gnun.html#PO-Files-and-Team">PO Files and Team</a>, for
+</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
more information.
-
- <p><strong>Remember:</strong> A choice of a particular VCS is a sensitive
+</p>
+<p><strong>Remember:</strong> A choice of a particular VCS is a sensitive
matter—some modern ones provide compelling features, but they also
bump the barrier for participation higher. The VCS is supposed to ease
collaborative maintenance—if it eases only you, project members just
-won't use it so that won't be a net win.
-
-<h5 class="subsubheading">Web-based Systems</h5>
+won’t use it so that won’t be a net win.
+</p>
+<a name="Web_002dbased-Systems"></a>
+<h4 class="subsubheading">Web-based Systems</h4>
<p>An alternative way to maintain translations is to use one of the
existing online editors. There are plans to install a web-based system
-for managing <samp><span class="file">.po</span></samp> files at Savannah,
including online editing and
+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>
- <p>Here is a short and probably incomplete list of such systems:
-
- <ul>
-<li>Pootle—<a
href="http://translate.sourceforge.net/wiki/pootle";>http://translate.sourceforge.net/wiki/pootle</a>
-
- <li>Vertaal—<a
href="http://code.google.com/p/vertaal";>http://code.google.com/p/vertaal</a>
+</li><li> Vertaal—<a
href="http://code.google.com/p/vertaal";>http://code.google.com/p/vertaal</a>
- <li>Narro—<a
href="http://code.google.com/p/narro";>http://code.google.com/p/narro</a>
+</li><li> Narro—<a
href="http://code.google.com/p/narro";>http://code.google.com/p/narro</a>
- <li>Launchpad—<a
href="https://dev.launchpad.net";>https://dev.launchpad.net</a>
+</li><li> Launchpad—<a
href="https://dev.launchpad.net";>https://dev.launchpad.net</a>
- </ul>
+</li></ul>
- <p>If you decide to use such a system, please make sure that no
+<p>If you decide to use such a system, please make sure that no
translations are published in HTML format there.
-
- <p>Note that to keep the <samp><span class="file">.pot</span></samp> files
regularly updated (assuming such
-a web-based system runs <samp><span class="command">msgmerge</span></samp>
automatically), you'll have
-to take care of the one-way regular sync from the ‘<samp><span
class="samp">www</span></samp>’ CVS
+</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.
-
-<div class="node">
-<a name="Co-leaders"></a>
+</p>
+<hr>
<a name="Co_002dleaders"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Savannah">Savannah</a>,
-Up: <a rel="up" accesskey="u" href="#Managing">Managing</a>
-
+<div class="header">
+<p>
+Previous: <a href="#Savannah" accesskey="p" rel="previous">Savannah</a>, Up:
<a href="#Managing" accesskey="u" rel="up">Managing</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<a name="Promoting-Members-As-Co_002dleaders"></a>
<h4 class="subsection">3.2.4 Promoting Members As Co-leaders</h4>
<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
to help. Note that a subsequently appointed team co-ordinator is not
-simply a <dfn>committer</dfn> with write access to the ‘<samp><span
class="samp">www</span></samp>’ repository;
+simply a <em>committer</em> with write access to the
‘<samp>www</samp>’ repository;
she has full responsibilities just like a single leader, although the
latter still remains the primary contact for the team.
-
- <p>If you'd like another person to act as a co-leader and help you with the
+</p>
+<p>If you’d like another person to act as a co-leader and help you with
the
management tasks, send a message to <a
href="mailto:address@hidden";>address@hidden</a>
with her name and Savannah account. She has to be already a member of
-‘<samp><span class="samp">www-</span><var>lang</var></samp>’.
-
- <p>The procedure for co-leaders is a simplified version of the one for a
+‘<samp>www-<var>lang</var></samp>’.
+</p>
+<p>The procedure for co-leaders is a simplified version of the one for a
new team or taking over an existing team. See <a href="#New-Team">New
Team</a>.
-
- <p>To remove co-ordinators, please write to
+</p>
+<p>To remove co-ordinators, please write to
<a href="mailto:address@hidden";>address@hidden</a> with details and rationale
for the
-removal. Do not edit <samp><span
class="file">README.translations.html</span></samp> yourself; this is
+removal. Do not edit <samp>README.translations.html</samp> yourself; this is
a final formality step to be performed by the Translation Managers.
-
-<div class="node">
+</p>
+<hr>
<a name="Reports"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Stepping-Down">Stepping Down</a>,
-Previous: <a rel="previous" accesskey="p" href="#Managing">Managing</a>,
-Up: <a rel="up" accesskey="u" href="#Leaders">Leaders</a>
-
+<div class="header">
+<p>
+Next: <a href="#Stepping-Down" accesskey="n" rel="next">Stepping Down</a>,
Previous: <a href="#Managing" accesskey="p" rel="previous">Managing</a>, Up: <a
href="#Leaders" accesskey="u" rel="up">Leaders</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<a name="Reporting-Team-Status"></a>
<h3 class="section">3.3 Reporting Team Status</h3>
<p>Team leaders must send an annual report about the status of the team. A
good report should include:
-
- <ul>
-<li>General information about the team's accomplishments during the past
+</p>
+<ul>
+<li> General information about the team’s accomplishments during the past
year, like:
- <ul>
-<li>A list of new translations.
+<ul class="no-bullet">
+<li>- A list of new translations.
- <li>New members since the last report.
+</li><li>- New members since the last report.
- <li>Current active members.
+</li><li>- Current active members.
- <li>Solved problems and other issues, if any. (Usual bug reports
and other
+</li><li>- Solved problems and other issues, if any. (Usual bug reports and
other
improvements/fixes to the existing translations do not count as
-<dfn>problems</dfn> in this sense.)
-</ul>
+<em>problems</em> in this sense.)
+</li></ul>
- <li>Current problems (technical or social), conflicts, and ideas for
sorting
+</li><li> Current problems (technical or social), conflicts, and ideas for
sorting
them out.
- <li>Anything else you consider important or worth mentioning.
-</ul>
+</li><li> Anything else you consider important or worth mentioning.
+</li></ul>
- <p>The best time to send a report is near the end of the year, for example
+<p>The best time to send a report is near the end of the year, for example
November. In any case, please do not send it later than December 15th,
as the Translation Manager has to prepare a general report to the FSF,
and it is better if it takes into account the reports of the team
leaders.
-
- <p>If there is no sensitive information in the report and you feel like
+</p>
+<p>If there is no sensitive information in the report and you feel like
sharing it, you can send it to <a
href="mailto:address@hidden";>address@hidden</a>
(which is still a private mailing list). That way, other list readers
may help with suggestions how to solve a particular issue. Informing
each other about the progress improves the community spirit.
-
- <p>If you do not wish to share some information that is in the report,
+</p>
+<p>If you do not wish to share some information that is in the report,
please send it to <a href="mailto:address@hidden";>address@hidden</a>.
-
-<div class="node">
+</p>
+<hr>
<a name="Stepping-Down"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Reports">Reports</a>,
-Up: <a rel="up" accesskey="u" href="#Leaders">Leaders</a>
-
+<div class="header">
+<p>
+Previous: <a href="#Reports" accesskey="p" rel="previous">Reports</a>, Up: <a
href="#Leaders" accesskey="u" rel="up">Leaders</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<a name="How-To-Retire-Painlessly"></a>
<h3 class="section">3.4 How To Retire Painlessly</h3>
-<p>When you feel you don't have the energy to manage the team successfully,
+<p>When you feel you don’t have the energy to manage the team
successfully,
or perhaps you start losing motivation, please inform
<a href="mailto:address@hidden";>address@hidden</a>. It would be substantially
easier if
you try to find a replacement or recommend a specific person—we will
try to find someone in any case, but your judgment is important and it
will be considered with priority.
-
- <p>An excellent way to step down is to do it with a
“plan”—suggest the
+</p>
+<p>An excellent way to step down is to do it with a
“plan”—suggest the
person you consider capable of doing the job as co-leader
(see <a href="#Co_002dleaders">Co-leaders</a>) and retire completely when she
is absolutely ready
to proceed without your further help and advice.
-
-<div class="node">
+</p>
+<hr>
<a name="Translation-Managers"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Translation-Tips">Translation
Tips</a>,
-Previous: <a rel="previous" accesskey="p" href="#Leaders">Leaders</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</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>
-
-<h2 class="chapter">4 ‘<samp><span
class="samp">trans-coord</span></samp>’ Admins</h2>
+<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.
-
-<div class="node">
+</p>
+<hr>
<a name="Translation-Tips"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Summary">Summary</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Translation-Managers">Translation Managers</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</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>
</div>
-
+<a name="Details-About-The-Translation-Process"></a>
<h2 class="chapter">5 Details About The Translation Process</h2>
<p>The purpose of this chapter is to summarize some odd and not so obvious
details about specific parts of the gnu.org website. Most of them
become well known as time goes by; however, practice shows that it is
difficult to figure them out at once.
-
- <p>Some limitations and oddities are just historical remnants from old
+</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>
+<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.
+</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.
+</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.
+</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.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Capitalization"
accesskey="5">Capitalization</a>:</td><td> </td><td align="left"
valign="top">To CAPITALIZE or not?
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Distribution-Terms"
accesskey="6">Distribution Terms</a>:</td><td> </td><td align="left"
valign="top">Translating distribution terms.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Terminology"
accesskey="7">Terminology</a>:</td><td> </td><td align="left"
valign="top">Dealing with terminology issues.
+</td></tr>
+</table>
-<ul class="menu">
-<li><a accesskey="1" href="#Migrating">Migrating</a>: How to
migrate to the new style.
-<li><a accesskey="2" href="#SSI">SSI</a>: Overview of SSI
#include directives.
-<li><a accesskey="3" href="#CSS">CSS</a>: General advice how
to use CSS.
-<li><a accesskey="4" href="#Priorities">Priorities</a>: What to
translate as a priority.
-<li><a accesskey="5" href="#Capitalization">Capitalization</a>: To
CAPITALIZE or not?
-<li><a accesskey="6" href="#Distribution-Terms">Distribution Terms</a>:
Translating distribution terms.
-<li><a accesskey="7" href="#Terminology">Terminology</a>: Dealing
with terminology issues.
-</ul>
-
-<div class="node">
+<hr>
<a name="Migrating"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#SSI">SSI</a>,
-Up: <a rel="up" accesskey="u" href="#Translation-Tips">Translation
Tips</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>
</div>
-
+<a name="Migration-To-The-New-Style"></a>
<h3 class="section">5.1 Migration To The New Style</h3>
<p>Migration to the new style should be straightforward, and this is one of
the problems GNUN set out to solve. If you have to migrate old-style
-translations, see <a href="gnun.html#Migrating">Migrating</a>.
+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>Subsequent migrations to newer HTML standards and newer look and feel
+</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.
-
-<div class="node">
+</p>
+<hr>
<a name="SSI"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#CSS">CSS</a>,
-Previous: <a rel="previous" accesskey="p" href="#Migrating">Migrating</a>,
-Up: <a rel="up" accesskey="u" href="#Translation-Tips">Translation
Tips</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
+<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:
-
- <dl>
-<dt><samp><span class="file">server/banner.html</span></samp><dd>This file
contains only <code>#include</code> directives, so the
+the <code>#include</code>’s used:
+</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.
-
- <br><dt><samp><span
class="file">server/body-include-1.html</span></samp><dd>Contains the top menu
with useful “skip to” links.
-
- <br><dt><samp><span
class="file">server/body-include-2.html</span></samp><dd>This is the file
containing the menus, the FSF widget, and any visible
+</p>
+</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><span class="file">server/po/body-include-2.</span><var>lang</var><span
class="file">.po</span></samp> is updated. Note that
+<samp>server/po/body-include-2.<var>lang</var>.po</samp> is updated. Note that
some validation errors originate from an error in
-<samp><span class="file">server/body-include-2.</span><var>lang</var><span
class="file">.html</span></samp> or some other template
+<samp>server/body-include-2.<var>lang</var>.html</samp> or some other template
file.
-
- <br><dt><samp><span
class="file">server/footer-text.html</span></samp><dd>This is a very short file
currently containing the “back to top” link.
+</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.
-
- <br><dt><samp><span class="file">server/header.html</span></samp><dd>The
declaration that is included in literally every file. It is
+</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
+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><span class="file">header.ar.html</span></samp> should contain this line:
-
- <pre class="example"> <html
xmlns="http://www.w3.org/1999/xhtml"; xml:lang="ar" lang="ar"
- dir="rtl">
-</pre>
- <br><dt><samp><span
class="file">server/head-include-1.html</span></samp><dd>This file (included
from <samp><span class="file">server/header.html</span></samp>) is very
important:
+<samp>header.ar.html</samp> should contain this line:
+</p>
+<div class="example">
+<pre class="example"><html xmlns="http://www.w3.org/1999/xhtml"
xml:lang="ar" lang="ar"
+ dir="rtl">
+</pre></div>
+
+</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><span class="file">server/head-include-1.</span><var>lang</var><span
class="file">.html</span></samp>, so browsers will obey it.
-
- <p>The encoding should be UTF-8. This is required because the English
text
+<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.
-
- <br><dt><samp><span
class="file">server/html5-header.html</span></samp><dd>This file is included in
newer pages using some entities introduced
+</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
+of HTML4 were rejected in HTML5, and our old pages don’t validate
as HTML5.
-
- <br><dt><samp><span
class="file">server/html5-head-include-1.html</span></samp><dd>Likewise, this
file replaces head-include-1.html for HTML5 pages.
-
- <br><dt><samp><span
class="file">server/head-include-2.html</span></samp><dd>Imports the standard
CSS, which can be overridden. See <a href="#CSS">CSS</a>.
-
- <br><dt><samp><span class="file">server/footer.html</span></samp><dd>This
is a very short and simple file (at least at the time of writing),
+</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><span class="file">footer-text.</span><var>lang</var><span
class="file">.html</span></samp> to be included.
-
- <br><dt><samp><span
class="file">server/outdated.html</span></samp><dd>This file is automatically
included in outdated translations. It
+<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.
@@ -1527,262 +1586,282 @@
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.
-
- <br><dt><samp><span
class="file">translations.include</span></samp><dd>The list of translations for
the homepage (and only the homepage). It
+</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.
-
- <br><dt><samp><span class="file">gnusflashes.include</span></samp><dd>A
portion of the most recent 3 news items from
-<samp><span class="file">server/whatsnew.html</span></samp>, generated
automatically. If your language
-does not have <samp><span
class="file">server/po/whatsnew.</span><var>lang</var><span
class="file">.po</span></samp>, this file will be
-used. Otherwise, if there is an existing localized homepage and you
-commit <samp><span class="file">whatsnew.</span><var>lang</var><span
class="file">.po</span></samp>, the homepage will be rebuilt to
-include the translated <samp><span
class="file">gnusflashes.</span><var>lang</var><span
class="file">.include</span></samp>.
-
- <br><dt><samp><span
class="file">server/whatsnew.include</span></samp><dd>Generated automatically,
this file is included from
-<samp><span class="file">server/whatsnew.html</span></samp>. Translations are
built automatically, and
-the localized <samp><span class="file">gnusflashes.include</span></samp> is
derived from it.
-
- <br><dt><samp><span
class="file">licenses/gpl-3.0-body.html</span></samp><dt><samp><span
class="file">licenses/fdl-1.3-body.html</span></samp><dt><samp><span
class="file">...</span></samp><dd>Some of the licenses have the text of the
license itself separated in
+</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><span class="file">.pot</span></samp> files, as
licenses have only
+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.
-
- <br><dt><samp><span
class="file">server/sidebar*.html</span></samp><dd>These files are
deprecated—they are remnants from an older design that
+</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
-<samp><span class="command">grep</span></samp> to check this.
+<code>grep</code> to check this.
+</p></dd>
</dl>
- <p>The files
-
-<!-- Use @itemize to avoid `underfull \hbox' warnings from TeX. -->
- <ul>
-<li><samp><span class="file">header.html</span></samp>
-<li><samp><span class="file">head-include-1.html</span></samp>
-<li><samp><span class="file">html5-header.html</span></samp>
-<li><samp><span class="file">html5-head-include-1.html</span></samp>
-<li><samp><span class="file">head-include-2.html</span></samp>
-<li><samp><span class="file">banner.html</span></samp>
-<li><samp><span class="file">body-include-1.html</span></samp>
-<li><samp><span class="file">body-include-2.html</span></samp>
-<li><samp><span class="file">footer.html</span></samp>
-<li><samp><span class="file">footer-text.html</span></samp>
-</ul>
+<p>The files
+</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>footer.html</samp>
+</li><li>- <samp>footer-text.html</samp>
+</li></ul>
- <p>in the <samp><span class="file">server</span></samp> sub-directory are
what webmasters call “the
+<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="gnun.html#Runtime-Variables">Runtime Variables</a>.
-
-<div class="node">
+<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="CSS"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Priorities">Priorities</a>,
-Previous: <a rel="previous" accesskey="p" href="#SSI">SSI</a>,
-Up: <a rel="up" accesskey="u" href="#Translation-Tips">Translation
Tips</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>
</div>
-
+<a name="How-To-Use-Custom-CSS"></a>
<h3 class="section">5.3 How To Use Custom CSS</h3>
-<p>The CSS file <samp><span class="file">layout.css</span></samp> gets
included (with three other CSS files)
+<p>The CSS file <samp>layout.css</samp> gets included (with three other CSS
files)
in almost all the English articles through
-<samp><span class="file">server/head-include-2.</span><var>lang</var><span
class="file">.html</span></samp>. However, sometimes this
-style isn't quite right for translations—many languages have much
+<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><span class="file">style.</span><var>lang</var><span
class="file">.css</span></samp> and add it <em>after</em> the
-directive to include <samp><span
class="file">server/head-include-2.</span><var>lang</var><span
class="file">.html</span></samp> and
+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><span class="file">server/banner.</span><var>lang</var><span
class="file">.html</span></samp>, i.e.
+<samp>server/banner.<var>lang</var>.html</samp>, i.e.
+</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></div>
-<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>
- <p>Override only what is necessary and looks broken in your language; do
+<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><span class="file">style.</span><var>lang</var><span
class="file">.css</span></samp> file looks like this:
-
-<pre class="example"> .inner { max-width: 65em; }
+<samp>style.<var>lang</var>.css</samp> file looks like this:
+</p>
+<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>
- #logo{background:url(/graphics/topbanner.bg.png) no-repeat;}
- #fssbox {font-size: 50%;}
-</pre>
- <p>This widens the menu and the area where the articles are displayed
+<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>When creating your own <samp><span
class="file">style.</span><var>lang</var><span class="file">.css</span></samp>,
don't forget to
-include the license notice from the <samp><span
class="file">layout.css</span></samp>, with a short
+</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>If using the default CSS style for translations does not give the
+</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="#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>
-<ul class="menu">
-<li><a accesskey="1" href="#topbanner">topbanner</a>: How to
localize the topbanner image.
-<li><a accesskey="2" href="#RTL">RTL</a>: Special notes about
RTL languages.
-</ul>
-
-<div class="node">
+<hr>
<a name="topbanner"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#RTL">RTL</a>,
-Up: <a rel="up" accesskey="u" href="#CSS">CSS</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>
</div>
+<a name="Localizing-The-topbanner-Image"></a>
+<h4 class="subsection">5.3.1 Localizing The <samp>topbanner</samp> Image</h4>
-<h4 class="subsection">5.3.1 Localizing The <samp><span
class="file">topbanner</span></samp> Image</h4>
-
-<p>If you'd like the nice gnu image to be localized (i.e. “GNU Operating
+<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:
-
- <ol type=1 start=1>
-<li>Copy <samp><span class="file">graphics/topbanner.svg</span></samp> as
-<samp><span class="file">graphics/topbanner.</span><var>lang</var><span
class="file">.svg</span></samp> where <var>lang</var> is the
+</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><span class="file">graphics/topbanner.</span><var>lang</var><span
class="file">.png</span></samp> (File -> Export Bitmap<small
class="dots">...</small>).
+<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
rel="footnote" href="#fn-4" name="fnd-4"><sup>4</sup></a>.
+Image). Don’t forget to save and <code>cvs add</code> the files<a
name="DOCF6" href="#FOOT6"><sup>6</sup></a>.
- <li>Create a <samp><span class="file">style.</span><var>lang</var><span
class="file">.css</span></samp> at the toplevel directory, if it
-doesn't exist already. Normally, you would need only one line in it,
+</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:
- <pre class="example">
#logo{background:url(/graphics/topbanner.<var>lang</var>.png) no-repeat;}
-</pre>
- <li>If not done already for other reasons, update
-<samp><span class="file">banner.</span><var>lang</var><span
class="file">.html</span></samp> to include the language specific
-<samp><span class="file">style.</span><var>lang</var><span
class="file">.css</span></samp>. See <a href="#CSS">CSS</a>.
- </ol>
+<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
+<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>.
-
-<div class="node">
+</p>
+<hr>
<a name="RTL"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#topbanner">topbanner</a>,
-Up: <a rel="up" accesskey="u" href="#CSS">CSS</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>
</div>
-
+<a name="Specific-Issues-Related-to-RTL"></a>
<h4 class="subsection">5.3.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
made. If your language is in this category, make sure to:
+</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>.
- <ul>
-<li>Set the attribute <code>dir="rtl"</code> in the <code>html</code> element
at
-<samp><span class="file">server/header.</span><var>lang</var><span
class="file">.html</span></samp>.
-
- <li>You <em>must</em> have a custom CSS to override some of the
pre-defined
-values. See <samp><span class="file">style.ar.css</span></samp> and
<samp><span class="file">style.fa.css</span></samp> to understand
+</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>.
-</ul>
+</li></ul>
- <p><strong>Important:</strong> Some articles contain their own
<code><style></code>
+<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
+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.
-
-<div class="node">
+</p>
+<hr>
<a name="Priorities"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#Capitalization">Capitalization</a>,
-Previous: <a rel="previous" accesskey="p" href="#CSS">CSS</a>,
-Up: <a rel="up" accesskey="u" href="#Translation-Tips">Translation
Tips</a>
-
+<div class="header">
+<p>
+Next: <a href="#Capitalization" accesskey="n" rel="next">Capitalization</a>,
Previous: <a href="#CSS" accesskey="p" rel="previous">CSS</a>, Up: <a
href="#Translation-Tips" accesskey="u" rel="up">Translation Tips</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<a name="What-To-Translate"></a>
<h3 class="section">5.4 What To Translate</h3>
<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><span class="file">philosophy</span></samp>, <samp><span
class="file">gnu</span></samp>,
-<samp><span class="file">education</span></samp>, <samp><span
class="file">distros</span></samp>,
-<samp><span class="file">copyleft</span></samp> and <samp><span
class="file">licenses</span></samp> are important. The others may be
+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'
+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>It is very important to keep existing translations up-to-date with the
+</p>
+<p>It is very important to keep existing translations up-to-date with the
respective English originals. This task should be higher priority than
-translating new articles. GNUN's <code>report</code> rule can help you to
-identify precisely which articles need updating; see <a
href="gnun.html#report">report</a>. There is a monthly cronjob which
+translating new articles. GNUN’s <code>report</code> rule can help you
to
+identify precisely which articles need updating; see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html#report";>report</a>
in <cite>The GNUnited Nations Manual</cite>. There is a monthly cronjob which
sends a verbose output to each team—by default, the address(es) used
is the Savannah account(s) of the admin(s) of the specific translation
project. If you want them changed, please write to
<a href="mailto:address@hidden";>address@hidden</a>.
-
- <p>It is strongly recommended translation teams to attempt to recruit
+</p>
+<p>GNUN also maintains reports about current status of translations of all
+active teams in <a
href="http://www.gnu.org/software/gnun/reports/";>http://www.gnu.org/software/gnun/reports/</a>.
If
+the page for your team is missing there, please ask
+<a href="mailto:address@hidden";>address@hidden</a> to add it to the cron job.
+</p>
+<p>It is strongly recommended translation teams to attempt to recruit
native English speakers in order to improve their translation process.
Translators sometimes misunderstand English idioms and expressions, and
as a result, they translate them incorrectly or in ways that are
suboptimal and confusing. These errors are trivial to discover for the
native English speaker.
-
- <p><em>Do not</em> translate articles under these directories:
-
- <dl>
-<dt><samp><span class="file">software/</span><var>pkg</var><span
class="file">/</span></samp><dd>These pages are maintained by the respective
<var>pkg</var> maintainers.
+</p>
+<p><em>Do not</em> translate articles under these directories:
+</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.
-
- <br><dt><samp><span class="file">brave-gnu-world</span></samp><dd>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
+</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.
-
- <br><dt><samp><span class="file">home.html</span></samp><dd>There is no
problem to translate this page, but don't make the mistake
+</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.
-
- <br><dt><samp><span
class="file">server/whatsnew.html</span></samp><dd>This is “What's
New”, also known as “GNU's Flashes”, also known as
+</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.
+</p></dd>
</dl>
-<div class="node">
+<hr>
<a name="Capitalization"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Distribution-Terms">Distribution
Terms</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Priorities">Priorities</a>,
-Up: <a rel="up" accesskey="u" href="#Translation-Tips">Translation
Tips</a>
-
+<div class="header">
+<p>
+Next: <a href="#Distribution-Terms" accesskey="n" rel="next">Distribution
Terms</a>, Previous: <a href="#Priorities" accesskey="p"
rel="previous">Priorities</a>, Up: <a href="#Translation-Tips" accesskey="u"
rel="up">Translation Tips</a> [<a href="#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
-
+<a name="When-To-CAPITALIZE"></a>
<h3 class="section">5.5 When To CAPITALIZE</h3>
<p>The English language has some rules for capitalization of titles,
@@ -1791,106 +1870,105 @@
consistently. They do not make sense for many other languages, but
unfortunately, many translators <em>erroneously duplicate</em> the
capitalization in their translation.
-
- <p>Examples for common (and correct) English capitalization is the title of
+</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´c
+rules it is wrong to write “Dlaczego Oprogramowanie Powinno Być
Wolne” (Polish) or “Fondation Pour Le Logiciel Libre”
(French).
-
- <p>Another prominent and widely spread mistake is to write your own
+</p>
+<p>Another prominent and widely spread mistake is to write your own
language with a capital letter in the <code>translations-list</code> when
languages are written beginning with a small letter according to your
-own rules. In other words, it is right to write ‘<samp><span
class="samp">English</span></samp>’ or
-‘<samp><span class="samp">Deutsch</span></samp>’ (because in
English and German languages are
-capitalized), but not ‘<samp><span
class="samp">Français</span></samp>’ or ‘<samp><span
class="samp">Português</span></samp>’—write
-them as ‘<samp><span class="samp">français</span></samp>’
or ‘<samp><span class="samp">português</span></samp>’,
respectively.
-
-<div class="node">
+own rules. In other words, it is right to write
‘<samp>English</samp>’ or
+‘<samp>Deutsch</samp>’ (because in English and German languages are
+capitalized), but not ‘<samp>Français</samp>’ or
‘<samp>Português</samp>’—write
+them as ‘<samp>français</samp>’ or
‘<samp>português</samp>’, respectively.
+</p>
+<hr>
<a name="Distribution-Terms"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Terminology">Terminology</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Capitalization">Capitalization</a>,
-Up: <a rel="up" accesskey="u" href="#Translation-Tips">Translation
Tips</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>
</div>
-
+<a name="Distribution-Terms-1"></a>
<h3 class="section">5.6 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.
The exact HTML for English pages to use is:
+</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>
-<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>
- <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
+<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:
-
- <ul>
-<li>Check at the bottom of the English deed page to see the list of
+</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>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> 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>The textarea on that page provides standard HTML. Note that we're not
+</li><li> The textarea on that page provides standard HTML. Note that
we’re not
using the graphic, just the text.
- </ul>
+</li></ul>
- <p>For example, here's the text they provide for Dutch:
+<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>
-<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>
- <p>Note that the link in this text is changed to point directly to the
+<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>Pages in languages that aren't supported by CC should prepare their own
+deed that’s in the same language as the page itself.
+</p>
+<p>Pages in languages that aren’t supported by CC should prepare their
own
translation, use it consistently throughout pages translated to that
language, and link to the English language deed. Also, please
write your own translation when the translation provided by CC is
not satisfactory for some reasons—for instance, as of May, 2012, their
German translation uses “Content”, which is a word to use with
caution
(see <a
href="http://www.gnu.org/philosophy/words-to-avoid.en.html#Content";>http://www.gnu.org/philosophy/words-to-avoid.en.html#Content</a>).
-
- <p>Note that translations should <em>not</em> change the jurisdiction of the
+</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.
-
-<div class="node">
+</p>
+<hr>
<a name="Terminology"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p"
href="#Distribution-Terms">Distribution Terms</a>,
-Up: <a rel="up" accesskey="u" href="#Translation-Tips">Translation
Tips</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>
</div>
-
+<a name="Language_002dspecific-Terminology"></a>
<h3 class="section">5.7 Language-specific Terminology</h3>
<p>This is a very important topic, not yet covered by this manual.
-
-<div class="node">
+</p>
+<hr>
<a name="Summary"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Copying-This-Manual">Copying
This Manual</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Translation-Tips">Translation Tips</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</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>
<p>In general, it is expected that all participants in the translation
@@ -1898,173 +1976,180 @@
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>This manual is a work in progress—it is not set in stone, and it
+</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
+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="#Mailing-Lists"
accesskey="1">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="#Savannah-Projects"
accesskey="2">Savannah Projects</a>:</td><td> </td><td align="left"
valign="top">Projects’ membership.
+</td></tr>
+</table>
-<ul class="menu">
-<li><a accesskey="1" href="#Mailing-Lists">Mailing Lists</a>: Summary of
mailing lists.
-<li><a accesskey="2" href="#Savannah-Projects">Savannah Projects</a>:
Projects' membership.
-</ul>
-
-<div class="node">
+<hr>
<a name="Mailing-Lists"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Savannah-Projects">Savannah
Projects</a>,
-Up: <a rel="up" accesskey="u" href="#Summary">Summary</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>
</div>
-
+<a name="Related-Mailing-Lists"></a>
<h3 class="section">6.1 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
participants in the process.
-
- <dl>
-<dt><a href="mailto:address@hidden";>address@hidden</a><dd>The basic discussion
list of the GNU Webmasters. All team leaders are
+</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>This is a private mailing list.
-
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>Commits to
the ‘<samp><span class="samp">www</span></samp>’ repository are
sent here. All Translation
+</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>This is a public mailing list, so everyone can subscribe and review the
-archives. The ‘<samp><span class="samp">www</span></samp>’ CVS
repository is also public.
-
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>The main
discussion list for the GNU Web Translators. Team leaders must
+</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>This is a private mailing list.
-
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>This is a
list for notifications about gnunews and GNUnited Nations
+</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><span class="samp">gnun</span></samp>’
topic via Mailman's user interface.
-Likewise, if you want to receive only <dfn>What's New</dfn> updates,
-subscribe to the ‘<samp><span class="samp">whatsnew</span></samp>’
topic.
-
- <p>Automatic announcements for new gnu.org translations (provided they're
+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><span class="samp">-ann</span></samp>’
topics for every GNUN-aware language, so it is a
+‘<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><span
class="samp">es-ann</span></samp>’
+Spanish translations, she can just subscribe to the
‘<samp>es-ann</samp>’
mailing list topic.
-
- <p>This is a public mailing list.
-
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>All
development of GNUN happens here. Commits to the ‘<samp><span
class="samp">trans-coord</span></samp>’
+</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>This is a public list, and <a
href="mailto:address@hidden";>address@hidden</a> is an alias.
-
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>All build
logs from the various GNUN automatic builds are sent to this
-list, so it is not a very pleasant thing to be subscribed, especially if
-you are not interested in GNUN's internals. However, everyone can use
-the web archives to check the log why a particular article was not built
-at expected.
-
- <p>This is a public list.
+</p>
+<p>This is a public list, and <a
href="mailto:address@hidden";>address@hidden</a> is an alias.
+</p></dd>
</dl>
-<div class="node">
+<hr>
<a name="Savannah-Projects"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Mailing-Lists">Mailing
Lists</a>,
-Up: <a rel="up" accesskey="u" href="#Summary">Summary</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>
</div>
-
+<a name="Savannah-Projects-Membership"></a>
<h3 class="section">6.2 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:
-
- <dl>
-<dt>‘<samp><span class="samp">www</span></samp>’<dd>The main
project which hosts the ‘<samp><span
class="samp">gnu.org</span></samp>’ Web repository.
+</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 leader's applications). All
+Translation Manager (in order to approve leader’s applications). All
team leaders (and co-leaders) should be members of this project.
-
- <p>Note that this project has no direct relationship with translators,
-although anything happening in ‘<samp><span
class="samp">www</span></samp>’ directly affects them. The
-‘<samp><span class="samp">www</span></samp>’ project is managed
separately and has a different (entirely
+</p>
+<p>Note that this project has no direct relationship with translators,
+although anything happening in ‘<samp>www</samp>’ directly affects
them. The
+‘<samp>www</samp>’ project is managed separately and has a
different (entirely
unrelated) process for approving contributors.
-
- <br><dt>‘<samp><span
class="samp">trans-coord</span></samp>’<dd>An organizational project
especially created for coordination and
+</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><span
class="samp">trans-coord</span></samp>’ ‘<samp><span
class="samp">Bugs</span></samp>’ tracker.
-
- <p>The admins of this project are the GNU Web Translation Managers.
-
- <br><dt>‘<samp><span
class="samp">www-</span><var>lang</var></samp>’<dd>All translation team
leaders of the language <var>lang</var> should be
-members of the project ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’. The admins of the
project
+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>www-<var>lang</var></samp>’</dt>
+<dd><p>All translation team leaders of the language <var>lang</var> should be
+members of the project ‘<samp>www-<var>lang</var></samp>’. The
admins of the project
are the team leader and the co-leaders, if any.
+</p></dd>
</dl>
-<div class="node">
+<hr>
<a name="Copying-This-Manual"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Summary">Summary</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</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>
+</div>
+<a name="GNU-Free-Documentation-License"></a>
+<h2 class="appendix">Appendix A GNU Free Documentation License</h2>
+<div align="center">Version 1.3, 3 November 2008
</div>
-<h2 class="appendix">Appendix A GNU Free Documentation License</h2>
+<div class="display">
+<pre class="display">Copyright © 2000, 2001, 2002, 2007, 2008 Free
Software Foundation, Inc.
+<a href="http://fsf.org/";>http://fsf.org/</a>
-<!-- The GNU Free Documentation License. -->
-<div align="center">Version 1.3, 3 November 2008</div>
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+</pre></div>
-<!-- This file is intended to be included within another document, -->
-<!-- hence no sectioning command or @node. -->
-<pre class="display"> Copyright © 2000, 2001, 2002, 2007, 2008 Free
Software Foundation, Inc.
- <a href="http://fsf.org/";>http://fsf.org/</a>
-
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-</pre>
- <ol type=1 start=0>
-<li>PREAMBLE
+<ol>
+<li> PREAMBLE
- <p>The purpose of this License is to make a manual, textbook, or other
-functional and useful document <dfn>free</dfn> in the sense of freedom: to
+<p>The purpose of this License is to make a manual, textbook, or other
+functional and useful document <em>free</em> in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher a way
to get credit for their work, while not being considered responsible
for modifications made by others.
-
- <p>This License is a kind of “copyleft”, which means that
derivative
+</p>
+<p>This License is a kind of “copyleft”, which means that
derivative
works of the document must themselves be free in the same sense. It
complements the GNU General Public License, which is a copyleft
license designed for free software.
-
- <p>We have designed this License in order to use it for manuals for free
+</p>
+<p>We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free
program should come with manuals providing the same freedoms that the
software does. But this License is not limited to software manuals;
it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
+</p>
+</li><li> APPLICABILITY AND DEFINITIONS
- <li>APPLICABILITY AND DEFINITIONS
-
- <p>This License applies to any manual or other work, in any medium, that
+<p>This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
@@ -2073,14 +2158,14 @@
licensee, and is addressed as “you”. You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.
-
- <p>A “Modified Version” of the Document means any work
containing the
+</p>
+<p>A “Modified Version” of the Document means any work containing
the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
-
- <p>A “Secondary Section” is a named appendix or a
front-matter section
+</p>
+<p>A “Secondary Section” is a named appendix or a front-matter
section
of the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document's overall
+publishers or authors of the Document to the Document’s overall
subject (or to related matters) and contains nothing that could fall
directly within that overall subject. (Thus, if the Document is in
part a textbook of mathematics, a Secondary Section may not explain
@@ -2088,21 +2173,21 @@
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
-
- <p>The “Invariant Sections” are certain Secondary Sections
whose titles
+</p>
+<p>The “Invariant Sections” are certain Secondary Sections whose
titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.
-
- <p>The “Cover Texts” are certain short passages of text that
are listed,
+</p>
+<p>The “Cover Texts” are certain short passages of text that are
listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.
-
- <p>A “Transparent” copy of the Document means a
machine-readable copy,
+</p>
+<p>A “Transparent” copy of the Document means a machine-readable
copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
@@ -2114,9 +2199,9 @@
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
of text. A copy that is not “Transparent” is called
“Opaque”.
-
- <p>Examples of suitable formats for Transparent copies include plain
-<span class="sc">ascii</span> without markup, Texinfo input format, LaTeX input
+</p>
+<p>Examples of suitable formats for Transparent copies include plain
+<small>ASCII</small> without markup, Texinfo input format, LaTeX input
format, <acronym>SGML</acronym> or <acronym>XML</acronym> using a publicly
available
<acronym>DTD</acronym>, and standard-conforming simple <acronym>HTML</acronym>,
PostScript or <acronym>PDF</acronym> designed for human modification. Examples
@@ -2127,35 +2212,35 @@
not generally available, and the machine-generated <acronym>HTML</acronym>,
PostScript or <acronym>PDF</acronym> produced by some word processors for
output purposes only.
-
- <p>The “Title Page” means, for a printed book, the title page
itself,
+</p>
+<p>The “Title Page” means, for a printed book, the title page
itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, “Title Page”
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work’s title,
preceding the beginning of the body of the text.
-
- <p>The “publisher” means any person or entity that
distributes copies
+</p>
+<p>The “publisher” means any person or entity that distributes
copies
of the Document to the public.
-
- <p>A section “Entitled XYZ” means a named subunit of the
Document whose
+</p>
+<p>A section “Entitled XYZ” means a named subunit of the Document
whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
specific section name mentioned below, such as “Acknowledgements”,
“Dedications”, “Endorsements”, or
“History”.) To “Preserve the Title”
of such a section when you modify the Document means that it remains a
section “Entitled XYZ” according to this definition.
-
- <p>The Document may include Warranty Disclaimers next to the notice which
+</p>
+<p>The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document. These Warranty
Disclaimers are considered to be included by reference in this
License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
+</p>
+</li><li> VERBATIM COPYING
- <li>VERBATIM COPYING
-
- <p>You may copy and distribute the Document in any medium, either
+<p>You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies
to the Document are reproduced in all copies, and that you add no other
@@ -2164,15 +2249,15 @@
copying of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough
number of copies you must also follow the conditions in section 3.
-
- <p>You may also lend copies, under the same conditions stated above, and
+</p>
+<p>You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
+</p>
+</li><li> COPYING IN QUANTITY
- <li>COPYING IN QUANTITY
-
- <p>If you publish printed copies (or copies in media that commonly have
+<p>If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
-Document's license notice requires Cover Texts, you must enclose the
+Document’s license notice requires Cover Texts, you must enclose the
copies in covers that carry, clearly and legibly, all these Cover
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
the back cover. Both covers must also clearly and legibly identify
@@ -2182,13 +2267,13 @@
Copying with changes limited to the covers, as long as they preserve
the title of the Document and satisfy these conditions, can be treated
as verbatim copying in other respects.
-
- <p>If the required texts for either cover are too voluminous to fit
+</p>
+<p>If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto adjacent
pages.
-
- <p>If you publish or distribute Opaque copies of the Document numbering
+</p>
+<p>If you publish or distribute Opaque copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy
a computer-network location from which the general network-using
@@ -2200,51 +2285,51 @@
location until at least one year after the last time you distribute an
Opaque copy (directly or through your agents or retailers) of that
edition to the public.
-
- <p>It is requested, but not required, that you contact the authors of the
+</p>
+<p>It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
+</p>
+</li><li> MODIFICATIONS
- <li>MODIFICATIONS
-
- <p>You may copy and distribute a Modified Version of the Document under
+<p>You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
the Modified Version under precisely this License, with the Modified
Version filling the role of the Document, thus licensing distribution
and modification of the Modified Version to whoever possesses a copy
of it. In addition, you must do these things in the Modified Version:
-
- <ol type=A start=1>
-<li>Use in the Title Page (and on the covers, if any) a title distinct
+</p>
+<ol>
+<li> Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions
(which should, if there were any, be listed in the History section
of the Document). You may use the same title as a previous version
if the original publisher of that version gives permission.
- <li>List on the Title Page, as authors, one or more persons or
entities
+</li><li> List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.
- <li>State on the Title page the name of the publisher of the
+</li><li> State on the Title page the name of the publisher of the
Modified Version, as the publisher.
- <li>Preserve all the copyright notices of the Document.
+</li><li> Preserve all the copyright notices of the Document.
- <li>Add an appropriate copyright notice for your modifications
+</li><li> Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
- <li>Include, immediately after the copyright notices, a license
notice
+</li><li> Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.
- <li>Preserve in that license notice the full lists of Invariant
Sections
-and required Cover Texts given in the Document's license notice.
+</li><li> Preserve in that license notice the full lists of Invariant Sections
+and required Cover Texts given in the Document’s license notice.
- <li>Include an unaltered copy of this License.
+</li><li> Include an unaltered copy of this License.
- <li>Preserve the section Entitled “History”, Preserve
its Title, and add
+</li><li> Preserve the section Entitled “History”, Preserve its
Title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page. If
there is no section Entitled “History” in the Document, create one
@@ -2252,7 +2337,7 @@
given on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.
- <li>Preserve the network location, if any, given in the Document for
+</li><li> Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the “History” section.
@@ -2260,38 +2345,38 @@
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
- <li>For any section Entitled “Acknowledgements” or
“Dedications”, Preserve
+</li><li> For any section Entitled “Acknowledgements” or
“Dedications”, Preserve
the Title of the section, and preserve in the section all the
substance and tone of each of the contributor acknowledgements and/or
dedications given therein.
- <li>Preserve all the Invariant Sections of the Document,
+</li><li> Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles. Section numbers
or the equivalent are not considered part of the section titles.
- <li>Delete any section Entitled “Endorsements”. Such a
section
+</li><li> Delete any section Entitled “Endorsements”. Such a
section
may not be included in the Modified Version.
- <li>Do not retitle any existing section to be Entitled
“Endorsements” or
+</li><li> Do not retitle any existing section to be Entitled
“Endorsements” or
to conflict in title with any Invariant Section.
- <li>Preserve any Warranty Disclaimers.
- </ol>
+</li><li> Preserve any Warranty Disclaimers.
+</li></ol>
- <p>If the Modified Version includes new front-matter sections or
+<p>If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no material
copied from the Document, you may at your option designate some or all
of these sections as invariant. To do this, add their titles to the
-list of Invariant Sections in the Modified Version's license notice.
+list of Invariant Sections in the Modified Version’s license notice.
These titles must be distinct from any other section titles.
-
- <p>You may add a section Entitled “Endorsements”, provided it
contains
+</p>
+<p>You may add a section Entitled “Endorsements”, provided it
contains
nothing but endorsements of your Modified Version by various
parties—for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a
standard.
-
- <p>You may add a passage of up to five words as a Front-Cover Text, and a
+</p>
+<p>You may add a passage of up to five words as a Front-Cover Text, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version. Only one passage of
Front-Cover Text and one of Back-Cover Text may be added by (or
@@ -2300,21 +2385,21 @@
by arrangement made by the same entity you are acting on behalf of,
you may not add another; but you may replace the old one, on explicit
permission from the previous publisher that added the old one.
-
- <p>The author(s) and publisher(s) of the Document do not by this License
+</p>
+<p>The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
+</p>
+</li><li> COMBINING DOCUMENTS
- <li>COMBINING DOCUMENTS
-
- <p>You may combine the Document with other documents released under this
+<p>You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its
license notice, and that you preserve all their Warranty Disclaimers.
-
- <p>The combined work need only contain one copy of this License, and
+</p>
+<p>The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by
@@ -2322,48 +2407,48 @@
author or publisher of that section if known, or else a unique number.
Make the same adjustment to the section titles in the list of
Invariant Sections in the license notice of the combined work.
-
- <p>In the combination, you must combine any sections Entitled
“History”
+</p>
+<p>In the combination, you must combine any sections Entitled
“History”
in the various original documents, forming one section Entitled
“History”; likewise combine any sections Entitled
“Acknowledgements”,
and any sections Entitled “Dedications”. You must delete all
sections Entitled “Endorsements.”
+</p>
+</li><li> COLLECTIONS OF DOCUMENTS
- <li>COLLECTIONS OF DOCUMENTS
-
- <p>You may make a collection consisting of the Document and other
documents
+<p>You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
License in the various documents with a single copy that is included in
the collection, provided that you follow the rules of this License for
verbatim copying of each of the documents in all other respects.
-
- <p>You may extract a single document from such a collection, and
distribute
+</p>
+<p>You may extract a single document from such a collection, and distribute
it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
+</p>
+</li><li> AGGREGATION WITH INDEPENDENT WORKS
- <li>AGGREGATION WITH INDEPENDENT WORKS
-
- <p>A compilation of the Document or its derivatives with other separate
+<p>A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, is called an “aggregate” if the copyright
resulting from the compilation is not used to limit the legal rights
-of the compilation's users beyond what the individual works permit.
+of the compilation’s users beyond what the individual works permit.
When the Document is included in an aggregate, this License does not
apply to the other works in the aggregate which are not themselves
derivative works of the Document.
-
- <p>If the Cover Text requirement of section 3 is applicable to these
+</p>
+<p>If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half of
-the entire aggregate, the Document's Cover Texts may be placed on
+the entire aggregate, the Document’s Cover Texts may be placed on
covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.
+</p>
+</li><li> TRANSLATION
- <li>TRANSLATION
-
- <p>Translation is considered a kind of modification, so you may
+<p>Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
@@ -2375,48 +2460,48 @@
of those notices and disclaimers. In case of a disagreement between
the translation and the original version of this License or a notice
or disclaimer, the original version will prevail.
-
- <p>If a section in the Document is Entitled
“Acknowledgements”,
+</p>
+<p>If a section in the Document is Entitled “Acknowledgements”,
“Dedications”, or “History”, the requirement (section
4) to Preserve
its Title (section 1) will typically require changing the actual
title.
+</p>
+</li><li> TERMINATION
- <li>TERMINATION
-
- <p>You may not copy, modify, sublicense, or distribute the Document
+<p>You may not copy, modify, sublicense, or distribute the Document
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense, or distribute it is void, and
will automatically terminate your rights under this License.
-
- <p>However, if you cease all violation of this License, then your license
+</p>
+<p>However, if you cease all violation of this License, then your license
from a particular copyright holder is reinstated (a) provisionally,
unless and until the copyright holder explicitly and finally
terminates your license, and (b) permanently, if the copyright holder
fails to notify you of the violation by some reasonable means prior to
60 days after the cessation.
-
- <p>Moreover, your license from a particular copyright holder is
+</p>
+<p>Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
-
- <p>Termination of your rights under this section does not terminate the
+</p>
+<p>Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, receipt of a copy of some or all of the same material does
not give you any rights to use it.
+</p>
+</li><li> FUTURE REVISIONS OF THIS LICENSE
- <li>FUTURE REVISIONS OF THIS LICENSE
-
- <p>The Free Software Foundation may publish new, revised versions
+<p>The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
<a href="http://www.gnu.org/copyleft/";>http://www.gnu.org/copyleft/</a>.
-
- <p>Each version of the License is given a distinguishing version number.
+</p>
+<p>Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
License “or any later version” applies to it, you have the option
of
following the terms and conditions either of that specified version or
@@ -2425,47 +2510,49 @@
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation. If the Document
specifies that a proxy can decide which future versions of this
-License can be used, that proxy's public statement of acceptance of a
+License can be used, that proxy’s public statement of acceptance of a
version permanently authorizes you to choose that version for the
Document.
+</p>
+</li><li> RELICENSING
- <li>RELICENSING
-
- <p>“Massive Multiauthor Collaboration Site” (or “MMC
Site”) means any
+<p>“Massive Multiauthor Collaboration Site” (or “MMC
Site”) means any
World Wide Web server that publishes copyrightable works and also
provides prominent facilities for anybody to edit those works. A
public wiki that anybody can edit is an example of such a server. A
“Massive Multiauthor Collaboration” (or “MMC”)
contained in the
site means any set of copyrightable works thus published on the MMC
site.
-
- <p>“CC-BY-SA” means the Creative Commons Attribution-Share
Alike 3.0
+</p>
+<p>“CC-BY-SA” means the Creative Commons Attribution-Share Alike
3.0
license published by Creative Commons Corporation, a not-for-profit
corporation with a principal place of business in San Francisco,
California, as well as future copyleft versions of that license
published by that same organization.
-
- <p>“Incorporate” means to publish or republish a Document, in
whole or
+</p>
+<p>“Incorporate” means to publish or republish a Document, in
whole or
in part, as part of another Document.
-
- <p>An MMC is “eligible for relicensing” if it is licensed
under this
+</p>
+<p>An MMC is “eligible for relicensing” if it is licensed under
this
License, and if all works that were first published under this License
somewhere other than this MMC, and subsequently incorporated in whole
or in part into the MMC, (1) had no cover texts or invariant sections,
and (2) were thus incorporated prior to November 1, 2008.
-
- <p>The operator of an MMC Site may republish an MMC contained in the site
+</p>
+<p>The operator of an MMC Site may republish an MMC contained in the site
under CC-BY-SA on the same site at any time before August 1, 2009,
provided the MMC is eligible for relicensing.
+</p>
+</li></ol>
- </ol>
-
+<a name="ADDENDUM_003a-How-to-use-this-License-for-your-documents"></a>
<h3 class="heading">ADDENDUM: How to use this License for your documents</h3>
<p>To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
license notices just after the title page:
-
+</p>
+<div class="smallexample">
<pre class="smallexample"> Copyright (C) <var>year</var> <var>your
name</var>.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
@@ -2473,43 +2560,60 @@
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is included in the section entitled ``GNU
Free Documentation License''.
-</pre>
- <p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
-replace the “with<small class="dots">...</small>Texts.” line with
this:
+</pre></div>
+<p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the “with…Texts.” line with this:
+</p>
+<div class="smallexample">
<pre class="smallexample"> with the Invariant Sections being <var>list
their titles</var>, with
the Front-Cover Texts being <var>list</var>, and with the Back-Cover
Texts
being <var>list</var>.
-</pre>
- <p>If you have Invariant Sections without Cover Texts, or some other
+</pre></div>
+
+<p>If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.
-
- <p>If your document contains nontrivial examples of program code, we
+</p>
+<p>If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License,
to permit their use in free software.
+</p>
+
+
-<!-- Local Variables: -->
-<!-- ispell-local-pdict: "ispell-dict" -->
-<!-- End: -->
- <div class="footnote">
+<div class="footnote">
<hr>
-<a name="texinfo-footnotes-in-document"></a><h4>Footnotes</h4><p
class="footnote"><small>[<a name="fn-1" href="#fnd-1">1</a>]</small>
Well—not really, but the goal is to maintain
-all of them.</p>
+<h4 class="footnotes-heading">Footnotes</h4>
- <p class="footnote"><small>[<a name="fn-2" href="#fnd-2">2</a>]</small> In
general, we try to avoid this and direct all new
+<h3><a name="FOOT1" href="#DOCF1">(1)</a></h3>
+<p>Well—not really, but the goal is to maintain
+all of them.</p>
+<h3><a name="FOOT2" href="#DOCF2">(2)</a></h3>
+<p>As of
+December 2012, there are over 250 files to translate in “important”
+directories; their volume is about 3.5 MB.</p>
+<h3><a name="FOOT3" href="#DOCF3">(3)</a></h3>
+<p>In general, we try to avoid this and direct all new
volunteers to the person who is already carrying out the process—this
-is also a verification if she can cooperate easily with others.</p>
-
- <p class="footnote"><small>[<a name="fn-3" href="#fnd-3">3</a>]</small>
This advice is applicable for the ‘<samp><span
class="samp">www</span></samp>’
+is also a verification if she can co-operate easily with others.</p>
+<h3><a name="FOOT4" href="#DOCF4">(4)</a></h3>
+<p>This advice is applicable for the ‘<samp>www</samp>’
repository only—feel free to write logs in your native language when
-committing in your project's Sources repository.</p>
-
- <p class="footnote"><small>[<a name="fn-4" href="#fnd-4">4</a>]</small> This
+committing in your team’s repositories.</p>
+<h3><a name="FOOT5" href="#DOCF5">(5)</a></h3>
+<p>Few years ago there still were
+committers using nonfree operating systems—we don’t dictate what
+OS people use, but we can at least prevent this technical kind
+of damage.</p>
+<h3><a name="FOOT6" href="#DOCF6">(6)</a></h3>
+<p>This
advice applies to all new files, of course.</p>
+</div>
+<hr>
- <hr></div>
-</body></html>
+</body>
+</html>
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.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
Binary files /tmp/cvsrbvMD1 and /tmp/cvsZQoLl3 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.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
Binary files /tmp/cvsTdTNg2 and /tmp/cvs1jK6Z3 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.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
Binary files /tmp/cvsE4Q0g5 and /tmp/cvshc6z16 differ
Index: web-trans/web-trans.pdf
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.pdf,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
Binary files /tmp/cvsAMAAS5 and /tmp/cvsDmHvG7 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.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
Binary files /tmp/cvs5yLOr8 and /tmp/cvsHCo5ia 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.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
Binary files /tmp/cvszf7n66 and /tmp/cvsUkFzZ8 differ
Index: web-trans/web-trans.txt
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.txt,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- web-trans/web-trans.txt 29 Sep 2012 06:53:48 -0000 1.10
+++ web-trans/web-trans.txt 4 Dec 2012 16:24:26 -0000 1.11
@@ -1,6 +1,3 @@
-Table of Contents
-*****************
-
GNU Web Translators Manual
1 Introduction
2 Team Members
@@ -29,12 +26,12 @@
3.2.4 Promoting Members As Co-leaders
3.3 Reporting Team Status
3.4 How To Retire Painlessly
-4 `trans-coord' Admins
+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.2 Summary of SSI '#include's
5.3 How To Use Custom CSS
- 5.3.1 Localizing The `topbanner' Image
+ 5.3.1 Localizing The 'topbanner' Image
5.3.2 Specific Issues Related to RTL
5.4 What To Translate
5.5 When To CAPITALIZE
@@ -44,8 +41,6 @@
6.1 Related Mailing Lists
6.2 Savannah Projects Membership
Appendix A GNU Free Documentation License
-
-
GNU Web Translators Manual
**************************
@@ -96,17 +91,17 @@
maintain on the long term translations of the various essays that
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, who are
+ 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 Savannah 'trans-coord' organizational project, which is managed by
the GNU Web Translation Managers. The manual is organized in chapters
that follow the organizational structure of the whole translation
project.
If you wish to join a translation team or contribute a translation or
two, *note Members::. If your intention is to form a translation team,
-*note Leaders::. The chapter about the `trans-coord' administrators
+*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::.
@@ -124,15 +119,15 @@
==================
To join a team, please first look at the existing teams at
-`http://www.gnu.org/server/standards/README.translations.html#TranslationsUnderway'.
+<http://www.gnu.org/server/standards/README.translations.html#TranslationsUnderway>.
Chances are that there is already an established team. If there is no
team listed for your language, this means that:
* There is no team established and there are no translations to this
language.
- * Some translations were submitted by occasional contributors, but
- no team has ever been formed.
+ * Some translations were submitted by occasional contributors, but no
+ team has ever been formed.
* The page is not updated to reflect the current situation (this
shouldn't happen, but it's a possibility anyway).
@@ -144,12 +139,11 @@
chapter, *note Leaders::.
Contacting the team is best done via Savannah--each translation team
-has its own project, named `www-LANG', with the project page being
-<https://savannah.gnu.org/projects/www-LANG>. Usually teams have
-mailing lists, typically in the form <address@hidden>. Some
-teams have homepages,
-<http://gnu.org/server/standards/translations/LANG> with additional
-contact details and procedures for team members.
+has its own project, named 'www-LANG', with the project page being
+'https://savannah.gnu.org/projects/www-LANG'. All teams should have
+mailing lists, typically in the form <address@hidden>. Some teams
+have homepages, 'http://gnu.org/server/standards/translations/LANG' with
+additional contact details and procedures for team members.
You could also write directly to the team leader via the Savannah
interface--that way your request will be recorded by Savannah and can be
@@ -179,23 +173,23 @@
team formed. There are two ways to do that--following the existing
procedures, which is the preferred way, and sending it as plain text,
which means more work for a limited group of volunteers (the Translation
-Managers) to convert the translation in `.po' format.
+Managers) to convert the translation in '.po' format.
2.2.1 How To Submit a Translation in PO Format
----------------------------------------------
All translations(1) are maintained via GNUN (see
-`http://www.gnu.org/software/gnun/'), which significantly eases
+<http://www.gnu.org/software/gnun/>), which significantly eases
maintenance and avoids the unpleasant situation where a translation is
-lagging behind the original. *Note Advantages: (gnun)Advantages.
+lagging behind the original. *Note (gnun)Advantages::.
- As of September 2008 all new translations at gnu.org are installed in
-`.po' format, and the `.html' is generated automatically. Here are the
+ Since September 2008 all new translations at gnu.org are installed in
+'.po' format, and the '.html' is generated automatically. Here are the
steps to produce and submit such a translation:
- * Make a checkout of the CVS Web repository of the `www' Savannah
+ * Make a checkout of the CVS Web repository of the 'www' Savannah
project. You can find generic instructions at
- `https://savannah.gnu.org/cvs/?group=www'. All updates to the
+ <https://savannah.gnu.org/cvs/?group=www>. All updates to the
website are done as commits in the repository, so you would need an
up-to-date working copy. Anonymous access works under any
circumstances, i.e. it is not mandatory to have a registered
@@ -204,14 +198,22 @@
cvs -z3 -d:pserver:address@hidden:/web/www co www/gnu
- This command will fetch only the `/gnu' directory--in other words,
- all articles at `http://gnu.org/gnu'.
+ This command will fetch only the '/gnu' directory--in other words,
+ all articles at <http://gnu.org/gnu>.
+
+ You can also fetch single files by their respective URLs. For
+ example, the URL for the template file of
+ <http://www.gnu.org/philosophy/free-sw.html> is
+ <http://www.gnu.org/philosophy/po/free-sw.pot>; the URL for its
+ LANG PO file (when available) is
+ <http://www.gnu.org/philosophy/po/free-sw.LANG.po>:
+
+ wget http://www.gnu.org/philosophy/po/free-sw.pot
* Assuming you already know the article you want to translate, you
- have to create an empty `ARTICLE.LANG.po' file and then translate
- all messages with a PO editor. *Note New Translation: (gnun)New
- Translation. For an almost complete list of PO editors, *note PO
- Files: (gnun)PO Files.
+ have to create an empty 'ARTICLE.LANG.po' file and then translate
+ all messages with a PO editor. *Note (gnun)New Translation::. For
+ an almost complete list of PO editors, *note (gnun)PO Files::.
* When you are pleased with the translation, check that the PO file
is valid and submit it to <address@hidden>, attached to
@@ -220,19 +222,14 @@
repository.
* In order GNUN to be able to generate (and subsequently update) a
- gettextized translation, the language should have the server
+ fully translated page, the language should have the server
templates available as PO files. These templates are short, and
- translating them shouldn't take much time. If the language code
- is present in the `TEMPLATE_LINGUAS' variable at
- `server/gnun/gnun.mk', then you don't have to do anything. If it
- is not, the required files are `server/po/head-include-2.LANG.po',
- `server/po/body-include-1.LANG.po',
- `server/po/body-include-2.LANG.po' and
- `server/po/footer-text.LANG.po'--you can translate and submit them
- in the usual way, together with the translation of the essay.
-
- Additional templates are defined via the EXTRA-TEMPLATES variable
- in `server/gnun/gnun.mk'.
+ translating them shouldn't take much time. If the language code is
+ present in the 'TEMPLATE_LINGUAS' variable at
+ 'server/gnun/gnun.mk', then you don't have to do anything. If it
+ is not, the required files are defined via the 'extra-templates'
+ variable in 'server/gnun/gnun.mk'--you can translate and submit
+ them in the usual way, together with the translation of the essay.
If you don't want to translate the templates for whatever
reason--do not worry, the web-translators will install empty
@@ -241,7 +238,7 @@
It is quite possible that there will be errors or typos, so once you
are informed that the translation is online, check it carefully and if
necessary, resubmit the PO file with corrections. Do not forget to run
-`cvs update' first and edit the updated `.po' file from the
+'cvs update' first and edit the updated '.po' file from the
repository--most probably the Translation Managers have already made
some modifications to it, usually to fix validation errors and to
complete the PO file header.
@@ -262,27 +259,30 @@
You should _never_ translate the HTML markup--i.e. _do not_ use the
"View Source" functionality of your browser to translate the raw HTML.
-Most of it is irrelevant, and automatically inherited from the markup
-of the original article. Simply save your translation in a plain text
-file (`.txt'), preferably in UTF-8 encoding. You can use any decent
-text editor for that--Emacs, Vim, gEdit, Kate, OpenOffice.org (the file
-should be saved as `.txt', not `.odt'), etc.
+Most of it is irrelevant, and automatically inherited from the markup of
+the original article. Simply save your translation in a plain text file
+('.txt'), preferably in UTF-8 encoding. You can use any decent text
+editor for that--Emacs, Vim, gEdit, Kate, OpenOffice.org (the file
+should be saved as '.txt', not '.odt'), etc.
Translate the title, the blue heading (if it differs slightly from
-the title) and the body of the article upto the link `back to top'.
-For example, for `http://www.gnu.org/philosophy/free-sw.html' that
-would be:
+the title) and the body of the article upto the link 'back to top'. For
+example, for <http://www.gnu.org/philosophy/free-sw.html> that would be:
+
+ What is free software? - GNU Project - Free Software Foundation (FSF)
- The Free Software Definition - GNU Project - Free Software Foundation
(FSF)
+ What is free software?
- We maintain this free software definition...
+ The Free Software Definition
+
+ The free software definition presents...
...
- ...If you would like to review the complete list of changes, you can
- do so on our cvsweb interface.
+ ...You can review the complete list of changes to the page through
+ the cvsweb interface.
Since web-translators do not speak all languages, it is essential to
mark somehow any inner markup, because very often it is hard to figure
-out what translated text should be enclosed inside `<em>' or `<a>'
+out what translated text should be enclosed inside '<em>' or '<a>'
elements, to name a few. The easiest way to do this is just to use the
corresponding HTML markup, although anything else is suitable. For
example, here is how to indicate that the link "History section" at the
@@ -292,12 +292,12 @@
Si quisiera revisar los cambios que hemos hecho, por favor vea la
{seccio'n historial} ma's abajo para ma's informacio'n.
- It is not necessary to include the value of the `href' attribute, as
+ It is not necessary to include the value of the 'href' attribute, as
it is already known.
If you wish your name to appear in the footer as a translator of the
-article, please also provide a translation of `Translation: YOUR NAME
-IN YOUR NATIVE LANGUAGE' or `Translated by: YOUR NAME IN YOUR NATIVE
+article, please also provide a translation of 'Translation: YOUR NAME IN
+YOUR NATIVE LANGUAGE' or 'Translated by: YOUR NAME IN YOUR NATIVE
LANGUAGE', as you prefer. Please also state if you wish your email
address to be published (some readers prefer to send suggestions
directly to the translator, but we certainly do not require that
@@ -328,14 +328,14 @@
exercising levels of control as she sees fit.
A prospective team co-ordinator should have perfect understanding of
-the GNU Philosophy and the various issues the free software movement
-set out to solve. Energy and time are always needed, as well as certain
+the GNU Philosophy and the various issues the free software movement set
+out to solve. Energy and time are always needed, as well as certain
communication skills.
However, a team leader is not a dictator (for life); every action
-and/or decision taken should have its justification and should stem
-from the goals of the project at large. Inefficient or inoperative
-leaders are replaced, if necessary.
+and/or decision taken should have its justification and should stem from
+the goals of the project at large. Inefficient or inoperative leaders
+are replaced, if necessary.
3.1 How To Form A New Team
==========================
@@ -346,40 +346,39 @@
and technical skills, and devotion. The only "bonus" team leaders have
is more work and more responsibilities.
- You should read and _all_ the documentation related to the
-translation process at the very least all important philosophy-related
-articles listed on
-`http://gnu.org/server/standards/README.translations.html' and
-`http://gnu.org/server/standards/translations/priorities.html' before
+ You should read _all_ the documentation related to the translation
+process and at the very least all important philosophy-related articles
+listed on <http://gnu.org/server/standards/README.translations.html> and
+<http://gnu.org/server/standards/translations/priorities.html> before
you decide to form a new team, or take over an orphaned team. Once you
have the internal feeling that having a gnu.org translation team for
your language is a must, and you are the one for this job, follow these
steps:
1. If you do not have a Savannah account, register at
- `https://savannah.gnu.org/account/register.php'. Write access to
+ <https://savannah.gnu.org/account/register.php>. Write access to
the repository and project membership is handled via Savannah, so
you would need an account in any case.
2. Checkout a complete working copy of the CVS Web repository as
- described at `https://savannah.gnu.org/cvs/?group=www'. If you
+ described at <https://savannah.gnu.org/cvs/?group=www>. If you
still don't have a Savannah account or if you have registered one,
but are not yet member of any Savannah project, refer to the
instructions under "Anonymous CVS Access". If you are already a
member of (any) Savannah project, you can proceed with "Project
- Member CVS Access via SSH", although you will still lack
- permission to commit (later, when it is granted, you can use the
- same working copy).
+ Member CVS Access via SSH", although you will still lack permission
+ to commit (later, when it is granted, you can use the same working
+ copy).
Examine the layout and structure of the repository. Basically, it
is mapped to the URL locations, more or less. Take a look at the
- most important materials to translate under `/philosophy', `/gnu',
- `/distros', `/copyleft' and `/licenses' directories just to get a
- rough estimate about the amount of work involved. If you are
+ most important materials to translate under '/philosophy', '/gnu',
+ '/distros', '/copyleft' and '/licenses' directories just to get a
+ rough estimate about the amount of work involved(1). If you are
still not scared and determined to go on further, excellent.
As you have probably observed, every directory that contains
- translatable articles has a `/po' sub-directory, which is where the
+ translatable articles has a '/po' sub-directory, which is where the
canonical source format of the translations is stored.
3. Submit your first message stating that you would like to establish
@@ -387,35 +386,34 @@
have read all the documentation and list the issues that remain
unclear for you. The Translation Managers will answer your
questions and send you the standard questionnaire for new team
- leaders. It is short and shouldn't take more than 10-30 minutes
- to complete. This questionnaire is important, as we consider it
+ leaders. It is short and shouldn't take more than 10-30 minutes to
+ complete. This questionnaire is important, as we consider it
crucial for any translation team co-ordinator to have a good
understanding of the philosophy of the free software movement.
4. Check if your language code is present in the variable
- `TEMPLATE_LINGUAS' at `server/gnun/gnun.mk'. If it is not, the
+ 'TEMPLATE_LINGUAS' at 'server/gnun/gnun.mk'. If it is not, the
first thing to do is to translate and submit to
<address@hidden> the following files (all in the
- `server/po/' directory): `head-include-2.LANG.po',
- `body-include-1.LANG.po', `body-include-2.LANG.po'
- `footer-text.LANG.po', `outdated.LANG.po',
- `skip-translations.LANG.po', and `top-addendum.LANG.po'. *Note
- New Translation: (gnun)New Translation.
+ 'server/po/' directory): 'head-include-2.LANG.po',
+ 'body-include-1.LANG.po', 'body-include-2.LANG.po'
+ 'footer-text.LANG.po', 'outdated.LANG.po',
+ 'skip-translations.LANG.po', and 'top-addendum.LANG.po'. *Note
+ (gnun)New Translation::.
- The language code (LANG) should be the ISO 639-1 code of the
- language, for example `hy' for Armenian or `el' for Greek. If
- there is no such code, use the ISO 639-2 one--e.g. `mai' for
- Maithili. If the language is a variant such as Brazilian
- Portuguese or Simplified Chinese, use small caps and a
- dash--`pt-br' and `zh-cn' instead of `pt_BR' and `zh_CN'.
+ language, for example 'hy' for Armenian or 'el' for Greek. If
+ the language is a variant such as Brazilian Portuguese or
+ Simplified Chinese, use small caps and a dash--'pt-br' and
+ 'zh-cn' instead of 'pt_BR' and 'zh_CN'.
- The PO file header and initial comments should be completed as
documented.
- - Do not use HTML entities for non-ASCII characters as in the
+ - 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.
+ there is 'ü' and this is a character from the alphabet of
+ your language, just write it as 'u"' directly.
5. Any prospective team leader should submit a few translations first.
This is a process of pointing errors and omissions (which are
@@ -423,58 +421,55 @@
is going to carry out these checks on her own, once the team is
approved. If there are existing translations that are not yet in
PO format, the best thing to do is to migrate one or two. You can
- use `find' to find out what's already in the repository, for
+ use 'find' to find out what's already in the repository, for
example:
find -name \*.LANG.html
6. Submit at least two translations of your own. We maintain a list
with priority articles at
- `http://www.gnu.org/server/standards/translations/priorities.html',
+ <http://www.gnu.org/server/standards/translations/priorities.html>,
although it is probably hard to start with one of them. Choose
whatever you wish, provided it is an essay and not an auxiliary
- page. Avoid translating the homepage or `whatsnew.html'--they are
- moving targets and keeping up would be only a distraction for both
- parties in the process. As usual, send the completed translation
- to <address@hidden>.
+ page. Avoid translating the homepage or 'planetfeeds.html'--they
+ are moving targets and keeping up would be only a distraction for
+ both parties in the process. As usual, send the completed
+ translation to <address@hidden>.
7. The Translation Managers will review your translations, and
- eventually comment on them (mostly technical details if there is
- no one among them speaking your language). Depending on the case,
- it might be required to submit a corrected file. In any event,
- please take into account the remarks in future work.
-
- 8. If all goes well, you will receive a response inviting you to
- apply for a new translation project at Savannah. The project name
- should be `www-LANG' where LANG is, unsurprisingly, the language
- code. If such a project already exists, this step will be skipped
- and you'll be made an administrator of the project. To register
- the project, go to `https://savannah.gnu.org/register/' and make
- sure you fill in the required fields. The "Group type" should be
- `www.gnu.org translation team', and "Project license"--`WebSite
- Only'. In the "Tarball URL" field enter a bogus URL such as
- `http://gnu.org'.
+ eventually comment on them (mostly technical details if there is no
+ one among them speaking your language). Depending on the case, it
+ might be required to submit a corrected file. In any event, please
+ take into account the remarks in future work.
+
+ 8. If all goes well, you will receive a response inviting you to apply
+ for a new translation project at Savannah. The project name should
+ be 'www-LANG' where LANG is, unsurprisingly, the language code. If
+ such a project already exists, this step will be skipped and you'll
+ be made an administrator of the project and its mailing lists. To
+ register the project, go to <https://savannah.gnu.org/register/>
+ and make sure you fill in the required fields. The "Group type"
+ should be 'www.gnu.org translation team', and "Project
+ license"--'WebSite Only'. In the "Tarball URL" field enter a bogus
+ URL such as 'http://gnu.org'.
- *Pay attention:* This step is a formality. You should proceed
- with the project registration only when you have been asked by
+ *Pay attention:* This step is a formality. You should proceed with
+ the project registration only when you have been asked by
<address@hidden> to do so. Otherwise, the submission may
appear in the task list of the Savannah Hackers for a fairly long
time, which is troublesome.
- 9. When the project is approved, the team information will be added
- to the list at `README.translations.html', you will become a
- member of the `www' project (thus granting you CVS write access to
- the whole repository--so be careful) and the `trans-coord'
- project. You'll also be subscribed to the following mailing lists:
+ 9. When the project is approved, the team information will be added to
+ the list at 'README.translations.html', you will become a member of
+ the 'www' project (thus granting you CVS write access to the whole
+ repository--so be careful) and the 'trans-coord' project. You'll
+ also be subscribed to the following mailing lists:
- www-commits
- trans-coord-discuss
- You'll have to request subscription to `www-discuss'
- yourself--this list is managed by the GNU Webmasters, but all team
- leaders are required to subscribe in order to receive important
- site-wide announcements.
+ - www-discuss
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
@@ -483,12 +478,12 @@
with the expected pace.
Applications for new teams are sometimes processed in
-parallel(1)--the most suitable candidate is chosen in this case. This
+parallel(2)--the most suitable candidate is chosen in this case. This
is, undoubtedly, based on a subjective judgment made by the Translation
Managers, and many factors are important.
The procedure for taking over an orphaned team is the same. Once
-completed, you will be made an admin of the respective `www-LANG'
+completed, you will be made an admin of the respective 'www-LANG'
Savannah project, or if it doesn't exist, invited to apply for
registration. Do not automatically remove old members just because you
are starting "afresh"--some of them might want to continue to
@@ -498,9 +493,12 @@
---------- Footnotes ----------
- (1) In general, we try to avoid this and direct all new volunteers
-to the person who is already carrying out the process--this is also a
-verification if she can cooperate easily with others.
+ (1) As of December 2012, there are over 250 files to translate in
+"important" directories; their volume is about 3.5 MB.
+
+ (2) In general, we try to avoid this and direct all new volunteers to
+the person who is already carrying out the process--this is also a
+verification if she can co-operate easily with others.
3.2 The Gentle Art of Managing A Translation Team
=================================================
@@ -535,8 +533,8 @@
Too many errors are just missed (especially if they are obvious) when
the translator does a final review of her own translation.
- It is good to establish a practice: Do not commit officially (i.e. in
-`www', which will appear online at `http://gnu.org' immediately) a
+ It is good to establish a practice: Do not commit officially (i.e.
+in 'www', which will appear online at <http://gnu.org> immediately) a
translation that is not yet reviewed by someone else who is not the
translator. Always perform a final review yourself even if the
translation has been checked by another member of the team. In other
@@ -547,12 +545,12 @@
list--the translator sends the new translation and participants comment
on specific parts, quoting them appropriately. The benefit of this
approach is that it is straightforward, but the drawback is that there
-is no automatic "record" about the conclusion of the specific
-discussion (or sub-thread) and sometimes such discussions easily
-digress, making it even harder to come up with a solution.
+is no automatic "record" about the conclusion of the specific discussion
+(or sub-thread) and sometimes such discussions easily digress, making it
+even harder to come up with a solution.
- Another way is to use Savannah's built-in trackers (the `Tasks' and
-`Bugs' trackers, specifically). This is further explained in the next
+ Another way is to use Savannah's built-in trackers (the 'Tasks' and
+'Bugs' trackers, specifically). This is further explained in the next
section, *note Tracking Tasks::. One way or another, you should create
some kind of review process.
@@ -572,12 +570,12 @@
slowing the translation process.
A solution to this specific problem is to distribute the load among
-more people. For example: Member D makes a translation of `foo.html'
-and uploads `foo.LANG.po' in the translation project's repository at
+more people. For example: Member D makes a translation of 'foo.html'
+and uploads 'foo.LANG.po' in the translation project's repository at
Savannah, marking the relevant task as "Ready for Test" (of course, the
equivalent is sending a message with the attached translation to the
-team's mailing list, or similar). Then Member A, B and C (or only A
-and B if C is currently busy) review it independently and post
+team's mailing list, or similar). Then Member A, B and C (or only A and
+B if C is currently busy) review it independently and post
comments/suggestions/errors in the bug tracker. Discussion goes on
between them and D, problems are rectified and finally the leader (who
may happen to be one of A, B, C, D) makes a final review. It is easier
@@ -588,10 +586,10 @@
leader. You can also set up an internal formal rule: If a member makes
a translation, he has to review another one (or two) as well.
- Some translations can take a fairly long time--the typical example
-is a complicated essay or a transcript of a speech. It is best to avoid
+ Some translations can take a fairly long time--the typical example is
+a complicated essay or a transcript of a speech. It is best to avoid
duplicate work by indicating, or better--recording, that someone is
-working on this specific article. The `Tasks' tracker is suitable for
+working on this specific article. The 'Tasks' tracker is suitable for
this purpose.
It is prudent to discuss the most convenient naming scheme and
@@ -603,40 +601,40 @@
Thus, a possible straightforward way to manage these tasks is:
* If someone starts working on a new translation, she creates a new
- task with a `Subject' indicating the article, for example simply
- `philosophy/bsd.html' and assigns it to herself.
+ task with a 'Subject' indicating the article, for example simply
+ 'philosophy/bsd.html' and assigns it to herself.
* When the translation is finished and ready for review, the
- translator changes the `Status' to "Ready For Test".
+ translator changes the 'Status' to "Ready For Test".
* Other members review it, and open bugs relevant to one specific
- problem. It is usually better not to conflate two different
- issues together--it makes them harder to discuss, and hard to
- track them by severity. Some are grammatical errors, some are
- fundamental ones that change the whole meaning, some are simply
- suggestions for improvement. It helps if the project admin
- creates new Category fields for every article, for instance
- `gnu/gnu-history.LANG.html', `philosophy/microsoft.LANG.html'--it
- would enable functionality like "Show me all bugs ever reported
- against this translation", which is useful.
+ problem. It is usually better not to conflate two different issues
+ together--it makes them harder to discuss, and hard to track them
+ by severity. Some are grammatical errors, some are fundamental
+ ones that change the whole meaning, some are simply suggestions for
+ improvement. It helps if the project admin creates new Category
+ fields for every article, for instance 'gnu/gnu-history.LANG.html',
+ 'philosophy/microsoft.LANG.html'--it would enable functionality
+ like "Show me all bugs ever reported against this translation",
+ which is useful.
* Once the bugs (or at least the important bugs) are fixed, the team
leader can make the final review and install the translation in the
- official repository, marking the task as `Done'. Bugs that are not
- resolved should remain opened, naturally.
+ official repository, marking the task as 'Done'. Bugs that are not
+ resolved should remain open, naturally.
Of course, teams can choose to manage these things using external
resources and eventually other bug (or issue) tracking systems.
Whatever you decide, please make sure that bugs can be reported using
free software only, and that the software providing that service is
free. It makes an extremely bad impression if a reader has to report a
-problem about a gnu.org translation via non-free hosting platforms like
+problem about a gnu.org translation via nonfree hosting platforms like
SourceForge.
If you use a certain facility (i.e. a bug tracking system) to manage
bugs in translations, it is best to take advantage of
-`generic.LANG.html' and advertise it on every page. *Note
-generic.LANG.html: (gnun)generic.LANG.html, for details.
+'generic.LANG.html' and advertise it on every page. *Note
+(gnun)generic.LANG.html::, for details.
3.2.1.2 How To Proceed With Unreviewed Translations
...................................................
@@ -649,21 +647,19 @@
It is important to record somehow that this published translation
still lacks appropriate review. If the suggestion in the previous
-section is implemented, it would mean leaving the relevant task `Open'
-and `Ready For Test' despite the translation being officially online.
+section is implemented, it would mean leaving the relevant task 'Open'
+and 'Ready For Test' despite the translation being officially online.
You may also add a comment to the PO file.
3.2.2 CVS Commits And Best Practices
------------------------------------
-As all team leaders have write access to the CVS repository of the
-`www' project, this technically means that they are able to modify
-every single file in it, and also those of the Web CVS repositories of
-other projects at Savannah. This vote of confidence should never be
-abused--the only files team co-ordinators should add/update are those
-relevant to their translation work. It is OK to fix an obvious typo in
-an original article; for anything else please report to
-<address@hidden>.
+As all team leaders have write access to the CVS repository of the 'www'
+project, this technically means that they are able to modify every
+single file in it. This vote of confidence should never be abused--the
+only files team co-ordinators should add/update are those relevant to
+their translation work. It is OK to fix an obvious typo in an original
+article; for anything else please report to <address@hidden>.
If you wish to volunteer as webmaster and help with generic webmaster
work and RT tickets, that is perfectly fine--please follow the
@@ -672,19 +668,19 @@
If a particular page has issues with the markup which create problems
for your language, please inform <address@hidden>. For
-general issues that affect more articles, or for severe problems,
-please write to <address@hidden>.
+general issues that affect more articles, or for severe problems, please
+write to <address@hidden>.
It is recommended to read the entire CVS manual at least once, for a
basic understanding of how this VCS works. *Note Concurrent Versions
-System: (cvs)Top. It is not necessary to become an expert--the `www'
+System: (cvs)Top. It is not necessary to become an expert--the 'www'
project does not use complex features like tags, vendor branches,
merging, etc. as they are not very useful for a live website.
However, you'd probably have to learn how to use CVS for effective
-work--to extract information from the history, review diffs and
-specific changes, synchronize with the working repository of the team
-(if any), adding/removing files, etc.
+work--to extract information from the history, review diffs and specific
+changes, synchronize with the working repository of the team (if any),
+adding/removing files, etc.
If you make changes that affect more than one file but the change is
coherent, please do it as a single commit. This will generate only one
@@ -692,8 +688,9 @@
files about semantically the same change. Always write commit logs in
English(1), providing a short description of the change. If you modify
a file that is not an article but a script or part of software (such as
-`server/gnun/gnun.mk'), it would be nice to follow the GNU Coding
-Standards and describe the change precisely. For example, do not write:
+'server/gnun/gnun.mk'), it would be nice to follow the GNU Coding
+Standards and describe the change precisely. *Note Log Messages:
+(standards)Change Logs. For example, do not write:
Added support for Nepali.
@@ -707,34 +704,36 @@
and
- (HOME_LINGUAS): Add `pa'.
+ (FUZZY_DIFF_LINGUAS): Add `pa'.
This makes it easier for others to search for a particular change in
the history.
- If you add a binary file (for example, `.png'), do it with `cvs
+ If you add a binary file (for example, '.png'), do it with 'cvs
commit -kb FILE'. This turns off keyword substitution, which prevents
-RCS keywords like `$Id$' to get expanded, subsequently corrupting the
-file. *Note Substitution Modes: (cvs)Substitution Modes. More
-importantly, using `-kb' prevents corruption of the binary when people
-using CVS clients under Windoze checkout, modify the file, and then
-commit it with messed EOLs. (Unfortunately there are still committers
-using non-free operating systems--we cannot dictate what OS people use,
-but we can at least try to prevent damage.)
+RCS keywords like '$Id$' to get expanded, subsequently corrupting the
+file. *Note (cvs)Substitution Modes::. More importantly, using '-kb'
+prevents corruption of the binary when people using CVS clients under
+infamous OS checkout, modify the file, and then commit it with messed
+ends of lines.(2)
Although not absolutely compulsory, it is recommended that every team
-leader subscribes to <address@hidden>. It is useful to examine
-the diffs of your own messages, if you miss something while inspecting
-the diff before the commit. In any case, a team leader should be
-subscribed to that list to avoid his own commit messages to be
-moderated. If you absolutely do not desire receiving all traffic, just
-disable mail delivery in Mailman's user interface.
+leader subscribes to <address@hidden>. It is useful to examine the
+diffs of your own messages, if you miss something while inspecting the
+diff before the commit. In any case, a team leader should be subscribed
+to that list to avoid his own commit messages to be moderated. If you
+absolutely do not desire receiving all traffic, just disable mail
+delivery in Mailman's user interface.
---------- Footnotes ----------
- (1) This advice is applicable for the `www' repository only--feel
+ (1) This advice is applicable for the 'www' repository only--feel
free to write logs in your native language when committing in your
-project's Sources repository.
+team's repositories.
+
+ (2) Few years ago there still were committers using nonfree operating
+systems--we don't dictate what OS people use, but we can at least
+prevent this technical kind of damage.
3.2.3 Taking Advantage of Savannah
----------------------------------
@@ -747,12 +746,12 @@
Using external hosting facilities may seem justified sometimes. Some
teams may have already established repositories and/or bug tracking
-systems where usual contributors already have access. Some team
-members prefer to work within the established infrastructure of a broad
+systems where usual contributors already have access. Some team members
+prefer to work within the established infrastructure of a broad
translation team (for whatever reason), but this is discouraged. It is
required that every team has a mailing list at Savannah (*note Savannah
-Mailing Lists::), because it is easier to pass its management to the
-new co-ordinator when the old one steps down, and it helps to keep the
+Mailing Lists::), because it is easier to pass its management to the new
+co-ordinator when the old one steps down, and it helps to keep the
archives at one place for future members of the team. Likewise, it is
better to use Savannah for the team's repository and bugs/tasks, but
this is not mandatory.
@@ -796,10 +795,10 @@
It is a good idea to mark inactive members, for example if there is
no interaction (bug reports, new translations, updates to existing
translations, proof-reading) for at least six months. You can do that
-by unmarking the `On Duty' checkbox for the respective project member
-under `Set Permissions'. Inactive members have absolutely the same
+by unmarking the 'On Duty' checkbox for the respective project member
+under 'Set Permissions'. Inactive members have absolutely the same
rights as active ones--the only exception is that they don't count for
-the total number of members, and they appear separately on `View
+the total number of members, and they appear separately on 'View
Members'.
3.2.3.2 Homepage of The Team
@@ -807,9 +806,9 @@
Every Savannah project has a Web repository, which is, for technical and
historical reasons, only CVS. By default it is mapped to
-<http://www.gnu.org/server/standards/translations/LANG>; to add files
-to it first make a checkout, following the instructions at
-<https://savannah.gnu.org/cvs/?group=www-LANG>.
+'http://www.gnu.org/server/standards/translations/LANG'; to add files to
+it first make a checkout, following the instructions at
+'https://savannah.gnu.org/cvs/?group=www-LANG'.
It is recommended to describe all team-specific procedures, if there
are any. That way, you can point potential team members to the
@@ -817,44 +816,42 @@
explaining every volunteer separately.
All team-specific pages should follow the usual linking criteria (see
-`http://gnu.org/server/standards/README.webmastering.html#pollinking'
+<http://gnu.org/server/standards/README.webmastering.html#pollinking>
and the FSF HTML Style Sheet
-Guidelines--`http://gnu.org/server/fsf-html-style-sheet.html').
+Guidelines--<http://gnu.org/server/fsf-html-style-sheet.html>).
For historical reasons, team-specific materials were available in the
-`www' repository, under ad-hoc locations as `/spanish', `/wwwsr', etc.
-These locations are deprecated, and the contents will be moved without
-warning to `/graveyard' in the `trans-coord' _Sources_ repository,
-following the original `www' layout (that is, if there were any
-sub-directories, they will be retained).
+'www' repository, under ad-hoc locations as '/spanish', '/wwwsr', etc.
+These locations are deprecated, and the contents will be removed without
+warning.
3.2.3.3 Support Tracker
.......................
This tracker is supposed to be related to things about the _project
management_ itself, i.e. project members may report here missing
-functionality and/or features that requires the project admin(s)'s
-action. Do not use it for anything else as it quickly becomes
-confusing. It is OK to disable it if the team is small.
+functionality and/or features that requires the project admin's action.
+Do not use it for anything else as it quickly becomes confusing. It is
+OK to disable it if the team is small.
3.2.3.4 Tasks Tracker
.....................
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
-is possible to use this tracker to "announce" to the team members that
-a specific article should be translated. The one who volunteers may
+is possible to use this tracker to "announce" to the team members that a
+specific article should be translated. The one who volunteers may
assign the task to herself.
Teams may use this tracker to avoid duplicate work, by declaring that
they intend to work on a specific translation.
- Feel free to organize the `Tasks' management as you see fit.
+ Feel free to organize the 'Tasks' management as you see fit.
3.2.3.5 Bugs Tracker
....................
-The `Bugs' tracker is designed for tracking bugs. You can use for
+The 'Bugs' tracker is designed for tracking bugs. You can use for
several purposes:
* Suggest readers to report bugs there.
@@ -862,8 +859,8 @@
* Use it for all kinds of internal team tasks.
* Forward bugs reported against LANG translations in the
- `trans-coord' project and assign them to the specific maintainer
- (who is supposed to be a `www-LANG' project member), if you have
+ 'trans-coord' project and assign them to the specific maintainer
+ (who is supposed to be a 'www-LANG' project member), if you have
such policy.
3.2.3.6 Patch Tracker
@@ -872,9 +869,9 @@
This tracker doesn't make much sense for translation projects, as the
original on which the translation is based is volatile and the
translation "patch" is 100% guaranteed not to apply cleanly very soon
-after it is submitted. Even ignoring this detail, this specific
-feature is slowly marching towards complete deprecation, as there are
-much better ways to submit patches nowadays.
+after it is submitted. Even ignoring this detail, this specific feature
+is slowly marching towards complete deprecation, as there are much
+better ways to submit patches nowadays.
You should disable this feature, as it causes only confusion.
@@ -882,7 +879,7 @@
....................
That is a way to inform newcomers and interested people (who visit the
-project page from time to time, or subscribe to the `News' RSS feed)
+project page from time to time, or subscribe to the 'News' RSS feed)
about a major change or event within the project.
You can also setup news entries to be sent to a mailing list (that's
@@ -899,11 +896,11 @@
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 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 the history for new translators.
+team when the co-ordinator disappears; its archive will also give access
+to the history for new translators.
You can create new mailing lists via the Savannah interface.
However, this should be done after some thought. If the project
@@ -918,12 +915,11 @@
An easy way to keep up with changes in the original articles and to
manage continuous contributions is to keep all translations in the
translation project's Sources repository. That way, it is easy to edit
-draft translations and install them in `www' only when they're ready.
+draft translations and install them in 'www' only when they're ready.
It is also convenient to update the translation (merge any changes from
the original) while it is still under review.
- *Note PO Files and Team: (gnun)PO Files and Team, for more
-information.
+ *Note (gnun)PO Files and Team::, 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
@@ -936,29 +932,28 @@
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
+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').
+(<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'
+ * Pootle--<http://translate.sourceforge.net/wiki/pootle>
- * Narro--`http://code.google.com/p/narro'
+ * Vertaal--<http://code.google.com/p/vertaal>
- * Launchpad--`https://dev.launchpad.net'
+ * 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.
+ Note that to keep the '.pot' files regularly updated (assuming such a
+web-based system runs 'msgmerge' automatically), you'll have to take
+care of the one-way regular sync from the 'www' CVS repository.
3.2.4 Promoting Members As Co-leaders
-------------------------------------
@@ -966,21 +961,21 @@
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
to help. Note that a subsequently appointed team co-ordinator is not
-simply a "committer" with write access to the `www' repository; she has
+simply a "committer" with write access to the 'www' repository; she has
full responsibilities just like a single leader, although the latter
still remains the primary contact for the team.
If you'd like another person to act as a co-leader and help you with
the management tasks, send a message to <address@hidden> with
her name and Savannah account. She has to be already a member of
-`www-LANG'.
+'www-LANG'.
The procedure for co-leaders is a simplified version of the one for a
new team or taking over an existing team. *Note New Team::.
To remove co-ordinators, please write to <address@hidden>
with details and rationale for the removal. Do not edit
-`README.translations.html' yourself; this is a final formality step to
+'README.translations.html' yourself; this is a final formality step to
be performed by the Translation Managers.
3.3 Reporting Team Status
@@ -1010,8 +1005,8 @@
The best time to send a report is near the end of the year, for
example November. In any case, please do not send it later than
December 15th, as the Translation Manager has to prepare a general
-report to the FSF, and it is better if it takes into account the
-reports of the team leaders.
+report to the FSF, and it is better if it takes into account the reports
+of the team leaders.
If there is no sensitive information in the report and you feel like
sharing it, you can send it to <address@hidden> (which is
@@ -1037,7 +1032,7 @@
Co-leaders::) and retire completely when she is absolutely ready to
proceed without your further help and advice.
-4 `trans-coord' Admins
+4 'trans-coord' Admins
**********************
This chapter is not yet written. The current admins know what to do,
@@ -1061,177 +1056,159 @@
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 Migrating: (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.
+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.
-5.2 Summary of SSI `#include's
+5.2 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:
+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/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'
+'server/body-include-1.html'
Contains the top menu with useful "skip to" links.
-`server/body-include-2.html'
+'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.
+ 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/body-include-2.LANG.html' or some other template file.
-`server/footer-text.html'
+'server/footer-text.html'
This is a very short file currently containing the "back to top"
link. Also translatable via GNUN.
-`server/header.html'
+'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:
+ 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:
+'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.
+ 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.
+ 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'
+'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'
+'server/html5-head-include-1.html'
Likewise, this file replaces head-include-1.html for HTML5 pages.
-`server/head-include-2.html'
+'server/head-include-2.html'
Imports the standard CSS, which can be overridden. *Note CSS::.
-`server/footer.html'
+'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.
+ 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'
+'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
+ 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.
-`translations.include'
+'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.
-`gnusflashes.include'
- A portion of the most recent 3 news items from
- `server/whatsnew.html', generated automatically. If your language
- does not have `server/po/whatsnew.LANG.po', this file will be
- used. Otherwise, if there is an existing localized homepage and
- you commit `whatsnew.LANG.po', the homepage will be rebuilt to
- include the translated `gnusflashes.LANG.include'.
-
-`server/whatsnew.include'
- Generated automatically, this file is included from
- `server/whatsnew.html'. Translations are built automatically, and
- the localized `gnusflashes.include' is derived from it.
-
-`licenses/gpl-3.0-body.html'
-`licenses/fdl-1.3-body.html'
-`...'
+'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.
+ "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'
+'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.
+ 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'
+ - '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'
+ - 'footer.html'
+ - 'footer-text.html'
- - `body-include-2.html'
-
- - `footer.html'
-
- - `footer-text.html'
-
- in the `server' sub-directory are what webmasters call "the server
+ 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 Runtime Variables:
-(gnun)Runtime Variables.
+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
+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
+'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.
+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" -->
@@ -1240,7 +1217,7 @@
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
+gnu.org website. A typical language-specific 'style.LANG.css' file
looks like this:
.inner { max-width: 65em; }
@@ -1249,14 +1226,13 @@
#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).
+(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.
+ 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)
@@ -1266,28 +1242,28 @@
with appropriate explanation (which may include a demonstration of the
bug, such as a screenshot).
-5.3.1 Localizing The `topbanner' Image
+5.3.1 Localizing The 'topbanner' Image
--------------------------------------
If you'd like the nice gnu image to be localized (i.e. "GNU Operating
System" to appear in your native language, here are the steps:
- 1. Copy `graphics/topbanner.svg' as `graphics/topbanner.LANG.svg'
+ 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).
+ 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
+ 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::.
+ 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
@@ -1300,47 +1276,51 @@
5.3.2 Specific Issues Related to RTL
------------------------------------
-Unfortunately, the `http://gnu.org' website does not have excellent
+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'.
+ * 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
+ 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.
+ *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
+<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.
It is very important to keep existing translations up-to-date with
the respective English originals. This task should be higher priority
-than translating new articles. GNUN's `report' rule can help you to
-identify precisely which articles need updating; *note report:
-(gnun)report. There is a monthly cronjob which sends a verbose output
-to each team--by default, the address(es) used is the Savannah
-account(s) of the admin(s) of the specific translation project. If you
-want them changed, please write to <address@hidden>.
+than translating new articles. GNUN's 'report' rule can help you to
+identify precisely which articles need updating; *note (gnun)report::.
+There is a monthly cronjob which sends a verbose output to each team--by
+default, the address(es) used is the Savannah account(s) of the admin(s)
+of the specific translation project. If you want them changed, please
+write to <address@hidden>.
+
+ GNUN also maintains reports about current status of translations of
+all active teams in <http://www.gnu.org/software/gnun/reports/>. If the
+page for your team is missing there, please ask
+<address@hidden> to add it to the cron job.
It is strongly recommended translation teams to attempt to recruit
native English speakers in order to improve their translation process.
@@ -1351,24 +1331,24 @@
_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
+'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'
+'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'
+'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'
+'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.
@@ -1383,19 +1363,18 @@
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
+ 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 `translations-list' when
-languages are written beginning with a small letter according to your
-own rules. In other words, it is right to write `English' or `Deutsch'
-(because in English and German languages are capitalized), but not
-`Franc,ais' or `Portugue^s'--write them as `franc,ais' or `portugue^s',
-respectively.
+language with a capital letter in the 'translations-list' when languages
+are written beginning with a small letter according to your own rules.
+In other words, it is right to write 'English' or 'Deutsch' (because in
+English and German languages are capitalized), but not 'Franc,ais' or
+'Portugue^s'--write them as 'franc,ais' or 'portugue^s', respectively.
5.6 Distribution Terms
======================
@@ -1410,13 +1389,13 @@
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
+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:
* 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.
+ languages they support. Follow the link the language that you want
+ a translation for, if available.
* Follow the "Use this license for your own work" link near the
bottom of the translated deed page--it's in distinct yellow text.
@@ -1424,7 +1403,6 @@
* The textarea on that page provides standard HTML. Note that we're
not using the graphic, just the text.
-
For example, here's the text they provide for Dutch:
Dit werk is gelicenseerd onder een <a rel="license"
@@ -1442,7 +1420,7 @@
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 `http://www.gnu.org/philosophy/words-to-avoid.en.html#Content').
+(see <http://www.gnu.org/philosophy/words-to-avoid.en.html#Content>).
Note that translations should _not_ change the jurisdiction of the
license; they should _always_ link to the CC BY-ND 3.0 _United States_
@@ -1471,8 +1449,8 @@
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
+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
@@ -1482,94 +1460,80 @@
process, and a brief description about how they relate to the various
participants in the process.
-<address@hidden>
The basic discussion list of the GNU Webmasters. All team leaders
are required to subscribe.
This is a private mailing list.
-<address@hidden>
- Commits to the `www' repository are sent here. All Translation
+ Commits to the 'www' repository are sent here. All Translation
Managers are required to subscribe. It is strongly recommended
that team leaders subscribe--in any case they should, and mail
delivery can be disabled personally.
- This is a public mailing list, so everyone can subscribe and
- review the archives. The `www' CVS repository is also public.
+ This is a public mailing list, so everyone can subscribe and review
+ the archives. The 'www' CVS repository is also public.
-<address@hidden>
- The main discussion list for the GNU Web Translators. Team
- leaders must subscribe, as errors from GNUN are mailed here.
- Active team members are highly recommended to join as well,
- because the changes in general policies for translations are also
- announced and discussed here.
+ 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.
This is a private mailing list.
-<address@hidden>
This is a list for notifications about gnunews and GNUnited Nations
releases. It is not mandatory to subscribe to it, although the
traffic is very low. If you want to track only GNUN release
- announcements, subscribe to the `gnun' topic via Mailman's user
+ announcements, subscribe to the 'gnun' topic via Mailman's user
interface. Likewise, if you want to receive only "What's New"
- updates, subscribe to the `whatsnew' topic.
+ updates, subscribe to the 'whatsnew' topic.
Automatic announcements for new gnu.org translations (provided
they're handled by GNUN) are also delivered here. There are
- separate `LANG-ann' topics for every GNUN-aware language, so it is
+ separate 'LANG-ann' 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
- `es-ann' mailing list topic.
+ 'es-ann' mailing list topic.
This is a public mailing list.
-<address@hidden>
- All development of GNUN happens here. Commits to the `trans-coord'
+ All development of GNUN happens here. Commits to the 'trans-coord'
repository are also sent to this list.
This is a public list, and <address@hidden> is an alias.
-<address@hidden>
- All build logs from the various GNUN automatic builds are sent to
- this list, so it is not a very pleasant thing to be subscribed,
- especially if you are not interested in GNUN's internals.
- However, everyone can use the web archives to check the log why a
- particular article was not built at expected.
-
- This is a public list.
-
6.2 Savannah Projects Membership
================================
Participants in the www.gnu.org translations process normally have to be
members of the following Savannah projects, depending on the case:
-`www'
- The main project which hosts the `gnu.org' Web repository.
+'www'
+ The main project which hosts the 'gnu.org' Web repository.
Administrators are the Chief Webmaster, entrusted webmasters and
the Translation Manager (in order to approve leader's
- applications). All team leaders (and co-leaders) should be
- members of this project.
+ applications). All team leaders (and co-leaders) should be members
+ of this project.
Note that this project has no direct relationship with translators,
- although anything happening in `www' directly affects them. The
- `www' project is managed separately and has a different (entirely
+ although anything happening in 'www' directly affects them. The
+ 'www' project is managed separately and has a different (entirely
unrelated) process for approving contributors.
-`trans-coord'
- An organizational project especially created for coordination and
+'trans-coord'
+ 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
- <address@hidden> are often redirected to the
- `trans-coord' `Bugs' tracker.
+ <address@hidden> are often redirected to the 'trans-coord'
+ 'Bugs' tracker.
The admins of this project are the GNU Web Translation Managers.
-`www-LANG'
- All translation team leaders of the language LANG should be
- members of the project `www-LANG'. The admins of the project are
- the team leader and the co-leaders, if any.
+'www-LANG'
+ All translation team leaders of the language LANG should be members
+ of the project 'www-LANG'. The admins of the project are the team
+ leader and the co-leaders, if any.
Appendix A GNU Free Documentation License
*****************************************
@@ -1577,7 +1541,7 @@
Version 1.3, 3 November 2008
Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
- `http://fsf.org/'
+ <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@@ -1602,21 +1566,21 @@
free program should come with manuals providing the same freedoms
that the software does. But this License is not limited to
software manuals; it can be used for any textual work, regardless
- of subject matter or whether it is published as a printed book.
- We recommend this License principally for works whose purpose is
+ of subject matter or whether it is published as a printed book. We
+ recommend this License principally for works whose purpose is
instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium,
- that contains a notice placed by the copyright holder saying it
- can be distributed under the terms of this License. Such a notice
+ that contains a notice placed by the copyright holder saying it can
+ be distributed under the terms of this License. Such a notice
grants a world-wide, royalty-free license, unlimited in duration,
to use that work under the conditions stated herein. The
"Document", below, refers to any such manual or work. Any member
- of the public is a licensee, and is addressed as "you". You
- accept the license if you copy, modify or distribute the work in a
- way requiring permission under copyright law.
+ of the public is a licensee, and is addressed as "you". You accept
+ the license if you copy, modify or distribute the work in a way
+ requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
@@ -1634,12 +1598,12 @@
regarding them.
The "Invariant Sections" are certain Secondary Sections whose
- titles are designated, as being those of Invariant Sections, in
- the notice that says that the Document is released under this
- License. If a section does not fit the above definition of
- Secondary then it is not allowed to be designated as Invariant.
- The Document may contain zero Invariant Sections. If the Document
- does not identify any Invariant Sections then there are none.
+ titles are designated, as being those of Invariant Sections, in the
+ notice that says that the Document is released under this License.
+ If a section does not fit the above definition of Secondary then it
+ is not allowed to be designated as Invariant. The Document may
+ contain zero Invariant Sections. If the Document does not identify
+ any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
@@ -1650,27 +1614,27 @@
A "Transparent" copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
- straightforwardly with generic text editors or (for images
- composed of pixels) generic paint programs or (for drawings) some
- widely available drawing editor, and that is suitable for input to
- text formatters or for automatic translation to a variety of
- formats suitable for input to text formatters. A copy made in an
- otherwise Transparent file format whose markup, or absence of
- markup, has been arranged to thwart or discourage subsequent
- modification by readers is not Transparent. An image format is
- not Transparent if used for any substantial amount of text. A
- copy that is not "Transparent" is called "Opaque".
+ straightforwardly with generic text editors or (for images composed
+ of pixels) generic paint programs or (for drawings) some widely
+ available drawing editor, and that is suitable for input to text
+ formatters or for automatic translation to a variety of formats
+ suitable for input to text formatters. A copy made in an otherwise
+ Transparent file format whose markup, or absence of markup, has
+ been arranged to thwart or discourage subsequent modification by
+ readers is not Transparent. An image format is not Transparent if
+ used for any substantial amount of text. A copy that is not
+ "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format,
- SGML or XML using a publicly available DTD, and
- standard-conforming simple HTML, PostScript or PDF designed for
- human modification. Examples of transparent image formats include
- PNG, XCF and JPG. Opaque formats include proprietary formats that
- can be read and edited only by proprietary word processors, SGML or
- XML for which the DTD and/or processing tools are not generally
- available, and the machine-generated HTML, PostScript or PDF
- produced by some word processors for output purposes only.
+ SGML or XML using a publicly available DTD, and standard-conforming
+ simple HTML, PostScript or PDF designed for human modification.
+ Examples of transparent image formats include PNG, XCF and JPG.
+ Opaque formats include proprietary formats that can be read and
+ edited only by proprietary word processors, SGML or XML for which
+ the DTD and/or processing tools are not generally available, and
+ the machine-generated HTML, PostScript or PDF produced by some word
+ processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the
@@ -1708,8 +1672,8 @@
may not use technical measures to obstruct or control the reading
or further copying of the copies you make or distribute. However,
you may accept compensation in exchange for copies. If you
- distribute a large enough number of copies you must also follow
- the conditions in section 3.
+ distribute a large enough number of copies you must also follow the
+ conditions in section 3.
You may also lend copies, under the same conditions stated above,
and you may publicly display copies.
@@ -1723,12 +1687,11 @@
these Cover Texts: Front-Cover Texts on the front cover, and
Back-Cover Texts on the back cover. Both covers must also clearly
and legibly identify you as the publisher of these copies. The
- front cover must present the full title with all words of the
- title equally prominent and visible. You may add other material
- on the covers in addition. Copying with changes limited to the
- covers, as long as they preserve the title of the Document and
- satisfy these conditions, can be treated as verbatim copying in
- other respects.
+ front cover must present the full title with all words of the title
+ equally prominent and visible. You may add other material on the
+ covers in addition. Copying with changes limited to the covers, as
+ long as they preserve the title of the Document and satisfy these
+ conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
@@ -1736,40 +1699,39 @@
adjacent pages.
If you publish or distribute Opaque copies of the Document
- numbering more than 100, you must either include a
- machine-readable Transparent copy along with each Opaque copy, or
- state in or with each Opaque copy a computer-network location from
- which the general network-using public has access to download
- using public-standard network protocols a complete Transparent
- copy of the Document, free of added material. If you use the
- latter option, you must take reasonably prudent steps, when you
- begin distribution of Opaque copies in quantity, to ensure that
- this Transparent copy will remain thus accessible at the stated
- location until at least one year after the last time you
- distribute an Opaque copy (directly or through your agents or
- retailers) of that edition to the public.
+ numbering more than 100, you must either include a machine-readable
+ Transparent copy along with each Opaque copy, or state in or with
+ each Opaque copy a computer-network location from which the general
+ network-using public has access to download using public-standard
+ network protocols a complete Transparent copy of the Document, free
+ of added material. If you use the latter option, you must take
+ reasonably prudent steps, when you begin distribution of Opaque
+ copies in quantity, to ensure that this Transparent copy will
+ remain thus accessible at the stated location until at least one
+ year after the last time you distribute an Opaque copy (directly or
+ through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of
- the Document well before redistributing any large number of
- copies, to give them a chance to provide you with an updated
- version of the Document.
+ the Document well before redistributing any large number of copies,
+ to give them a chance to provide you with an updated version of the
+ Document.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you
- release the Modified Version under precisely this License, with
- the Modified Version filling the role of the Document, thus
- licensing distribution and modification of the Modified Version to
- whoever possesses a copy of it. In addition, you must do these
- things in the Modified Version:
+ release the Modified Version under precisely this License, with the
+ Modified Version filling the role of the Document, thus licensing
+ distribution and modification of the Modified Version to whoever
+ possesses a copy of it. In addition, you must do these things in
+ the Modified Version:
A. Use in the Title Page (and on the covers, if any) a title
- distinct from that of the Document, and from those of
- previous versions (which should, if there were any, be listed
- in the History section of the Document). You may use the
- same title as a previous version if the original publisher of
- that version gives permission.
+ distinct from that of the Document, and from those of previous
+ versions (which should, if there were any, be listed in the
+ History section of the Document). You may use the same title
+ as a previous version if the original publisher of that
+ version gives permission.
B. List on the Title Page, as authors, one or more persons or
entities responsible for authorship of the modifications in
@@ -1799,31 +1761,30 @@
I. Preserve the section Entitled "History", Preserve its Title,
and add to it an item stating at least the title, year, new
- authors, and publisher of the Modified Version as given on
- the Title Page. If there is no section Entitled "History" in
- the Document, create one stating the title, year, authors,
- and publisher of the Document as given on its Title Page,
- then add an item describing the Modified Version as stated in
- the previous sentence.
+ authors, and publisher of the Modified Version as given on the
+ Title Page. If there is no section Entitled "History" in the
+ Document, create one stating the title, year, authors, and
+ publisher of the Document as given on its Title Page, then add
+ an item describing the Modified Version as stated in the
+ previous sentence.
J. Preserve the network location, if any, given in the Document
for public access to a Transparent copy of the Document, and
likewise the network locations given in the Document for
- previous versions it was based on. These may be placed in
- the "History" section. You may omit a network location for a
- work that was published at least four years before the
- Document itself, or if the original publisher of the version
- it refers to gives permission.
+ previous versions it was based on. These may be placed in the
+ "History" section. You may omit a network location for a work
+ that was published at least four years before the Document
+ itself, or if the original publisher of the version it refers
+ to gives permission.
K. For any section Entitled "Acknowledgements" or "Dedications",
- Preserve the Title of the section, and preserve in the
- section all the substance and tone of each of the contributor
+ Preserve the Title of the section, and preserve in the section
+ all the substance and tone of each of the contributor
acknowledgements and/or dedications given therein.
- L. Preserve all the Invariant Sections of the Document,
- unaltered in their text and in their titles. Section numbers
- or the equivalent are not considered part of the section
- titles.
+ L. Preserve all the Invariant Sections of the Document, unaltered
+ in their text and in their titles. Section numbers or the
+ equivalent are not considered part of the section titles.
M. Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
@@ -1836,11 +1797,11 @@
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no
- material copied from the Document, you may at your option
- designate some or all of these sections as invariant. To do this,
- add their titles to the list of Invariant Sections in the Modified
- Version's license notice. These titles must be distinct from any
- other section titles.
+ material copied from the Document, you may at your option designate
+ some or all of these sections as invariant. To do this, add their
+ titles to the list of Invariant Sections in the Modified Version's
+ license notice. These titles must be distinct from any other
+ section titles.
You may add a section Entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
@@ -1849,15 +1810,15 @@
definition of a standard.
You may add a passage of up to five words as a Front-Cover Text,
- and a passage of up to 25 words as a Back-Cover Text, to the end
- of the list of Cover Texts in the Modified Version. Only one
- passage of Front-Cover Text and one of Back-Cover Text may be
- added by (or through arrangements made by) any one entity. If the
- Document already includes a cover text for the same cover,
- previously added by you or by arrangement made by the same entity
- you are acting on behalf of, you may not add another; but you may
- replace the old one, on explicit permission from the previous
- publisher that added the old one.
+ and a passage of up to 25 words as a Back-Cover Text, to the end of
+ the list of Cover Texts in the Modified Version. Only one passage
+ of Front-Cover Text and one of Back-Cover Text may be added by (or
+ through arrangements made by) any one entity. If the Document
+ already includes a cover text for the same cover, previously added
+ by you or by arrangement made by the same entity you are acting on
+ behalf of, you may not add another; but you may replace the old
+ one, on explicit permission from the previous publisher that added
+ the old one.
The author(s) and publisher(s) of the Document do not by this
License give permission to use their names for publicity for or to
@@ -1867,8 +1828,8 @@
You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for
- modified versions, provided that you include in the combination
- all of the Invariant Sections of all of the original documents,
+ modified versions, provided that you include in the combination all
+ of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your
combined work in its license notice, and that you preserve all
their Warranty Disclaimers.
@@ -1895,20 +1856,20 @@
documents released under this License, and replace the individual
copies of this License in the various documents with a single copy
that is included in the collection, provided that you follow the
- rules of this License for verbatim copying of each of the
- documents in all other respects.
+ rules of this License for verbatim copying of each of the documents
+ in all other respects.
You may extract a single document from such a collection, and
distribute it individually under this License, provided you insert
- a copy of this License into the extracted document, and follow
- this License in all other respects regarding verbatim copying of
- that document.
+ a copy of this License into the extracted document, and follow this
+ License in all other respects regarding verbatim copying of that
+ document.
7. AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Document or its derivatives with other
- separate and independent documents or works, in or on a volume of
- a storage or distribution medium, is called an "aggregate" if the
+ separate and independent documents or works, in or on a volume of a
+ storage or distribution medium, is called an "aggregate" if the
copyright resulting from the compilation is not used to limit the
legal rights of the compilation's users beyond what the individual
works permit. When the Document is included in an aggregate, this
@@ -1953,8 +1914,8 @@
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
- provisionally, unless and until the copyright holder explicitly
- and finally terminates your license, and (b) permanently, if the
+ provisionally, unless and until the copyright holder explicitly and
+ finally terminates your license, and (b) permanently, if the
copyright holder fails to notify you of the violation by some
reasonable means prior to 60 days after the cessation.
@@ -1966,10 +1927,10 @@
after your receipt of the notice.
Termination of your rights under this section does not terminate
- the licenses of parties who have received copies or rights from
- you under this License. If your rights have been terminated and
- not permanently reinstated, receipt of a copy of some or all of
- the same material does not give you any rights to use it.
+ the licenses of parties who have received copies or rights from you
+ under this License. If your rights have been terminated and not
+ permanently reinstated, receipt of a copy of some or all of the
+ same material does not give you any rights to use it.
10. FUTURE REVISIONS OF THIS LICENSE
@@ -1977,18 +1938,18 @@
the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
- `http://www.gnu.org/copyleft/'.
+ <http://www.gnu.org/copyleft/>.
Each version of the License is given a distinguishing version
number. If the Document specifies that a particular numbered
version of this License "or any later version" applies to it, you
have the option of following the terms and conditions either of
that specified version or of any later version that has been
- published (not as a draft) by the Free Software Foundation. If
- the Document does not specify a version number of this License,
- you may choose any version ever published (not as a draft) by the
- Free Software Foundation. If the Document specifies that a proxy
- can decide which future versions of this License can be used, that
+ published (not as a draft) by the Free Software Foundation. If the
+ Document does not specify a version number of this License, you may
+ choose any version ever published (not as a draft) by the Free
+ Software Foundation. If the Document specifies that a proxy can
+ decide which future versions of this License can be used, that
proxy's public statement of acceptance of a version permanently
authorizes you to choose that version for the Document.
@@ -2022,7 +1983,6 @@
site under CC-BY-SA on the same site at any time before August 1,
2009, provided the MMC is eligible for relicensing.
-
ADDENDUM: How to use this License for your documents
====================================================
@@ -2050,7 +2010,7 @@
situation.
If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of
-free software license, such as the GNU General Public License, to
-permit their use in free software.
+recommend releasing these examples in parallel under your choice of free
+software license, such as the GNU General Public License, to permit
+their use in free software.
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.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
Binary files /tmp/cvsfzI5J9 and /tmp/cvsuQifHb 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.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/CSS.html 28 Jun 2012 21:04:21 -0000 1.9
+++ web-trans/html_node/CSS.html 4 Dec 2012 16:24:26 -0000 1.10
@@ -1,102 +1,138 @@
-<html lang="en">
-<head>
-<title>CSS - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Translation-Tips.html#Translation-Tips"
title="Translation Tips">
-<link rel="prev" href="SSI.html#SSI" title="SSI">
-<link rel="next" href="Priorities.html#Priorities" title="Priorities">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: CSS</title>
+
+<meta name="description" content="GNU Web Translators Manual: CSS">
+<meta name="keywords" content="GNU Web Translators Manual: CSS">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Translation-Tips.html#Translation-Tips" rel="up"
title="Translation Tips">
+<link href="topbanner.html#topbanner" rel="next" title="topbanner">
+<link href="SSI.html#SSI" rel="previous" title="SSI">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="CSS"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Priorities.html#Priorities">Priorities</a>,
-Previous: <a rel="previous" accesskey="p" href="SSI.html#SSI">SSI</a>,
-Up: <a rel="up" accesskey="u"
href="Translation-Tips.html#Translation-Tips">Translation Tips</a>
-<hr>
+Next: <a href="Priorities.html#Priorities" accesskey="n"
rel="next">Priorities</a>, Previous: <a href="SSI.html#SSI" accesskey="p"
rel="previous">SSI</a>, Up: <a href="Translation-Tips.html#Translation-Tips"
accesskey="u" rel="up">Translation Tips</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="How-To-Use-Custom-CSS"></a>
<h3 class="section">5.3 How To Use Custom CSS</h3>
-<p>The CSS file <samp><span class="file">layout.css</span></samp> gets
included (with three other CSS files)
+<p>The CSS file <samp>layout.css</samp> gets included (with three other CSS
files)
in almost all the English articles through
-<samp><span class="file">server/head-include-2.</span><var>lang</var><span
class="file">.html</span></samp>. However, sometimes this
-style isn't quite right for translations—many languages have much
+<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><span class="file">style.</span><var>lang</var><span
class="file">.css</span></samp> and add it <em>after</em> the
-directive to include <samp><span
class="file">server/head-include-2.</span><var>lang</var><span
class="file">.html</span></samp> and
+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><span class="file">server/banner.</span><var>lang</var><span
class="file">.html</span></samp>, i.e.
+<samp>server/banner.<var>lang</var>.html</samp>, i.e.
+</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></div>
-<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>
- <p>Override only what is necessary and looks broken in your language; do
+<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><span class="file">style.</span><var>lang</var><span
class="file">.css</span></samp> file looks like this:
-
-<pre class="example"> .inner { max-width: 65em; }
+<samp>style.<var>lang</var>.css</samp> file looks like this:
+</p>
+<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>
- #logo{background:url(/graphics/topbanner.bg.png) no-repeat;}
- #fssbox {font-size: 50%;}
-</pre>
- <p>This widens the menu and the area where the articles are displayed
+<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>When creating your own <samp><span
class="file">style.</span><var>lang</var><span class="file">.css</span></samp>,
don't forget to
-include the license notice from the <samp><span
class="file">layout.css</span></samp>, with a short
+</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>If using the default CSS style for translations does not give the
+</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="topbanner.html#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.html#RTL"
accesskey="2">RTL</a>:</td><td> </td><td align="left"
valign="top">Special notes about RTL languages.
+</td></tr>
+</table>
+
+<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>
+</div>
-<ul class="menu">
-<li><a accesskey="1" href="topbanner.html#topbanner">topbanner</a>:
How to localize the topbanner image.
-<li><a accesskey="2" href="RTL.html#RTL">RTL</a>: Special
notes about RTL languages.
-</ul>
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Capitalization.html 28 Jun 2012 21:04:21 -0000
1.8
+++ web-trans/html_node/Capitalization.html 4 Dec 2012 16:24:26 -0000
1.9
@@ -1,52 +1,74 @@
-<html lang="en">
-<head>
-<title>Capitalization - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Translation-Tips.html#Translation-Tips"
title="Translation Tips">
-<link rel="prev" href="Priorities.html#Priorities" title="Priorities">
-<link rel="next" href="Distribution-Terms.html#Distribution-Terms"
title="Distribution Terms">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Capitalization</title>
+
+<meta name="description" content="GNU Web Translators Manual: Capitalization">
+<meta name="keywords" content="GNU Web Translators Manual: Capitalization">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Translation-Tips.html#Translation-Tips" rel="up"
title="Translation Tips">
+<link href="Distribution-Terms.html#Distribution-Terms" rel="next"
title="Distribution Terms">
+<link href="Priorities.html#Priorities" rel="previous" title="Priorities">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Capitalization"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Distribution-Terms.html#Distribution-Terms">Distribution Terms</a>,
-Previous: <a rel="previous" accesskey="p"
href="Priorities.html#Priorities">Priorities</a>,
-Up: <a rel="up" accesskey="u"
href="Translation-Tips.html#Translation-Tips">Translation Tips</a>
-<hr>
+Next: <a href="Distribution-Terms.html#Distribution-Terms" accesskey="n"
rel="next">Distribution Terms</a>, Previous: <a
href="Priorities.html#Priorities" accesskey="p" rel="previous">Priorities</a>,
Up: <a href="Translation-Tips.html#Translation-Tips" accesskey="u"
rel="up">Translation Tips</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="When-To-CAPITALIZE"></a>
<h3 class="section">5.5 When To CAPITALIZE</h3>
<p>The English language has some rules for capitalization of titles,
@@ -55,20 +77,23 @@
consistently. They do not make sense for many other languages, but
unfortunately, many translators <em>erroneously duplicate</em> the
capitalization in their translation.
-
- <p>Examples for common (and correct) English capitalization is the title of
+</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´c
+rules it is wrong to write “Dlaczego Oprogramowanie Powinno Być
Wolne” (Polish) or “Fondation Pour Le Logiciel Libre”
(French).
-
- <p>Another prominent and widely spread mistake is to write your own
+</p>
+<p>Another prominent and widely spread mistake is to write your own
language with a capital letter in the <code>translations-list</code> when
languages are written beginning with a small letter according to your
-own rules. In other words, it is right to write ‘<samp><span
class="samp">English</span></samp>’ or
-‘<samp><span class="samp">Deutsch</span></samp>’ (because in
English and German languages are
-capitalized), but not ‘<samp><span
class="samp">Français</span></samp>’ or ‘<samp><span
class="samp">Português</span></samp>’—write
-them as ‘<samp><span class="samp">français</span></samp>’
or ‘<samp><span class="samp">português</span></samp>’,
respectively.
+own rules. In other words, it is right to write
‘<samp>English</samp>’ or
+‘<samp>Deutsch</samp>’ (because in English and German languages are
+capitalized), but not ‘<samp>Français</samp>’ or
‘<samp>Português</samp>’—write
+them as ‘<samp>français</samp>’ or
‘<samp>português</samp>’, respectively.
+</p>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Co_002dleaders.html 28 Jun 2012 21:04:21 -0000
1.8
+++ web-trans/html_node/Co_002dleaders.html 4 Dec 2012 16:24:26 -0000
1.9
@@ -1,72 +1,98 @@
-<html lang="en">
-<head>
-<title>Co-leaders - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Managing.html#Managing" title="Managing">
-<link rel="prev" href="Savannah.html#Savannah" title="Savannah">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Co-leaders</title>
+
+<meta name="description" content="GNU Web Translators Manual: Co-leaders">
+<meta name="keywords" content="GNU Web Translators Manual: Co-leaders">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Managing.html#Managing" rel="up" title="Managing">
+<link href="Reports.html#Reports" rel="next" title="Reports">
+<link href="Savannah-VCS.html#Savannah-VCS" rel="previous" title="Savannah
VCS">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
-<a name="Co-leaders"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Co_002dleaders"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="Savannah.html#Savannah">Savannah</a>,
-Up: <a rel="up" accesskey="u" href="Managing.html#Managing">Managing</a>
-<hr>
+Previous: <a href="Savannah.html#Savannah" accesskey="p"
rel="previous">Savannah</a>, Up: <a href="Managing.html#Managing" accesskey="u"
rel="up">Managing</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="Promoting-Members-As-Co_002dleaders"></a>
<h4 class="subsection">3.2.4 Promoting Members As Co-leaders</h4>
<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
to help. Note that a subsequently appointed team co-ordinator is not
-simply a <dfn>committer</dfn> with write access to the ‘<samp><span
class="samp">www</span></samp>’ repository;
+simply a <em>committer</em> with write access to the
‘<samp>www</samp>’ repository;
she has full responsibilities just like a single leader, although the
latter still remains the primary contact for the team.
-
- <p>If you'd like another person to act as a co-leader and help you with the
+</p>
+<p>If you’d like another person to act as a co-leader and help you with
the
management tasks, send a message to <a
href="mailto:address@hidden";>address@hidden</a>
with her name and Savannah account. She has to be already a member of
-‘<samp><span class="samp">www-</span><var>lang</var></samp>’.
-
- <p>The procedure for co-leaders is a simplified version of the one for a
+‘<samp>www-<var>lang</var></samp>’.
+</p>
+<p>The procedure for co-leaders is a simplified version of the one for a
new team or taking over an existing team. See <a
href="New-Team.html#New-Team">New Team</a>.
-
- <p>To remove co-ordinators, please write to
+</p>
+<p>To remove co-ordinators, please write to
<a href="mailto:address@hidden";>address@hidden</a> with details and rationale
for the
-removal. Do not edit <samp><span
class="file">README.translations.html</span></samp> yourself; this is
+removal. Do not edit <samp>README.translations.html</samp> yourself; this is
a final formality step to be performed by the Translation Managers.
+</p>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Commits.html 28 Jun 2012 21:04:21 -0000 1.8
+++ web-trans/html_node/Commits.html 4 Dec 2012 16:24:26 -0000 1.9
@@ -1,136 +1,178 @@
-<html lang="en">
-<head>
-<title>Commits - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Managing.html#Managing" title="Managing">
-<link rel="prev" href="Review.html#Review" title="Review">
-<link rel="next" href="Savannah.html#Savannah" title="Savannah">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Commits</title>
+
+<meta name="description" content="GNU Web Translators Manual: Commits">
+<meta name="keywords" content="GNU Web Translators Manual: Commits">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Managing.html#Managing" rel="up" title="Managing">
+<link href="Savannah.html#Savannah" rel="next" title="Savannah">
+<link href="Unreviewed-Translations.html#Unreviewed-Translations"
rel="previous" title="Unreviewed Translations">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Commits"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Savannah.html#Savannah">Savannah</a>,
-Previous: <a rel="previous" accesskey="p"
href="Review.html#Review">Review</a>,
-Up: <a rel="up" accesskey="u" href="Managing.html#Managing">Managing</a>
-<hr>
+Next: <a href="Savannah.html#Savannah" accesskey="n" rel="next">Savannah</a>,
Previous: <a href="Review.html#Review" accesskey="p" rel="previous">Review</a>,
Up: <a href="Managing.html#Managing" accesskey="u" rel="up">Managing</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="CVS-Commits-And-Best-Practices"></a>
<h4 class="subsection">3.2.2 CVS Commits And Best Practices</h4>
<p>As all team leaders have write access to the CVS repository of the
-‘<samp><span class="samp">www</span></samp>’ project, this
technically means that they are able to modify
-every single file in it, and also those of the Web CVS repositories of
-other projects at Savannah. This vote of confidence should never be
+‘<samp>www</samp>’ project, this technically means that they are
able to modify
+every single file in it. This vote of confidence should never be
abused—the only files team co-ordinators should add/update are those
relevant to their translation work. It is OK to fix an obvious typo in
an original article; for anything else please report to
<a href="mailto:address@hidden";>address@hidden</a>.
-
- <p>If you wish to volunteer as webmaster and help with generic webmaster
+</p>
+<p>If you wish to volunteer as webmaster and help with generic webmaster
work and RT tickets, that is perfectly fine—please follow the
established (by the GNU Webmasters) procedure. If you are approved, you
-can modify such pages wearing your “webmaster's hat”.
-
- <p>If a particular page has issues with the markup which create problems
+can modify such pages wearing your “webmaster’s hat”.
+</p>
+<p>If a particular page has issues with the markup which create problems
for your language, please inform <a
href="mailto:address@hidden";>address@hidden</a>.
For general issues that affect more articles, or for severe problems,
please write to <a href="mailto:address@hidden";>address@hidden</a>.
-
- <p>It is recommended to read the entire CVS manual at least once, for a
-basic understanding of how this VCS works. See <a
href="../cvs/index.html#Top">Concurrent Versions System</a>. It is not
-necessary to become an expert—the ‘<samp><span
class="samp">www</span></samp>’ project does not use
+</p>
+<p>It is recommended to read the entire CVS manual at least once, for a
+basic understanding of how this VCS works. See <a
href="../cvs/index.html#Top">Concurrent
+Versions System</a> in <cite>Version Management with CVS</cite>. It is not
+necessary to become an expert—the ‘<samp>www</samp>’ project
does not use
complex features like tags, vendor branches, merging, etc. as they are
not very useful for a live website.
-
- <p>However, you'd probably have to learn how to use CVS for effective
+</p>
+<p>However, you’d probably have to learn how to use CVS for effective
work—to extract information from the history, review diffs and
specific changes, synchronize with the working repository of the team
(if any), adding/removing files, etc.
-
- <p>If you make changes that affect more than one file but the change is
+</p>
+<p>If you make changes that affect more than one file but the change is
coherent, please do it as a single commit. This will generate only one
message to <a href="mailto:address@hidden";>address@hidden</a>, which is better
than 5 messages
for 5 files about semantically the same change. Always write commit
-logs in English<a rel="footnote" href="#fn-1" name="fnd-1"><sup>1</sup></a>,
providing a short
+logs in English<a name="DOCF4" href="#FOOT4"><sup>4</sup></a>, providing a
short
description of the change. If you modify a file that is not an article
-but a script or part of software (such as <samp><span
class="file">server/gnun/gnun.mk</span></samp>),
+but a script or part of software (such as <samp>server/gnun/gnun.mk</samp>),
it would be nice to follow the GNU Coding Standards and describe the
-change precisely. For example, do not write:
+change precisely. See <a
href="http://www.gnu.org/prep/standards/html_node/Change-Logs.html#Change-Logs";>Change
Logs</a> in <cite>The GNU Coding Standards</cite>. For example, do not write:
+</p>
+<div class="example">
+<pre class="example">Added support for Nepali.
+</pre></div>
+
+<p>or
+</p>
+<div class="example">
+<pre class="example">Yay! First commit of the Panjabi homepage!
+</pre></div>
+
+<p>Instead, write the log as follows:
+</p>
+<div class="example">
+<pre class="example">(TEMPLATE_LINGUAS): Add `ne'.
+</pre></div>
+
+<p>and
+</p>
+<div class="example">
+<pre class="example">(FUZZY_DIFF_LINGUAS): Add `pa'.
+</pre></div>
-<pre class="example"> Added support for Nepali.
-</pre>
- <p>or
-
-<pre class="example"> Yay! First commit of the Panjabi homepage!
-</pre>
- <p>Instead, write the log as follows:
-
-<pre class="example"> (TEMPLATE_LINGUAS): Add `ne'.
-</pre>
- <p>and
-
-<pre class="example"> (HOME_LINGUAS): Add `pa'.
-</pre>
- <p>This makes it easier for others to search for a particular change in the
+<p>This makes it easier for others to search for a particular change in the
history.
-
- <p>If you add a binary file (for example, <samp><span
class="file">.png</span></samp>), do it with
-<code>cvs commit -kb </code><var>file</var>. This turns off keyword
substitution,
-which prevents RCS keywords like ‘<samp><span class="samp">$<!-- /@w
-->Id$</span></samp>’ to get expanded,
-subsequently corrupting the file. See <a
href="../cvs/Substitution-Modes.html#Substitution-Modes">Substitution
Modes</a>. More importantly, using <samp><span class="option">-kb</span></samp>
+</p>
+<p>If you add a binary file (for example, <samp>.png</samp>), do it with
+<code>cvs commit -kb <var>file</var></code>. This turns off keyword
substitution,
+which prevents RCS keywords like ‘<samp>$<!-- /@w -->Id$</samp>’
to get expanded,
+subsequently corrupting the file. See <a
href="../cvs/Substitution-Modes.html#Substitution-Modes">Substitution Modes</a>
in <cite>Version Management with CVS</cite>. More importantly, using
<samp>-kb</samp>
prevents corruption of the binary when people using CVS clients under
-Windoze checkout, modify the file, and then commit it with messed EOLs.
-(Unfortunately there are still committers using non-free operating
-systems—we cannot dictate what OS people use, but we can at least try
-to prevent damage.)
-
- <p>Although not absolutely compulsory, it is recommended that every team
+infamous OS checkout, modify the file, and then commit it with
+messed ends of lines.<a name="DOCF5" href="#FOOT5"><sup>5</sup></a>
+</p>
+<p>Although not absolutely compulsory, it is recommended that every team
leader subscribes to <a href="mailto:address@hidden";>address@hidden</a>. It
is useful to
examine the diffs of your own messages, if you miss something while
inspecting the diff before the commit. In any case, a team leader
should be subscribed to that list to avoid his own commit messages to be
moderated. If you absolutely do not desire receiving all traffic, just
-disable mail delivery in Mailman's user interface.
-
- <div class="footnote">
+disable mail delivery in Mailman’s user interface.
+</p>
+<div class="footnote">
<hr>
-<h4>Footnotes</h4><p class="footnote"><small>[<a name="fn-1"
href="#fnd-1">1</a>]</small> This advice is applicable for the
‘<samp><span class="samp">www</span></samp>’
+<h4 class="footnotes-heading">Footnotes</h4>
+
+<h3><a name="FOOT4" href="#DOCF4">(4)</a></h3>
+<p>This advice is applicable for the ‘<samp>www</samp>’
repository only—feel free to write logs in your native language when
-committing in your project's Sources repository.</p>
+committing in your team’s repositories.</p>
+<h3><a name="FOOT5" href="#DOCF5">(5)</a></h3>
+<p>Few years ago there still were
+committers using nonfree operating systems—we don’t dictate what
+OS people use, but we can at least prevent this technical kind
+of damage.</p>
+</div>
+<hr>
+<div class="header">
+<p>
+Next: <a href="Savannah.html#Savannah" accesskey="n" rel="next">Savannah</a>,
Previous: <a href="Review.html#Review" accesskey="p" rel="previous">Review</a>,
Up: <a href="Managing.html#Managing" accesskey="u" rel="up">Managing</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
+</div>
- <hr></div>
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Copying-This-Manual.html 28 Jun 2012 21:04:21
-0000 1.8
+++ web-trans/html_node/Copying-This-Manual.html 4 Dec 2012 16:24:26
-0000 1.9
@@ -1,89 +1,113 @@
-<html lang="en">
-<head>
-<title>Copying This Manual - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Summary.html#Summary" title="Summary">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Copying This Manual</title>
+
+<meta name="description" content="GNU Web Translators Manual: Copying This
Manual">
+<meta name="keywords" content="GNU Web Translators Manual: Copying This
Manual">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Savannah-Projects.html#Savannah-Projects" rel="previous"
title="Savannah Projects">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Copying-This-Manual"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="Summary.html#Summary">Summary</a>,
-Up: <a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+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>
</div>
-
+<hr>
+<a name="GNU-Free-Documentation-License"></a>
<h2 class="appendix">Appendix A GNU Free Documentation License</h2>
-<!-- The GNU Free Documentation License. -->
-<div align="center">Version 1.3, 3 November 2008</div>
+<div align="center">Version 1.3, 3 November 2008
+</div>
+
+<div class="display">
+<pre class="display">Copyright © 2000, 2001, 2002, 2007, 2008 Free
Software Foundation, Inc.
+<a href="http://fsf.org/";>http://fsf.org/</a>
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+</pre></div>
-<!-- This file is intended to be included within another document, -->
-<!-- hence no sectioning command or @node. -->
-<pre class="display"> Copyright © 2000, 2001, 2002, 2007, 2008 Free
Software Foundation, Inc.
- <a href="http://fsf.org/";>http://fsf.org/</a>
-
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-</pre>
- <ol type=1 start=0>
-<li>PREAMBLE
+<ol>
+<li> PREAMBLE
- <p>The purpose of this License is to make a manual, textbook, or other
-functional and useful document <dfn>free</dfn> in the sense of freedom: to
+<p>The purpose of this License is to make a manual, textbook, or other
+functional and useful document <em>free</em> in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher a way
to get credit for their work, while not being considered responsible
for modifications made by others.
-
- <p>This License is a kind of “copyleft”, which means that
derivative
+</p>
+<p>This License is a kind of “copyleft”, which means that
derivative
works of the document must themselves be free in the same sense. It
complements the GNU General Public License, which is a copyleft
license designed for free software.
-
- <p>We have designed this License in order to use it for manuals for free
+</p>
+<p>We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free
program should come with manuals providing the same freedoms that the
software does. But this License is not limited to software manuals;
it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
+</p>
+</li><li> APPLICABILITY AND DEFINITIONS
- <li>APPLICABILITY AND DEFINITIONS
-
- <p>This License applies to any manual or other work, in any medium, that
+<p>This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
@@ -92,14 +116,14 @@
licensee, and is addressed as “you”. You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.
-
- <p>A “Modified Version” of the Document means any work
containing the
+</p>
+<p>A “Modified Version” of the Document means any work containing
the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
-
- <p>A “Secondary Section” is a named appendix or a
front-matter section
+</p>
+<p>A “Secondary Section” is a named appendix or a front-matter
section
of the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document's overall
+publishers or authors of the Document to the Document’s overall
subject (or to related matters) and contains nothing that could fall
directly within that overall subject. (Thus, if the Document is in
part a textbook of mathematics, a Secondary Section may not explain
@@ -107,21 +131,21 @@
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
-
- <p>The “Invariant Sections” are certain Secondary Sections
whose titles
+</p>
+<p>The “Invariant Sections” are certain Secondary Sections whose
titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.
-
- <p>The “Cover Texts” are certain short passages of text that
are listed,
+</p>
+<p>The “Cover Texts” are certain short passages of text that are
listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.
-
- <p>A “Transparent” copy of the Document means a
machine-readable copy,
+</p>
+<p>A “Transparent” copy of the Document means a machine-readable
copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
@@ -133,9 +157,9 @@
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
of text. A copy that is not “Transparent” is called
“Opaque”.
-
- <p>Examples of suitable formats for Transparent copies include plain
-<span class="sc">ascii</span> without markup, Texinfo input format, LaTeX input
+</p>
+<p>Examples of suitable formats for Transparent copies include plain
+<small>ASCII</small> without markup, Texinfo input format, LaTeX input
format, <acronym>SGML</acronym> or <acronym>XML</acronym> using a publicly
available
<acronym>DTD</acronym>, and standard-conforming simple <acronym>HTML</acronym>,
PostScript or <acronym>PDF</acronym> designed for human modification. Examples
@@ -146,35 +170,35 @@
not generally available, and the machine-generated <acronym>HTML</acronym>,
PostScript or <acronym>PDF</acronym> produced by some word processors for
output purposes only.
-
- <p>The “Title Page” means, for a printed book, the title page
itself,
+</p>
+<p>The “Title Page” means, for a printed book, the title page
itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, “Title Page”
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work’s title,
preceding the beginning of the body of the text.
-
- <p>The “publisher” means any person or entity that
distributes copies
+</p>
+<p>The “publisher” means any person or entity that distributes
copies
of the Document to the public.
-
- <p>A section “Entitled XYZ” means a named subunit of the
Document whose
+</p>
+<p>A section “Entitled XYZ” means a named subunit of the Document
whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
specific section name mentioned below, such as “Acknowledgements”,
“Dedications”, “Endorsements”, or
“History”.) To “Preserve the Title”
of such a section when you modify the Document means that it remains a
section “Entitled XYZ” according to this definition.
-
- <p>The Document may include Warranty Disclaimers next to the notice which
+</p>
+<p>The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document. These Warranty
Disclaimers are considered to be included by reference in this
License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
+</p>
+</li><li> VERBATIM COPYING
- <li>VERBATIM COPYING
-
- <p>You may copy and distribute the Document in any medium, either
+<p>You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies
to the Document are reproduced in all copies, and that you add no other
@@ -183,15 +207,15 @@
copying of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough
number of copies you must also follow the conditions in section 3.
-
- <p>You may also lend copies, under the same conditions stated above, and
+</p>
+<p>You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
+</p>
+</li><li> COPYING IN QUANTITY
- <li>COPYING IN QUANTITY
-
- <p>If you publish printed copies (or copies in media that commonly have
+<p>If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
-Document's license notice requires Cover Texts, you must enclose the
+Document’s license notice requires Cover Texts, you must enclose the
copies in covers that carry, clearly and legibly, all these Cover
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
the back cover. Both covers must also clearly and legibly identify
@@ -201,13 +225,13 @@
Copying with changes limited to the covers, as long as they preserve
the title of the Document and satisfy these conditions, can be treated
as verbatim copying in other respects.
-
- <p>If the required texts for either cover are too voluminous to fit
+</p>
+<p>If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto adjacent
pages.
-
- <p>If you publish or distribute Opaque copies of the Document numbering
+</p>
+<p>If you publish or distribute Opaque copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy
a computer-network location from which the general network-using
@@ -219,51 +243,51 @@
location until at least one year after the last time you distribute an
Opaque copy (directly or through your agents or retailers) of that
edition to the public.
-
- <p>It is requested, but not required, that you contact the authors of the
+</p>
+<p>It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
+</p>
+</li><li> MODIFICATIONS
- <li>MODIFICATIONS
-
- <p>You may copy and distribute a Modified Version of the Document under
+<p>You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
the Modified Version under precisely this License, with the Modified
Version filling the role of the Document, thus licensing distribution
and modification of the Modified Version to whoever possesses a copy
of it. In addition, you must do these things in the Modified Version:
-
- <ol type=A start=1>
-<li>Use in the Title Page (and on the covers, if any) a title distinct
+</p>
+<ol>
+<li> Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions
(which should, if there were any, be listed in the History section
of the Document). You may use the same title as a previous version
if the original publisher of that version gives permission.
- <li>List on the Title Page, as authors, one or more persons or
entities
+</li><li> List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.
- <li>State on the Title page the name of the publisher of the
+</li><li> State on the Title page the name of the publisher of the
Modified Version, as the publisher.
- <li>Preserve all the copyright notices of the Document.
+</li><li> Preserve all the copyright notices of the Document.
- <li>Add an appropriate copyright notice for your modifications
+</li><li> Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
- <li>Include, immediately after the copyright notices, a license
notice
+</li><li> Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.
- <li>Preserve in that license notice the full lists of Invariant
Sections
-and required Cover Texts given in the Document's license notice.
+</li><li> Preserve in that license notice the full lists of Invariant Sections
+and required Cover Texts given in the Document’s license notice.
- <li>Include an unaltered copy of this License.
+</li><li> Include an unaltered copy of this License.
- <li>Preserve the section Entitled “History”, Preserve
its Title, and add
+</li><li> Preserve the section Entitled “History”, Preserve its
Title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page. If
there is no section Entitled “History” in the Document, create one
@@ -271,7 +295,7 @@
given on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.
- <li>Preserve the network location, if any, given in the Document for
+</li><li> Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the “History” section.
@@ -279,38 +303,38 @@
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
- <li>For any section Entitled “Acknowledgements” or
“Dedications”, Preserve
+</li><li> For any section Entitled “Acknowledgements” or
“Dedications”, Preserve
the Title of the section, and preserve in the section all the
substance and tone of each of the contributor acknowledgements and/or
dedications given therein.
- <li>Preserve all the Invariant Sections of the Document,
+</li><li> Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles. Section numbers
or the equivalent are not considered part of the section titles.
- <li>Delete any section Entitled “Endorsements”. Such a
section
+</li><li> Delete any section Entitled “Endorsements”. Such a
section
may not be included in the Modified Version.
- <li>Do not retitle any existing section to be Entitled
“Endorsements” or
+</li><li> Do not retitle any existing section to be Entitled
“Endorsements” or
to conflict in title with any Invariant Section.
- <li>Preserve any Warranty Disclaimers.
- </ol>
+</li><li> Preserve any Warranty Disclaimers.
+</li></ol>
- <p>If the Modified Version includes new front-matter sections or
+<p>If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no material
copied from the Document, you may at your option designate some or all
of these sections as invariant. To do this, add their titles to the
-list of Invariant Sections in the Modified Version's license notice.
+list of Invariant Sections in the Modified Version’s license notice.
These titles must be distinct from any other section titles.
-
- <p>You may add a section Entitled “Endorsements”, provided it
contains
+</p>
+<p>You may add a section Entitled “Endorsements”, provided it
contains
nothing but endorsements of your Modified Version by various
parties—for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a
standard.
-
- <p>You may add a passage of up to five words as a Front-Cover Text, and a
+</p>
+<p>You may add a passage of up to five words as a Front-Cover Text, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version. Only one passage of
Front-Cover Text and one of Back-Cover Text may be added by (or
@@ -319,21 +343,21 @@
by arrangement made by the same entity you are acting on behalf of,
you may not add another; but you may replace the old one, on explicit
permission from the previous publisher that added the old one.
-
- <p>The author(s) and publisher(s) of the Document do not by this License
+</p>
+<p>The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
+</p>
+</li><li> COMBINING DOCUMENTS
- <li>COMBINING DOCUMENTS
-
- <p>You may combine the Document with other documents released under this
+<p>You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its
license notice, and that you preserve all their Warranty Disclaimers.
-
- <p>The combined work need only contain one copy of this License, and
+</p>
+<p>The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by
@@ -341,48 +365,48 @@
author or publisher of that section if known, or else a unique number.
Make the same adjustment to the section titles in the list of
Invariant Sections in the license notice of the combined work.
-
- <p>In the combination, you must combine any sections Entitled
“History”
+</p>
+<p>In the combination, you must combine any sections Entitled
“History”
in the various original documents, forming one section Entitled
“History”; likewise combine any sections Entitled
“Acknowledgements”,
and any sections Entitled “Dedications”. You must delete all
sections Entitled “Endorsements.”
+</p>
+</li><li> COLLECTIONS OF DOCUMENTS
- <li>COLLECTIONS OF DOCUMENTS
-
- <p>You may make a collection consisting of the Document and other
documents
+<p>You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
License in the various documents with a single copy that is included in
the collection, provided that you follow the rules of this License for
verbatim copying of each of the documents in all other respects.
-
- <p>You may extract a single document from such a collection, and
distribute
+</p>
+<p>You may extract a single document from such a collection, and distribute
it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
+</p>
+</li><li> AGGREGATION WITH INDEPENDENT WORKS
- <li>AGGREGATION WITH INDEPENDENT WORKS
-
- <p>A compilation of the Document or its derivatives with other separate
+<p>A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, is called an “aggregate” if the copyright
resulting from the compilation is not used to limit the legal rights
-of the compilation's users beyond what the individual works permit.
+of the compilation’s users beyond what the individual works permit.
When the Document is included in an aggregate, this License does not
apply to the other works in the aggregate which are not themselves
derivative works of the Document.
-
- <p>If the Cover Text requirement of section 3 is applicable to these
+</p>
+<p>If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half of
-the entire aggregate, the Document's Cover Texts may be placed on
+the entire aggregate, the Document’s Cover Texts may be placed on
covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.
+</p>
+</li><li> TRANSLATION
- <li>TRANSLATION
-
- <p>Translation is considered a kind of modification, so you may
+<p>Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
@@ -394,48 +418,48 @@
of those notices and disclaimers. In case of a disagreement between
the translation and the original version of this License or a notice
or disclaimer, the original version will prevail.
-
- <p>If a section in the Document is Entitled
“Acknowledgements”,
+</p>
+<p>If a section in the Document is Entitled “Acknowledgements”,
“Dedications”, or “History”, the requirement (section
4) to Preserve
its Title (section 1) will typically require changing the actual
title.
+</p>
+</li><li> TERMINATION
- <li>TERMINATION
-
- <p>You may not copy, modify, sublicense, or distribute the Document
+<p>You may not copy, modify, sublicense, or distribute the Document
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense, or distribute it is void, and
will automatically terminate your rights under this License.
-
- <p>However, if you cease all violation of this License, then your license
+</p>
+<p>However, if you cease all violation of this License, then your license
from a particular copyright holder is reinstated (a) provisionally,
unless and until the copyright holder explicitly and finally
terminates your license, and (b) permanently, if the copyright holder
fails to notify you of the violation by some reasonable means prior to
60 days after the cessation.
-
- <p>Moreover, your license from a particular copyright holder is
+</p>
+<p>Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
-
- <p>Termination of your rights under this section does not terminate the
+</p>
+<p>Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, receipt of a copy of some or all of the same material does
not give you any rights to use it.
+</p>
+</li><li> FUTURE REVISIONS OF THIS LICENSE
- <li>FUTURE REVISIONS OF THIS LICENSE
-
- <p>The Free Software Foundation may publish new, revised versions
+<p>The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
<a href="http://www.gnu.org/copyleft/";>http://www.gnu.org/copyleft/</a>.
-
- <p>Each version of the License is given a distinguishing version number.
+</p>
+<p>Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
License “or any later version” applies to it, you have the option
of
following the terms and conditions either of that specified version or
@@ -444,47 +468,49 @@
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation. If the Document
specifies that a proxy can decide which future versions of this
-License can be used, that proxy's public statement of acceptance of a
+License can be used, that proxy’s public statement of acceptance of a
version permanently authorizes you to choose that version for the
Document.
+</p>
+</li><li> RELICENSING
- <li>RELICENSING
-
- <p>“Massive Multiauthor Collaboration Site” (or “MMC
Site”) means any
+<p>“Massive Multiauthor Collaboration Site” (or “MMC
Site”) means any
World Wide Web server that publishes copyrightable works and also
provides prominent facilities for anybody to edit those works. A
public wiki that anybody can edit is an example of such a server. A
“Massive Multiauthor Collaboration” (or “MMC”)
contained in the
site means any set of copyrightable works thus published on the MMC
site.
-
- <p>“CC-BY-SA” means the Creative Commons Attribution-Share
Alike 3.0
+</p>
+<p>“CC-BY-SA” means the Creative Commons Attribution-Share Alike
3.0
license published by Creative Commons Corporation, a not-for-profit
corporation with a principal place of business in San Francisco,
California, as well as future copyleft versions of that license
published by that same organization.
-
- <p>“Incorporate” means to publish or republish a Document, in
whole or
+</p>
+<p>“Incorporate” means to publish or republish a Document, in
whole or
in part, as part of another Document.
-
- <p>An MMC is “eligible for relicensing” if it is licensed
under this
+</p>
+<p>An MMC is “eligible for relicensing” if it is licensed under
this
License, and if all works that were first published under this License
somewhere other than this MMC, and subsequently incorporated in whole
or in part into the MMC, (1) had no cover texts or invariant sections,
and (2) were thus incorporated prior to November 1, 2008.
-
- <p>The operator of an MMC Site may republish an MMC contained in the site
+</p>
+<p>The operator of an MMC Site may republish an MMC contained in the site
under CC-BY-SA on the same site at any time before August 1, 2009,
provided the MMC is eligible for relicensing.
+</p>
+</li></ol>
- </ol>
-
+<a name="ADDENDUM_003a-How-to-use-this-License-for-your-documents"></a>
<h3 class="heading">ADDENDUM: How to use this License for your documents</h3>
<p>To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
license notices just after the title page:
-
+</p>
+<div class="smallexample">
<pre class="smallexample"> Copyright (C) <var>year</var> <var>your
name</var>.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
@@ -492,25 +518,36 @@
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is included in the section entitled ``GNU
Free Documentation License''.
-</pre>
- <p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
-replace the “with<small class="dots">...</small>Texts.” line with
this:
+</pre></div>
+<p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the “with…Texts.” line with this:
+</p>
+<div class="smallexample">
<pre class="smallexample"> with the Invariant Sections being <var>list
their titles</var>, with
the Front-Cover Texts being <var>list</var>, and with the Back-Cover
Texts
being <var>list</var>.
-</pre>
- <p>If you have Invariant Sections without Cover Texts, or some other
+</pre></div>
+
+<p>If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.
-
- <p>If your document contains nontrivial examples of program code, we
+</p>
+<p>If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License,
to permit their use in free software.
+</p>
+
+
+
+<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>
+</div>
+
-<!-- Local Variables: -->
-<!-- ispell-local-pdict: "ispell-dict" -->
-<!-- End: -->
-</body></html>
+</body>
+</html>
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.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- web-trans/html_node/Distribution-Terms.html 28 Jun 2012 21:04:21 -0000
1.4
+++ web-trans/html_node/Distribution-Terms.html 4 Dec 2012 16:24:26 -0000
1.5
@@ -1,106 +1,140 @@
-<html lang="en">
-<head>
-<title>Distribution Terms - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Translation-Tips.html#Translation-Tips"
title="Translation Tips">
-<link rel="prev" href="Capitalization.html#Capitalization"
title="Capitalization">
-<link rel="next" href="Terminology.html#Terminology" title="Terminology">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Distribution Terms</title>
+
+<meta name="description" content="GNU Web Translators Manual: Distribution
Terms">
+<meta name="keywords" content="GNU Web Translators Manual: Distribution Terms">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Translation-Tips.html#Translation-Tips" rel="up"
title="Translation Tips">
+<link href="Terminology.html#Terminology" rel="next" title="Terminology">
+<link href="Capitalization.html#Capitalization" rel="previous"
title="Capitalization">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Distribution-Terms"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Terminology.html#Terminology">Terminology</a>,
-Previous: <a rel="previous" accesskey="p"
href="Capitalization.html#Capitalization">Capitalization</a>,
-Up: <a rel="up" accesskey="u"
href="Translation-Tips.html#Translation-Tips">Translation Tips</a>
-<hr>
+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>
</div>
-
+<hr>
+<a name="Distribution-Terms-1"></a>
<h3 class="section">5.6 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.
The exact HTML for English pages to use is:
+</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>
-<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>
- <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
+<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:
-
- <ul>
-<li>Check at the bottom of the English deed page to see the list of
+</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>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> 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>The textarea on that page provides standard HTML. Note that we're not
+</li><li> The textarea on that page provides standard HTML. Note that
we’re not
using the graphic, just the text.
- </ul>
+</li></ul>
- <p>For example, here's the text they provide for Dutch:
+<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>
-<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>
- <p>Note that the link in this text is changed to point directly to the
+<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>Pages in languages that aren't supported by CC should prepare their own
+deed that’s in the same language as the page itself.
+</p>
+<p>Pages in languages that aren’t supported by CC should prepare their
own
translation, use it consistently throughout pages translated to that
language, and link to the English language deed. Also, please
write your own translation when the translation provided by CC is
not satisfactory for some reasons—for instance, as of May, 2012, their
German translation uses “Content”, which is a word to use with
caution
(see <a
href="http://www.gnu.org/philosophy/words-to-avoid.en.html#Content";>http://www.gnu.org/philosophy/words-to-avoid.en.html#Content</a>).
-
- <p>Note that translations should <em>not</em> change the jurisdiction of the
+</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.
+</p>
+<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>
+</div>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Introduction.html 28 Jun 2012 21:04:21 -0000
1.8
+++ web-trans/html_node/Introduction.html 4 Dec 2012 16:24:26 -0000
1.9
@@ -1,60 +1,83 @@
-<html lang="en">
-<head>
-<title>Introduction - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="index.html#Top" title="Top">
-<link rel="next" href="Members.html#Members" title="Members">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Introduction</title>
+
+<meta name="description" content="GNU Web Translators Manual: Introduction">
+<meta name="keywords" content="GNU Web Translators Manual: Introduction">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Members.html#Members" rel="next" title="Members">
+<link href="index.html#Top" rel="previous" title="Top">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Introduction"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="Members.html#Members">Members</a>,
-Previous: <a rel="previous" accesskey="p" href="index.html#Top">Top</a>,
-Up: <a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Members.html#Members" accesskey="n" rel="next">Members</a>,
Previous: <a href="index.html#Top" accesskey="p" rel="previous">Top</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="Introduction-1"></a>
<h2 class="chapter">1 Introduction</h2>
<p>This manual is an attempt to describe in detail the process of
translating www.gnu.org articles—how to join a team, or start a new
one, the responsibilities of the team members and leaders, as well as
-some peculiarities of the GNU Project's website when it comes to
+some peculiarities of the GNU Project’s website when it comes to
localization.
-
- <p>The GNU website contains hundreds of documents, most of them
+</p>
+<p>The GNU website contains hundreds of documents, most of them
philosophical articles (essays) and technical documents which need to be
translated to make them available to a broader audience. This is
especially important for the philosophy-related materials, as many
@@ -63,14 +86,14 @@
translating a website this large is a hard job, and too often people
volunteering as translators get frustrated or lose interest in keeping
up with that work. Reading this manual, and the related GNUN manual
-(see <a href="../gnun/index.html#Top">GNUnited Nations</a>), is
+(see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/index.html#Top";>GNUnited
Nations</a> in <cite>The GNUnited Nations Manual</cite>), is
just the tip of the iceberg. This is not meant to discourage any
potential volunteer; rather, we prefer to be honest and to give
preliminary estimation of the work/responsibility involved—if you feel
you are not in a position to help you may move on to a smaller project
before going through all procedures.
-
- <p>It is important to realize that being a GNU Web Translator is a hard job
+</p>
+<p>It is important to realize that being a GNU Web Translator is a hard job
at all levels, but your help is much appreciated and is invaluable
contribution to the society. While there are many people who contribute
to our community by writing free software (and their number is
@@ -79,21 +102,30 @@
rather unfortunately, there are not so many volunteers willing to
maintain on the long term translations of the various essays that
describe the fundamental values of the free software movement.
-
- <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, who are
+</p>
+<p>Translators of the <a href="http://gnu.org";>http://gnu.org</a> website are
organized in
+language teams. Each team has one or more co-ordinators (a.k.a
+leaders), who are
responsible for the respective team. The co-ordinators participate in
-the Savannah ‘<samp><span class="samp">trans-coord</span></samp>’
organizational project, which is managed
+the Savannah ‘<samp>trans-coord</samp>’ organizational project,
which is managed
by the GNU Web Translation Managers. The manual is organized in
chapters that follow the organizational structure of the whole
translation project.
-
- <p>If you wish to join a translation team or contribute a translation or
+</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><span class="samp">trans-coord</span></samp>’
-administrators (a.k.a. <dfn>GNU Translation Managers</dfn>) describes all the
+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>.
+</p>
+<hr>
+<div class="header">
+<p>
+Next: <a href="Members.html#Members" accesskey="n" rel="next">Members</a>,
Previous: <a href="index.html#Top" accesskey="p" rel="previous">Top</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>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Joining.html 28 Jun 2012 21:04:21 -0000 1.8
+++ web-trans/html_node/Joining.html 4 Dec 2012 16:24:26 -0000 1.9
@@ -1,103 +1,135 @@
-<html lang="en">
-<head>
-<title>Joining - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Members.html#Members" title="Members">
-<link rel="next" href="Submitting.html#Submitting" title="Submitting">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Joining</title>
+
+<meta name="description" content="GNU Web Translators Manual: Joining">
+<meta name="keywords" content="GNU Web Translators Manual: Joining">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Members.html#Members" rel="up" title="Members">
+<link href="Submitting.html#Submitting" rel="next" title="Submitting">
+<link href="Members.html#Members" rel="previous" title="Members">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Joining"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Submitting.html#Submitting">Submitting</a>,
-Up: <a rel="up" accesskey="u" href="Members.html#Members">Members</a>
-<hr>
+Next: <a href="Submitting.html#Submitting" accesskey="n"
rel="next">Submitting</a>, Up: <a href="Members.html#Members" accesskey="u"
rel="up">Members</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="Joining-A-Team"></a>
<h3 class="section">2.1 Joining A Team</h3>
<p>To join a team, please first look at the existing teams at
<a
href="http://www.gnu.org/server/standards/README.translations.html#TranslationsUnderway";>http://www.gnu.org/server/standards/README.translations.html#TranslationsUnderway</a>.
Chances are that there is already an established team. If there is no
team listed for your language, this means that:
-
- <ul>
-<li>There is no team established and there are no translations to this
+</p>
+<ul>
+<li> There is no team established and there are no translations to this
language.
- <li>Some translations were submitted by occasional contributors, but no
team
+</li><li> Some translations were submitted by occasional contributors, but no
team
has ever been formed.
- <li>The page is not updated to reflect the current situation (this
shouldn't
-happen, but it's a possibility anyway).
-</ul>
+</li><li> The page is not updated to reflect the current situation (this
shouldn’t
+happen, but it’s a possibility anyway).
+</li></ul>
- <p>If the team is marked as <dfn>orphaned</dfn>, there is no problem: you
can
+<p>If the team is marked as <em>orphaned</em>, there is no problem: you can
still submit your translation to <a
href="mailto:address@hidden";>address@hidden</a>
(see <a href="Submitting.html#Submitting">Submitting</a>). In case you want
to establish a new translation
team or become a co-ordinator of an existing one, please refer to the
next chapter, see <a href="Leaders.html#Leaders">Leaders</a>.
-
- <p>Contacting the team is best done via Savannah—each translation team
-has its own project, named ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’, with the project
+</p>
+<p>Contacting the team is best done via Savannah—each translation team
+has its own project, named ‘<samp>www-<var>lang</var></samp>’,
with the project
page being
-<<code>https://savannah.gnu.org/projects/www-</code><var>lang</var>>.
-Usually teams have mailing lists, typically in the form
-<a href="mailto:www-<var>lang</var>address@hidden">www-<var>lang</var>-<small
class="dots">...</small>@gnu.org</a>. Some teams have homepages,
-<<code>http://gnu.org/server/standards/translations/</code><var>lang</var>>
+‘<code>https://savannah.gnu.org/projects/www-<var>lang</var></code>’.
+All teams should have mailing lists, typically in the form
+<a
href="mailto:www-lang-…@gnu.org";>www-<var>lang</var>-…@gnu.org</a>.
Some teams have homepages,
+‘<code>http://gnu.org/server/standards/translations/<var>lang</var></code>’
with additional contact details and procedures for team members.
-
- <p>You could also write directly to the team leader via the Savannah
+</p>
+<p>You could also write directly to the team leader via the Savannah
interface—that way your request will be recorded by Savannah and can be
tracked or completed when the membership is approved.
-
- <p>The actual process of submitting translations for review varies from
+</p>
+<p>The actual process of submitting translations for review varies from
team to team, as teams have certain liberties to organize themselves as
they see fit. Thus, this manual does not make any attempt to cover that
aspect—please refer to the team-specific documentation (if any) or ask
the co-ordinator.
-
- <p>Certainly, it is not mandatory to be an active team member to contribute
-a translation or two. If you feel that you don't have the time to
+</p>
+<p>Certainly, it is not mandatory to be an active team member to contribute
+a translation or two. If you feel that you don’t have the time to
participate actively, that is fine; you can still send your translation
to the team. No contributions should be rejected.
-
- <p>If you do not hear from the team within a reasonable time frame (say,
+</p>
+<p>If you do not hear from the team within a reasonable time frame (say,
two weeks), please write to <a href="mailto:address@hidden";>address@hidden</a>.
-
- <p>For general information about the translation process,
+</p>
+<p>For general information about the translation process,
see <a href="Translation-Tips.html#Translation-Tips">Translation Tips</a>.
+</p>
+<hr>
+<div class="header">
+<p>
+Next: <a href="Submitting.html#Submitting" accesskey="n"
rel="next">Submitting</a>, Up: <a href="Members.html#Members" accesskey="u"
rel="up">Members</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
+</div>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Leaders.html 28 Jun 2012 21:04:21 -0000 1.8
+++ web-trans/html_node/Leaders.html 4 Dec 2012 16:24:26 -0000 1.9
@@ -1,74 +1,104 @@
-<html lang="en">
-<head>
-<title>Leaders - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Members.html#Members" title="Members">
-<link rel="next" href="Translation-Managers.html#Translation-Managers"
title="Translation Managers">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Leaders</title>
+
+<meta name="description" content="GNU Web Translators Manual: Leaders">
+<meta name="keywords" content="GNU Web Translators Manual: Leaders">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="New-Team.html#New-Team" rel="next" title="New Team">
+<link href="Leaving-A-Team.html#Leaving-A-Team" rel="previous" title="Leaving
A Team">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Leaders"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Translation-Managers.html#Translation-Managers">Translation Managers</a>,
-Previous: <a rel="previous" accesskey="p"
href="Members.html#Members">Members</a>,
-Up: <a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+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>
</div>
-
+<hr>
+<a name="Team-Co_002dordinators"></a>
<h2 class="chapter">3 Team Co-ordinators</h2>
<p>A gnu.org translation team leader is the person who is ultimately
responsible for organizing and managing the team, including, but not
limited to, having the final say on contributed translations and
exercising levels of control as she sees fit.
-
- <p>A prospective team co-ordinator should have perfect understanding of the
+</p>
+<p>A prospective team co-ordinator should have perfect understanding of the
GNU Philosophy and the various issues the free software movement set out
to solve. Energy and time are always needed, as well as certain
communication skills.
-
- <p>However, a team leader is not a dictator (for life); every action and/or
+</p>
+<p>However, a team leader is not a dictator (for life); every action and/or
decision taken should have its justification and should stem from the
goals of the project at large. Inefficient or inoperative leaders are
replaced, if necessary.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="New-Team.html#New-Team"
accesskey="1">New Team</a>:</td><td> </td><td align="left"
valign="top">Procedures to establish a new team.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="Managing.html#Managing"
accesskey="2">Managing</a>:</td><td> </td><td align="left"
valign="top">General guidelines how to manage a team.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="Reports.html#Reports"
accesskey="3">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="4">Stepping
Down</a>:</td><td> </td><td align="left" valign="top">Orphaning the
team and finding a replacement.
+</td></tr>
+</table>
+
-<ul class="menu">
-<li><a accesskey="1" href="New-Team.html#New-Team">New Team</a>:
Procedures to establish a new team.
-<li><a accesskey="2" href="Managing.html#Managing">Managing</a>:
General guidelines how to manage a team.
-<li><a accesskey="3" href="Reports.html#Reports">Reports</a>:
Reporting team status and activity.
-<li><a accesskey="4" href="Stepping-Down.html#Stepping-Down">Stepping
Down</a>: Orphaning the team and finding a replacement.
-</ul>
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Leaving-A-Team.html 28 Jun 2012 21:04:21 -0000
1.8
+++ web-trans/html_node/Leaving-A-Team.html 4 Dec 2012 16:24:26 -0000
1.9
@@ -1,59 +1,86 @@
-<html lang="en">
-<head>
-<title>Leaving A Team - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Members.html#Members" title="Members">
-<link rel="prev" href="Submitting.html#Submitting" title="Submitting">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Leaving A Team</title>
+
+<meta name="description" content="GNU Web Translators Manual: Leaving A Team">
+<meta name="keywords" content="GNU Web Translators Manual: Leaving A Team">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Members.html#Members" rel="up" title="Members">
+<link href="Leaders.html#Leaders" rel="next" title="Leaders">
+<link href="Submitting-as-Plain-Text.html#Submitting-as-Plain-Text"
rel="previous" title="Submitting as Plain Text">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Leaving-A-Team"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="Submitting.html#Submitting">Submitting</a>,
-Up: <a rel="up" accesskey="u" href="Members.html#Members">Members</a>
-<hr>
+Previous: <a href="Submitting.html#Submitting" accesskey="p"
rel="previous">Submitting</a>, Up: <a href="Members.html#Members" accesskey="u"
rel="up">Members</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="Leaving-A-Team-1"></a>
<h3 class="section">2.3 Leaving A Team</h3>
-<p>When you realize that you don't have time or can't devote sufficient
+<p>When you realize that you don’t have time or can’t devote
sufficient
resources to perform the tasks anymore, it is prudent to inform the
translation team co-ordinator and possibly all the rest of the
team-mates. The team leader should always have a rough estimation about
the available translators, even though there are no reliable means to
establish that. Your announcement that you are stepping down
(temporarily or permanently) may help her in this regard.
+</p>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Mailing-Lists.html 28 Jun 2012 21:04:21 -0000
1.8
+++ web-trans/html_node/Mailing-Lists.html 4 Dec 2012 16:24:26 -0000
1.9
@@ -1,107 +1,141 @@
-<html lang="en">
-<head>
-<title>Mailing Lists - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Summary.html#Summary" title="Summary">
-<link rel="next" href="Savannah-Projects.html#Savannah-Projects"
title="Savannah Projects">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Mailing Lists</title>
+
+<meta name="description" content="GNU Web Translators Manual: Mailing Lists">
+<meta name="keywords" content="GNU Web Translators Manual: Mailing Lists">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Summary.html#Summary" rel="up" title="Summary">
+<link href="Savannah-Projects.html#Savannah-Projects" rel="next"
title="Savannah Projects">
+<link href="Summary.html#Summary" rel="previous" title="Summary">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Mailing-Lists"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Savannah-Projects.html#Savannah-Projects">Savannah Projects</a>,
-Up: <a rel="up" accesskey="u" href="Summary.html#Summary">Summary</a>
-<hr>
+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>
</div>
-
+<hr>
+<a name="Related-Mailing-Lists"></a>
<h3 class="section">6.1 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
participants in the process.
-
- <dl>
-<dt><a href="mailto:address@hidden";>address@hidden</a><dd>The basic discussion
list of the GNU Webmasters. All team leaders are
+</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>This is a private mailing list.
-
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>Commits to
the ‘<samp><span class="samp">www</span></samp>’ repository are
sent here. All Translation
+</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>This is a public mailing list, so everyone can subscribe and review the
-archives. The ‘<samp><span class="samp">www</span></samp>’ CVS
repository is also public.
-
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>The main
discussion list for the GNU Web Translators. Team leaders must
+</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>This is a private mailing list.
-
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>This is a
list for notifications about gnunews and GNUnited Nations
+</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><span class="samp">gnun</span></samp>’
topic via Mailman's user interface.
-Likewise, if you want to receive only <dfn>What's New</dfn> updates,
-subscribe to the ‘<samp><span class="samp">whatsnew</span></samp>’
topic.
-
- <p>Automatic announcements for new gnu.org translations (provided they're
+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><span class="samp">-ann</span></samp>’
topics for every GNUN-aware language, so it is a
+‘<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><span
class="samp">es-ann</span></samp>’
+Spanish translations, she can just subscribe to the
‘<samp>es-ann</samp>’
mailing list topic.
-
- <p>This is a public mailing list.
-
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>All
development of GNUN happens here. Commits to the ‘<samp><span
class="samp">trans-coord</span></samp>’
+</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>This is a public list, and <a
href="mailto:address@hidden";>address@hidden</a> is an alias.
-
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>All build
logs from the various GNUN automatic builds are sent to this
-list, so it is not a very pleasant thing to be subscribed, especially if
-you are not interested in GNUN's internals. However, everyone can use
-the web archives to check the log why a particular article was not built
-at expected.
+<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>
+</div>
- <p>This is a public list.
-</dl>
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Managing.html 28 Jun 2012 21:04:21 -0000 1.8
+++ web-trans/html_node/Managing.html 4 Dec 2012 16:24:26 -0000 1.9
@@ -1,56 +1,78 @@
-<html lang="en">
-<head>
-<title>Managing - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Leaders.html#Leaders" title="Leaders">
-<link rel="prev" href="New-Team.html#New-Team" title="New Team">
-<link rel="next" href="Reports.html#Reports" title="Reports">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Managing</title>
+
+<meta name="description" content="GNU Web Translators Manual: Managing">
+<meta name="keywords" content="GNU Web Translators Manual: Managing">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Leaders.html#Leaders" rel="up" title="Leaders">
+<link href="Review.html#Review" rel="next" title="Review">
+<link href="New-Team.html#New-Team" rel="previous" title="New Team">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Managing"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="Reports.html#Reports">Reports</a>,
-Previous: <a rel="previous" accesskey="p"
href="New-Team.html#New-Team">New Team</a>,
-Up: <a rel="up" accesskey="u" href="Leaders.html#Leaders">Leaders</a>
-<hr>
+Next: <a href="Reports.html#Reports" accesskey="n" rel="next">Reports</a>,
Previous: <a href="New-Team.html#New-Team" accesskey="p" rel="previous">New
Team</a>, Up: <a href="Leaders.html#Leaders" accesskey="u" rel="up">Leaders</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="The-Gentle-Art-of-Managing-A-Translation-Team"></a>
<h3 class="section">3.2 The Gentle Art of Managing A Translation Team</h3>
<p>It is not our ambition to describe all activities involved in managing a
-team—it's very likely that you will encounter new problems, take care
+team—it’s very likely that you will encounter new problems, take
care
of tasks nobody else is aware of, or invent new techniques and
approaches in your quest to keep things running. Managing a team is a
hard task on all counts: communication with others, recruiting
@@ -58,22 +80,29 @@
decisions, leading discussions about terminology issues, handling
personal conflicts within the team, technical skills when
reviewing/merging/syncing translations, etc. The list goes on and on.
-
- <p>This manual can only summarize some of the most common issues and
+</p>
+<p>This manual can only summarize some of the most common issues and
<em>suggest</em> ways to deal with them. It is up to the team leader to
establish the precise team procedures and practices.
-
- <p>The <a href="mailto:address@hidden";>address@hidden</a> mailing list was
specifically
+</p>
+<p>The <a href="mailto:address@hidden";>address@hidden</a> mailing list was
specifically
created to discuss issues that leaders encounter while managing the
teams, and for general organizational work. Feel free to discuss
anything related to the translation process there.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="Review.html#Review"
accesskey="1">Review</a>:</td><td> </td><td align="left"
valign="top">The importance of peer review.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="Commits.html#Commits"
accesskey="2">Commits</a>:</td><td> </td><td align="left"
valign="top">What to modify, and how.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="Savannah.html#Savannah"
accesskey="3">Savannah</a>:</td><td> </td><td align="left"
valign="top">Using Savannah resources.
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Co_002dleaders.html#Co_002dleaders"
accesskey="4">Co-leaders</a>:</td><td> </td><td align="left"
valign="top">Promoting co-leaders, when necessary.
+</td></tr>
+</table>
+
-<ul class="menu">
-<li><a accesskey="1" href="Review.html#Review">Review</a>: The
importance of peer review.
-<li><a accesskey="2" href="Commits.html#Commits">Commits</a>:
What to modify, and how.
-<li><a accesskey="3" href="Savannah.html#Savannah">Savannah</a>:
Using Savannah resources.
-<li><a accesskey="4" href="Co_002dleaders.html#Co_002dleaders">Co-leaders</a>:
Promoting co-leaders, when necessary.
-</ul>
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Members.html 28 Jun 2012 21:04:21 -0000 1.8
+++ web-trans/html_node/Members.html 4 Dec 2012 16:24:26 -0000 1.9
@@ -1,64 +1,93 @@
-<html lang="en">
-<head>
-<title>Members - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Introduction.html#Introduction" title="Introduction">
-<link rel="next" href="Leaders.html#Leaders" title="Leaders">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Members</title>
+
+<meta name="description" content="GNU Web Translators Manual: Members">
+<meta name="keywords" content="GNU Web Translators Manual: Members">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Joining.html#Joining" rel="next" title="Joining">
+<link href="Introduction.html#Introduction" rel="previous"
title="Introduction">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Members"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="Leaders.html#Leaders">Leaders</a>,
-Previous: <a rel="previous" accesskey="p"
href="Introduction.html#Introduction">Introduction</a>,
-Up: <a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Leaders.html#Leaders" accesskey="n" rel="next">Leaders</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>]</p>
</div>
-
+<hr>
+<a name="Team-Members"></a>
<h2 class="chapter">2 Team Members</h2>
<p>Being a team member means to co-operate with a group of other people,
working under the co-ordinatorship of the appointed team leader.
Usually, this involves translating articles and reviewing/proof-reading
-other people's translations, participating in discussions about
+other people’s translations, participating in discussions about
terminology issues, and sometimes performing clean-up tasks.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="Joining.html#Joining"
accesskey="1">Joining</a>:</td><td> </td><td align="left"
valign="top">How to join a translation team.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="Submitting.html#Submitting"
accesskey="2">Submitting</a>:</td><td> </td><td align="left"
valign="top">Submitting a translation when there is no team.
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Leaving-A-Team.html#Leaving-A-Team" accesskey="3">Leaving A
Team</a>:</td><td> </td><td align="left" valign="top">Leave when you
have to.
+</td></tr>
+</table>
+
-<ul class="menu">
-<li><a accesskey="1" href="Joining.html#Joining">Joining</a>: How
to join a translation team.
-<li><a accesskey="2" href="Submitting.html#Submitting">Submitting</a>:
Submitting a translation when there is no team.
-<li><a accesskey="3" href="Leaving-A-Team.html#Leaving-A-Team">Leaving A
Team</a>: Leave when you have to.
-</ul>
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Migrating.html 28 Jun 2012 21:04:21 -0000 1.8
+++ web-trans/html_node/Migrating.html 4 Dec 2012 16:24:27 -0000 1.9
@@ -1,62 +1,89 @@
-<html lang="en">
-<head>
-<title>Migrating - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Translation-Tips.html#Translation-Tips"
title="Translation Tips">
-<link rel="next" href="SSI.html#SSI" title="SSI">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Migrating</title>
+
+<meta name="description" content="GNU Web Translators Manual: Migrating">
+<meta name="keywords" content="GNU Web Translators Manual: Migrating">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Translation-Tips.html#Translation-Tips" rel="up"
title="Translation Tips">
+<link href="SSI.html#SSI" rel="next" title="SSI">
+<link href="Translation-Tips.html#Translation-Tips" rel="previous"
title="Translation Tips">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Migrating"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="SSI.html#SSI">SSI</a>,
-Up: <a rel="up" accesskey="u"
href="Translation-Tips.html#Translation-Tips">Translation Tips</a>
-<hr>
+Next: <a href="SSI.html#SSI" accesskey="n" rel="next">SSI</a>, Up: <a
href="Translation-Tips.html#Translation-Tips" accesskey="u"
rel="up">Translation Tips</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="Migration-To-The-New-Style"></a>
<h3 class="section">5.1 Migration To The New Style</h3>
<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="../gnun/Migrating.html#Migrating">Migrating</a>.
+translations, see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/Migrating.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>Subsequent migrations to newer HTML standards and newer look and feel
+</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>
+
- </body></html>
+</body>
+</html>
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.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/New-Team.html 29 Sep 2012 06:53:49 -0000 1.9
+++ web-trans/html_node/New-Team.html 4 Dec 2012 16:24:27 -0000 1.10
@@ -1,50 +1,74 @@
-<html lang="en">
-<head>
-<title>New Team - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Leaders.html#Leaders" title="Leaders">
-<link rel="next" href="Managing.html#Managing" title="Managing">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: New Team</title>
+
+<meta name="description" content="GNU Web Translators Manual: New Team">
+<meta name="keywords" content="GNU Web Translators Manual: New Team">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Leaders.html#Leaders" rel="up" title="Leaders">
+<link href="Managing.html#Managing" rel="next" title="Managing">
+<link href="Leaders.html#Leaders" rel="previous" title="Leaders">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="New-Team"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Managing.html#Managing">Managing</a>,
-Up: <a rel="up" accesskey="u" href="Leaders.html#Leaders">Leaders</a>
-<hr>
+Next: <a href="Managing.html#Managing" accesskey="n" rel="next">Managing</a>,
Up: <a href="Leaders.html#Leaders" accesskey="u" rel="up">Leaders</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="How-To-Form-A-New-Team"></a>
<h3 class="section">3.1 How To Form A New Team</h3>
<p>Establishing a new team is not hard, but a certain procedure ought to be
@@ -52,10 +76,10 @@
a long-term engagement that requires a lot of spare time, communication
and technical skills, and devotion. The only “bonus” team leaders
have is more work and more responsibilities.
-
- <p>You should read and <em>all</em> the documentation related to the
-translation process at the very least all important philosophy-related
-articles listed on
+</p>
+<p>You should read <em>all</em> the documentation related to the
+translation process and at the very least all important
+philosophy-related articles listed on
<a
href="http://gnu.org/server/standards/README.translations.html";>http://gnu.org/server/standards/README.translations.html</a>
and
<a
href="http://gnu.org/server/standards/translations/priorities.html";>http://gnu.org/server/standards/translations/priorities.html</a>
@@ -63,163 +87,176 @@
Once you have the internal feeling that having a gnu.org translation
team for your language is a must, and you are the one for this job,
follow these steps:
-
- <ol type=1 start=1>
-<li>If you do not have a Savannah account, register at
+</p>
+<ol>
+<li> If you do not have a Savannah account, register at
<a
href="https://savannah.gnu.org/account/register.php";>https://savannah.gnu.org/account/register.php</a>.
Write access
to the repository and project membership is handled via Savannah, so you
would need an account in any case.
- <li>Checkout a complete working copy of the CVS Web repository as
described
+</li><li> Checkout a complete working copy of the CVS Web repository as
described
at <a
href="https://savannah.gnu.org/cvs/?group=www";>https://savannah.gnu.org/cvs/?group=www</a>.
If you still
-don't have a Savannah account or if you have registered one, but are not
+don’t have a Savannah account or if you have registered one, but are not
yet member of any Savannah project, refer to the instructions under
“Anonymous CVS Access”. If you are already a member of (any)
Savannah
project, you can proceed with “Project Member CVS Access via SSH”,
although you will still lack permission to commit (later, when it is
granted, you can use the same working copy).
- <p>Examine the layout and structure of the repository. Basically, it is
+<p>Examine the layout and structure of the repository. Basically, it is
mapped to the URL locations, more or less. Take a look at the most
-important materials to translate under <samp><span
class="file">/philosophy</span></samp>, <samp><span
class="file">/gnu</span></samp>,
-<samp><span class="file">/distros</span></samp>, <samp><span
class="file">/copyleft</span></samp> and <samp><span
class="file">/licenses</span></samp> directories just
-to get a rough estimate about the amount of work involved. If you are
+important materials to translate under <samp>/philosophy</samp>,
<samp>/gnu</samp>,
+<samp>/distros</samp>, <samp>/copyleft</samp> and <samp>/licenses</samp>
directories just
+to get a rough estimate about the amount of work involved<a name="DOCF2"
href="#FOOT2"><sup>2</sup></a>. If you are
still not scared and determined to go on further, excellent.
-
- <p>As you have probably observed, every directory that contains
-translatable articles has a <samp><span class="file">/po</span></samp>
sub-directory, which is where the
+</p>
+<p>As you have probably observed, every directory that contains
+translatable articles has a <samp>/po</samp> sub-directory, which is where the
canonical source format of the translations is stored.
-
- <li>Submit your first message stating that you would like to establish a
new
+</p>
+</li><li> Submit your first message stating that you would like to establish a
new
team to <a href="mailto:address@hidden";>address@hidden</a>; please mention
that you have
read all the documentation and list the issues that remain unclear for
you. The Translation Managers will answer your questions and send you
the standard questionnaire for new team leaders. It is short and
-shouldn't take more than 10–30 minutes to complete. This questionnaire
+shouldn’t take more than 10–30 minutes to complete. This
questionnaire
is important, as we consider it crucial for any translation team
co-ordinator to have a good understanding of the philosophy of the free
software movement.
- <li>Check if your language code is
+</li><li> Check if your language code is
present in the variable <code>TEMPLATE_LINGUAS</code> at
-<samp><span class="file">server/gnun/gnun.mk</span></samp>. If it is not, the
first thing to do is to
+<samp>server/gnun/gnun.mk</samp>. If it is not, the first thing to do is to
translate and submit to <a href="mailto:address@hidden";>address@hidden</a> the
following
-files (all in the <samp><span class="file">server/po/</span></samp> directory):
-<samp><span class="file">head-include-2.</span><var>lang</var><span
class="file">.po</span></samp>,
-<samp><span class="file">body-include-1.</span><var>lang</var><span
class="file">.po</span></samp>,
-<samp><span class="file">body-include-2.</span><var>lang</var><span
class="file">.po</span></samp>
-<samp><span class="file">footer-text.</span><var>lang</var><span
class="file">.po</span></samp>,
-<samp><span class="file">outdated.</span><var>lang</var><span
class="file">.po</span></samp>,
-<samp><span class="file">skip-translations.</span><var>lang</var><span
class="file">.po</span></samp>,
-and <samp><span class="file">top-addendum.</span><var>lang</var><span
class="file">.po</span></samp>.
-See <a href="../gnun/New-Translation.html#New-Translation">New Translation</a>.
-
- <ul>
-<li>The language code (<var>lang</var>) should be the ISO 639-1 code of the
-language, for example ‘<samp><span class="samp">hy</span></samp>’
for Armenian or ‘<samp><span class="samp">el</span></samp>’ for
Greek. If
-there is no such code, use the ISO 639-2 one—e.g. ‘<samp><span
class="samp">mai</span></samp>’ for
-Maithili. If the language is a variant such as Brazilian Portuguese or
-Simplified Chinese, use small caps and a dash—‘<samp><span
class="samp">pt-br</span></samp>’ and
-‘<samp><span class="samp">zh-cn</span></samp>’ instead of
‘<samp><span class="samp">pt_BR</span></samp>’ and
‘<samp><span class="samp">zh_CN</span></samp>’.
+files (all in the <samp>server/po/</samp> directory):
+<samp>head-include-2.<var>lang</var>.po</samp>,
+<samp>body-include-1.<var>lang</var>.po</samp>,
+<samp>body-include-2.<var>lang</var>.po</samp>
+<samp>footer-text.<var>lang</var>.po</samp>,
+<samp>outdated.<var>lang</var>.po</samp>,
+<samp>skip-translations.<var>lang</var>.po</samp>,
+and <samp>top-addendum.<var>lang</var>.po</samp>.
+See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/New-Translation.html#New-Translation";>New
Translation</a> in <cite>The GNUnited Nations Manual</cite>.
+
+<ul class="no-bullet">
+<li>- The language code (<var>lang</var>) should be the ISO 639-1 code of the
+language, for example ‘<samp>hy</samp>’ for Armenian or
‘<samp>el</samp>’ for Greek. If
+the language is a variant such as Brazilian Portuguese or
+Simplified Chinese, use small caps and a
dash—‘<samp>pt-br</samp>’ and
+‘<samp>zh-cn</samp>’ instead of ‘<samp>pt_BR</samp>’
and ‘<samp>zh_CN</samp>’.
- <li>The PO file header and initial comments should be completed as
+</li><li>- The PO file header and initial comments should be completed as
documented.
- <li>Do not use HTML entities for non-ASCII characters as in the
English
+</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><span class="samp">&uuml;</span></samp>’ and this is a
character from the alphabet of your
-language, just write it as ‘<samp><span
class="samp">ü</span></samp>’ directly.
-</ul>
+‘<samp>&uuml;</samp>’ and this is a character from the
alphabet of your
+language, just write it as ‘<samp>ü</samp>’ directly.
+</li></ul>
- <li>Any prospective team leader should submit a few translations first.
+</li><li> Any prospective team leader should submit a few translations first.
This is a process of pointing errors and omissions (which are expected
-and natural); it's an important thing to do as the leader is going to
+and natural); it’s an important thing to do as the leader is going to
carry out these checks on her own, once the team is approved. If there
are existing translations that are not yet in PO format, the best thing
-to do is to migrate one or two. You can use <samp><span
class="command">find</span></samp> to find out
-what's already in the repository, for example:
+to do is to migrate one or two. You can use <code>find</code> to find out
+what’s already in the repository, for example:
+
+<div class="example">
+<pre class="example">find -name \*.<var>lang</var>.html
+</pre></div>
- <pre class="example"> find -name \*.<var>lang</var>.html
-</pre>
- <li>Submit at least two translations of your own. We maintain a list with
+</li><li> Submit at least two translations of your own. We maintain a list
with
priority articles at
<a
href="http://www.gnu.org/server/standards/translations/priorities.html";>http://www.gnu.org/server/standards/translations/priorities.html</a>,
although it is probably hard to start with one of them. Choose whatever
you wish, provided it is an essay and not an auxiliary page. Avoid
-translating the homepage or <samp><span
class="file">whatsnew.html</span></samp>—they are moving
+translating the homepage or <samp>planetfeeds.html</samp>—they are moving
targets and keeping up would be only a distraction for both parties in
the process. As usual, send the completed translation to
<a href="mailto:address@hidden";>address@hidden</a>.
- <li>The Translation Managers will review your translations, and eventually
+</li><li> The Translation Managers will review your translations, and
eventually
comment on them (mostly technical details if there is no one among them
speaking your language). Depending on the case, it might be required to
submit a corrected file. In any event, please take into account the
remarks in future work.
- <li>If all goes well, you will receive a response inviting you to apply
for
+</li><li> If all goes well, you will receive a response inviting you to apply
for
a new translation project at Savannah. The project name should be
-‘<samp><span class="samp">www-</span><var>lang</var></samp>’ where
<var>lang</var> is, unsurprisingly, the language
+‘<samp>www-<var>lang</var></samp>’ where <var>lang</var> is,
unsurprisingly, the language
code. If such a project already exists, this step will be skipped and
-you'll be made an administrator of the project. To register the
+you’ll be made an administrator of the project and its mailing lists.
+To register the
project, go to <a
href="https://savannah.gnu.org/register/";>https://savannah.gnu.org/register/</a>
and make sure
you fill in the required fields. The “Group type” should be
-‘<samp><span class="samp">www.gnu.org translation
team</span></samp>’, and “Project
-license”—‘<samp><span class="samp">WebSite
Only</span></samp>’. In the “Tarball URL” field enter a
-bogus URL such as ‘<samp><span
class="samp">http://gnu.org</span></samp>’.
+‘<samp>www.gnu.org translation team</samp>’, and “Project
+license”—‘<samp>WebSite Only</samp>’. In the
“Tarball URL” field enter a
+bogus URL such as ‘<samp>http://gnu.org</samp>’.
- <p><strong>Pay attention:</strong> This step is a formality. You should
proceed
+<p><strong>Pay attention:</strong> This step is a formality. You should
proceed
with the project registration only when you have been asked by
<a href="mailto:address@hidden";>address@hidden</a> to do so. Otherwise, the
submission
may appear in the task list of the Savannah Hackers for a fairly long
time, which is troublesome.
-
- <li>When the project is approved, the team information will be added to
the
-list at <samp><span class="file">README.translations.html</span></samp>, you
will become a member of the
-‘<samp><span class="samp">www</span></samp>’ project (thus
granting you CVS write access to the whole
-repository—so be careful) and the ‘<samp><span
class="samp">trans-coord</span></samp>’ project. You'll
+</p>
+</li><li> When the project is approved, the team information will be added to
the
+list at <samp>README.translations.html</samp>, you will become a member of the
+‘<samp>www</samp>’ project (thus granting you CVS write access to
the whole
+repository—so be careful) and the ‘<samp>trans-coord</samp>’
project. You’ll
also be subscribed to the following mailing lists:
- <ul>
-<li>www-commits
+<ul class="no-bullet">
+<li>- www-commits
- <li>trans-coord-discuss
-</ul>
+</li><li>- trans-coord-discuss
- <p>You'll have to request subscription to ‘<samp><span
class="samp">www-discuss</span></samp>’
-yourself—this list is managed by the GNU Webmasters, but all team
-leaders are required to subscribe in order to receive important
-site-wide announcements.
- </ol>
+</li><li>- www-discuss
+</li></ul>
- <p>The whole process should not take more than two weeks or maximum a
+</li></ol>
+
+<p>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
web-translators are badly lagging behind and do not process the requests
with the expected pace.
-
- <p>Applications for new teams are sometimes processed in
-parallel<a rel="footnote" href="#fn-1" name="fnd-1"><sup>1</sup></a>—the
+</p>
+<p>Applications for new teams are sometimes processed in
+parallel<a name="DOCF3" href="#FOOT3"><sup>3</sup></a>—the
most suitable candidate is chosen in this case. This is, undoubtedly,
based on a subjective judgment made by the Translation Managers, and
many factors are important.
-
- <p>The procedure for taking over an orphaned team is the same. Once
+</p>
+<p>The procedure for taking over an orphaned team is the same. Once
completed, you will be made an admin of the respective
-‘<samp><span class="samp">www-</span><var>lang</var></samp>’
Savannah project, or if it doesn't exist, invited
+‘<samp>www-<var>lang</var></samp>’ Savannah project, or if it
doesn’t exist, invited
to apply for registration. Do not automatically remove old members just
because you are starting “afresh”—some of them might want to
-continue to contribute. Contact them privately, explaining that you're
+continue to contribute. Contact them privately, explaining that you’re
the new appointed team co-ordinator, and ask them if they would be
willing to continue their involvement in the team.
-
- <div class="footnote">
+</p>
+<div class="footnote">
<hr>
-<h4>Footnotes</h4><p class="footnote"><small>[<a name="fn-1"
href="#fnd-1">1</a>]</small> In general, we try to avoid this and direct all new
+<h4 class="footnotes-heading">Footnotes</h4>
+
+<h3><a name="FOOT2" href="#DOCF2">(2)</a></h3>
+<p>As of
+December 2012, there are over 250 files to translate in “important”
+directories; their volume is about 3.5 MB.</p>
+<h3><a name="FOOT3" href="#DOCF3">(3)</a></h3>
+<p>In general, we try to avoid this and direct all new
volunteers to the person who is already carrying out the process—this
-is also a verification if she can cooperate easily with others.</p>
+is also a verification if she can co-operate easily with others.</p>
+</div>
+<hr>
+<div class="header">
+<p>
+Next: <a href="Managing.html#Managing" accesskey="n" rel="next">Managing</a>,
Up: <a href="Leaders.html#Leaders" accesskey="u" rel="up">Leaders</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
+</div>
- <hr></div>
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Priorities.html 28 Jun 2012 21:04:21 -0000 1.8
+++ web-trans/html_node/Priorities.html 4 Dec 2012 16:24:27 -0000 1.9
@@ -1,102 +1,145 @@
-<html lang="en">
-<head>
-<title>Priorities - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Translation-Tips.html#Translation-Tips"
title="Translation Tips">
-<link rel="prev" href="CSS.html#CSS" title="CSS">
-<link rel="next" href="Capitalization.html#Capitalization"
title="Capitalization">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Priorities</title>
+
+<meta name="description" content="GNU Web Translators Manual: Priorities">
+<meta name="keywords" content="GNU Web Translators Manual: Priorities">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Translation-Tips.html#Translation-Tips" rel="up"
title="Translation Tips">
+<link href="Capitalization.html#Capitalization" rel="next"
title="Capitalization">
+<link href="RTL.html#RTL" rel="previous" title="RTL">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Priorities"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Capitalization.html#Capitalization">Capitalization</a>,
-Previous: <a rel="previous" accesskey="p" href="CSS.html#CSS">CSS</a>,
-Up: <a rel="up" accesskey="u"
href="Translation-Tips.html#Translation-Tips">Translation Tips</a>
-<hr>
+Next: <a href="Capitalization.html#Capitalization" accesskey="n"
rel="next">Capitalization</a>, Previous: <a href="CSS.html#CSS" accesskey="p"
rel="previous">CSS</a>, Up: <a href="Translation-Tips.html#Translation-Tips"
accesskey="u" rel="up">Translation Tips</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="What-To-Translate"></a>
<h3 class="section">5.4 What To Translate</h3>
<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><span class="file">philosophy</span></samp>, <samp><span
class="file">gnu</span></samp>,
-<samp><span class="file">education</span></samp>, <samp><span
class="file">distros</span></samp>,
-<samp><span class="file">copyleft</span></samp> and <samp><span
class="file">licenses</span></samp> are important. The others may be
+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'
+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>It is very important to keep existing translations up-to-date with the
+</p>
+<p>It is very important to keep existing translations up-to-date with the
respective English originals. This task should be higher priority than
-translating new articles. GNUN's <code>report</code> rule can help you to
-identify precisely which articles need updating; see <a
href="../gnun/report.html#report">report</a>. There is a monthly cronjob which
+translating new articles. GNUN’s <code>report</code> rule can help you
to
+identify precisely which articles need updating; see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/report.html#report";>report</a>
in <cite>The GNUnited Nations Manual</cite>. There is a monthly cronjob which
sends a verbose output to each team—by default, the address(es) used
is the Savannah account(s) of the admin(s) of the specific translation
project. If you want them changed, please write to
<a href="mailto:address@hidden";>address@hidden</a>.
-
- <p>It is strongly recommended translation teams to attempt to recruit
+</p>
+<p>GNUN also maintains reports about current status of translations of all
+active teams in <a
href="http://www.gnu.org/software/gnun/reports/";>http://www.gnu.org/software/gnun/reports/</a>.
If
+the page for your team is missing there, please ask
+<a href="mailto:address@hidden";>address@hidden</a> to add it to the cron job.
+</p>
+<p>It is strongly recommended translation teams to attempt to recruit
native English speakers in order to improve their translation process.
Translators sometimes misunderstand English idioms and expressions, and
as a result, they translate them incorrectly or in ways that are
suboptimal and confusing. These errors are trivial to discover for the
native English speaker.
-
- <p><em>Do not</em> translate articles under these directories:
-
- <dl>
-<dt><samp><span class="file">software/</span><var>pkg</var><span
class="file">/</span></samp><dd>These pages are maintained by the respective
<var>pkg</var> maintainers.
+</p>
+<p><em>Do not</em> translate articles under these directories:
+</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.
-
- <br><dt><samp><span class="file">brave-gnu-world</span></samp><dd>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
+</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.
-
- <br><dt><samp><span class="file">home.html</span></samp><dd>There is no
problem to translate this page, but don't make the mistake
+</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.
-
- <br><dt><samp><span
class="file">server/whatsnew.html</span></samp><dd>This is “What's
New”, also known as “GNU's Flashes”, also known as
+</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.
+</p></dd>
</dl>
- </body></html>
+<hr>
+<div class="header">
+<p>
+Next: <a href="Capitalization.html#Capitalization" accesskey="n"
rel="next">Capitalization</a>, Previous: <a href="CSS.html#CSS" accesskey="p"
rel="previous">CSS</a>, Up: <a href="Translation-Tips.html#Translation-Tips"
accesskey="u" rel="up">Translation Tips</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
+</div>
+
+
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/RTL.html 28 Jun 2012 21:04:21 -0000 1.8
+++ web-trans/html_node/RTL.html 4 Dec 2012 16:24:27 -0000 1.9
@@ -1,74 +1,101 @@
-<html lang="en">
-<head>
-<title>RTL - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="CSS.html#CSS" title="CSS">
-<link rel="prev" href="topbanner.html#topbanner" title="topbanner">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: RTL</title>
+
+<meta name="description" content="GNU Web Translators Manual: RTL">
+<meta name="keywords" content="GNU Web Translators Manual: RTL">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="CSS.html#CSS" rel="up" title="CSS">
+<link href="Priorities.html#Priorities" rel="next" title="Priorities">
+<link href="topbanner.html#topbanner" rel="previous" title="topbanner">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="RTL"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="topbanner.html#topbanner">topbanner</a>,
-Up: <a rel="up" accesskey="u" href="CSS.html#CSS">CSS</a>
-<hr>
+Previous: <a href="topbanner.html#topbanner" accesskey="p"
rel="previous">topbanner</a>, Up: <a href="CSS.html#CSS" accesskey="u"
rel="up">CSS</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="Specific-Issues-Related-to-RTL"></a>
<h4 class="subsection">5.3.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
made. If your language is in this category, make sure to:
+</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>.
- <ul>
-<li>Set the attribute <code>dir="rtl"</code> in the <code>html</code> element
at
-<samp><span class="file">server/header.</span><var>lang</var><span
class="file">.html</span></samp>.
-
- <li>You <em>must</em> have a custom CSS to override some of the
pre-defined
-values. See <samp><span class="file">style.ar.css</span></samp> and
<samp><span class="file">style.fa.css</span></samp> to understand
+</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.html#CSS">CSS</a>.
-</ul>
+</li></ul>
- <p><strong>Important:</strong> Some articles contain their own
<code><style></code>
+<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
+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>
+
- </body></html>
+</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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Reports.html 28 Jun 2012 21:04:22 -0000 1.8
+++ web-trans/html_node/Reports.html 4 Dec 2012 16:24:27 -0000 1.9
@@ -1,93 +1,118 @@
-<html lang="en">
-<head>
-<title>Reports - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Leaders.html#Leaders" title="Leaders">
-<link rel="prev" href="Managing.html#Managing" title="Managing">
-<link rel="next" href="Stepping-Down.html#Stepping-Down" title="Stepping Down">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Reports</title>
+
+<meta name="description" content="GNU Web Translators Manual: Reports">
+<meta name="keywords" content="GNU Web Translators Manual: Reports">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Leaders.html#Leaders" rel="up" title="Leaders">
+<link href="Stepping-Down.html#Stepping-Down" rel="next" title="Stepping Down">
+<link href="Co_002dleaders.html#Co_002dleaders" rel="previous"
title="Co-leaders">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Reports"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Stepping-Down.html#Stepping-Down">Stepping Down</a>,
-Previous: <a rel="previous" accesskey="p"
href="Managing.html#Managing">Managing</a>,
-Up: <a rel="up" accesskey="u" href="Leaders.html#Leaders">Leaders</a>
-<hr>
+Next: <a href="Stepping-Down.html#Stepping-Down" accesskey="n"
rel="next">Stepping Down</a>, Previous: <a href="Managing.html#Managing"
accesskey="p" rel="previous">Managing</a>, Up: <a href="Leaders.html#Leaders"
accesskey="u" rel="up">Leaders</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="Reporting-Team-Status"></a>
<h3 class="section">3.3 Reporting Team Status</h3>
<p>Team leaders must send an annual report about the status of the team. A
good report should include:
-
- <ul>
-<li>General information about the team's accomplishments during the past
+</p>
+<ul>
+<li> General information about the team’s accomplishments during the past
year, like:
- <ul>
-<li>A list of new translations.
+<ul class="no-bullet">
+<li>- A list of new translations.
- <li>New members since the last report.
+</li><li>- New members since the last report.
- <li>Current active members.
+</li><li>- Current active members.
- <li>Solved problems and other issues, if any. (Usual bug reports
and other
+</li><li>- Solved problems and other issues, if any. (Usual bug reports and
other
improvements/fixes to the existing translations do not count as
-<dfn>problems</dfn> in this sense.)
-</ul>
+<em>problems</em> in this sense.)
+</li></ul>
- <li>Current problems (technical or social), conflicts, and ideas for
sorting
+</li><li> Current problems (technical or social), conflicts, and ideas for
sorting
them out.
- <li>Anything else you consider important or worth mentioning.
-</ul>
+</li><li> Anything else you consider important or worth mentioning.
+</li></ul>
- <p>The best time to send a report is near the end of the year, for example
+<p>The best time to send a report is near the end of the year, for example
November. In any case, please do not send it later than December 15th,
as the Translation Manager has to prepare a general report to the FSF,
and it is better if it takes into account the reports of the team
leaders.
-
- <p>If there is no sensitive information in the report and you feel like
+</p>
+<p>If there is no sensitive information in the report and you feel like
sharing it, you can send it to <a
href="mailto:address@hidden";>address@hidden</a>
(which is still a private mailing list). That way, other list readers
may help with suggestions how to solve a particular issue. Informing
each other about the progress improves the community spirit.
-
- <p>If you do not wish to share some information that is in the report,
+</p>
+<p>If you do not wish to share some information that is in the report,
please send it to <a href="mailto:address@hidden";>address@hidden</a>.
+</p>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Review.html 28 Jun 2012 21:04:22 -0000 1.8
+++ web-trans/html_node/Review.html 4 Dec 2012 16:24:27 -0000 1.9
@@ -1,50 +1,74 @@
-<html lang="en">
-<head>
-<title>Review - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Managing.html#Managing" title="Managing">
-<link rel="next" href="Commits.html#Commits" title="Commits">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Review</title>
+
+<meta name="description" content="GNU Web Translators Manual: Review">
+<meta name="keywords" content="GNU Web Translators Manual: Review">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Managing.html#Managing" rel="up" title="Managing">
+<link href="Tracking-Tasks.html#Tracking-Tasks" rel="next" title="Tracking
Tasks">
+<link href="Managing.html#Managing" rel="previous" title="Managing">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Review"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="Commits.html#Commits">Commits</a>,
-Up: <a rel="up" accesskey="u" href="Managing.html#Managing">Managing</a>
-<hr>
+Next: <a href="Commits.html#Commits" accesskey="n" rel="next">Commits</a>, Up:
<a href="Managing.html#Managing" accesskey="u" rel="up">Managing</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="Peer-Review"></a>
<h4 class="subsection">3.2.1 Peer Review</h4>
<p>First and foremost, find at least one person for peer review. You will
@@ -54,33 +78,43 @@
larger group) is crucial for the quality of the translation process.
Too many errors are just missed (especially if they are obvious) when
the translator does a final review of her own translation.
-
- <p>It is good to establish a practice: Do not commit officially (i.e. in
-‘<samp><span class="samp">www</span></samp>’, which will appear
online at <a href="http://gnu.org";>http://gnu.org</a>
+</p>
+<p>It is good to establish a practice: Do not commit officially (i.e. in
+‘<samp>www</samp>’, which will appear online at <a
href="http://gnu.org";>http://gnu.org</a>
immediately) a translation that is not yet reviewed by someone else who
is not the translator. Always perform a final review yourself even if
the translation has been checked by another member of the team. In
other words, every translation installed at gnu.org should pass through
your hands (read: eyes).
-
- <p>One common technique for performing such reviews is to use a mailing
+</p>
+<p>One common technique for performing such reviews is to use a mailing
list—the translator sends the new translation and participants comment
on specific parts, quoting them appropriately. The benefit of this
approach is that it is straightforward, but the drawback is that there
is no automatic “record” about the conclusion of the specific
discussion (or sub-thread) and sometimes such discussions easily
digress, making it even harder to come up with a solution.
-
- <p>Another way is to use Savannah's built-in trackers (the
‘<samp><span class="samp">Tasks</span></samp>’ and
-‘<samp><span class="samp">Bugs</span></samp>’ trackers,
specifically). This is further explained in the
+</p>
+<p>Another way is to use Savannah’s built-in trackers (the
‘<samp>Tasks</samp>’ and
+‘<samp>Bugs</samp>’ trackers, specifically). This is further
explained in the
next section, see <a href="Tracking-Tasks.html#Tracking-Tasks">Tracking
Tasks</a>. One way or another, you should
create some kind of review process.
-
-<ul class="menu">
-<li><a accesskey="1" href="Tracking-Tasks.html#Tracking-Tasks">Tracking
Tasks</a>: Using Savannah to track tasks and bugs.
-<li><a accesskey="2"
href="Unreviewed-Translations.html#Unreviewed-Translations">Unreviewed
Translations</a>: What to do with translations that are
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a
href="Tracking-Tasks.html#Tracking-Tasks" accesskey="1">Tracking
Tasks</a>:</td><td> </td><td align="left" valign="top">Using
Savannah to track tasks and bugs.
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Unreviewed-Translations.html#Unreviewed-Translations"
accesskey="2">Unreviewed Translations</a>:</td><td> </td><td
align="left" valign="top">What to do with translations that are
not reviewed.
-</ul>
+</td></tr>
+</table>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Commits.html#Commits" accesskey="n" rel="next">Commits</a>, Up:
<a href="Managing.html#Managing" accesskey="u" rel="up">Managing</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
+</div>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/SSI.html 28 Jun 2012 21:04:22 -0000 1.8
+++ web-trans/html_node/SSI.html 4 Dec 2012 16:24:27 -0000 1.9
@@ -1,116 +1,161 @@
-<html lang="en">
-<head>
-<title>SSI - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Translation-Tips.html#Translation-Tips"
title="Translation Tips">
-<link rel="prev" href="Migrating.html#Migrating" title="Migrating">
-<link rel="next" href="CSS.html#CSS" title="CSS">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: SSI</title>
+
+<meta name="description" content="GNU Web Translators Manual: SSI">
+<meta name="keywords" content="GNU Web Translators Manual: SSI">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Translation-Tips.html#Translation-Tips" rel="up"
title="Translation Tips">
+<link href="CSS.html#CSS" rel="next" title="CSS">
+<link href="Migrating.html#Migrating" rel="previous" title="Migrating">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="SSI"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="CSS.html#CSS">CSS</a>,
-Previous: <a rel="previous" accesskey="p"
href="Migrating.html#Migrating">Migrating</a>,
-Up: <a rel="up" accesskey="u"
href="Translation-Tips.html#Translation-Tips">Translation Tips</a>
-<hr>
+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>
</div>
-
+<hr>
+<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
+<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:
-
- <dl>
-<dt><samp><span class="file">server/banner.html</span></samp><dd>This file
contains only <code>#include</code> directives, so the
+the <code>#include</code>’s used:
+</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.
-
- <br><dt><samp><span
class="file">server/body-include-1.html</span></samp><dd>Contains the top menu
with useful “skip to” links.
-
- <br><dt><samp><span
class="file">server/body-include-2.html</span></samp><dd>This is the file
containing the menus, the FSF widget, and any visible
+</p>
+</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><span class="file">server/po/body-include-2.</span><var>lang</var><span
class="file">.po</span></samp> is updated. Note that
+<samp>server/po/body-include-2.<var>lang</var>.po</samp> is updated. Note that
some validation errors originate from an error in
-<samp><span class="file">server/body-include-2.</span><var>lang</var><span
class="file">.html</span></samp> or some other template
+<samp>server/body-include-2.<var>lang</var>.html</samp> or some other template
file.
-
- <br><dt><samp><span
class="file">server/footer-text.html</span></samp><dd>This is a very short file
currently containing the “back to top” link.
+</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.
-
- <br><dt><samp><span class="file">server/header.html</span></samp><dd>The
declaration that is included in literally every file. It is
+</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
+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><span class="file">header.ar.html</span></samp> should contain this line:
-
- <pre class="example"> <html
xmlns="http://www.w3.org/1999/xhtml"; xml:lang="ar" lang="ar"
- dir="rtl">
-</pre>
- <br><dt><samp><span
class="file">server/head-include-1.html</span></samp><dd>This file (included
from <samp><span class="file">server/header.html</span></samp>) is very
important:
+<samp>header.ar.html</samp> should contain this line:
+</p>
+<div class="example">
+<pre class="example"><html xmlns="http://www.w3.org/1999/xhtml"
xml:lang="ar" lang="ar"
+ dir="rtl">
+</pre></div>
+
+</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><span class="file">server/head-include-1.</span><var>lang</var><span
class="file">.html</span></samp>, so browsers will obey it.
-
- <p>The encoding should be UTF-8. This is required because the English
text
+<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.
-
- <br><dt><samp><span
class="file">server/html5-header.html</span></samp><dd>This file is included in
newer pages using some entities introduced
+</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
+of HTML4 were rejected in HTML5, and our old pages don’t validate
as HTML5.
-
- <br><dt><samp><span
class="file">server/html5-head-include-1.html</span></samp><dd>Likewise, this
file replaces head-include-1.html for HTML5 pages.
-
- <br><dt><samp><span
class="file">server/head-include-2.html</span></samp><dd>Imports the standard
CSS, which can be overridden. See <a href="CSS.html#CSS">CSS</a>.
-
- <br><dt><samp><span class="file">server/footer.html</span></samp><dd>This
is a very short and simple file (at least at the time of writing),
+</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.html#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><span class="file">footer-text.</span><var>lang</var><span
class="file">.html</span></samp> to be included.
-
- <br><dt><samp><span
class="file">server/outdated.html</span></samp><dd>This file is automatically
included in outdated translations. It
+<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.
@@ -118,60 +163,75 @@
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.
-
- <br><dt><samp><span
class="file">translations.include</span></samp><dd>The list of translations for
the homepage (and only the homepage). It
+</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.
-
- <br><dt><samp><span class="file">gnusflashes.include</span></samp><dd>A
portion of the most recent 3 news items from
-<samp><span class="file">server/whatsnew.html</span></samp>, generated
automatically. If your language
-does not have <samp><span
class="file">server/po/whatsnew.</span><var>lang</var><span
class="file">.po</span></samp>, this file will be
-used. Otherwise, if there is an existing localized homepage and you
-commit <samp><span class="file">whatsnew.</span><var>lang</var><span
class="file">.po</span></samp>, the homepage will be rebuilt to
-include the translated <samp><span
class="file">gnusflashes.</span><var>lang</var><span
class="file">.include</span></samp>.
-
- <br><dt><samp><span
class="file">server/whatsnew.include</span></samp><dd>Generated automatically,
this file is included from
-<samp><span class="file">server/whatsnew.html</span></samp>. Translations are
built automatically, and
-the localized <samp><span class="file">gnusflashes.include</span></samp> is
derived from it.
-
- <br><dt><samp><span
class="file">licenses/gpl-3.0-body.html</span></samp><dt><samp><span
class="file">licenses/fdl-1.3-body.html</span></samp><dt><samp><span
class="file">...</span></samp><dd>Some of the licenses have the text of the
license itself separated in
+</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><span class="file">.pot</span></samp> files, as
licenses have only
+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.
-
- <br><dt><samp><span
class="file">server/sidebar*.html</span></samp><dd>These files are
deprecated—they are remnants from an older design that
+</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
-<samp><span class="command">grep</span></samp> to check this.
+<code>grep</code> to check this.
+</p></dd>
</dl>
- <p>The files
+<p>The files
+</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>footer.html</samp>
+</li><li>- <samp>footer-text.html</samp>
+</li></ul>
-<!-- Use @itemize to avoid `underfull \hbox' warnings from TeX. -->
- <ul>
-<li><samp><span class="file">header.html</span></samp>
-<li><samp><span class="file">head-include-1.html</span></samp>
-<li><samp><span class="file">html5-header.html</span></samp>
-<li><samp><span class="file">html5-head-include-1.html</span></samp>
-<li><samp><span class="file">head-include-2.html</span></samp>
-<li><samp><span class="file">banner.html</span></samp>
-<li><samp><span class="file">body-include-1.html</span></samp>
-<li><samp><span class="file">body-include-2.html</span></samp>
-<li><samp><span class="file">footer.html</span></samp>
-<li><samp><span class="file">footer-text.html</span></samp>
-</ul>
-
- <p>in the <samp><span class="file">server</span></samp> sub-directory are
what webmasters call “the
+<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="../gnun/Runtime-Variables.html#Runtime-Variables">Runtime Variables</a>.
+<code>GRACE</code> variable has no effect for them. See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/Runtime-Variables.html#Runtime-Variables";>Runtime
+Variables</a> in <cite>The GNUnited Nations Manual</cite>.
+</p>
+<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>
+</div>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Savannah-Bugs.html 28 Jun 2012 21:04:22 -0000
1.8
+++ web-trans/html_node/Savannah-Bugs.html 4 Dec 2012 16:24:27 -0000
1.9
@@ -1,67 +1,92 @@
-<html lang="en">
-<head>
-<title>Savannah Bugs - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Savannah.html#Savannah" title="Savannah">
-<link rel="prev" href="Savannah-Tasks.html#Savannah-Tasks" title="Savannah
Tasks">
-<link rel="next" href="Savannah-Patch.html#Savannah-Patch" title="Savannah
Patch">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Savannah Bugs</title>
+
+<meta name="description" content="GNU Web Translators Manual: Savannah Bugs">
+<meta name="keywords" content="GNU Web Translators Manual: Savannah Bugs">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Savannah.html#Savannah" rel="up" title="Savannah">
+<link href="Savannah-Patch.html#Savannah-Patch" rel="next" title="Savannah
Patch">
+<link href="Savannah-Tasks.html#Savannah-Tasks" rel="previous" title="Savannah
Tasks">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Savannah-Bugs"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Savannah-Patch.html#Savannah-Patch">Savannah Patch</a>,
-Previous: <a rel="previous" accesskey="p"
href="Savannah-Tasks.html#Savannah-Tasks">Savannah Tasks</a>,
-Up: <a rel="up" accesskey="u" href="Savannah.html#Savannah">Savannah</a>
-<hr>
+Next: <a href="Savannah-Patch.html#Savannah-Patch" accesskey="n"
rel="next">Savannah Patch</a>, Previous: <a
href="Savannah-Tasks.html#Savannah-Tasks" accesskey="p" rel="previous">Savannah
Tasks</a>, Up: <a href="Savannah.html#Savannah" accesskey="u"
rel="up">Savannah</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
+<hr>
+<a name="Bugs-Tracker"></a>
+<h4 class="subsubsection">3.2.3.5 Bugs Tracker</h4>
-<h5 class="subsubsection">3.2.3.5 Bugs Tracker</h5>
-
-<p>The ‘<samp><span class="samp">Bugs</span></samp>’ tracker is
designed for tracking bugs. You can use for
+<p>The ‘<samp>Bugs</samp>’ tracker is designed for tracking bugs.
You can use for
several purposes:
+</p>
+<ul>
+<li> Suggest readers to report bugs there.
+
+</li><li> Use it for all kinds of internal team tasks.
+
+</li><li> Forward bugs reported against <var>lang</var> translations in the
+‘<samp>trans-coord</samp>’ project and assign them to the specific
maintainer
+(who is supposed to be a ‘<samp>www-<var>lang</var></samp>’
project member), if you
+have such policy.
+</li></ul>
- <ul>
-<li>Suggest readers to report bugs there.
-
- <li>Use it for all kinds of internal team tasks.
- <li>Forward bugs reported against <var>lang</var> translations in the
-‘<samp><span class="samp">trans-coord</span></samp>’ project and
assign them to the specific maintainer
-(who is supposed to be a ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’ project member), if you
-have such policy.
-</ul>
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Savannah-Homepage.html 28 Jun 2012 21:04:22 -0000
1.8
+++ web-trans/html_node/Savannah-Homepage.html 4 Dec 2012 16:24:27 -0000
1.9
@@ -1,77 +1,99 @@
-<html lang="en">
-<head>
-<title>Savannah Homepage - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Savannah.html#Savannah" title="Savannah">
-<link rel="prev" href="Savannah-Members.html#Savannah-Members" title="Savannah
Members">
-<link rel="next" href="Savannah-Support.html#Savannah-Support" title="Savannah
Support">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Savannah Homepage</title>
+
+<meta name="description" content="GNU Web Translators Manual: Savannah
Homepage">
+<meta name="keywords" content="GNU Web Translators Manual: Savannah Homepage">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Savannah.html#Savannah" rel="up" title="Savannah">
+<link href="Savannah-Support.html#Savannah-Support" rel="next" title="Savannah
Support">
+<link href="Savannah-Members.html#Savannah-Members" rel="previous"
title="Savannah Members">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Savannah-Homepage"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Savannah-Support.html#Savannah-Support">Savannah Support</a>,
-Previous: <a rel="previous" accesskey="p"
href="Savannah-Members.html#Savannah-Members">Savannah Members</a>,
-Up: <a rel="up" accesskey="u" href="Savannah.html#Savannah">Savannah</a>
-<hr>
+Next: <a href="Savannah-Support.html#Savannah-Support" accesskey="n"
rel="next">Savannah Support</a>, Previous: <a
href="Savannah-Members.html#Savannah-Members" accesskey="p"
rel="previous">Savannah Members</a>, Up: <a href="Savannah.html#Savannah"
accesskey="u" rel="up">Savannah</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
-<h5 class="subsubsection">3.2.3.2 Homepage of The Team</h5>
+<hr>
+<a name="Homepage-of-The-Team"></a>
+<h4 class="subsubsection">3.2.3.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
-<<code>http://www.gnu.org/server/standards/translations/</code><var>lang</var>>;
+‘<code>http://www.gnu.org/server/standards/translations/<var>lang</var></code>’;
to add files to it first make a checkout, following the instructions at
-<<code>https://savannah.gnu.org/cvs/?group=www-</code><var>lang</var>>.
-
- <p>It is recommended to describe all team-specific procedures, if there are
+‘<code>https://savannah.gnu.org/cvs/?group=www-<var>lang</var></code>’.
+</p>
+<p>It is recommended to describe all team-specific procedures, if there are
any. That way, you can point potential team members to the
corresponding page containing these instructions, instead of repeatedly
explaining every volunteer separately.
-
- <p>All team-specific pages should follow the usual linking criteria (see
+</p>
+<p>All team-specific pages should follow the usual linking criteria (see
<a
href="http://gnu.org/server/standards/README.webmastering.html#pollinking";>http://gnu.org/server/standards/README.webmastering.html#pollinking</a>
and the FSF HTML Style Sheet
Guidelines—<a
href="http://gnu.org/server/fsf-html-style-sheet.html";>http://gnu.org/server/fsf-html-style-sheet.html</a>).
+</p>
+<p>For historical reasons, team-specific materials were available in the
+‘<samp>www</samp>’ repository, under ad-hoc locations as
<samp>/spanish</samp>,
+<samp>/wwwsr</samp>, etc. These locations are deprecated, and the contents
+will be removed without warning.
+</p>
- <p>For historical reasons, team-specific materials were available in the
-‘<samp><span class="samp">www</span></samp>’ repository, under
ad-hoc locations as <samp><span class="file">/spanish</span></samp>,
-<samp><span class="file">/wwwsr</span></samp>, etc. These locations are
deprecated, and the contents
-will be moved without warning to <samp><span
class="file">/graveyard</span></samp> in the
-‘<samp><span class="samp">trans-coord</span></samp>’
<em>Sources</em> repository, following the original
-‘<samp><span class="samp">www</span></samp>’ layout (that is, if
there were any sub-directories, they will
-be retained).
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Savannah-Mailing-Lists.html 28 Jun 2012 21:04:22
-0000 1.8
+++ web-trans/html_node/Savannah-Mailing-Lists.html 4 Dec 2012 16:24:27
-0000 1.9
@@ -1,69 +1,94 @@
-<html lang="en">
-<head>
-<title>Savannah Mailing Lists - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Savannah.html#Savannah" title="Savannah">
-<link rel="prev" href="Savannah-News.html#Savannah-News" title="Savannah News">
-<link rel="next" href="Savannah-VCS.html#Savannah-VCS" title="Savannah VCS">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Savannah Mailing Lists</title>
+
+<meta name="description" content="GNU Web Translators Manual: Savannah Mailing
Lists">
+<meta name="keywords" content="GNU Web Translators Manual: Savannah Mailing
Lists">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Savannah.html#Savannah" rel="up" title="Savannah">
+<link href="Savannah-VCS.html#Savannah-VCS" rel="next" title="Savannah VCS">
+<link href="Savannah-News.html#Savannah-News" rel="previous" title="Savannah
News">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Savannah-Mailing-Lists"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Savannah-VCS.html#Savannah-VCS">Savannah VCS</a>,
-Previous: <a rel="previous" accesskey="p"
href="Savannah-News.html#Savannah-News">Savannah News</a>,
-Up: <a rel="up" accesskey="u" href="Savannah.html#Savannah">Savannah</a>
-<hr>
+Next: <a href="Savannah-VCS.html#Savannah-VCS" accesskey="n"
rel="next">Savannah VCS</a>, Previous: <a
href="Savannah-News.html#Savannah-News" accesskey="p" rel="previous">Savannah
News</a>, Up: <a href="Savannah.html#Savannah" accesskey="u"
rel="up">Savannah</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
-
-<h5 class="subsubsection">3.2.3.8 Managing Mailing Lists</h5>
+<hr>
+<a name="Managing-Mailing-Lists"></a>
+<h4 class="subsubsection">3.2.3.8 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><span
class="samp">www-</span><var>lang</var><span
class="samp">-</span></samp>’.
-
- <p>The list will make it possible for the GNU project to contact the team
+name of the list should begin with
‘<samp>www-<var>lang</var>-</samp>’.
+</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
the history for new translators.
-
- <p>You can create new mailing lists via the Savannah interface. However,
+</p>
+<p>You can create new mailing lists via the Savannah interface. However,
this should be done after some thought. If the project membership is
low (<= 10 members), there is no need to create more than one mailing
list.
+</p>
+<p>You can redirect all messages generated by the trackers to any list.
+</p>
- <p>You can redirect all messages generated by the trackers to any list.
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Savannah-Members.html 28 Jun 2012 21:04:22 -0000
1.8
+++ web-trans/html_node/Savannah-Members.html 4 Dec 2012 16:24:28 -0000
1.9
@@ -1,69 +1,96 @@
-<html lang="en">
-<head>
-<title>Savannah Members - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Savannah.html#Savannah" title="Savannah">
-<link rel="next" href="Savannah-Homepage.html#Savannah-Homepage"
title="Savannah Homepage">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Savannah Members</title>
+
+<meta name="description" content="GNU Web Translators Manual: Savannah
Members">
+<meta name="keywords" content="GNU Web Translators Manual: Savannah Members">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Savannah.html#Savannah" rel="up" title="Savannah">
+<link href="Savannah-Homepage.html#Savannah-Homepage" rel="next"
title="Savannah Homepage">
+<link href="Savannah.html#Savannah" rel="previous" title="Savannah">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Savannah-Members"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Savannah-Homepage.html#Savannah-Homepage">Savannah Homepage</a>,
-Up: <a rel="up" accesskey="u" href="Savannah.html#Savannah">Savannah</a>
-<hr>
+Next: <a href="Savannah-Homepage.html#Savannah-Homepage" accesskey="n"
rel="next">Savannah Homepage</a>, Up: <a href="Savannah.html#Savannah"
accesskey="u" rel="up">Savannah</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
-<h5 class="subsubsection">3.2.3.1 Managing Members</h5>
+<hr>
+<a name="Managing-Members"></a>
+<h4 class="subsubsection">3.2.3.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
-of the project's resources, and tracking their number is one of the ways
+of the project’s resources, and tracking their number is one of the ways
for web-translators to determine the status of the team.
-
- <p>It is OK if a particular contributor wants to translate an article or
+</p>
+<p>It is OK if a particular contributor wants to translate an article or
two and does not want to be engaged with the team on a long-term basis.
In such situations, there is no need to add her as a member.
-
- <p>It is a good idea to mark inactive members, for example if there is no
+</p>
+<p>It is a good idea to mark inactive members, for example if there is no
interaction (bug reports, new translations, updates to existing
translations, proof-reading) for at least six months. You can do that
-by unmarking the ‘<samp><span class="samp">On Duty</span></samp>’
checkbox for the respective project
-member under ‘<samp><span class="samp">Set
Permissions</span></samp>’. Inactive members have absolutely
-the same rights as active ones—the only exception is that they don't
+by unmarking the ‘<samp>On Duty</samp>’ checkbox for the
respective project
+member under ‘<samp>Set Permissions</samp>’. Inactive members
have absolutely
+the same rights as active ones—the only exception is that they
don’t
count for the total number of members, and they appear separately on
-‘<samp><span class="samp">View Members</span></samp>’.
+‘<samp>View Members</samp>’.
+</p>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Savannah-News.html 28 Jun 2012 21:04:22 -0000
1.8
+++ web-trans/html_node/Savannah-News.html 4 Dec 2012 16:24:28 -0000
1.9
@@ -1,65 +1,90 @@
-<html lang="en">
-<head>
-<title>Savannah News - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Savannah.html#Savannah" title="Savannah">
-<link rel="prev" href="Savannah-Patch.html#Savannah-Patch" title="Savannah
Patch">
-<link rel="next" href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists"
title="Savannah Mailing Lists">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Savannah News</title>
+
+<meta name="description" content="GNU Web Translators Manual: Savannah News">
+<meta name="keywords" content="GNU Web Translators Manual: Savannah News">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Savannah.html#Savannah" rel="up" title="Savannah">
+<link href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists" rel="next"
title="Savannah Mailing Lists">
+<link href="Savannah-Patch.html#Savannah-Patch" rel="previous" title="Savannah
Patch">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Savannah-News"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists">Savannah Mailing
Lists</a>,
-Previous: <a rel="previous" accesskey="p"
href="Savannah-Patch.html#Savannah-Patch">Savannah Patch</a>,
-Up: <a rel="up" accesskey="u" href="Savannah.html#Savannah">Savannah</a>
-<hr>
+Next: <a href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists"
accesskey="n" rel="next">Savannah Mailing Lists</a>, Previous: <a
href="Savannah-Patch.html#Savannah-Patch" accesskey="p" rel="previous">Savannah
Patch</a>, Up: <a href="Savannah.html#Savannah" accesskey="u"
rel="up">Savannah</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
-
-<h5 class="subsubsection">3.2.3.7 News Tracker</h5>
+<hr>
+<a name="News-Tracker"></a>
+<h4 class="subsubsection">3.2.3.7 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><span
class="samp">News</span></samp>’ RSS
+project page from time to time, or subscribe to the
‘<samp>News</samp>’ RSS
feed) about a major change or event within the project.
-
- <p>You can also setup news entries to be sent to a mailing list (that's
+</p>
+<p>You can also setup news entries to be sent to a mailing list (that’s
possible for the other trackers as well).
-
- <p>The purpose of this feature is informational—if members need to
know
+</p>
+<p>The purpose of this feature is informational—if members need to know
about an important change (in practices, procedures, etc.), it is
perfectly OK to announce it here. Some teams use it to announce new
translations, which is also fine.
+</p>
+
- </body></html>
+</body>
+</html>
Index: web-trans/html_node/Savannah-Patch.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Patch.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Savannah-Patch.html 28 Jun 2012 21:04:22 -0000
1.8
+++ web-trans/html_node/Savannah-Patch.html 4 Dec 2012 16:24:28 -0000
1.9
@@ -1,62 +1,87 @@
-<html lang="en">
-<head>
-<title>Savannah Patch - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Savannah.html#Savannah" title="Savannah">
-<link rel="prev" href="Savannah-Bugs.html#Savannah-Bugs" title="Savannah Bugs">
-<link rel="next" href="Savannah-News.html#Savannah-News" title="Savannah News">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Savannah Patch</title>
+
+<meta name="description" content="GNU Web Translators Manual: Savannah Patch">
+<meta name="keywords" content="GNU Web Translators Manual: Savannah Patch">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Savannah.html#Savannah" rel="up" title="Savannah">
+<link href="Savannah-News.html#Savannah-News" rel="next" title="Savannah News">
+<link href="Savannah-Bugs.html#Savannah-Bugs" rel="previous" title="Savannah
Bugs">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Savannah-Patch"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Savannah-News.html#Savannah-News">Savannah News</a>,
-Previous: <a rel="previous" accesskey="p"
href="Savannah-Bugs.html#Savannah-Bugs">Savannah Bugs</a>,
-Up: <a rel="up" accesskey="u" href="Savannah.html#Savannah">Savannah</a>
-<hr>
+Next: <a href="Savannah-News.html#Savannah-News" accesskey="n"
rel="next">Savannah News</a>, Previous: <a
href="Savannah-Bugs.html#Savannah-Bugs" accesskey="p" rel="previous">Savannah
Bugs</a>, Up: <a href="Savannah.html#Savannah" accesskey="u"
rel="up">Savannah</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
+<hr>
+<a name="Patch-Tracker"></a>
+<h4 class="subsubsection">3.2.3.6 Patch Tracker</h4>
-<h5 class="subsubsection">3.2.3.6 Patch Tracker</h5>
-
-<p>This tracker doesn't make much sense for translation projects, as the
+<p>This tracker doesn’t make much sense for translation projects, as the
original on which the translation is based is volatile and the
-translation <dfn>patch</dfn> is 100% guaranteed not to apply cleanly very
+translation <em>patch</em> is 100% guaranteed not to apply cleanly very
soon after it is submitted. Even ignoring this detail, this specific
feature is slowly marching towards complete deprecation, as there are
much better ways to submit patches nowadays.
+</p>
+<p>You should disable this feature, as it causes only confusion.
+</p>
- <p>You should disable this feature, as it causes only confusion.
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Savannah-Projects.html 28 Jun 2012 21:04:22 -0000
1.8
+++ web-trans/html_node/Savannah-Projects.html 4 Dec 2012 16:24:28 -0000
1.9
@@ -1,77 +1,110 @@
-<html lang="en">
-<head>
-<title>Savannah Projects - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Summary.html#Summary" title="Summary">
-<link rel="prev" href="Mailing-Lists.html#Mailing-Lists" title="Mailing Lists">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Savannah Projects</title>
+
+<meta name="description" content="GNU Web Translators Manual: Savannah
Projects">
+<meta name="keywords" content="GNU Web Translators Manual: Savannah Projects">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Summary.html#Summary" rel="up" title="Summary">
+<link href="Copying-This-Manual.html#Copying-This-Manual" rel="next"
title="Copying This Manual">
+<link href="Mailing-Lists.html#Mailing-Lists" rel="previous" title="Mailing
Lists">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Savannah-Projects"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="Mailing-Lists.html#Mailing-Lists">Mailing Lists</a>,
-Up: <a rel="up" accesskey="u" href="Summary.html#Summary">Summary</a>
-<hr>
+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>
</div>
-
+<hr>
+<a name="Savannah-Projects-Membership"></a>
<h3 class="section">6.2 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:
-
- <dl>
-<dt>‘<samp><span class="samp">www</span></samp>’<dd>The main
project which hosts the ‘<samp><span
class="samp">gnu.org</span></samp>’ Web repository.
+</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 leader's applications). All
+Translation Manager (in order to approve leader’s applications). All
team leaders (and co-leaders) should be members of this project.
-
- <p>Note that this project has no direct relationship with translators,
-although anything happening in ‘<samp><span
class="samp">www</span></samp>’ directly affects them. The
-‘<samp><span class="samp">www</span></samp>’ project is managed
separately and has a different (entirely
+</p>
+<p>Note that this project has no direct relationship with translators,
+although anything happening in ‘<samp>www</samp>’ directly affects
them. The
+‘<samp>www</samp>’ project is managed separately and has a
different (entirely
unrelated) process for approving contributors.
-
- <br><dt>‘<samp><span
class="samp">trans-coord</span></samp>’<dd>An organizational project
especially created for coordination and
+</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><span
class="samp">trans-coord</span></samp>’ ‘<samp><span
class="samp">Bugs</span></samp>’ tracker.
-
- <p>The admins of this project are the GNU Web Translation Managers.
-
- <br><dt>‘<samp><span
class="samp">www-</span><var>lang</var></samp>’<dd>All translation team
leaders of the language <var>lang</var> should be
-members of the project ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’. The admins of the
project
+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>www-<var>lang</var></samp>’</dt>
+<dd><p>All translation team leaders of the language <var>lang</var> should be
+members of the project ‘<samp>www-<var>lang</var></samp>’. The
admins of the project
are the team leader and the co-leaders, if any.
+</p></dd>
</dl>
- </body></html>
+
+
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Savannah-Support.html 28 Jun 2012 21:04:22 -0000
1.8
+++ web-trans/html_node/Savannah-Support.html 4 Dec 2012 16:24:28 -0000
1.9
@@ -1,59 +1,84 @@
-<html lang="en">
-<head>
-<title>Savannah Support - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Savannah.html#Savannah" title="Savannah">
-<link rel="prev" href="Savannah-Homepage.html#Savannah-Homepage"
title="Savannah Homepage">
-<link rel="next" href="Savannah-Tasks.html#Savannah-Tasks" title="Savannah
Tasks">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Savannah Support</title>
+
+<meta name="description" content="GNU Web Translators Manual: Savannah
Support">
+<meta name="keywords" content="GNU Web Translators Manual: Savannah Support">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Savannah.html#Savannah" rel="up" title="Savannah">
+<link href="Savannah-Tasks.html#Savannah-Tasks" rel="next" title="Savannah
Tasks">
+<link href="Savannah-Homepage.html#Savannah-Homepage" rel="previous"
title="Savannah Homepage">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Savannah-Support"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Savannah-Tasks.html#Savannah-Tasks">Savannah Tasks</a>,
-Previous: <a rel="previous" accesskey="p"
href="Savannah-Homepage.html#Savannah-Homepage">Savannah Homepage</a>,
-Up: <a rel="up" accesskey="u" href="Savannah.html#Savannah">Savannah</a>
-<hr>
+Next: <a href="Savannah-Tasks.html#Savannah-Tasks" accesskey="n"
rel="next">Savannah Tasks</a>, Previous: <a
href="Savannah-Homepage.html#Savannah-Homepage" accesskey="p"
rel="previous">Savannah Homepage</a>, Up: <a href="Savannah.html#Savannah"
accesskey="u" rel="up">Savannah</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
-<h5 class="subsubsection">3.2.3.3 Support Tracker</h5>
+<hr>
+<a name="Support-Tracker"></a>
+<h4 class="subsubsection">3.2.3.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
-functionality and/or features that requires the project admin(s)'s
+functionality and/or features that requires the project admin’s
action. Do not use it for anything else as it quickly becomes
confusing. It is OK to disable it if the team is small.
+</p>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Savannah-Tasks.html 28 Jun 2012 21:04:22 -0000
1.8
+++ web-trans/html_node/Savannah-Tasks.html 4 Dec 2012 16:24:28 -0000
1.9
@@ -1,64 +1,89 @@
-<html lang="en">
-<head>
-<title>Savannah Tasks - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Savannah.html#Savannah" title="Savannah">
-<link rel="prev" href="Savannah-Support.html#Savannah-Support" title="Savannah
Support">
-<link rel="next" href="Savannah-Bugs.html#Savannah-Bugs" title="Savannah Bugs">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Savannah Tasks</title>
+
+<meta name="description" content="GNU Web Translators Manual: Savannah Tasks">
+<meta name="keywords" content="GNU Web Translators Manual: Savannah Tasks">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Savannah.html#Savannah" rel="up" title="Savannah">
+<link href="Savannah-Bugs.html#Savannah-Bugs" rel="next" title="Savannah Bugs">
+<link href="Savannah-Support.html#Savannah-Support" rel="previous"
title="Savannah Support">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Savannah-Tasks"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Savannah-Bugs.html#Savannah-Bugs">Savannah Bugs</a>,
-Previous: <a rel="previous" accesskey="p"
href="Savannah-Support.html#Savannah-Support">Savannah Support</a>,
-Up: <a rel="up" accesskey="u" href="Savannah.html#Savannah">Savannah</a>
-<hr>
+Next: <a href="Savannah-Bugs.html#Savannah-Bugs" accesskey="n"
rel="next">Savannah Bugs</a>, Previous: <a
href="Savannah-Support.html#Savannah-Support" accesskey="p"
rel="previous">Savannah Support</a>, Up: <a href="Savannah.html#Savannah"
accesskey="u" rel="up">Savannah</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
-<h5 class="subsubsection">3.2.3.4 Tasks Tracker</h5>
+<hr>
+<a name="Tasks-Tracker"></a>
+<h4 class="subsubsection">3.2.3.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
is possible to use this tracker to “announce” to the team members
that
a specific article should be translated. The one who volunteers may
assign the task to herself.
-
- <p>Teams may use this tracker to avoid duplicate work, by declaring that
+</p>
+<p>Teams may use this tracker to avoid duplicate work, by declaring that
they intend to work on a specific translation.
+</p>
+<p>Feel free to organize the ‘<samp>Tasks</samp>’ management as
you see fit.
+</p>
- <p>Feel free to organize the ‘<samp><span
class="samp">Tasks</span></samp>’ management as you see fit.
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Savannah-VCS.html 28 Jun 2012 21:04:23 -0000
1.8
+++ web-trans/html_node/Savannah-VCS.html 4 Dec 2012 16:24:28 -0000
1.9
@@ -1,98 +1,131 @@
-<html lang="en">
-<head>
-<title>Savannah VCS - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Savannah.html#Savannah" title="Savannah">
-<link rel="prev" href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists"
title="Savannah Mailing Lists">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Savannah VCS</title>
+
+<meta name="description" content="GNU Web Translators Manual: Savannah VCS">
+<meta name="keywords" content="GNU Web Translators Manual: Savannah VCS">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Savannah.html#Savannah" rel="up" title="Savannah">
+<link href="Co_002dleaders.html#Co_002dleaders" rel="next" title="Co-leaders">
+<link href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists" rel="previous"
title="Savannah Mailing Lists">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Savannah-VCS"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists">Savannah Mailing
Lists</a>,
-Up: <a rel="up" accesskey="u" href="Savannah.html#Savannah">Savannah</a>
-<hr>
+Previous: <a href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists"
accesskey="p" rel="previous">Savannah Mailing Lists</a>, Up: <a
href="Savannah.html#Savannah" accesskey="u" rel="up">Savannah</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-
-<h5 class="subsubsection">3.2.3.9 Version Control Systems</h5>
+<hr>
+<a name="Version-Control-Systems"></a>
+<h4 class="subsubsection">3.2.3.9 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
-translation project's Sources repository. That way, it is easy to edit
-draft translations and install them in ‘<samp><span
class="samp">www</span></samp>’ only when they're
+translation project’s Sources repository. That way, it is easy to edit
+draft translations and install them in ‘<samp>www</samp>’ only
when they’re
ready. It is also convenient to update the translation (merge any
changes from the original) while it is still under review.
-
- <p>See <a href="../gnun/PO-Files-and-Team.html#PO-Files-and-Team">PO Files
and Team</a>, for
+</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
more information.
-
- <p><strong>Remember:</strong> A choice of a particular VCS is a sensitive
+</p>
+<p><strong>Remember:</strong> A choice of a particular VCS is a sensitive
matter—some modern ones provide compelling features, but they also
bump the barrier for participation higher. The VCS is supposed to ease
collaborative maintenance—if it eases only you, project members just
-won't use it so that won't be a net win.
-
-<h5 class="subsubheading">Web-based Systems</h5>
+won’t use it so that won’t be a net win.
+</p>
+<a name="Web_002dbased-Systems"></a>
+<h4 class="subsubheading">Web-based Systems</h4>
<p>An alternative way to maintain translations is to use one of the
existing online editors. There are plans to install a web-based system
-for managing <samp><span class="file">.po</span></samp> files at Savannah,
including online editing and
+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>
- <p>Here is a short and probably incomplete list of such systems:
-
- <ul>
-<li>Pootle—<a
href="http://translate.sourceforge.net/wiki/pootle";>http://translate.sourceforge.net/wiki/pootle</a>
-
- <li>Vertaal—<a
href="http://code.google.com/p/vertaal";>http://code.google.com/p/vertaal</a>
+</li><li> Vertaal—<a
href="http://code.google.com/p/vertaal";>http://code.google.com/p/vertaal</a>
- <li>Narro—<a
href="http://code.google.com/p/narro";>http://code.google.com/p/narro</a>
+</li><li> Narro—<a
href="http://code.google.com/p/narro";>http://code.google.com/p/narro</a>
- <li>Launchpad—<a
href="https://dev.launchpad.net";>https://dev.launchpad.net</a>
+</li><li> Launchpad—<a
href="https://dev.launchpad.net";>https://dev.launchpad.net</a>
- </ul>
+</li></ul>
- <p>If you decide to use such a system, please make sure that no
+<p>If you decide to use such a system, please make sure that no
translations are published in HTML format there.
-
- <p>Note that to keep the <samp><span class="file">.pot</span></samp> files
regularly updated (assuming such
-a web-based system runs <samp><span class="command">msgmerge</span></samp>
automatically), you'll have
-to take care of the one-way regular sync from the ‘<samp><span
class="samp">www</span></samp>’ CVS
+</p>
+<p>Note that to keep the <samp>.pot</samp> files regularly updated (assuming
such
+a web-based system runs <code>msgmerge</code> automatically), you’ll have
+to take care of the one-way regular sync from the
‘<samp>www</samp>’ CVS
repository.
+</p>
+<hr>
+<div class="header">
+<p>
+Previous: <a href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists"
accesskey="p" rel="previous">Savannah Mailing Lists</a>, Up: <a
href="Savannah.html#Savannah" accesskey="u" rel="up">Savannah</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
+</div>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Savannah.html 28 Jun 2012 21:04:23 -0000 1.8
+++ web-trans/html_node/Savannah.html 4 Dec 2012 16:24:28 -0000 1.9
@@ -1,61 +1,83 @@
-<html lang="en">
-<head>
-<title>Savannah - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Managing.html#Managing" title="Managing">
-<link rel="prev" href="Commits.html#Commits" title="Commits">
-<link rel="next" href="Co_002dleaders.html#Co_002dleaders" title="Co-leaders">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Savannah</title>
+
+<meta name="description" content="GNU Web Translators Manual: Savannah">
+<meta name="keywords" content="GNU Web Translators Manual: Savannah">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Managing.html#Managing" rel="up" title="Managing">
+<link href="Savannah-Members.html#Savannah-Members" rel="next" title="Savannah
Members">
+<link href="Commits.html#Commits" rel="previous" title="Commits">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Savannah"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Co_002dleaders.html#Co_002dleaders">Co-leaders</a>,
-Previous: <a rel="previous" accesskey="p"
href="Commits.html#Commits">Commits</a>,
-Up: <a rel="up" accesskey="u" href="Managing.html#Managing">Managing</a>
-<hr>
+Next: <a href="Co_002dleaders.html#Co_002dleaders" accesskey="n"
rel="next">Co-leaders</a>, Previous: <a href="Commits.html#Commits"
accesskey="p" rel="previous">Commits</a>, Up: <a href="Managing.html#Managing"
accesskey="u" rel="up">Managing</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="Taking-Advantage-of-Savannah"></a>
<h4 class="subsection">3.2.3 Taking Advantage of Savannah</h4>
<p>Every translation team should have a project in Savannah. There are
some teams that use their own resources outside from Savannah; although
-there's no obligation to use Savannah for team work, the need for a
-Savannah project for each language is obvious: it's a standard way to
+there’s no obligation to use Savannah for team work, the need for a
+Savannah project for each language is obvious: it’s a standard way to
find information for translation teams and their contacts.
-
- <p>Using external hosting facilities may seem justified sometimes. Some
+</p>
+<p>Using external hosting facilities may seem justified sometimes. Some
teams may have already established repositories and/or bug tracking
systems where usual contributors already have access. Some team
members prefer to work within the established infrastructure of a
@@ -64,44 +86,61 @@
(see <a href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists">Savannah
Mailing Lists</a>), because it is easier to pass its
management to the new co-ordinator when the old one steps down, and it
helps to keep the archives at one place for future members of the
-team. Likewise, it is better to use Savannah for the team's
+team. Likewise, it is better to use Savannah for the team’s
repository and bugs/tasks, but this is not mandatory.
-
- <p>However, it is important to remember that regardless of the technical
+</p>
+<p>However, it is important to remember that regardless of the technical
resources which a team decides to use, the responsibility of the team
co-ordinator remains the same.
-
- <p>Those teams that are using Savannah have a broad variety of tools at
+</p>
+<p>Those teams that are using Savannah have a broad variety of tools at
hand: team membership management, documents, trackers (bugs, tasks and
support), alerts, CVS (and any other VCS that Savannah supports), home
pages, etc. How each team uses these resources is up to the team
itself, but it often turns out to choose Savannah for nearly all of
the team activities, as it requires almost zero work; the Savannah
Hackers are happy to support us.
-
- <p>Whatever you (in your capacity as a team leader) decide, please do it
+</p>
+<p>Whatever you (in your capacity as a team leader) decide, please do it
with caution: some organizational decisions may become ineffective as
time goes by, and some may not scale well when the team grows. If the
team is young and has a couple of members, it is better to refrain from
such decision and discuss them with all the members when their number
grows. Two or three people do not need a rocket platform or complex
wizardry to do their work.
-
- <p>The next sections contain suggestions about how a team can use the
+</p>
+<p>The next sections contain suggestions about how a team can use the
facilities provided by Savannah. It is not mandatory to follow them,
they are just suggestions.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a
href="Savannah-Members.html#Savannah-Members" accesskey="1">Savannah
Members</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Savannah-Homepage.html#Savannah-Homepage" accesskey="2">Savannah
Homepage</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Savannah-Support.html#Savannah-Support" accesskey="3">Savannah
Support</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Savannah-Tasks.html#Savannah-Tasks" accesskey="4">Savannah
Tasks</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Savannah-Bugs.html#Savannah-Bugs" accesskey="5">Savannah
Bugs</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Savannah-Patch.html#Savannah-Patch" accesskey="6">Savannah
Patch</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Savannah-News.html#Savannah-News" accesskey="7">Savannah
News</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists"
accesskey="8">Savannah Mailing Lists</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Savannah-VCS.html#Savannah-VCS" accesskey="9">Savannah
VCS</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+</table>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Co_002dleaders.html#Co_002dleaders" accesskey="n"
rel="next">Co-leaders</a>, Previous: <a href="Commits.html#Commits"
accesskey="p" rel="previous">Commits</a>, Up: <a href="Managing.html#Managing"
accesskey="u" rel="up">Managing</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
+</div>
-<ul class="menu">
-<li><a accesskey="1" href="Savannah-Members.html#Savannah-Members">Savannah
Members</a>
-<li><a accesskey="2" href="Savannah-Homepage.html#Savannah-Homepage">Savannah
Homepage</a>
-<li><a accesskey="3" href="Savannah-Support.html#Savannah-Support">Savannah
Support</a>
-<li><a accesskey="4" href="Savannah-Tasks.html#Savannah-Tasks">Savannah
Tasks</a>
-<li><a accesskey="5" href="Savannah-Bugs.html#Savannah-Bugs">Savannah Bugs</a>
-<li><a accesskey="6" href="Savannah-Patch.html#Savannah-Patch">Savannah
Patch</a>
-<li><a accesskey="7" href="Savannah-News.html#Savannah-News">Savannah News</a>
-<li><a accesskey="8"
href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists">Savannah Mailing
Lists</a>
-<li><a accesskey="9" href="Savannah-VCS.html#Savannah-VCS">Savannah VCS</a>
-</ul>
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Stepping-Down.html 28 Jun 2012 21:04:23 -0000
1.8
+++ web-trans/html_node/Stepping-Down.html 4 Dec 2012 16:24:28 -0000
1.9
@@ -1,63 +1,90 @@
-<html lang="en">
-<head>
-<title>Stepping Down - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Leaders.html#Leaders" title="Leaders">
-<link rel="prev" href="Reports.html#Reports" title="Reports">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Stepping Down</title>
+
+<meta name="description" content="GNU Web Translators Manual: Stepping Down">
+<meta name="keywords" content="GNU Web Translators Manual: Stepping Down">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Leaders.html#Leaders" rel="up" title="Leaders">
+<link href="Translation-Managers.html#Translation-Managers" rel="next"
title="Translation Managers">
+<link href="Reports.html#Reports" rel="previous" title="Reports">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Stepping-Down"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="Reports.html#Reports">Reports</a>,
-Up: <a rel="up" accesskey="u" href="Leaders.html#Leaders">Leaders</a>
-<hr>
+Previous: <a href="Reports.html#Reports" accesskey="p"
rel="previous">Reports</a>, Up: <a href="Leaders.html#Leaders" accesskey="u"
rel="up">Leaders</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="How-To-Retire-Painlessly"></a>
<h3 class="section">3.4 How To Retire Painlessly</h3>
-<p>When you feel you don't have the energy to manage the team successfully,
+<p>When you feel you don’t have the energy to manage the team
successfully,
or perhaps you start losing motivation, please inform
<a href="mailto:address@hidden";>address@hidden</a>. It would be substantially
easier if
you try to find a replacement or recommend a specific person—we will
try to find someone in any case, but your judgment is important and it
will be considered with priority.
-
- <p>An excellent way to step down is to do it with a
“plan”—suggest the
+</p>
+<p>An excellent way to step down is to do it with a
“plan”—suggest the
person you consider capable of doing the job as co-leader
(see <a href="Co_002dleaders.html#Co_002dleaders">Co-leaders</a>) and retire
completely when she is absolutely ready
to proceed without your further help and advice.
+</p>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Submitting-as-PO.html 28 Jun 2012 21:04:23 -0000
1.8
+++ web-trans/html_node/Submitting-as-PO.html 4 Dec 2012 16:24:28 -0000
1.9
@@ -1,63 +1,88 @@
-<html lang="en">
-<head>
-<title>Submitting as PO - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Submitting.html#Submitting" title="Submitting">
-<link rel="next" href="Submitting-as-Plain-Text.html#Submitting-as-Plain-Text"
title="Submitting as Plain Text">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Submitting as PO</title>
+
+<meta name="description" content="GNU Web Translators Manual: Submitting as
PO">
+<meta name="keywords" content="GNU Web Translators Manual: Submitting as PO">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Submitting.html#Submitting" rel="up" title="Submitting">
+<link href="Submitting-as-Plain-Text.html#Submitting-as-Plain-Text" rel="next"
title="Submitting as Plain Text">
+<link href="Submitting.html#Submitting" rel="previous" title="Submitting">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Submitting-as-PO"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Submitting-as-Plain-Text.html#Submitting-as-Plain-Text">Submitting as
Plain Text</a>,
-Up: <a rel="up" accesskey="u"
href="Submitting.html#Submitting">Submitting</a>
-<hr>
+Next: <a href="Submitting-as-Plain-Text.html#Submitting-as-Plain-Text"
accesskey="n" rel="next">Submitting as Plain Text</a>, Up: <a
href="Submitting.html#Submitting" accesskey="u" rel="up">Submitting</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="How-To-Submit-a-Translation-in-PO-Format"></a>
<h4 class="subsection">2.2.1 How To Submit a Translation in PO Format</h4>
-<p>All translations<a rel="footnote" href="#fn-1"
name="fnd-1"><sup>1</sup></a> are maintained via GNUN (see
+<p>All translations<a name="DOCF1" href="#FOOT1"><sup>1</sup></a> are
maintained via GNUN (see
<a
href="http://www.gnu.org/software/gnun/";>http://www.gnu.org/software/gnun/</a>),
which significantly eases
maintenance and avoids the unpleasant situation where a translation is
-lagging behind the original. See <a
href="../gnun/Advantages.html#Advantages">Advantages</a>.
-
- <p>As of September 2008 all new translations at gnu.org are installed in
-<samp><span class="file">.po</span></samp> format, and the <samp><span
class="file">.html</span></samp> is generated automatically.
+lagging behind the original. See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/Advantages.html#Advantages";>Advantages</a>
in <cite>The GNUnited
+Nations Manual</cite>.
+</p>
+<p>Since September 2008 all new translations at gnu.org are installed in
+<samp>.po</samp> format, and the <samp>.html</samp> is generated automatically.
Here are the steps to produce and submit such a translation:
-
- <ul>
-<li>Make a checkout of the CVS Web repository of the ‘<samp><span
class="samp">www</span></samp>’ Savannah
+</p>
+<ul>
+<li> Make a checkout of the CVS Web repository of the
‘<samp>www</samp>’ Savannah
project. You can find generic instructions at
<a
href="https://savannah.gnu.org/cvs/?group=www";>https://savannah.gnu.org/cvs/?group=www</a>.
All updates to the
website are done as commits in the repository, so you would need an
@@ -66,56 +91,73 @@
Savannah to use it. You can also check out only a specific directory,
for example:
- <pre class="example"> cvs -z3 -d:pserver:address@hidden:/web/www
co www/gnu
-</pre>
- <p>This command will fetch only the <samp><span
class="file">/gnu</span></samp> directory—in other words,
-all articles at <a href="http://gnu.org/gnu";>http://gnu.org/gnu</a>.
+<div class="example">
+<pre class="example">cvs -z3 -d:pserver:address@hidden:/web/www co www/gnu
+</pre></div>
- <li>Assuming you already know the article you want to translate, you have
to
-create an empty <samp><var>article</var><span
class="file">.</span><var>lang</var><span class="file">.po</span></samp> file
and then
-translate all messages with a PO editor. See <a
href="../gnun/New-Translation.html#New-Translation">New Translation</a>. For
an almost complete list of PO
-editors, see <a href="../gnun/PO-Files.html#PO-Files">PO Files</a>.
+<p>This command will fetch only the <samp>/gnu</samp> directory—in other
words,
+all articles at <a href="http://gnu.org/gnu";>http://gnu.org/gnu</a>.
+</p>
+<p>You can also fetch single files by their respective URLs. For example,
+the URL for the template file of
+<a
href="http://www.gnu.org/philosophy/free-sw.html";>http://www.gnu.org/philosophy/free-sw.html</a>
is
+<a
href="http://www.gnu.org/philosophy/po/free-sw.pot";>http://www.gnu.org/philosophy/po/free-sw.pot</a>;
the URL for
+its <var>lang</var> PO file (when available) is
+<a
href="http://www.gnu.org/philosophy/po/free-sw.lang.po";>http://www.gnu.org/philosophy/po/free-sw.lang.po</a>:
+</p>
+<div class="example">
+<pre class="example">wget http://www.gnu.org/philosophy/po/free-sw.pot
+</pre></div>
+
+</li><li> Assuming you already know the article you want to translate, you
have to
+create an empty <samp><var>article</var>.<var>lang</var>.po</samp> file and
then
+translate all messages with a PO editor. See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/New-Translation.html#New-Translation";>New
Translation</a> in <cite>The GNUnited Nations Manual</cite>. For an almost
complete list of PO
+editors, see <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/PO-Files.html#PO-Files";>PO
Files</a> in <cite>The GNUnited Nations Manual</cite>.
- <li>When you are pleased with the translation, check that the PO file is
+</li><li> When you are pleased with the translation, check that the PO file is
valid and submit it to <a href="mailto:address@hidden";>address@hidden</a>,
attached to
your message. The web-translators will review (to the best of their
ability) the translation and will install it in the repository.
- <li>In order GNUN to be able to generate (and subsequently update) a
-gettextized translation, the language should have the server templates
+</li><li> In order GNUN to be able to generate (and subsequently update) a
fully
+translated page, the language should have the server templates
available as PO files. These templates are short, and translating them
-shouldn't take much time. If the language code is present in the
-<code>TEMPLATE_LINGUAS</code> variable at <samp><span
class="file">server/gnun/gnun.mk</span></samp>, then you
-don't have to do anything. If it is not, the required files are
-<samp><span class="file">server/po/head-include-2.</span><var>lang</var><span
class="file">.po</span></samp>,
-<samp><span class="file">server/po/body-include-1.</span><var>lang</var><span
class="file">.po</span></samp>,
-<samp><span class="file">server/po/body-include-2.</span><var>lang</var><span
class="file">.po</span></samp> and
-<samp><span class="file">server/po/footer-text.</span><var>lang</var><span
class="file">.po</span></samp>—you can translate and
+shouldn’t take much time. If the language code is present in the
+<code>TEMPLATE_LINGUAS</code> variable at <samp>server/gnun/gnun.mk</samp>,
then you
+don’t have to do anything. If it is not, the required files
+are defined via the <code>extra-templates</code> variable
+in <samp>server/gnun/gnun.mk</samp>—you can translate and
submit them in the usual way, together with the translation of the
essay.
- <p>Additional templates are defined via the <var>extra-templates</var>
variable
-in <samp><span class="file">server/gnun/gnun.mk</span></samp>.
-
- <p>If you don't want to translate the templates for whatever
reason—do
+<p>If you don’t want to translate the templates for whatever
reason—do
not worry, the web-translators will install empty templates (which means
the English strings will be used).
-</ul>
+</p></li></ul>
- <p>It is quite possible that there will be errors or typos, so once you are
+<p>It is quite possible that there will be errors or typos, so once you are
informed that the translation is online, check it carefully and if
necessary, resubmit the PO file with corrections. Do not forget to run
-<code>cvs update</code> first and edit the updated <samp><span
class="file">.po</span></samp> file from the
+<code>cvs update</code> first and edit the updated <samp>.po</samp> file from
the
repository—most probably the Translation Managers have already made
some modifications to it, usually to fix validation errors and to
complete the PO file header.
-
- <div class="footnote">
+</p>
+<div class="footnote">
<hr>
-<h4>Footnotes</h4><p class="footnote"><small>[<a name="fn-1"
href="#fnd-1">1</a>]</small> Well—not really, but the goal is to maintain
+<h4 class="footnotes-heading">Footnotes</h4>
+
+<h3><a name="FOOT1" href="#DOCF1">(1)</a></h3>
+<p>Well—not really, but the goal is to maintain
all of them.</p>
+</div>
+<hr>
+<div class="header">
+<p>
+Next: <a href="Submitting-as-Plain-Text.html#Submitting-as-Plain-Text"
accesskey="n" rel="next">Submitting as Plain Text</a>, Up: <a
href="Submitting.html#Submitting" accesskey="u" rel="up">Submitting</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
+</div>
- <hr></div>
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Submitting-as-Plain-Text.html 28 Jun 2012 21:04:23
-0000 1.8
+++ web-trans/html_node/Submitting-as-Plain-Text.html 4 Dec 2012 16:24:28
-0000 1.9
@@ -1,50 +1,74 @@
-<html lang="en">
-<head>
-<title>Submitting as Plain Text - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Submitting.html#Submitting" title="Submitting">
-<link rel="prev" href="Submitting-as-PO.html#Submitting-as-PO"
title="Submitting as PO">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Submitting as Plain Text</title>
+
+<meta name="description" content="GNU Web Translators Manual: Submitting as
Plain Text">
+<meta name="keywords" content="GNU Web Translators Manual: Submitting as Plain
Text">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Submitting.html#Submitting" rel="up" title="Submitting">
+<link href="Leaving-A-Team.html#Leaving-A-Team" rel="next" title="Leaving A
Team">
+<link href="Submitting-as-PO.html#Submitting-as-PO" rel="previous"
title="Submitting as PO">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Submitting-as-Plain-Text"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="Submitting-as-PO.html#Submitting-as-PO">Submitting as PO</a>,
-Up: <a rel="up" accesskey="u"
href="Submitting.html#Submitting">Submitting</a>
-<hr>
+Previous: <a href="Submitting-as-PO.html#Submitting-as-PO" accesskey="p"
rel="previous">Submitting as PO</a>, Up: <a href="Submitting.html#Submitting"
accesskey="u" rel="up">Submitting</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="How-To-Submit-a-Translation-as-Plain-Text"></a>
<h4 class="subsection">2.2.2 How To Submit a Translation as Plain Text</h4>
<p>If you feel the procedure described in the previous section is too
@@ -53,29 +77,35 @@
the GNU Web Translation Managers, which can be tricky sometimes, and
naturally, means more work for them and slower processing of your
request.
-
- <p>You should <em>never</em> translate the HTML markup—i.e. <em>do
not</em>
+</p>
+<p>You should <em>never</em> translate the HTML markup—i.e. <em>do
not</em>
use the “View Source” functionality of your browser to translate
the
raw HTML. Most of it is irrelevant, and automatically inherited from
the markup of the original article. Simply save your translation in a
-plain text file (<samp><span class="file">.txt</span></samp>), preferably in
UTF-8 encoding. You can
+plain text file (<samp>.txt</samp>), preferably in UTF-8 encoding. You can
use any decent text editor for that—Emacs, Vim, gEdit, Kate,
-OpenOffice.org (the file should be saved as <samp><span
class="file">.txt</span></samp>, not
-<samp><span class="file">.odt</span></samp>), etc.
-
- <p>Translate the title, the blue heading (if it differs slightly from the
-title) and the body of the article upto the link ‘<samp><span
class="samp">back to top</span></samp>’.
+OpenOffice.org (the file should be saved as <samp>.txt</samp>, not
+<samp>.odt</samp>), etc.
+</p>
+<p>Translate the title, the blue heading (if it differs slightly from the
+title) and the body of the article upto the link ‘<samp>back to
top</samp>’.
For example, for <a
href="http://www.gnu.org/philosophy/free-sw.html";>http://www.gnu.org/philosophy/free-sw.html</a>
that would be:
+</p>
+<div class="example">
+<pre class="example">What is free software? - GNU Project - Free Software
Foundation (FSF)
+
+What is free software?
-<pre class="example"> The Free Software Definition - GNU Project - Free
Software Foundation (FSF)
+The Free Software Definition
- We maintain this free software definition...
- ...
- ...If you would like to review the complete list of changes, you can
- do so on our cvsweb interface.
-</pre>
- <p>Since web-translators do not speak all languages, it is essential to
+The free software definition presents…
+…
+…You can review the complete list of changes to the page through
+the cvsweb interface.
+</pre></div>
+
+<p>Since web-translators do not speak all languages, it is essential to
mark somehow any inner markup, because very often it is hard to figure
out what translated text should be enclosed inside <code><em></code> or
<code><a></code> elements, to name a few. The easiest way to do this is
just
@@ -83,25 +113,35 @@
suitable. For example, here is how to indicate that the link “History
section” at the first paragraph of the same article should correspond
to “sección historial” in the translation:
+</p>
+<div class="example">
+<pre class="example">Si quisiera revisar los cambios que hemos hecho, por
favor vea la
+{sección historial} más abajo para más información.
+</pre></div>
-<pre class="example"> Si quisiera revisar los cambios que hemos hecho, por
favor vea la
- {sección historial} más abajo para más
información.
-</pre>
- <p>It is not necessary to include the value of the <code>href</code>
attribute,
+<p>It is not necessary to include the value of the <code>href</code> attribute,
as it is already known.
-
- <p>If you wish your name to appear in the footer as a translator of the
-article, please also provide a translation of ‘<samp><span
class="samp">Translation:
-</span><var>your name in your native language</var></samp>’ or
‘<samp><span class="samp">Translated by:
-</span><var>your name in your native language</var></samp>’, as you
prefer. Please also
+</p>
+<p>If you wish your name to appear in the footer as a translator of the
+article, please also provide a translation of ‘<samp>Translation:
+<var>your name in your native language</var></samp>’ or
‘<samp>Translated by:
+<var>your name in your native language</var></samp>’, as you prefer.
Please also
state if you wish your email address to be published (some readers
prefer to send suggestions directly to the translator, but we certainly
do not require that translators must publish their address).
-
- <p>Finally, send the translation to <a
href="mailto:address@hidden";>address@hidden</a>,
+</p>
+<p>Finally, send the translation to <a
href="mailto:address@hidden";>address@hidden</a>,
either inline or as an attachment to your message. Once online, please
check for any errors or omissions that may have resulted from the
conversion process, and report them back.
+</p>
+<hr>
+<div class="header">
+<p>
+Previous: <a href="Submitting-as-PO.html#Submitting-as-PO" accesskey="p"
rel="previous">Submitting as PO</a>, Up: <a href="Submitting.html#Submitting"
accesskey="u" rel="up">Submitting</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
+</div>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Submitting.html 28 Jun 2012 21:04:23 -0000 1.8
+++ web-trans/html_node/Submitting.html 4 Dec 2012 16:24:28 -0000 1.9
@@ -1,64 +1,91 @@
-<html lang="en">
-<head>
-<title>Submitting - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Members.html#Members" title="Members">
-<link rel="prev" href="Joining.html#Joining" title="Joining">
-<link rel="next" href="Leaving-A-Team.html#Leaving-A-Team" title="Leaving A
Team">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Submitting</title>
+
+<meta name="description" content="GNU Web Translators Manual: Submitting">
+<meta name="keywords" content="GNU Web Translators Manual: Submitting">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Members.html#Members" rel="up" title="Members">
+<link href="Submitting-as-PO.html#Submitting-as-PO" rel="next"
title="Submitting as PO">
+<link href="Joining.html#Joining" rel="previous" title="Joining">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Submitting"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Leaving-A-Team.html#Leaving-A-Team">Leaving A Team</a>,
-Previous: <a rel="previous" accesskey="p"
href="Joining.html#Joining">Joining</a>,
-Up: <a rel="up" accesskey="u" href="Members.html#Members">Members</a>
-<hr>
+Next: <a href="Leaving-A-Team.html#Leaving-A-Team" accesskey="n"
rel="next">Leaving A Team</a>, Previous: <a href="Joining.html#Joining"
accesskey="p" rel="previous">Joining</a>, Up: <a href="Members.html#Members"
accesskey="u" rel="up">Members</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="How-To-Submit-a-Translation"></a>
<h3 class="section">2.2 How To Submit a Translation</h3>
<p>Everyone can still submit translations even if there is no translation
team formed. There are two ways to do that—following the existing
procedures, which is the preferred way, and sending it as plain text,
which means more work for a limited group of volunteers (the Translation
-Managers) to convert the translation in <samp><span
class="file">.po</span></samp> format.
+Managers) to convert the translation in <samp>.po</samp> format.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a
href="Submitting-as-PO.html#Submitting-as-PO" accesskey="1">Submitting as
PO</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Submitting-as-Plain-Text.html#Submitting-as-Plain-Text"
accesskey="2">Submitting as Plain Text</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+</table>
+
-<ul class="menu">
-<li><a accesskey="1" href="Submitting-as-PO.html#Submitting-as-PO">Submitting
as PO</a>
-<li><a accesskey="2"
href="Submitting-as-Plain-Text.html#Submitting-as-Plain-Text">Submitting as
Plain Text</a>
-</ul>
- </body></html>
+</body>
+</html>
Index: web-trans/html_node/Summary.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/Summary.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Summary.html 28 Jun 2012 21:04:23 -0000 1.8
+++ web-trans/html_node/Summary.html 4 Dec 2012 16:24:28 -0000 1.9
@@ -1,51 +1,74 @@
-<html lang="en">
-<head>
-<title>Summary - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Translation-Tips.html#Translation-Tips"
title="Translation Tips">
-<link rel="next" href="Copying-This-Manual.html#Copying-This-Manual"
title="Copying This Manual">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Summary</title>
+
+<meta name="description" content="GNU Web Translators Manual: Summary">
+<meta name="keywords" content="GNU Web Translators Manual: Summary">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Mailing-Lists.html#Mailing-Lists" rel="next" title="Mailing Lists">
+<link href="Terminology.html#Terminology" rel="previous" title="Terminology">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Summary"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Copying-This-Manual.html#Copying-This-Manual">Copying This Manual</a>,
-Previous: <a rel="previous" accesskey="p"
href="Translation-Tips.html#Translation-Tips">Translation Tips</a>,
-Up: <a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Copying-This-Manual.html#Copying-This-Manual" accesskey="n"
rel="next">Copying This Manual</a>, Previous: <a
href="Translation-Tips.html#Translation-Tips" accesskey="p"
rel="previous">Translation Tips</a>, Up: <a href="index.html#Top" accesskey="u"
rel="up">Top</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="Overview-Of-The-Translation-Process"></a>
<h2 class="chapter">6 Overview Of The Translation Process</h2>
<p>In general, it is expected that all participants in the translation
@@ -53,22 +76,27 @@
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>This manual is a work in progress—it is not set in stone, and it
+</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
+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="Mailing-Lists.html#Mailing-Lists" accesskey="1">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="Savannah-Projects.html#Savannah-Projects" accesskey="2">Savannah
Projects</a>:</td><td> </td><td align="left"
valign="top">Projects’ membership.
+</td></tr>
+</table>
+
-<ul class="menu">
-<li><a accesskey="1" href="Mailing-Lists.html#Mailing-Lists">Mailing
Lists</a>: Summary of mailing lists.
-<li><a accesskey="2" href="Savannah-Projects.html#Savannah-Projects">Savannah
Projects</a>: Projects' membership.
-</ul>
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Terminology.html 28 Jun 2012 21:04:23 -0000
1.8
+++ web-trans/html_node/Terminology.html 4 Dec 2012 16:24:28 -0000
1.9
@@ -1,53 +1,80 @@
-<html lang="en">
-<head>
-<title>Terminology - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Translation-Tips.html#Translation-Tips"
title="Translation Tips">
-<link rel="prev" href="Distribution-Terms.html#Distribution-Terms"
title="Distribution Terms">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Terminology</title>
+
+<meta name="description" content="GNU Web Translators Manual: Terminology">
+<meta name="keywords" content="GNU Web Translators Manual: Terminology">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Translation-Tips.html#Translation-Tips" rel="up"
title="Translation Tips">
+<link href="Summary.html#Summary" rel="next" title="Summary">
+<link href="Distribution-Terms.html#Distribution-Terms" rel="previous"
title="Distribution Terms">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Terminology"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="Distribution-Terms.html#Distribution-Terms">Distribution Terms</a>,
-Up: <a rel="up" accesskey="u"
href="Translation-Tips.html#Translation-Tips">Translation Tips</a>
-<hr>
+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>
</div>
-
+<hr>
+<a name="Language_002dspecific-Terminology"></a>
<h3 class="section">5.7 Language-specific Terminology</h3>
<p>This is a very important topic, not yet covered by this manual.
+</p>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Tracking-Tasks.html 28 Jun 2012 21:04:23 -0000
1.8
+++ web-trans/html_node/Tracking-Tasks.html 4 Dec 2012 16:24:28 -0000
1.9
@@ -1,51 +1,75 @@
-<html lang="en">
-<head>
-<title>Tracking Tasks - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Review.html#Review" title="Review">
-<link rel="next" href="Unreviewed-Translations.html#Unreviewed-Translations"
title="Unreviewed Translations">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Tracking Tasks</title>
+
+<meta name="description" content="GNU Web Translators Manual: Tracking Tasks">
+<meta name="keywords" content="GNU Web Translators Manual: Tracking Tasks">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Review.html#Review" rel="up" title="Review">
+<link href="Unreviewed-Translations.html#Unreviewed-Translations" rel="next"
title="Unreviewed Translations">
+<link href="Review.html#Review" rel="previous" title="Review">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Tracking-Tasks"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Unreviewed-Translations.html#Unreviewed-Translations">Unreviewed
Translations</a>,
-Up: <a rel="up" accesskey="u" href="Review.html#Review">Review</a>
-<hr>
+Next: <a href="Unreviewed-Translations.html#Unreviewed-Translations"
accesskey="n" rel="next">Unreviewed Translations</a>, Up: <a
href="Review.html#Review" accesskey="u" rel="up">Review</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-
-<h5 class="subsubsection">3.2.1.1 How To Track Tasks and Bugs Using
Savannah</h5>
+<hr>
+<a name="How-To-Track-Tasks-and-Bugs-Using-Savannah"></a>
+<h4 class="subsubsection">3.2.1.1 How To Track Tasks and Bugs Using
Savannah</h4>
<p>The team leader has to make sure that prospective translations are
reviewed, that they do not contain obvious errors and/or confusing
@@ -58,13 +82,13 @@
such tasks. Team co-ordinators often do not manage to make such reviews
in time, resulting in frustration among the team members and generally
slowing the translation process.
-
- <p>A solution to this specific problem is to distribute the load among more
-people. For example: Member D makes a translation of <samp><span
class="file">foo.html</span></samp>
-and uploads <samp><span class="file">foo.</span><var>lang</var><span
class="file">.po</span></samp> in the translation project's
+</p>
+<p>A solution to this specific problem is to distribute the load among more
+people. For example: Member D makes a translation of <samp>foo.html</samp>
+and uploads <samp>foo.<var>lang</var>.po</samp> in the translation
project’s
repository at Savannah, marking the relevant task as “Ready for
Test”
(of course, the equivalent is sending a message with the attached
-translation to the team's mailing list, or similar). Then Member A, B
+translation to the team’s mailing list, or similar). Then Member A, B
and C (or only A and B if C is currently busy) review it independently
and post comments/suggestions/errors in the bug tracker. Discussion
goes on between them and D, problems are rectified and finally the
@@ -76,59 +100,67 @@
shoulders of the leader. You can also set up an internal formal rule:
If a member makes a translation, he has to review another one (or two)
as well.
-
- <p>Some translations can take a fairly long time—the typical example
is a
+</p>
+<p>Some translations can take a fairly long time—the typical example is a
complicated essay or a transcript of a speech. It is best to avoid
duplicate work by indicating, or better—recording, that someone is
-working on this specific article. The ‘<samp><span
class="samp">Tasks</span></samp>’ tracker is suitable
+working on this specific article. The ‘<samp>Tasks</samp>’
tracker is suitable
for this purpose.
-
- <p>It is prudent to discuss the most convenient naming scheme and practice
+</p>
+<p>It is prudent to discuss the most convenient naming scheme and practice
among team members, and publish the convention and/or rules at the
-team's homepage. Note that you can create <dfn>Custom Fields</dfn> in the
+team’s homepage. Note that you can create <em>Custom Fields</em> in the
trackers, and resolved bugs can be searched based on these custom
values.
+</p>
+<p>Thus, a possible straightforward way to manage these tasks is:
+</p>
+<ul>
+<li> If someone starts working on a new translation, she creates a new task
+with a ‘<samp>Subject</samp>’ indicating the article, for example
simply
+‘<samp>philosophy/bsd.html</samp>’ and assigns it to herself.
- <p>Thus, a possible straightforward way to manage these tasks is:
-
- <ul>
-<li>If someone starts working on a new translation, she creates a new task
-with a ‘<samp><span class="samp">Subject</span></samp>’ indicating
the article, for example simply
-‘<samp><span class="samp">philosophy/bsd.html</span></samp>’ and
assigns it to herself.
-
- <li>When the translation is finished and ready for review, the translator
-changes the ‘<samp><span class="samp">Status</span></samp>’ to
“Ready For Test”.
+</li><li> When the translation is finished and ready for review, the translator
+changes the ‘<samp>Status</samp>’ to “Ready For Test”.
- <li>Other members review it, and open bugs relevant to one specific
problem.
+</li><li> Other members review it, and open bugs relevant to one specific
problem.
It is usually better not to conflate two different issues together—it
makes them harder to discuss, and hard to track them by severity. Some
are grammatical errors, some are fundamental ones that change the whole
meaning, some are simply suggestions for improvement. It helps if the
project admin creates new Category fields for every article, for
-instance ‘<samp><span
class="samp">gnu/gnu-history.</span><var>lang</var><span
class="samp">.html</span></samp>’,
-‘<samp><span
class="samp">philosophy/microsoft.</span><var>lang</var><span
class="samp">.html</span></samp>’—it would enable
+instance ‘<samp>gnu/gnu-history.<var>lang</var>.html</samp>’,
+‘<samp>philosophy/microsoft.<var>lang</var>.html</samp>’—it
would enable
functionality like “Show me all bugs ever reported against this
translation”, which is useful.
- <li>Once the bugs (or at least the important bugs) are fixed, the team
+</li><li> Once the bugs (or at least the important bugs) are fixed, the team
leader can make the final review and install the translation in the
-official repository, marking the task as ‘<samp><span
class="samp">Done</span></samp>’. Bugs that are not
-resolved should remain opened, naturally.
-</ul>
+official repository, marking the task as ‘<samp>Done</samp>’.
Bugs that are not
+resolved should remain open, naturally.
+</li></ul>
- <p>Of course, teams can choose to manage these things using external
+<p>Of course, teams can choose to manage these things using external
resources and eventually other bug (or issue) tracking systems.
Whatever you decide, please make sure that bugs can be reported using
free software only, and that the software providing that service is
free. It makes an extremely bad impression if a reader has to report a
-problem about a gnu.org translation via non-free hosting platforms like
+problem about a gnu.org translation via nonfree hosting platforms like
SourceForge.
-
- <p>If you use a certain facility (i.e. a bug tracking system) to manage
+</p>
+<p>If you use a certain facility (i.e. a bug tracking system) to manage
bugs in translations, it is best to take advantage of
-<samp><span class="file">generic.</span><var>lang</var><span
class="file">.html</span></samp> and advertise it on every page.
-See <a
href="../gnun/generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml">generic.LANG.html</a>,
for
+<samp>generic.<var>lang</var>.html</samp> and advertise it on every page.
+See <a
href="http://www.gnu.org/software/trans-coord/manual/gnun/html_node/generic_002eLANG_002ehtml.html#generic_002eLANG_002ehtml";>generic.LANG.html</a>
in <cite>The GNUnited Nations Manual</cite>, for
details.
+</p>
+<hr>
+<div class="header">
+<p>
+Next: <a href="Unreviewed-Translations.html#Unreviewed-Translations"
accesskey="n" rel="next">Unreviewed Translations</a>, Up: <a
href="Review.html#Review" accesskey="u" rel="up">Review</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
+</div>
+
- </body></html>
+</body>
+</html>
Index: web-trans/html_node/Translation-Managers.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Translation-Managers.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Translation-Managers.html 28 Jun 2012 21:04:24
-0000 1.8
+++ web-trans/html_node/Translation-Managers.html 4 Dec 2012 16:24:28
-0000 1.9
@@ -1,55 +1,81 @@
-<html lang="en">
-<head>
-<title>Translation Managers - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Leaders.html#Leaders" title="Leaders">
-<link rel="next" href="Translation-Tips.html#Translation-Tips"
title="Translation Tips">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Translation Managers</title>
+
+<meta name="description" content="GNU Web Translators Manual: Translation
Managers">
+<meta name="keywords" content="GNU Web Translators Manual: Translation
Managers">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Translation-Tips.html#Translation-Tips" rel="next"
title="Translation Tips">
+<link href="Stepping-Down.html#Stepping-Down" rel="previous" title="Stepping
Down">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Translation-Managers"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Translation-Tips.html#Translation-Tips">Translation Tips</a>,
-Previous: <a rel="previous" accesskey="p"
href="Leaders.html#Leaders">Leaders</a>,
-Up: <a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Translation-Tips.html#Translation-Tips" accesskey="n"
rel="next">Translation Tips</a>, Previous: <a href="Leaders.html#Leaders"
accesskey="p" rel="previous">Leaders</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>
-
-<h2 class="chapter">4 ‘<samp><span
class="samp">trans-coord</span></samp>’ Admins</h2>
+<hr>
+<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>
+
- </body></html>
+</body>
+</html>
Index: web-trans/html_node/Translation-Tips.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Translation-Tips.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Translation-Tips.html 28 Jun 2012 21:04:24 -0000
1.8
+++ web-trans/html_node/Translation-Tips.html 4 Dec 2012 16:24:28 -0000
1.9
@@ -1,72 +1,105 @@
-<html lang="en">
-<head>
-<title>Translation Tips - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Translation-Managers.html#Translation-Managers"
title="Translation Managers">
-<link rel="next" href="Summary.html#Summary" title="Summary">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Translation Tips</title>
+
+<meta name="description" content="GNU Web Translators Manual: Translation
Tips">
+<meta name="keywords" content="GNU Web Translators Manual: Translation Tips">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Migrating.html#Migrating" rel="next" title="Migrating">
+<link href="Translation-Managers.html#Translation-Managers" rel="previous"
title="Translation Managers">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Translation-Tips"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="Summary.html#Summary">Summary</a>,
-Previous: <a rel="previous" accesskey="p"
href="Translation-Managers.html#Translation-Managers">Translation Managers</a>,
-Up: <a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Summary.html#Summary" accesskey="n" rel="next">Summary</a>,
Previous: <a href="Translation-Managers.html#Translation-Managers"
accesskey="p" rel="previous">Translation Managers</a>, Up: <a
href="index.html#Top" accesskey="u" rel="up">Top</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-
+<hr>
+<a name="Details-About-The-Translation-Process"></a>
<h2 class="chapter">5 Details About The Translation Process</h2>
<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>Some limitations and oddities are just historical remnants from old
+</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>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="Migrating.html#Migrating"
accesskey="1">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.html#SSI"
accesskey="2">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.html#CSS"
accesskey="3">CSS</a>:</td><td> </td><td align="left"
valign="top">General advice how to use CSS.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="Priorities.html#Priorities"
accesskey="4">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="Capitalization.html#Capitalization"
accesskey="5">Capitalization</a>:</td><td> </td><td align="left"
valign="top">To CAPITALIZE or not?
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Distribution-Terms.html#Distribution-Terms" accesskey="6">Distribution
Terms</a>:</td><td> </td><td align="left" valign="top">Translating
distribution terms.
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="Terminology.html#Terminology"
accesskey="7">Terminology</a>:</td><td> </td><td align="left"
valign="top">Dealing with terminology issues.
+</td></tr>
+</table>
+
-<ul class="menu">
-<li><a accesskey="1" href="Migrating.html#Migrating">Migrating</a>:
How to migrate to the new style.
-<li><a accesskey="2" href="SSI.html#SSI">SSI</a>: Overview of
SSI #include directives.
-<li><a accesskey="3" href="CSS.html#CSS">CSS</a>: General
advice how to use CSS.
-<li><a accesskey="4" href="Priorities.html#Priorities">Priorities</a>:
What to translate as a priority.
-<li><a accesskey="5"
href="Capitalization.html#Capitalization">Capitalization</a>: To
CAPITALIZE or not?
-<li><a accesskey="6"
href="Distribution-Terms.html#Distribution-Terms">Distribution Terms</a>:
Translating distribution terms.
-<li><a accesskey="7" href="Terminology.html#Terminology">Terminology</a>:
Dealing with terminology issues.
-</ul>
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/Unreviewed-Translations.html 28 Jun 2012 21:04:24
-0000 1.8
+++ web-trans/html_node/Unreviewed-Translations.html 4 Dec 2012 16:24:28
-0000 1.9
@@ -1,63 +1,90 @@
-<html lang="en">
-<head>
-<title>Unreviewed Translations - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Review.html#Review" title="Review">
-<link rel="prev" href="Tracking-Tasks.html#Tracking-Tasks" title="Tracking
Tasks">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Unreviewed Translations</title>
+
+<meta name="description" content="GNU Web Translators Manual: Unreviewed
Translations">
+<meta name="keywords" content="GNU Web Translators Manual: Unreviewed
Translations">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Review.html#Review" rel="up" title="Review">
+<link href="Commits.html#Commits" rel="next" title="Commits">
+<link href="Tracking-Tasks.html#Tracking-Tasks" rel="previous" title="Tracking
Tasks">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Unreviewed-Translations"></a>
+<div class="header">
<p>
-Previous: <a rel="previous" accesskey="p"
href="Tracking-Tasks.html#Tracking-Tasks">Tracking Tasks</a>,
-Up: <a rel="up" accesskey="u" href="Review.html#Review">Review</a>
-<hr>
+Previous: <a href="Tracking-Tasks.html#Tracking-Tasks" accesskey="p"
rel="previous">Tracking Tasks</a>, Up: <a href="Review.html#Review"
accesskey="u" rel="up">Review</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>]</p>
</div>
-
-<h5 class="subsubsection">3.2.1.2 How To Proceed With Unreviewed
Translations</h5>
+<hr>
+<a name="How-To-Proceed-With-Unreviewed-Translations"></a>
+<h4 class="subsubsection">3.2.1.2 How To Proceed With Unreviewed
Translations</h4>
<p>Sometimes a translation (typically your own) is not reviewed by anyone
else for a fairly long time. This is unfortunate, but there is no
reason to keep it in draft state forever. If nobody reviewed it for a
substantially long period (like 3 or 4 months), commit it as it is.
Readers may report bugs as well (and they do!).
-
- <p>It is important to record somehow that this published translation still
+</p>
+<p>It is important to record somehow that this published translation still
lacks appropriate review. If the suggestion in the previous section is
-implemented, it would mean leaving the relevant task ‘<samp><span
class="samp">Open</span></samp>’ and
-‘<samp><span class="samp">Ready For Test</span></samp>’ despite
the translation being officially online.
+implemented, it would mean leaving the relevant task
‘<samp>Open</samp>’ and
+‘<samp>Ready For Test</samp>’ despite the translation being
officially online.
You may also add a comment to the PO file.
+</p>
+
- </body></html>
+</body>
+</html>
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.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- web-trans/html_node/index.html 28 Jun 2012 21:04:24 -0000 1.8
+++ web-trans/html_node/index.html 4 Dec 2012 16:24:29 -0000 1.9
@@ -1,148 +1,191 @@
-<html lang="en">
-<head>
-<title>GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled "GNU Free Documentation License."
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: Top</title>
+
+<meta name="description" content="GNU Web Translators Manual: Top">
+<meta name="keywords" content="GNU Web Translators Manual: Top">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="#Top" rel="start" title="Top">
+<link href="#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="../dir/index.html" rel="up" title="(dir)">
+<link href="Introduction.html#Introduction" rel="next" title="Introduction">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<h1 class="settitle">GNU Web Translators Manual</h1>
- <div class="contents">
-<h2>Table of Contents</h2>
-<ul>
-<li><a name="toc_Top" href="index.html#Top">GNU Web Translators Manual</a>
-<li><a name="toc_Introduction" href="Introduction.html#Introduction">1
Introduction</a>
-<li><a name="toc_Members" href="Members.html#Members">2 Team Members</a>
-<ul>
-<li><a href="Joining.html#Joining">2.1 Joining A Team</a>
-<li><a href="Submitting.html#Submitting">2.2 How To Submit a Translation</a>
-<ul>
-<li><a href="Submitting-as-PO.html#Submitting-as-PO">2.2.1 How To Submit a
Translation in PO Format</a>
-<li><a href="Submitting-as-Plain-Text.html#Submitting-as-Plain-Text">2.2.2 How
To Submit a Translation as Plain Text</a>
-</li></ul>
-<li><a href="Leaving-A-Team.html#Leaving-A-Team">2.3 Leaving A Team</a>
-</li></ul>
-<li><a name="toc_Leaders" href="Leaders.html#Leaders">3 Team Co-ordinators</a>
-<ul>
-<li><a href="New-Team.html#New-Team">3.1 How To Form A New Team</a>
-<li><a href="Managing.html#Managing">3.2 The Gentle Art of Managing A
Translation Team</a>
-<ul>
-<li><a href="Review.html#Review">3.2.1 Peer Review</a>
-<ul>
-<li><a href="Tracking-Tasks.html#Tracking-Tasks">3.2.1.1 How To Track Tasks
and Bugs Using Savannah</a>
-<li><a href="Unreviewed-Translations.html#Unreviewed-Translations">3.2.1.2 How
To Proceed With Unreviewed Translations</a>
-</li></ul>
-<li><a href="Commits.html#Commits">3.2.2 CVS Commits And Best Practices</a>
-<li><a href="Savannah.html#Savannah">3.2.3 Taking Advantage of Savannah</a>
-<ul>
-<li><a href="Savannah-Members.html#Savannah-Members">3.2.3.1 Managing
Members</a>
-<li><a href="Savannah-Homepage.html#Savannah-Homepage">3.2.3.2 Homepage of The
Team</a>
-<li><a href="Savannah-Support.html#Savannah-Support">3.2.3.3 Support
Tracker</a>
-<li><a href="Savannah-Tasks.html#Savannah-Tasks">3.2.3.4 Tasks Tracker</a>
-<li><a href="Savannah-Bugs.html#Savannah-Bugs">3.2.3.5 Bugs Tracker</a>
-<li><a href="Savannah-Patch.html#Savannah-Patch">3.2.3.6 Patch Tracker</a>
-<li><a href="Savannah-News.html#Savannah-News">3.2.3.7 News Tracker</a>
-<li><a href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists">3.2.3.8
Managing Mailing Lists</a>
-<li><a href="Savannah-VCS.html#Savannah-VCS">3.2.3.9 Version Control
Systems</a>
-</li></ul>
-<li><a href="Co_002dleaders.html#Co_002dleaders">3.2.4 Promoting Members As
Co-leaders</a>
-</li></ul>
-<li><a href="Reports.html#Reports">3.3 Reporting Team Status</a>
-<li><a href="Stepping-Down.html#Stepping-Down">3.4 How To Retire Painlessly</a>
-</li></ul>
-<li><a name="toc_Translation-Managers"
href="Translation-Managers.html#Translation-Managers">4 ‘<samp><span
class="samp">trans-coord</span></samp>’ Admins</a>
-<li><a name="toc_Translation-Tips"
href="Translation-Tips.html#Translation-Tips">5 Details About The Translation
Process</a>
-<ul>
-<li><a href="Migrating.html#Migrating">5.1 Migration To The New Style</a>
-<li><a href="SSI.html#SSI">5.2 Summary of SSI <code>#include</code>s</a>
-<li><a href="CSS.html#CSS">5.3 How To Use Custom CSS</a>
-<ul>
-<li><a href="topbanner.html#topbanner">5.3.1 Localizing The <samp><span
class="file">topbanner</span></samp> Image</a>
-<li><a href="RTL.html#RTL">5.3.2 Specific Issues Related to RTL</a>
-</li></ul>
-<li><a href="Priorities.html#Priorities">5.4 What To Translate</a>
-<li><a href="Capitalization.html#Capitalization">5.5 When To CAPITALIZE</a>
-<li><a href="Distribution-Terms.html#Distribution-Terms">5.6 Distribution
Terms</a>
-<li><a href="Terminology.html#Terminology">5.7 Language-specific
Terminology</a>
-</li></ul>
-<li><a name="toc_Summary" href="Summary.html#Summary">6 Overview Of The
Translation Process</a>
-<ul>
-<li><a href="Mailing-Lists.html#Mailing-Lists">6.1 Related Mailing Lists</a>
-<li><a href="Savannah-Projects.html#Savannah-Projects">6.2 Savannah Projects
Membership</a>
-</li></ul>
-<li><a name="toc_Copying-This-Manual"
href="Copying-This-Manual.html#Copying-This-Manual">Appendix A GNU Free
Documentation License</a>
-</li></ul>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+<h1 class="settitle" align="center">GNU Web Translators Manual</h1>
+
+
+
+<a name="SEC_Contents"></a>
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="no-bullet">
+ <li><a name="toc-Introduction-1" href="Introduction.html#Introduction">1
Introduction</a></li>
+ <li><a name="toc-Team-Members" href="Members.html#Members">2 Team Members</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Joining-A-Team" href="Joining.html#Joining">2.1 Joining A
Team</a></li>
+ <li><a name="toc-How-To-Submit-a-Translation"
href="Submitting.html#Submitting">2.2 How To Submit a Translation</a>
+ <ul class="no-bullet">
+ <li><a name="toc-How-To-Submit-a-Translation-in-PO-Format"
href="Submitting-as-PO.html#Submitting-as-PO">2.2.1 How To Submit a Translation
in PO Format</a></li>
+ <li><a name="toc-How-To-Submit-a-Translation-as-Plain-Text"
href="Submitting-as-Plain-Text.html#Submitting-as-Plain-Text">2.2.2 How To
Submit a Translation as Plain Text</a></li>
+ </ul></li>
+ <li><a name="toc-Leaving-A-Team-1"
href="Leaving-A-Team.html#Leaving-A-Team">2.3 Leaving A Team</a></li>
+ </ul></li>
+ <li><a name="toc-Team-Co_002dordinators" href="Leaders.html#Leaders">3 Team
Co-ordinators</a>
+ <ul class="no-bullet">
+ <li><a name="toc-How-To-Form-A-New-Team" href="New-Team.html#New-Team">3.1
How To Form A New Team</a></li>
+ <li><a name="toc-The-Gentle-Art-of-Managing-A-Translation-Team"
href="Managing.html#Managing">3.2 The Gentle Art of Managing A Translation
Team</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Peer-Review" href="Review.html#Review">3.2.1 Peer
Review</a>
+ <ul class="no-bullet">
+ <li><a name="toc-How-To-Track-Tasks-and-Bugs-Using-Savannah"
href="Tracking-Tasks.html#Tracking-Tasks">3.2.1.1 How To Track Tasks and Bugs
Using Savannah</a></li>
+ <li><a name="toc-How-To-Proceed-With-Unreviewed-Translations"
href="Unreviewed-Translations.html#Unreviewed-Translations">3.2.1.2 How To
Proceed With Unreviewed Translations</a></li>
+ </ul></li>
+ <li><a name="toc-CVS-Commits-And-Best-Practices"
href="Commits.html#Commits">3.2.2 CVS Commits And Best Practices</a></li>
+ <li><a name="toc-Taking-Advantage-of-Savannah"
href="Savannah.html#Savannah">3.2.3 Taking Advantage of Savannah</a>
+ <ul class="no-bullet">
+ <li><a name="toc-Managing-Members"
href="Savannah-Members.html#Savannah-Members">3.2.3.1 Managing Members</a></li>
+ <li><a name="toc-Homepage-of-The-Team"
href="Savannah-Homepage.html#Savannah-Homepage">3.2.3.2 Homepage of The
Team</a></li>
+ <li><a name="toc-Support-Tracker"
href="Savannah-Support.html#Savannah-Support">3.2.3.3 Support Tracker</a></li>
+ <li><a name="toc-Tasks-Tracker"
href="Savannah-Tasks.html#Savannah-Tasks">3.2.3.4 Tasks Tracker</a></li>
+ <li><a name="toc-Bugs-Tracker"
href="Savannah-Bugs.html#Savannah-Bugs">3.2.3.5 Bugs Tracker</a></li>
+ <li><a name="toc-Patch-Tracker"
href="Savannah-Patch.html#Savannah-Patch">3.2.3.6 Patch Tracker</a></li>
+ <li><a name="toc-News-Tracker"
href="Savannah-News.html#Savannah-News">3.2.3.7 News Tracker</a></li>
+ <li><a name="toc-Managing-Mailing-Lists"
href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists">3.2.3.8 Managing
Mailing Lists</a></li>
+ <li><a name="toc-Version-Control-Systems"
href="Savannah-VCS.html#Savannah-VCS">3.2.3.9 Version Control Systems</a></li>
+ </ul></li>
+ <li><a name="toc-Promoting-Members-As-Co_002dleaders"
href="Co_002dleaders.html#Co_002dleaders">3.2.4 Promoting Members As
Co-leaders</a></li>
+ </ul></li>
+ <li><a name="toc-Reporting-Team-Status" href="Reports.html#Reports">3.3
Reporting Team Status</a></li>
+ <li><a name="toc-How-To-Retire-Painlessly"
href="Stepping-Down.html#Stepping-Down">3.4 How To Retire Painlessly</a></li>
+ </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>
+ <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>
+ </ul></li>
+ <li><a name="toc-What-To-Translate" href="Priorities.html#Priorities">5.4
What To Translate</a></li>
+ <li><a name="toc-When-To-CAPITALIZE"
href="Capitalization.html#Capitalization">5.5 When To CAPITALIZE</a></li>
+ <li><a name="toc-Distribution-Terms-1"
href="Distribution-Terms.html#Distribution-Terms">5.6 Distribution
Terms</a></li>
+ <li><a name="toc-Language_002dspecific-Terminology"
href="Terminology.html#Terminology">5.7 Language-specific Terminology</a></li>
+ </ul></li>
+ <li><a name="toc-Overview-Of-The-Translation-Process"
href="Summary.html#Summary">6 Overview Of The Translation Process</a>
+ <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>
</div>
-<div class="node">
<a name="Top"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n"
href="Introduction.html#Introduction">Introduction</a>,
-Up: <a rel="up" accesskey="u" href="../index.html#dir">(dir)</a>
-<hr>
+Next: <a href="Introduction.html#Introduction" accesskey="n"
rel="next">Introduction</a>, Up: <a href="../dir/index.html" accesskey="u"
rel="up">(dir)</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
-
-<h2 class="unnumbered">GNU Web Translators Manual</h2>
+<hr>
+<a name="GNU-Web-Translators-Manual"></a>
+<h1 class="top">GNU Web Translators Manual</h1>
<p>This manual is a guide for the GNU Web Translators.<br> Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- <pre class="sp">
-
-</pre>
-Copyright © 2009, 2010, 2011, 2012 Free Software
+</p><br>
+<p>Copyright © 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
-
- <blockquote>
-Permission is granted to copy, distribute and/or modify this document
+</p>
+<blockquote>
+<p>Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled “GNU Free
Documentation License.”
-</blockquote>
+</p></blockquote>
-<ul class="menu">
-<li><a accesskey="1" href="Introduction.html#Introduction">Introduction</a>:
Begin of the journey.
-<li><a accesskey="2" href="Members.html#Members">Members</a>:
Information for translation team members.
-<li><a accesskey="3" href="Leaders.html#Leaders">Leaders</a>:
Guidelines and procedures for team leaders.
-<li><a accesskey="4"
href="Translation-Managers.html#Translation-Managers">Translation Managers</a>:
Responsibilities of the GNU Web Translation
+
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a
href="Introduction.html#Introduction"
accesskey="1">Introduction</a>:</td><td> </td><td align="left"
valign="top">Begin of the journey.
+</td></tr>
+<tr><td align="left" valign="top">• <a href="Members.html#Members"
accesskey="2">Members</a>:</td><td> </td><td align="left"
valign="top">Information for translation team members.
+</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.
-<li><a accesskey="5" href="Translation-Tips.html#Translation-Tips">Translation
Tips</a>: Explanation of some non-obvious things.
-<li><a accesskey="6" href="Summary.html#Summary">Summary</a>:
Overview.
-<!-- * Index:: -->
-<li><a accesskey="7"
href="Copying-This-Manual.html#Copying-This-Manual">Copying This Manual</a>:
The GNU Free Documentation License.
-</ul>
+</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.
+</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.
+</td></tr>
+</table>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Introduction.html#Introduction" accesskey="n"
rel="next">Introduction</a>, Up: <a href="../dir/index.html" accesskey="u"
rel="up">(dir)</a> [<a href="#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
+</div>
+
- </body></html>
+</body>
+</html>
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.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- web-trans/html_node/topbanner.html 28 Jun 2012 21:04:24 -0000 1.9
+++ web-trans/html_node/topbanner.html 4 Dec 2012 16:24:29 -0000 1.10
@@ -1,87 +1,117 @@
-<html lang="en">
-<head>
-<title>topbanner - GNU Web Translators Manual</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="GNU Web Translators Manual">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="CSS.html#CSS" title="CSS">
-<link rel="next" href="RTL.html#RTL" title="RTL">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
<!--
This manual is a guide for the GNU Web Translators.
-Last updated on
+ Last updated on
28.06.2012, for GNUnited Nations version 0.6.
- Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Copyright (C) 2009, 2010, 2011, 2012 Free Software
Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.3 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled ``GNU Free Documentation License.''
- -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled "GNU Free
+Documentation License." -->
+<!-- Created by GNU Texinfo 4.13.90, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>GNU Web Translators Manual: topbanner</title>
+
+<meta name="description" content="GNU Web Translators Manual: topbanner">
+<meta name="keywords" content="GNU Web Translators Manual: topbanner">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="CSS.html#CSS" rel="up" title="CSS">
+<link href="RTL.html#RTL" rel="next" title="RTL">
+<link href="CSS.html#CSS" rel="previous" title="CSS">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="topbanner"></a>
+<div class="header">
<p>
-Next: <a rel="next" accesskey="n" href="RTL.html#RTL">RTL</a>,
-Up: <a rel="up" accesskey="u" href="CSS.html#CSS">CSS</a>
-<hr>
+Next: <a href="RTL.html#RTL" accesskey="n" rel="next">RTL</a>, Up: <a
href="CSS.html#CSS" accesskey="u" rel="up">CSS</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>]</p>
</div>
+<hr>
+<a name="Localizing-The-topbanner-Image"></a>
+<h4 class="subsection">5.3.1 Localizing The <samp>topbanner</samp> Image</h4>
-<h4 class="subsection">5.3.1 Localizing The <samp><span
class="file">topbanner</span></samp> Image</h4>
-
-<p>If you'd like the nice gnu image to be localized (i.e. “GNU Operating
+<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:
-
- <ol type=1 start=1>
-<li>Copy <samp><span class="file">graphics/topbanner.svg</span></samp> as
-<samp><span class="file">graphics/topbanner.</span><var>lang</var><span
class="file">.svg</span></samp> where <var>lang</var> is the
+</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><span class="file">graphics/topbanner.</span><var>lang</var><span
class="file">.png</span></samp> (File -> Export Bitmap<small
class="dots">...</small>).
+<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
rel="footnote" href="#fn-1" name="fnd-1"><sup>1</sup></a>.
+Image). Don’t forget to save and <code>cvs add</code> the files<a
name="DOCF6" href="#FOOT6"><sup>6</sup></a>.
- <li>Create a <samp><span class="file">style.</span><var>lang</var><span
class="file">.css</span></samp> at the toplevel directory, if it
-doesn't exist already. Normally, you would need only one line in it,
+</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:
- <pre class="example">
#logo{background:url(/graphics/topbanner.<var>lang</var>.png) no-repeat;}
-</pre>
- <li>If not done already for other reasons, update
-<samp><span class="file">banner.</span><var>lang</var><span
class="file">.html</span></samp> to include the language specific
-<samp><span class="file">style.</span><var>lang</var><span
class="file">.css</span></samp>. See <a href="CSS.html#CSS">CSS</a>.
- </ol>
+<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.html#CSS">CSS</a>.
+</li></ol>
- <p>If you feel uncomfortable manipulating images—don't despair! Send
a
+<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>.
-
- <div class="footnote">
+</p>
+<div class="footnote">
<hr>
-<h4>Footnotes</h4><p class="footnote"><small>[<a name="fn-1"
href="#fnd-1">1</a>]</small> This
+<h4 class="footnotes-heading">Footnotes</h4>
+
+<h3><a name="FOOT6" href="#DOCF6">(6)</a></h3>
+<p>This
advice applies to all new files, of course.</p>
+</div>
- <hr></div>
- </body></html>
+</body>
+</html>
- trans-coord/manual gnun/gnun.dvi.gz gnun/gnun.h...,
Pavel Kharitonov <=