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

[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:&nbsp;<a rel="next" accesskey="n" href="#Introduction">Introduction</a>,
-Up:&nbsp;<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&rsquo;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&rsquo;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&rsquo;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&rsquo;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> &nbsp; [<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 &copy; 2008, 2009, 2010, 2011, 2012 Free Software
+</p><br>
+<p>Copyright &copy; 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 &ldquo;GNU Free
 Documentation License.&rdquo;
-</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:&nbsp;<a rel="next" accesskey="n" href="#Usage">Usage</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Top">Top</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a href="#Introduction" 
accesskey="1">Introduction</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Overview of GNUnited Nations.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Usage" 
accesskey="2">Usage</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Basic usage, invocation and tips.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Internals" 
accesskey="3">Internals</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Dive into GNUN.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Bugs" 
accesskey="4">Bugs</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">How to report bugs.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Index" 
accesskey="5">Index</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Copying-This-Manual" 
accesskey="6">Copying This Manual</a>:</td><td>&nbsp;&nbsp;</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> &nbsp; [<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&rsquo;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">&bull; <a href="#Overview" 
accesskey="1">Overview</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">What is GNUN and why is necessary?
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Concepts" 
accesskey="2">Concepts</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Basic concepts and goals.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Advantages" 
accesskey="3">Advantages</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">The goodness GNUN brings.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Disadvantages" 
accesskey="4">Disadvantages</a>:</td><td>&nbsp;&nbsp;</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:&nbsp;<a rel="next" accesskey="n" href="#Concepts">Concepts</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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:&nbsp;<a rel="next" accesskey="n" href="#Advantages">Advantages</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Overview">Overview</a>,
-Up:&nbsp;<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> &nbsp; [<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 &ldquo;PO template&rdquo;) 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">     .---&lt;--- * Original ARTICLE.html
-     |
-     |   .---&gt; ARTICLE.pot ---&gt; * ARTICLE.LANG.po ---&gt;---.
-     `---+                                               |
+</p>
+<div class="example">
+<pre class="example">.---&lt;--- * Original ARTICLE.html
+|
+|   .---&gt; ARTICLE.pot ---&gt; * ARTICLE.LANG.po ---&gt;---.
+`---+                                               |
          `---&gt;---.   .------&lt;----------------------------'
                  |   |
                  |   `---.
                  |       +---&gt; Translated ARTICLE.LANG.html
                  `-------'
-</pre>
-   <p>The indication &lsquo;<samp><span class="samp">*</span></samp>&rsquo; 
appears in two places in this picture, and means
+</pre></div>
+
+<p>The indication &lsquo;<samp>*</samp>&rsquo; 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 &lsquo;<samp><span class="samp">make -C 
server/gnun</span></samp>&rsquo;.  This is the primary way to invoke
+running &lsquo;<samp>make -C server/gnun</samp>&rsquo;.  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
-&lsquo;<samp><span class="samp">gettext</span></samp>&rsquo; 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>
+&lsquo;<samp>gettext</samp>&rsquo; 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
-&lt;<code>http://www.gnu.org/philosophy/free-sw.html</code>&gt; 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&rsquo;s control is kept in the 
&lsquo;www&rsquo;
+repository under a special directory <samp>po/</samp>, which is a
+sub-directory of the relevant directory in the &lsquo;www&rsquo; tree.  So, for
+&lsquo;<code>http://www.gnu.org/philosophy/free-sw.html</code>&rsquo; 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 &ldquo;inject&rdquo; general information about a
 translation team&mdash;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&rsquo; credits are
+also handled, as well as translators&rsquo; 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:&nbsp;<a rel="next" accesskey="n" href="#Disadvantages">Disadvantages</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Concepts">Concepts</a>,
-Up:&nbsp;<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> &nbsp; [<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 &lsquo;www&rsquo; 
repository).  A
 single change to such a file will affect literally <em>all</em>
 articles, translated or not.
 
-     <li>Urgent notices.  Sometimes an &ldquo;urgent&rdquo; notice is added by 
the
+</li><li> Urgent notices.  Sometimes an &ldquo;urgent&rdquo; 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&rsquo; 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&mdash;lots of errors and 
typos
+</li><li> Simplification of the translation process&mdash;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&mdash;it would be substantially easier to
+</li><li> Markup consistency site-wide&mdash;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 &ldquo;fuzzy&rdquo; strings in the PO files, newly added ones will
 appear as &ldquo;untranslated&rdquo;, and deleted will appear as 
&ldquo;obsolete&rdquo;. 
 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:&nbsp;<a rel="previous" accesskey="p" 
href="#Advantages">Advantages</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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:&nbsp;<a rel="next" accesskey="n" href="#Internals">Internals</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Introduction">Introduction</a>,
-Up:&nbsp;<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> &nbsp; [<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>&mdash;Murphy's Law
-
-                                              <p>Murphy is an optimist.
-                                               <p>&mdash;O'Rielly's Law
-</div>
-
-   <pre class="sp">
-
-</pre>
+<p align="right">If anything may go wrong, it will definitely go wrong.
+&mdash;Murphy&rsquo;s Law
+</p>
+<p align="right">Murphy is an optimist.
+&mdash;O&rsquo;Rielly&rsquo;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, &ldquo;invoking&rdquo; 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> &hellip;]</code> while the working 
directory is
+the root in the &lsquo;www&rsquo; 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">&bull; <a href="#Invoking-GNUN" 
accesskey="1">Invoking GNUN</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">How to trigger a (re)build.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Main-Variables" 
accesskey="2">Main Variables</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Specifying what to build.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#PO-Files" accesskey="3">PO 
Files</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">The gentle 
art of editing PO files.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Webmaster-Tips" 
accesskey="4">Webmaster Tips</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">The webmaster&rsquo;s guide to GNUnited Nations&rsquo;
                           galaxy. 
-</ul>
+</td></tr>
+</table>
 
-<div class="node">
+<hr>
 <a name="Invoking-GNUN"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Main-Variables">Main 
Variables</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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
+&lsquo;www&rsquo; 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 &lsquo;<samp><span 
class="samp">$(pkgdatadadir)</span></samp>&rsquo; (<samp><span 
class="file">/usr/local/share/gnun</span></samp> with
-the default &lsquo;<samp><span class="samp">prefix</span></samp>&rsquo;) so 
you can just create symlinks pointing to
+installed in &lsquo;<samp>$(pkgdatadadir)</samp>&rsquo; 
(<samp>/usr/local/share/gnun</samp> with
+the default &lsquo;<samp>prefix</samp>&rsquo;) 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 &lsquo;www&rsquo;.)
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a href="#Runtime-Variables" 
accesskey="1">Runtime Variables</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Variables to control the build process.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Special-Targets" 
accesskey="2">Special Targets</a>:</td><td>&nbsp;&nbsp;</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:&nbsp;<a rel="next" accesskey="n" href="#Special-Targets">Special 
Targets</a>,
-Up:&nbsp;<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> &nbsp; 
[<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>&lsquo;<samp><span 
class="samp">VCS=no</span></samp>&rsquo;<dt>&lsquo;<samp><span 
class="samp">...</span></samp>&rsquo;<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>&lsquo;<samp>VCS=no</samp>&rsquo;</dt>
+<dt>&lsquo;<samp>&hellip;</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">VCS=yes</span></samp>&rsquo;<dd>Automatically add any new files in 
the repository (CVS, Subversion or
+that expects assigning the value &lsquo;no&rsquo;.
+</p>
+</dd>
+<dt>&lsquo;<samp>VCS=yes</samp>&rsquo;</dt>
+<dd><p>Automatically add any new files in the repository (CVS, Subversion or
 GNU Bazaar&mdash;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>&lsquo;<samp><span 
class="samp">VCS=always</span></samp>&rsquo;<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>&lsquo;<samp>VCS=always</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">VALIDATE=no</span></samp>&rsquo;<dt>&lsquo;<samp><span 
class="samp">...</span></samp>&rsquo;<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>&lsquo;<samp>VALIDATE=no</samp>&rsquo;</dt>
+<dt>&lsquo;<samp>&hellip;</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">VALIDATE=yes</span></samp>&rsquo;<dd>Validates all original 
articles before generating the POTs, to ensure
+</p>
+</dd>
+<dt>&lsquo;<samp>VALIDATE=yes</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">NOTIFY=no</span></samp>&rsquo;<dt>&lsquo;<samp><span 
class="samp">...</span></samp>&rsquo;<dd>Do not send email notifications about 
errors.  This is the default.
-
-     <br><dt>&lsquo;<samp><span 
class="samp">NOTIFY=yes</span></samp>&rsquo;<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>&lsquo;<samp>NOTIFY=no</samp>&rsquo;</dt>
+<dt>&lsquo;<samp>&hellip;</samp>&rsquo;</dt>
+<dd><p>Do not send email notifications about errors.  This is the default.
+</p>
+</dd>
+<dt>&lsquo;<samp>NOTIFY=yes</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">ANNOUNCE=yes</span></samp>&rsquo;<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>&lsquo;<samp>ANNOUNCE=yes</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">VERBOSE=yes</span></samp>&rsquo;<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>&lsquo;<samp>VERBOSE=yes</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">GRACE=</span><var>days</var></samp>&rsquo;<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>&lsquo;<samp>GRACE=<var>days</var></samp>&rsquo;</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 &ldquo;grace&rdquo; 
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>&lsquo;<samp><span 
class="samp">OUTDATED-GRACE=</span><var>days</var></samp>&rsquo;<dd>Grace 
period for the out-of-date notice.  When the variable
+</p>
+<a name="index-OUTDATED_002dGRACE"></a>
+</dd>
+<dt>&lsquo;<samp>OUTDATED-GRACE=<var>days</var></samp>&rsquo;</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 &lsquo;www&rsquo; 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>&lsquo;<samp><span 
class="samp">TEAM=</span><var>lang</var></samp>&rsquo;<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>&lsquo;<samp>TEAM=<var>lang</var></samp>&rsquo;</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)&mdash;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&mdash;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:&nbsp;<a rel="previous" accesskey="p" 
href="#Runtime-Variables">Runtime Variables</a>,
-Up:&nbsp;<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> &nbsp; [<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&mdash;the 
filesets they affect are
+<code>make</code> reads the makefiles&mdash;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">&bull; <a href="#no_002dgrace_002ditems" 
accesskey="1">no-grace-items</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#update_002dlocalized_002dURLs" 
accesskey="2">update-localized-URLs</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#sync" 
accesskey="3">sync</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#report" 
accesskey="4">report</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#triggers" 
accesskey="5">triggers</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#validate_002dall" 
accesskey="6">validate-all</a>:</td><td>&nbsp;&nbsp;</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:&nbsp;<a rel="next" accesskey="n" 
href="#update_002dlocalized_002dURLs">update-localized-URLs</a>,
-Up:&nbsp;<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> &nbsp; [<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:&nbsp;<a rel="next" accesskey="n" href="#sync">sync</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#no_002dgrace_002ditems">no-grace-items</a>,
-Up:&nbsp;<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> 
&nbsp; [<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:&nbsp;<a rel="next" accesskey="n" href="#report">report</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#update_002dlocalized_002dURLs">update-localized-URLs</a>,
-Up:&nbsp;<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> &nbsp; [<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,
+&lsquo;www&rsquo;.  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 &lsquo;official instance&rsquo; 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 &lsquo;build&rsquo; 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
+&lsquo;yes&rsquo; then the synchronized files are committed to the 
&lsquo;testing&rsquo;
 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 &ldquo;verbatim&rdquo; 
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 &ldquo;verbatim&rdquo; 
server templates
+that are not under GNUN&rsquo;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:&nbsp;<a rel="next" accesskey="n" href="#triggers">triggers</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#sync">sync</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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:&nbsp;<a rel="next" accesskey="n" 
href="#validate_002dall">validate-all</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#report">report</a>,
-Up:&nbsp;<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> &nbsp; [<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&mdash;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 &hellip;; 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 &amp;&gt;/dev/null; \
+</p>
+<div class="example">
+<pre class="example">25 4,12,20 * * *  cd $HOME/projects/www; cvs -q update 
&amp;&gt;/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."; \
+                    &quot;Automatic update by GNUnited Nations.&quot;; \
                          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 &ldquo;bound branch&rdquo; 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 &ldquo;triggered&rdquo; after the main build.
-
-<div class="node">
-<a name="validate-all"></a>
+</p>
+<hr>
 <a name="validate_002dall"></a>
-<p><hr>
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#triggers">triggers</a>,
-Up:&nbsp;<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> &nbsp; 
[<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&rsquo;s
+control.  It is needed because GNUN doesn&rsquo;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:&nbsp;<a rel="next" accesskey="n" href="#PO-Files">PO Files</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Invoking-GNUN">Invoking 
GNUN</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo; 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>&lsquo;<samp><span 
class="samp">TEMPLATE_LINGUAS</span></samp>&rsquo;<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>&lsquo;<samp>TEMPLATE_LINGUAS</samp>&rsquo;</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&rsquo;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>&lsquo;<samp><span 
class="samp">extra-templates</span></samp>&rsquo;<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>&lsquo;<samp>extra-templates</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">optional-templates</span></samp>&rsquo;<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>&lsquo;<samp>optional-templates</samp>&rsquo;</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&rsquo;t been converted to PO files won&rsquo;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>&lsquo;<samp><span 
class="samp">FUZZY_DIFF_LINGUAS</span></samp>&rsquo;<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>&lsquo;<samp>FUZZY_DIFF_LINGUAS</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">HOME_LINGUAS</span></samp>&rsquo;<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>&lsquo;<samp><span
 class="samp">ROOT</span></samp>&rsquo;<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>&lsquo;<samp>ROOT</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">ALL_DIRS</span></samp>&rsquo;<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>&lsquo;<samp><span 
class="samp">gnu</span></samp>&rsquo;<dt>&lsquo;<samp><span 
class="samp">philosophy</span></samp>&rsquo;<dt>&lsquo;<samp><span 
class="samp">...directory...</span></samp>&rsquo;<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>&lsquo;<samp>ALL_DIRS</samp>&rsquo;</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>&lsquo;<samp>gnu</samp>&rsquo;</dt>
+<dt>&lsquo;<samp>philosophy</samp>&rsquo;</dt>
+<dt>&lsquo;<samp>&hellip;directory&hellip;</samp>&rsquo;</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:&nbsp;<a rel="next" accesskey="n" href="#Webmaster-Tips">Webmaster 
Tips</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Main-Variables">Main 
Variables</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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&rsquo;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
-&lt;RET&gt;</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&mdash;the GNOME PO editor.  See
+</li><li> Gtranslator&mdash;the GNOME PO editor.  See
 <a 
href="http://projects.gnome.org/gtranslator/";>http://projects.gnome.org/gtranslator/</a>.
 
-     <li>Lokalize&mdash;the KDE 4 editor.  See
+</li><li> Lokalize&mdash;the KDE 4 editor.  See
 <a 
href="http://userbase.kde.org/Lokalize";>http://userbase.kde.org/Lokalize</a>.
 
-     <li>KBabel&mdash;the KDE 3 editor.  No longer supported, but might be
+</li><li> KBabel&mdash;the KDE 3 editor.  No longer supported, but might be
 available on some old systems.
 
-     <li>Poedit&mdash;another popular editor that is based on the 
<code>wxWidgets</code>
+</li><li> Poedit&mdash;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&mdash;a relevantly new editor that supports also the XLIFF 
format
+</li><li> Virtaal&mdash;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&mdash;ftplugin for the Vim editor.  The best option for people who
+</li><li> po.vim&mdash;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">&bull; <a href="#New-Translation" 
accesskey="1">New Translation</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">How to start a new translation.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Migrating" 
accesskey="2">Migrating</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">How to migrate an existing translation to a PO
+                          format under GNUN&rsquo;s control.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#GNU-News" accesskey="3">GNU 
News</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to handle 
&ldquo;whatsnew&rdquo; (a.k.a. &ldquo;gnunews&rdquo;).
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#PO-Tips" accesskey="4">PO 
Tips</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Tips and hints 
for translators.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#generic_002eLANG_002ehtml" 
accesskey="5">generic.LANG.html</a>:</td><td>&nbsp;&nbsp;</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">&bull; <a href="#languages_002etxt" 
accesskey="6">languages.txt</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Specifying canonical names for languages.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#PO-Files-and-Team" 
accesskey="7">PO Files and Team</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">How to maintain translations in the team&rsquo;s
                           repository. 
-<li><a accesskey="8" href="#Compendia">Compendia</a>:            Using 
translation memory.
-
-   </ul>
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Compendia" 
accesskey="8">Compendia</a>:</td><td>&nbsp;&nbsp;</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:&nbsp;<a rel="next" accesskey="n" href="#Migrating">Migrating</a>,
-Up:&nbsp;<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> &nbsp; [<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 &ldquo;templated&rdquo; (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 &lt;address@hidden&gt;, YEAR.
+#
+#, fuzzy
+msgid &quot;&quot;
+msgstr &quot;&quot;
+&quot;Project-Id-Version: PACKAGE VERSION\n&quot;
+&quot;POT-Creation-Date: 2008-02-06 16:25-0500\n&quot;
+&quot;PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n&quot;
+&quot;Last-Translator: FULL NAME &lt;address@hidden&gt;\n&quot;
+&quot;Language-Team: LANGUAGE &lt;address@hidden&gt;\n&quot;
+&quot;MIME-Version: 1.0\n&quot;
+&quot;Content-Type: text/plain; charset=CHARSET\n&quot;
+&quot;Content-Transfer-Encoding: ENCODING\n&quot;
+</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 &lt;address@hidden&gt;, 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 &lt;address@hidden&gt;\n"
-     "Language-Team: LANGUAGE &lt;address@hidden&gt;\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>&lsquo;<samp><span 
class="samp">Project-Id-Version</span></samp>&rsquo;<dd>Add here the filename 
of the original article, without the
+</p>
+<a name="index-PO-headers"></a>
+<dl compact="compact">
+<dt>&lsquo;<samp>Project-Id-Version</samp>&rsquo;</dt>
+<dd><p>Add here the filename of the original article, without the
 sub-directory, like &ldquo;body-include-1.html&rdquo; or 
&ldquo;free-sw.html&rdquo;.
-
-     <br><dt>&lsquo;<samp><span 
class="samp">POT-Creation-Date</span></samp>&rsquo;<dd>Do not edit this field, 
it is already set when the POT is created.
-
-     <br><dt>&lsquo;<samp><span 
class="samp">PO-Revision-Date</span></samp>&rsquo;<dd>Likewise, do not edit.  
This field is automatically filled in when you
+</p>
+</dd>
+<dt>&lsquo;<samp>POT-Creation-Date</samp>&rsquo;</dt>
+<dd><p>Do not edit this field, it is already set when the POT is created.
+</p>
+</dd>
+<dt>&lsquo;<samp>PO-Revision-Date</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">Last-Translator</span></samp>&rsquo;<dd>The name and email address 
of the last translator who has edited the
+</p>
+</dd>
+<dt>&lsquo;<samp>Last-Translator</samp>&rsquo;</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 &lt;address@hidden&gt;
-</pre>
-     <br><dt>&lsquo;<samp><span 
class="samp">Language-Team</span></samp>&rsquo;<dd>This field should contain 
the mailing list on which the translation
-team can be reached&mdash;usually <a 
href="mailto:address@hidden";>www-LANG-<small 
class="dots">...</small>@gnu.org</a>. 
+</p>
+<div class="example">
+<pre class="example">Elvis Parsley &lt;address@hidden&gt;
+</pre></div>
+
+</dd>
+<dt>&lsquo;<samp>Language-Team</samp>&rsquo;</dt>
+<dd><p>This field should contain the mailing list on which the translation
+team can be reached&mdash;usually <a 
href="mailto:www-LANG-&hellip;@gnu.org";>www-LANG-&hellip;@gnu.org</a>.
 Example:
-
-     <pre class="example">          Czech &lt;address@hidden&gt;
-</pre>
-     <br><dt>&lsquo;<samp><span 
class="samp">MIME-Version</span></samp>&rsquo;<dd>Leave it like it is.
-
-     <br><dt>&lsquo;<samp><span 
class="samp">Content-Type</span></samp>&rsquo;<dd>Usually this is 
<code>text/plain; charset=UTF-8</code>; change the charset
+</p>
+<div class="example">
+<pre class="example">Czech &lt;address@hidden&gt;
+</pre></div>
+
+</dd>
+<dt>&lsquo;<samp>MIME-Version</samp>&rsquo;</dt>
+<dd><p>Leave it like it is.
+</p>
+</dd>
+<dt>&lsquo;<samp>Content-Type</samp>&rsquo;</dt>
+<dd><p>Usually this is <code>text/plain; charset=UTF-8</code>; change the 
charset
 accordingly.
-
-     <br><dt>&lsquo;<samp><span 
class="samp">Content-Transfer-Encoding</span></samp>&rsquo;<dd>Set this to 
<code>8bit</code>.  Note that the PO file header ends with this
-field, and it should contain a newline (&lsquo;<samp><span 
class="samp">\n</span></samp>&rsquo;).  Unfortunately, some
+</p>
+</dd>
+<dt>&lsquo;<samp>Content-Transfer-Encoding</samp>&rsquo;</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 (&lsquo;<samp>\n</samp>&rsquo;).  
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&rsquo;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 &lt;address@hidden&gt;, 2008.
+#
+msgid &quot;&quot;
+msgstr &quot;&quot;
+&quot;Project-Id-Version: free-sw.html\n&quot;
+&quot;POT-Creation-Date: 2008-02-06 16:25-0500\n&quot;
+&quot;PO-Revision-Date: 2008-02-09 15:23+0200\n&quot;
+&quot;Last-Translator: Yavor Doganov &lt;address@hidden&gt;\n&quot;
+&quot;Language-Team: Bulgarian &lt;address@hidden&gt;\n&quot;
+&quot;MIME-Version: 1.0\n&quot;
+&quot;Content-Type: text/plain; charset=UTF-8\n&quot;
+&quot;Content-Transfer-Encoding: 8-bit\n&quot;
+</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 &lt;address@hidden&gt;, 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 &lt;address@hidden&gt;\n"
-     "Language-Team: Bulgarian &lt;address@hidden&gt;\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 &ldquo;fuzzy&rdquo; marker; you should 
&ldquo;unfuzzy&rdquo; the
+<p>Notice the absence of the &ldquo;fuzzy&rdquo; marker; you should 
&ldquo;unfuzzy&rdquo; the
 header after entering the necessary information (this is done by
-simply pressing &lt;TAB&gt; 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>&rsquo;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>&lsquo;<samp><span class="samp">*GNUN-SLOT: TRANSLATOR'S 
NOTES*</span></samp>&rsquo;<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>&lsquo;<samp>*GNUN-SLOT: TRANSLATOR'S NOTES*</samp>&rsquo;</dt>
+<dd><p>This is for translator&rsquo;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, &lt;SPC&gt;.
-
-     <p><a name="index-credits_002c-translators-68"></a><a 
name="index-translators_0027-credits-69"></a><br><dt>&lsquo;<samp><span 
class="samp">*GNUN-SLOT: TRANSLATOR'S CREDITS*</span></samp>&rsquo;<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>&lsquo;<samp>*GNUN-SLOT: TRANSLATOR'S CREDITS*</samp>&rsquo;</dt>
+<dd><p>This is again optional, and should contain the name (and address) of
 the person who made the translation.  &ldquo;Translate&rdquo; this string as a
-space (&lt;SPC&gt;) 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 &ldquo;normalize&rdquo; 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 ()
+  &quot;Filter current po-mode buffer through `msgcat' tool to wrap all 
lines.&quot;
        (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 &quot;po-wrap.&quot;))
+           (tmp-buf (generate-new-buffer &quot;*temp*&quot;)))
        (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)))
+                   &quot;msgcat&quot; 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&rsquo;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">&bull; <a href="#Notes-Slot" 
accesskey="1">Notes Slot</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">How to handle translator&rsquo;s notes.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Credits-Slot" 
accesskey="2">Credits Slot</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Translator&rsquo;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:&nbsp;<a rel="next" accesskey="n" href="#Credits-Slot">Credits Slot</a>,
-Up:&nbsp;<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> &nbsp; 
[<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&rsquo;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&rsquo;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 &ldquo;translate&rdquo; the
-<code>msgstr</code> as a space (&lt;SPC&gt;)&mdash;otherwise the PO file will 
be
+translation doesn&rsquo;t have notes, you should &ldquo;translate&rdquo; the
+<code>msgstr</code> as a space (<tt class="key">SPC</tt>)&mdash;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&rsquo; notes in a PO file:
+</p>
+<div class="example">
+<pre class="example"># type: Content of: &lt;p&gt;
+msgid &quot;&quot;
+&quot;To understand the concept, you should think of &lt;q&gt;free&lt;/q&gt; 
&quot;
+&quot;as in &lt;q&gt;free speech,&lt;/q&gt; not as in &lt;q&gt;free 
beer.&lt;/q&gt;&quot;
+msgstr &quot;&quot;
+&quot;Translated message, where you want to clarify beer&lt;sup&gt;&lt;a &quot;
+&quot;href=\&quot;#TransNote1\&quot;&gt;1&lt;/a&gt;&lt;/sup&gt;, presumably 
because the &quot;
+&quot;expression in your language is different&quot;
+&hellip;
+&hellip;
+# type: Content of: &lt;div&gt;
+#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
+msgid &quot;*GNUN-SLOT: TRANSLATOR'S NOTES*&quot;
+msgstr &quot;&quot;
+&quot;&lt;h3&gt;Translator's notes&lt;/h3&gt;\n&quot;
+&quot;&lt;ol&gt;\n&quot;
+&quot;&lt;li id=\&quot;TransNote1\&quot;&gt;Note clarifying the 
text.&lt;/li&gt;\n&quot;
+&quot;&lt;/ol&gt;\n&quot;
+</pre></div>
 
-<pre class="example">     # type: Content of: &lt;p&gt;
-     msgid ""
-     "To understand the concept, you should think of &lt;q&gt;free&lt;/q&gt; "
-     "as in &lt;q&gt;free speech,&lt;/q&gt; not as in &lt;q&gt;free 
beer.&lt;/q&gt;"
-     msgstr ""
-     "Translated message, where you want to clarify beer&lt;sup&gt;&lt;a "
-     "href=\"#TransNote1\"&gt;1&lt;/a&gt;&lt;/sup&gt;, presumably because the "
-     "expression in your language is different"
-     ...
-     ...
-     # type: Content of: &lt;div&gt;
-     #. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
-     msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
-     msgstr ""
-     "&lt;h3&gt;Translator's notes&lt;/h3&gt;\n"
-     "&lt;ol&gt;\n"
-     "&lt;li id=\"TransNote1\"&gt;Note clarifying the text.&lt;/li&gt;\n"
-     "&lt;/ol&gt;\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. &lsquo;<samp><span 
class="samp">TransNote2</span></samp>&rsquo;, &lsquo;<samp><span 
class="samp">TransNote3</span></samp>&rsquo;, etc. and
+incremented number, i.e. &lsquo;<samp>TransNote2</samp>&rsquo;, 
&lsquo;<samp>TransNote3</samp>&rsquo;, etc. and
 you have to add them as more <code>&lt;li&gt;</code> elements accordingly.
-
-   <p>Do not worry about the <code>\n</code> character&mdash;it is inserted
-automatically when you press &lt;RET&gt;.  It is not compulsory that
+</p>
+<p>Do not worry about the <code>\n</code> character&mdash;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&rsquo; 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&mdash;when these features
 are implemented.
-
-<div class="node">
+</p>
+<hr>
 <a name="Credits-Slot"></a>
-<p><hr>
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Notes-Slot">Notes 
Slot</a>,
-Up:&nbsp;<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> 
&nbsp; [<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&rsquo;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 &ldquo;footer&rdquo; 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 &ldquo;translate&rdquo; it as a <tt 
class="key">SPC</tt> if
+you don&rsquo;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">&lt;b&gt;Traduction&lt;/b&gt;: Benjamin Drieu 
+&lt;a 
href=&quot;mailto:address@hidden&quot;&gt;&amp;lt;address@hidden&amp;gt;&lt;/a&gt;,
+2007, 2008.
+</pre></div>
 
-   <p>Like the previous slot, you should &ldquo;translate&rdquo; it as a 
&lt;SPC&gt; 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">     &lt;b&gt;Traduction&lt;/b&gt;: Benjamin Drieu
-     &lt;a 
href="mailto:address@hidden"&gt;&amp;lt;address@hidden&amp;gt;&lt;/a&gt;,
-     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&rsquo;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:&nbsp;<a rel="next" accesskey="n" href="#GNU-News">GNU News</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#New-Translation">New 
Translation</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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 &ldquo;<code>-C
+<p>If you have no compendium, just omit the &ldquo;<code>-C
 compendium.lang.po</code>&rdquo; 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
 &ldquo;fuzzy&rdquo; (unless you use a compendium); you still should make sure 
that
 the translations correspond to the original and remove those 
&ldquo;fuzzy&rdquo;
 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&eacute;dric Corazza &lt;address@hidden&gt;, 2006, 2008.
+# Jer&ocirc;me Dominguez &lt;address@hidden&gt;, 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&eacute;dric Corazza &lt;address@hidden&gt;, 2006, 2008.
-     # Jer&ocirc;me Dominguez &lt;address@hidden&gt;, 2007.
-</pre>
-   <p>In this example, it is clear that C&eacute;dric made the initial
+<p>In this example, it is clear that C&eacute;dric made the initial
 translation, Jer&ocirc;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:&nbsp;<a rel="next" accesskey="n" href="#PO-Tips">PO Tips</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Migrating">Migrating</a>,
-Up:&nbsp;<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> &nbsp; [<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 &ldquo;What's 
New&rdquo;, also
+</p>
+<p>The GNU website has infrastructure for supporting &ldquo;What&rsquo;s 
New&rdquo;, also
 known as &ldquo;GNU News&rdquo;.  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:&nbsp;<a rel="next" accesskey="n" 
href="#generic_002eLANG_002ehtml">generic.LANG.html</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#GNU-News">GNU News</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;s control.
+</p>
+</li><li> If you don&rsquo;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 &ldquo;obsolete&rdquo; 
strings&mdash;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&rsquo;t have to update a PO file if it contains
 obsolete strings&mdash;do this only if it has &ldquo;fuzzy&rdquo; or
 &ldquo;untranslated&rdquo;, 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&mdash;for example 
if
+</li><li> You can add comments to every message in a PO file&mdash;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>&lt;pre&gt;</code> 
elements,
 which normally you would want to preserve verbatim.
 
-     <li>If you translate &ldquo;Free Software Foundation, Inc.&rdquo; in your 
native
+</li><li> If you translate &ldquo;Free Software Foundation, Inc.&rdquo; in 
your native
 language in the copyright notice, then please prepend the English name
 to the <code>&lt;address&gt;</code>; otherwise it looks awkward in most
 languages.  Example:
 
-     <pre class="example">          # type: Content of: 
&lt;div&gt;&lt;address&gt;
-          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: &lt;div&gt;&lt;address&gt;
+msgid &quot;51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA&quot;
+msgstr &quot;&quot;
+&quot;Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, &quot;
+&quot;Boston, MA 02110-1301, USA&quot;
+</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&mdash;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:&nbsp;<a rel="next" accesskey="n" 
href="#languages_002etxt">languages.txt</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#PO-Tips">PO Tips</a>,
-Up:&nbsp;<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> &nbsp; [<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">&lt;p&gt;To join the Fooish translation team, see &lt;a
+href=&quot;http://gnu.org/server/standards/translations/foo&quot;&gt;the
+Foo team homepage&lt;/a&gt;.&lt;/p&gt;
+</pre></div>
 
-<pre class="example">     &lt;p&gt;To join the Fooish translation team, see 
&lt;a
-     href="http://gnu.org/server/standards/translations/www-foo"&gt;the
-     Foo team homepage&lt;/a&gt;.&lt;/p&gt;
-</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&rsquo; 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:&nbsp;<a rel="next" accesskey="n" href="#PO-Files-and-Team">PO Files and 
Team</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#generic_002eLANG_002ehtml">generic.LANG.html</a>,
-Up:&nbsp;<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> &nbsp; [<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 &ldquo;#&rdquo;) or a definition for a language.  
A
-language is defined by three &lt;TAB&gt;-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">&lt;!-- begin translinks file --&gt;
+&lt;div id=&quot;translations&quot;&gt;
+&lt;ul class=&quot;translations-list&quot;&gt;
+&lt;!-- German --&gt;
+&lt;li&gt;&lt;a 
href=&quot;/distros/screenshot.de.html&quot;&gt;Deutsch&lt;/a&gt;&amp;nbsp;[de]&lt;/li&gt;
+&lt;!-- English --&gt;
+&lt;li&gt;&lt;a 
href=&quot;/distros/screenshot.html&quot;&gt;English&lt;/a&gt;&amp;nbsp;[en]&lt;/li&gt;
+&lt;!-- Polish --&gt;
+&lt;li&gt;&lt;a 
href=&quot;/distros/screenshot.pl.html&quot;&gt;polski&lt;/a&gt;&amp;nbsp;[pl]&lt;/li&gt;
+&lt;/ul&gt;
+&lt;/div&gt; &lt;!-- id=&quot;translations&quot; --&gt;
+&lt;!-- end translinks file --&gt;
+</pre></div>
 
-<pre class="example">     de   German  Deutsch
-</pre>
-   <p>The generated list of translations may look like this:
-
-<pre class="example">     &lt;!-- begin translinks file --&gt;
-     &lt;div id="translations"&gt;
-     &lt;ul class="translations-list"&gt;
-     &lt;!-- German --&gt;
-     &lt;li&gt;&lt;a 
href="/distros/screenshot.de.html"&gt;Deutsch&lt;/a&gt;&amp;nbsp;[de]&lt;/li&gt;
-     &lt;!-- English --&gt;
-     &lt;li&gt;&lt;a 
href="/distros/screenshot.html"&gt;English&lt;/a&gt;&amp;nbsp;[en]&lt;/li&gt;
-     &lt;!-- Polish --&gt;
-     &lt;li&gt;&lt;a 
href="/distros/screenshot.pl.html"&gt;polski&lt;/a&gt;&amp;nbsp;[pl]&lt;/li&gt;
-     &lt;/ul&gt;
-     &lt;/div&gt; &lt;!-- id="translations" --&gt;
-     &lt;!-- end translinks file --&gt;
-</pre>
-   <div class="node">
+<hr>
 <a name="PO-Files-and-Team"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Compendia">Compendia</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#languages_002etxt">languages.txt</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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 &ldquo;official&rdquo; Web repository of the Savannah 
project
-`www', where normally only the coordinators of translation teams have
+<p>GNUN operates on the &ldquo;official&rdquo; Web repository of the Savannah 
project
+&lsquo;www&rsquo;, 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&rsquo;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 
&lsquo;<samp><span class="samp">gnun</span></samp>&rsquo; package is a
+</p>
+<p>The file <samp>GNUmakefile.team</samp> in the 
&lsquo;<samp>gnun</samp>&rsquo; 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&rsquo;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&mdash;it is applicable
+</p>
+<a name="index-team-workflow"></a>
+<p>The following diagram illustrates a typical workflow&mdash;it is applicable
 for small, medium and large teams:
-
-<pre class="example">     +----------+                   +-------------------+
-     | ``www''  |                   |   ``www-LANG''    |
-     |   Web    |------&gt;----&gt;-------|Sources repository |
-     |repository|  automatic merge  +-------------------+
-     +----------+                         |    |     |
+</p>
+<div class="example">
+<pre class="example">+----------+                   +-------------------+
+| ``www''  |                   |   ``www-LANG''    |
+|   Web    |------&gt;----&gt;-------|Sources repository |
+|repository|  automatic merge  +-------------------+
++----------+                         |    |     |
           |                               |    |     `-- Member A
           +------------&lt;----&lt;-------------'    |
                        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&rsquo;s
 repository&mdash;when a translation is ready, the leader checks it in in the
-official `www' repository.  If an original article changes,
+official &lsquo;www&rsquo; 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&rsquo;s Sources repository, from where the
+coordinator will pick it up and install it in &lsquo;www&rsquo;.
+</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&rsquo;s Sources repository.  Then create directories and
+sub-directories exactly as they are in &lsquo;www&rsquo;.  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 &lsquo;www&rsquo;, for example:
+</p>
+<div class="example">
+<pre class="example">Root
        |
        |--GNUmakefile
        |--home.<var>lang</var>.po
-       |--...
+  |--&hellip;
        |--gnu
        |   |
        |   |
        |   +--linux-and-gnu.<var>lang</var>.po
        |   +--manifesto.<var>lang</var>.po
-       |   +--...
+  |   +--&hellip;
        |
        |
        +--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
-       |     +--...
+  |     +--&hellip;
        |
-       +--...
-</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.
+  +--&hellip;
+</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 &ldquo;build&rdquo;.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a 
href="#GNUmakefile_002eteam-Variables" accesskey="1">GNUmakefile.team 
Variables</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#GNUmakefile_002eteam-Targets" accesskey="2">GNUmakefile.team 
Targets</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#GNUmakefile_002eteam-and-Cron" accesskey="3">GNUmakefile.team and 
Cron</a>:</td><td>&nbsp;&nbsp;</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:&nbsp;<a rel="next" accesskey="n" 
href="#GNUmakefile_002eteam-and-Cron">GNUmakefile.team and Cron</a>,
-Up:&nbsp;<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> &nbsp; [<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>&lsquo;<samp><span class="samp">TEAM</span></samp>&rsquo;<dd>Set this to 
the language code, like <code>bg</code> or <code>pt-br</code>.
-
-     <br><dt>&lsquo;<samp><span 
class="samp">wwwdir</span></samp>&rsquo;<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>&lsquo;<samp>TEAM</samp>&rsquo;</dt>
+<dd><p>Set this to the language code, like <code>bg</code> or 
<code>pt-br</code>.
+</p>
+</dd>
+<dt>&lsquo;<samp>wwwdir</samp>&rsquo;</dt>
+<dd><p>The relative or absolute path to the working copy of the master 
&lsquo;www&rsquo;
+repository.  So if you have checked out your project&rsquo;s Sources
+repository at <samp>~/projects/www-<var>lang</var></samp> and the 
&lsquo;www&rsquo; 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>&lsquo;<samp><span class="samp">VERBOSE=yes</span></samp>&rsquo;<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>&lsquo;<samp>VERBOSE=yes</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">VCS=yes</span></samp>&rsquo;<dd>Update both &lsquo;<samp><span 
class="samp">www</span></samp>&rsquo; and &lsquo;<samp><span 
class="samp">www-</span><var>lang</var></samp>&rsquo; repositories, then
+</p>
+</dd>
+<dt>&lsquo;<samp>VCS=yes</samp>&rsquo;</dt>
+<dd><p>Update both &lsquo;<samp>www</samp>&rsquo; and 
&lsquo;<samp>www-<var>lang</var></samp>&rsquo; 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> &nbsp; [<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&rsquo;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 &ldquo;www&rdquo; 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&mdash;<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> &hellip;
+$ cvs diff
+$ cvs commit -m &quot;Some descriptive message.&quot;
+</pre></div>
+
+</dd>
+<dt><code>clean</code></dt>
+<dd><p>Deletes all backup and auto-generated files that some PO editors leave
+behind, namely&mdash;<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&mdash;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&rsquo; benefit.
+</p>
+<hr>
 <a name="GNUmakefile_002eteam-and-Cron"></a>
-<p><hr>
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#GNUmakefile_002eteam-Variables">GNUmakefile.team Variables</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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&rsquo;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 &quot;Weekly statistics&quot; \
                             www-<var>lang</var>address@hidden
-</pre>
-   <p><strong>Caution:</strong> Most cron implementations do not allow the 
character
-`\' as a line continuation character&mdash;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
+&lsquo;\&rsquo; as a line continuation character&mdash;the example shown is 
made that
+way for better readability.
+</p>
+<hr>
 <a name="Compendia"></a>
-<p><hr>
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#PO-Files-and-Team">PO 
Files and Team</a>,
-Up:&nbsp;<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> 
&nbsp; [<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 &lsquo;www&rsquo; 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&rsquo;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 &ldquo;fuzzy&rdquo; to
+<samp>compendium.<var>lang</var>.po</samp>.  This file is also used to fill
+missing translations, but it doesn&rsquo;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 
&ldquo;fuzzy&rdquo; 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&mdash;for instance,
-GNUN slots for translators' notes.  See <a href="#Notes-Slot">Notes Slot</a>.  
They are not
+GNUN slots for translators&rsquo; 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&rsquo;t be added to <samp>compendium.pot</samp>.
+</p>
+<hr>
 <a name="Webmaster-Tips"></a>
-<p><hr>
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#PO-Files">PO Files</a>,
-Up:&nbsp;<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> &nbsp; [<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&mdash;it is not mandatory to follow them,
-but doing so will make translators' lives substantially easier.
-
-   <p>First and foremost, respect translators' work&mdash;it is ungrateful and
+but doing so will make translators&rsquo; lives substantially easier.
+</p>
+<p>First and foremost, respect translators&rsquo; work&mdash;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&rsquo;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&mdash;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&rsquo;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">&bull; <a href="#Validation" 
accesskey="1">Validation</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">How to verify the documents.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Comments-for-Translators" 
accesskey="2">Comments for Translators</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">Passing comments to translators.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Modifying-Boilerplates" 
accesskey="3">Modifying Boilerplates</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Localized-URLs" 
accesskey="4">Localized URLs</a>:</td><td>&nbsp;&nbsp;</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">&bull; <a href="#Splitting-Long-Passages" 
accesskey="5">Splitting Long Passages</a>:</td><td>&nbsp;&nbsp;</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:&nbsp;<a rel="next" accesskey="n" 
href="#Comments-for-Translators">Comments for Translators</a>,
-Up:&nbsp;<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> &nbsp; [<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:&nbsp;<a rel="next" accesskey="n" 
href="#Modifying-Boilerplates">Modifying Boilerplates</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Validation">Validation</a>,
-Up:&nbsp;<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> &nbsp; [<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">&lt;p&gt;
+&lt;!--TRANSLATORS: Note that foo is bar in this context.--&gt;
+The fooish bar mumbles bazzling.
+&lt;/p&gt;
+</pre></div>
+
+<p>This will result in:
+</p>
+<div class="example">
+<pre class="example"># type: Content of: &lt;p&gt;
+#. TRANSLATORS: Note that foo is bar in this context.
+msgid &quot;The fooish bar mumbles bazzling.&quot;
+msgstr &quot;&quot;
+</pre></div>
 
-<pre class="example">     &lt;p&gt;
-     &lt;!--TRANSLATORS: Note that foo is bar in this context.--&gt;
-     The fooish bar mumbles bazzling.
-     &lt;/p&gt;
-</pre>
-   <p>This will result in:
-
-<pre class="example">     # type: Content of: &lt;p&gt;
-     #. 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>&lt;!--</code>), since this will
 unnecessarily indent the comment in the POT.
-
-<div class="node">
+</p>
+<hr>
 <a name="Modifying-Boilerplates"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Localized-URLs">Localized 
URLs</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Comments-for-Translators">Comments for Translators</a>,
-Up:&nbsp;<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> &nbsp; [<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 &amp; 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&rsquo;s control.  Of course, this does not
 mean that no changes should happen&mdash;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:&nbsp;<a rel="next" accesskey="n" 
href="#Splitting-Long-Passages">Splitting Long Passages</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Modifying-Boilerplates">Modifying Boilerplates</a>,
-Up:&nbsp;<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> &nbsp; [<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">     &lt;!-- GNUN: localize URL /philosophy/category.png,
+</p>
+<div class="example">
+<pre class="example">&lt;!-- GNUN: localize URL /philosophy/category.png,
       /licenses/template-diagram.png and /graphics/jesus-cartoon.jpg --&gt;
-</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 
&lsquo;and&rsquo;,
+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&rsquo;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:&nbsp;<a rel="previous" accesskey="p" 
href="#Localized-URLs">Localized URLs</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo; life easier, it is desirable to keep
 the paragraphs short (no more than 350&ndash;700 characters).  If rearranging
 the paragraphs is not an option, you can use a conventional separator,
-<code>&lt;span class="gnun-split"&gt;&lt;/span&gt;</code>:
+<code>&lt;span class=&quot;gnun-split&quot;&gt;&lt;/span&gt;</code>:
+</p>
+<div class="example">
+<pre class="example">&lt;p&gt;GNUN splits typical text by paragraphs, and 
translators write
+the translations for the resulting parts of the text
+one by one. &lt;span class=&quot;gnun-split&quot;&gt;&lt;/span&gt; When a part
+is too long, it is hard to translate and proofread the translation;
+the likelihood of skipping some phrases is relatively high.&lt;/p&gt;
+</pre></div>
 
-<pre class="example">     &lt;p&gt;GNUN splits typical text by paragraphs, and 
translators write
-     the translations for the resulting parts of the text
-     one by one. &lt;span class="gnun-split"&gt;&lt;/span&gt; When a part
-     is too long, it is hard to translate and proofread the translation;
-     the likelihood of skipping some phrases is relatively high.&lt;/p&gt;
-</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:&nbsp;<a rel="next" accesskey="n" href="#Bugs">Bugs</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Usage">Usage</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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">&bull; <a href="#Scripts" 
accesskey="1">Scripts</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Helper scripts.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Rules" 
accesskey="2">Rules</a>:</td><td>&nbsp;&nbsp;</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:&nbsp;<a rel="next" accesskey="n" href="#Rules">Rules</a>,
-Up:&nbsp;<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> &nbsp; [<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">&bull; <a 
href="#gnun_002dadd_002dfuzzy_002ddiff" 
accesskey="1">gnun-add-fuzzy-diff</a>:</td><td>&nbsp;&nbsp;</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">&bull; <a href="#gnun_002ddiff_002dpo" 
accesskey="2">gnun-diff-po</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Compare two revisions of a PO file.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#gnun_002dinit_002dpo" 
accesskey="3">gnun-init-po</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Initialize a new translation.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#gnun_002dpreconvert" 
accesskey="4">gnun-preconvert</a>:</td><td>&nbsp;&nbsp;</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:&nbsp;<a rel="next" accesskey="n" 
href="#gnun_002dadd_002dfuzzy_002ddiff">gnun-add-fuzzy-diff</a>,
-Up:&nbsp;<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 &ldquo;prototype&rdquo; 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&mdash;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> 
&ldquo;injects&rdquo; 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">&bull; <a 
href="#gnun_002dmerge_002dpreconverted" 
accesskey="5">gnun-merge-preconverted</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">Run the second step of the conversion.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#gnun_002dreport" 
accesskey="6">gnun-report</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Generate report in HTML format.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#gnun_002dvalidate_002dhtml" 
accesskey="7">gnun-validate-html</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Validate HTML file.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#mailfail" 
accesskey="8">mailfail</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#validate_002dhtml_002dnotify" 
accesskey="9">validate-html-notify</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#gnun_002dclear_002dprevious">gnun-clear-previous</a>:</td><td>&nbsp;&nbsp;</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:&nbsp;<a rel="next" accesskey="n" 
href="#gnun_002dinit_002dpo">gnun-init-po</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#make_002dprototype">make-prototype</a>,
-Up:&nbsp;<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> &nbsp; [<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> &nbsp; [<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 &gt; 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:&nbsp;<a rel="next" accesskey="n" 
href="#gnun_002dpreconvert">gnun-preconvert</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#gnun_002dadd_002dfuzzy_002ddiff">gnun-add-fuzzy-diff</a>,
-Up:&nbsp;<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> &nbsp; [<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 &lt;list&gt;</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 &ldquo;bg&rdquo;.  The suffix also defines
+</p>
+</dd>
+<dt><samp>-d</samp></dt>
+<dt><samp>--disable-diffs</samp></dt>
+<dd><p>Don&rsquo;t add diffs to previous messages.
+</p>
+</dd>
+<dt><samp>-g</samp></dt>
+<dt><samp>--team=&quot;<var>team &lt;list&gt;</var>&quot;</samp></dt>
+<dd><p>Specify team&rsquo;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 &ldquo;bg&rdquo;.  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 &lt;email&gt;</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=&quot;<var>full name 
&lt;email&gt;</var>&quot;</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:&nbsp;<a rel="next" accesskey="n" 
href="#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#gnun_002dinit_002dpo">gnun-init-po</a>,
-Up:&nbsp;<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> &nbsp; [<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:&nbsp;<a rel="next" accesskey="n" 
href="#gnun_002dvalidate_002dhtml">gnun-validate-html</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#gnun_002dpreconvert">gnun-preconvert</a>,
-Up:&nbsp;<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> &nbsp; [<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 &ldquo;previous&rdquo; 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> &nbsp; [<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 
&lsquo;www&rsquo;
+repository.
+</p>
+<p>The results are written to standard output.  Example:
+</p>
+<div class="example">
+<pre class="example">gnun-report --root=../www -t bg &gt; 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, &lsquo;ml&rsquo;.
+</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, &lsquo;Malayalam&rsquo;.  When 
this option
+is missing, <code>gnun-report</code> tries to figure out the language name
+based on the language code provided with the &ldquo;-t&rdquo; 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:&nbsp;<a rel="next" accesskey="n" href="#mailfail">mailfail</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#gnun_002dmerge_002dpreconverted">gnun-merge-preconverted</a>,
-Up:&nbsp;<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> &nbsp; [<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 &ldquo;validate&rdquo; both the
+<p>This is a Bash script whose purpose is to &ldquo;validate&rdquo; 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:&nbsp;<a rel="next" accesskey="n" 
href="#validate_002dhtml_002dnotify">validate-html-notify</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#gnun_002dvalidate_002dhtml">gnun-validate-html</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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&hellip;</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 &quot;Bad PO&quot; 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 &lsquo;Bad PO&rsquo; 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:&nbsp;<a rel="next" accesskey="n" 
href="#gnun_002dclear_002dprevious">gnun-clear-previous</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#mailfail">mailfail</a>,
-Up:&nbsp;<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> &nbsp; [<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&mdash;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&mdash;use <code>mailfail</code> for that.  See <a 
href="#mailfail">mailfail</a>.
+</p>
+<hr>
 <a name="gnun_002dclear_002dprevious"></a>
-<p><hr>
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#validate_002dhtml_002dnotify">validate-html-notify</a>,
-Up:&nbsp;<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> &nbsp; [<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
-&lsquo;<samp><span class="samp">gettext</span></samp>&rsquo; tools and their 
options.
-
-   <p><samp><span class="command">gnun-clear-previous</span></samp> deletes 
the <dfn>previous</dfn> messages in a
+&lsquo;<samp>gettext</samp>&rsquo; 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:&nbsp;<a rel="previous" accesskey="p" href="#Scripts">Scripts</a>,
-Up:&nbsp;<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> &nbsp; [<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:&nbsp;<a rel="next" accesskey="n" href="#Index">Index</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Internals">Internals</a>,
-Up:&nbsp;<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> &nbsp; [<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> &nbsp; [<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: &nbsp; </th><td><a class="summary-letter" 
href="#Index_cp_letter-A"><b>A</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-B"><b>B</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-C"><b>C</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-D"><b>D</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-E"><b>E</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-F"><b>F</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-G"><b>G</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-I"><b>I</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-L"><b>L</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-M"><b>M</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-N"><b>N</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-O"><b>O</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-P"><b>P</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-R"><b>R</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-S"><b>S</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-T"><b>T</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-V"><b>V</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-W"><b>W</b></a>
+ &nbsp; 
+</td></tr></table>
+<table class="index-cp" border="0">
+<tr><td></td><th align="left">Index Entry</th><td>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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&rsquo; 
credits</a>:</td><td>&nbsp;</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&rsquo; 
credits</a>:</td><td>&nbsp;</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&rsquo; 
notes</a>:</td><td>&nbsp;</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&rsquo; 
notes</a>:</td><td>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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: &nbsp; </th><td><a class="summary-letter" 
href="#Index_cp_letter-A"><b>A</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-B"><b>B</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-C"><b>C</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-D"><b>D</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-E"><b>E</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-F"><b>F</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-G"><b>G</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-I"><b>I</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-L"><b>L</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-M"><b>M</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-N"><b>N</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-O"><b>O</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-P"><b>P</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-R"><b>R</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-S"><b>S</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-T"><b>T</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-V"><b>V</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-W"><b>W</b></a>
+ &nbsp; 
+</td></tr></table>
 
-<div class="node">
+<hr>
 <a name="Copying-This-Manual"></a>
-<p><hr>
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Index">Index</a>,
-Up:&nbsp;<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> &nbsp; [<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 &copy; 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 &copy; 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 &ldquo;copyleft&rdquo;, which means that 
derivative
+</p>
+<p>This License is a kind of &ldquo;copyleft&rdquo;, 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 &ldquo;you&rdquo;.  You accept the license if you
 copy, modify or distribute the work in a way requiring permission
 under copyright law.
-
-     <p>A &ldquo;Modified Version&rdquo; of the Document means any work 
containing the
+</p>
+<p>A &ldquo;Modified Version&rdquo; 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 &ldquo;Secondary Section&rdquo; is a named appendix or a 
front-matter section
+</p>
+<p>A &ldquo;Secondary Section&rdquo; 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&rsquo;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 &ldquo;Invariant Sections&rdquo; are certain Secondary Sections 
whose titles
+</p>
+<p>The &ldquo;Invariant Sections&rdquo; 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 &ldquo;Cover Texts&rdquo; are certain short passages of text that 
are listed,
+</p>
+<p>The &ldquo;Cover Texts&rdquo; 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 &ldquo;Transparent&rdquo; copy of the Document means a 
machine-readable copy,
+</p>
+<p>A &ldquo;Transparent&rdquo; 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 &ldquo;Transparent&rdquo; is called 
&ldquo;Opaque&rdquo;.
-
-     <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 &ldquo;Title Page&rdquo; means, for a printed book, the title page 
itself,
+</p>
+<p>The &ldquo;Title Page&rdquo; 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, &ldquo;Title Page&rdquo; 
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work&rsquo;s title,
 preceding the beginning of the body of the text.
-
-     <p>The &ldquo;publisher&rdquo; means any person or entity that 
distributes copies
+</p>
+<p>The &ldquo;publisher&rdquo; means any person or entity that distributes 
copies
 of the Document to the public.
-
-     <p>A section &ldquo;Entitled XYZ&rdquo; means a named subunit of the 
Document whose
+</p>
+<p>A section &ldquo;Entitled XYZ&rdquo; 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 &ldquo;Acknowledgements&rdquo;,
 &ldquo;Dedications&rdquo;, &ldquo;Endorsements&rdquo;, or 
&ldquo;History&rdquo;.)  To &ldquo;Preserve the Title&rdquo;
 of such a section when you modify the Document means that it remains a
 section &ldquo;Entitled XYZ&rdquo; 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&rsquo;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&rsquo;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 &ldquo;History&rdquo;, Preserve 
its Title, and add
+</li><li> Preserve the section Entitled &ldquo;History&rdquo;, 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 &ldquo;History&rdquo; 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 &ldquo;History&rdquo; 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 &ldquo;Acknowledgements&rdquo; or 
&ldquo;Dedications&rdquo;, Preserve
+</li><li> For any section Entitled &ldquo;Acknowledgements&rdquo; or 
&ldquo;Dedications&rdquo;, 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 &ldquo;Endorsements&rdquo;.  Such a 
section
+</li><li> Delete any section Entitled &ldquo;Endorsements&rdquo;.  Such a 
section
 may not be included in the Modified Version.
 
-          <li>Do not retitle any existing section to be Entitled 
&ldquo;Endorsements&rdquo; or
+</li><li> Do not retitle any existing section to be Entitled 
&ldquo;Endorsements&rdquo; 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&rsquo;s license notice.
 These titles must be distinct from any other section titles.
-
-     <p>You may add a section Entitled &ldquo;Endorsements&rdquo;, provided it 
contains
+</p>
+<p>You may add a section Entitled &ldquo;Endorsements&rdquo;, provided it 
contains
 nothing but endorsements of your Modified Version by various
 parties&mdash;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 
&ldquo;History&rdquo;
+</p>
+<p>In the combination, you must combine any sections Entitled 
&ldquo;History&rdquo;
 in the various original documents, forming one section Entitled
 &ldquo;History&rdquo;; likewise combine any sections Entitled 
&ldquo;Acknowledgements&rdquo;,
 and any sections Entitled &ldquo;Dedications&rdquo;.  You must delete all
 sections Entitled &ldquo;Endorsements.&rdquo;
+</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 &ldquo;aggregate&rdquo; 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&rsquo;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&rsquo;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 
&ldquo;Acknowledgements&rdquo;,
+</p>
+<p>If a section in the Document is Entitled &ldquo;Acknowledgements&rdquo;,
 &ldquo;Dedications&rdquo;, or &ldquo;History&rdquo;, 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 &ldquo;or any later version&rdquo; 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&rsquo;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>&ldquo;Massive Multiauthor Collaboration Site&rdquo; (or &ldquo;MMC 
Site&rdquo;) means any
+<p>&ldquo;Massive Multiauthor Collaboration Site&rdquo; (or &ldquo;MMC 
Site&rdquo;) 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
 &ldquo;Massive Multiauthor Collaboration&rdquo; (or &ldquo;MMC&rdquo;) 
contained in the
 site means any set of copyrightable works thus published on the MMC
 site.
-
-     <p>&ldquo;CC-BY-SA&rdquo; means the Creative Commons Attribution-Share 
Alike 3.0
+</p>
+<p>&ldquo;CC-BY-SA&rdquo; 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>&ldquo;Incorporate&rdquo; means to publish or republish a Document, in 
whole or
+</p>
+<p>&ldquo;Incorporate&rdquo; means to publish or republish a Document, in 
whole or
 in part, as part of another Document.
-
-     <p>An MMC is &ldquo;eligible for relicensing&rdquo; if it is licensed 
under this
+</p>
+<p>An MMC is &ldquo;eligible for relicensing&rdquo; 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 &ldquo;with<small class="dots">...</small>Texts.&rdquo; line with 
this:
+</pre></div>
 
+<p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the &ldquo;with&hellip;Texts.&rdquo; 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:&nbsp;<a rel="next" accesskey="n" href="#Copying-This-Manual">Copying 
This Manual</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Bugs">Bugs</a>,
-Up:&nbsp;<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 &ldquo;messages&rdquo; in gettext's context) 
are
+typically strings (also known as &ldquo;messages&rdquo; in gettext&rsquo;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 (&ldquo;po for
 anything&rdquo;), 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 
&ldquo;no-grace&rdquo;
-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&rsquo; 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:&nbsp;<a rel="next" accesskey="n" 
href="Disadvantages.html#Disadvantages">Disadvantages</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Concepts.html#Concepts">Concepts</a>,
-Up:&nbsp;<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> 
&nbsp; [<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 &lsquo;www&rsquo; 
repository).  A
 single change to such a file will affect literally <em>all</em>
 articles, translated or not.
 
-     <li>Urgent notices.  Sometimes an &ldquo;urgent&rdquo; notice is added by 
the
+</li><li> Urgent notices.  Sometimes an &ldquo;urgent&rdquo; 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&rsquo; 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&mdash;lots of errors and 
typos
+</li><li> Simplification of the translation process&mdash;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&mdash;it would be substantially easier to
+</li><li> Markup consistency site-wide&mdash;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 &ldquo;fuzzy&rdquo; strings in the PO files, newly added ones will
 appear as &ldquo;untranslated&rdquo;, and deleted will appear as 
&ldquo;obsolete&rdquo;. 
 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> 
&nbsp; [<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:&nbsp;<a rel="next" accesskey="n" href="Index.html#Index">Index</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Internals.html#Internals">Internals</a>,
-Up:&nbsp;<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> &nbsp; [<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:&nbsp;<a rel="next" accesskey="n" 
href="Modifying-Boilerplates.html#Modifying-Boilerplates">Modifying 
Boilerplates</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Validation.html#Validation">Validation</a>,
-Up:&nbsp;<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> &nbsp; [<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">&lt;p&gt;
+&lt;!--TRANSLATORS: Note that foo is bar in this context.--&gt;
+The fooish bar mumbles bazzling.
+&lt;/p&gt;
+</pre></div>
+
+<p>This will result in:
+</p>
+<div class="example">
+<pre class="example"># type: Content of: &lt;p&gt;
+#. TRANSLATORS: Note that foo is bar in this context.
+msgid &quot;The fooish bar mumbles bazzling.&quot;
+msgstr &quot;&quot;
+</pre></div>
 
-<pre class="example">     &lt;p&gt;
-     &lt;!--TRANSLATORS: Note that foo is bar in this context.--&gt;
-     The fooish bar mumbles bazzling.
-     &lt;/p&gt;
-</pre>
-   <p>This will result in:
-
-<pre class="example">     # type: Content of: &lt;p&gt;
-     #. 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>&lt;!--</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:&nbsp;<a rel="previous" accesskey="p" 
href="PO-Files-and-Team.html#PO-Files-and-Team">PO Files and Team</a>,
-Up:&nbsp;<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> &nbsp; [<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 &lsquo;www&rsquo; 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&rsquo;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 &ldquo;fuzzy&rdquo; to
+<samp>compendium.<var>lang</var>.po</samp>.  This file is also used to fill
+missing translations, but it doesn&rsquo;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 
&ldquo;fuzzy&rdquo; 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&mdash;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&rsquo; 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&rsquo;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> &nbsp; [<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:&nbsp;<a rel="next" accesskey="n" 
href="Advantages.html#Advantages">Advantages</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Overview.html#Overview">Overview</a>,
-Up:&nbsp;<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> 
&nbsp; [<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 &ldquo;PO template&rdquo;) 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">     .---&lt;--- * Original ARTICLE.html
-     |
-     |   .---&gt; ARTICLE.pot ---&gt; * ARTICLE.LANG.po ---&gt;---.
-     `---+                                               |
+</p>
+<div class="example">
+<pre class="example">.---&lt;--- * Original ARTICLE.html
+|
+|   .---&gt; ARTICLE.pot ---&gt; * ARTICLE.LANG.po ---&gt;---.
+`---+                                               |
          `---&gt;---.   .------&lt;----------------------------'
                  |   |
                  |   `---.
                  |       +---&gt; Translated ARTICLE.LANG.html
                  `-------'
-</pre>
-   <p>The indication &lsquo;<samp><span class="samp">*</span></samp>&rsquo; 
appears in two places in this picture, and means
+</pre></div>
+
+<p>The indication &lsquo;<samp>*</samp>&rsquo; 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 &lsquo;<samp><span class="samp">make -C 
server/gnun</span></samp>&rsquo;.  This is the primary way to invoke
+running &lsquo;<samp>make -C server/gnun</samp>&rsquo;.  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
-&lsquo;<samp><span class="samp">gettext</span></samp>&rsquo; 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>
+&lsquo;<samp>gettext</samp>&rsquo; 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
-&lt;<code>http://www.gnu.org/philosophy/free-sw.html</code>&gt; 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&rsquo;s control is kept in the 
&lsquo;www&rsquo;
+repository under a special directory <samp>po/</samp>, which is a
+sub-directory of the relevant directory in the &lsquo;www&rsquo; tree.  So, for
+&lsquo;<code>http://www.gnu.org/philosophy/free-sw.html</code>&rsquo; 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 &ldquo;inject&rdquo; general information about a
 translation team&mdash;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&rsquo; credits are
+also handled, as well as translators&rsquo; 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 &ldquo;messages&rdquo; in gettext's context) 
are
+typically strings (also known as &ldquo;messages&rdquo; in gettext&rsquo;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 (&ldquo;po for
 anything&rdquo;), 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> 
&nbsp; [<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:&nbsp;<a rel="previous" accesskey="p" 
href="Index.html#Index">Index</a>,
-Up:&nbsp;<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> &nbsp; [<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 &copy; 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 &copy; 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 &ldquo;copyleft&rdquo;, which means that 
derivative
+</p>
+<p>This License is a kind of &ldquo;copyleft&rdquo;, 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 &ldquo;you&rdquo;.  You accept the license if you
 copy, modify or distribute the work in a way requiring permission
 under copyright law.
-
-     <p>A &ldquo;Modified Version&rdquo; of the Document means any work 
containing the
+</p>
+<p>A &ldquo;Modified Version&rdquo; 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 &ldquo;Secondary Section&rdquo; is a named appendix or a 
front-matter section
+</p>
+<p>A &ldquo;Secondary Section&rdquo; 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&rsquo;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 &ldquo;Invariant Sections&rdquo; are certain Secondary Sections 
whose titles
+</p>
+<p>The &ldquo;Invariant Sections&rdquo; 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 &ldquo;Cover Texts&rdquo; are certain short passages of text that 
are listed,
+</p>
+<p>The &ldquo;Cover Texts&rdquo; 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 &ldquo;Transparent&rdquo; copy of the Document means a 
machine-readable copy,
+</p>
+<p>A &ldquo;Transparent&rdquo; 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 &ldquo;Transparent&rdquo; is called 
&ldquo;Opaque&rdquo;.
-
-     <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 &ldquo;Title Page&rdquo; means, for a printed book, the title page 
itself,
+</p>
+<p>The &ldquo;Title Page&rdquo; 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, &ldquo;Title Page&rdquo; 
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work&rsquo;s title,
 preceding the beginning of the body of the text.
-
-     <p>The &ldquo;publisher&rdquo; means any person or entity that 
distributes copies
+</p>
+<p>The &ldquo;publisher&rdquo; means any person or entity that distributes 
copies
 of the Document to the public.
-
-     <p>A section &ldquo;Entitled XYZ&rdquo; means a named subunit of the 
Document whose
+</p>
+<p>A section &ldquo;Entitled XYZ&rdquo; 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 &ldquo;Acknowledgements&rdquo;,
 &ldquo;Dedications&rdquo;, &ldquo;Endorsements&rdquo;, or 
&ldquo;History&rdquo;.)  To &ldquo;Preserve the Title&rdquo;
 of such a section when you modify the Document means that it remains a
 section &ldquo;Entitled XYZ&rdquo; 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&rsquo;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&rsquo;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 &ldquo;History&rdquo;, Preserve 
its Title, and add
+</li><li> Preserve the section Entitled &ldquo;History&rdquo;, 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 &ldquo;History&rdquo; 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 &ldquo;History&rdquo; 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 &ldquo;Acknowledgements&rdquo; or 
&ldquo;Dedications&rdquo;, Preserve
+</li><li> For any section Entitled &ldquo;Acknowledgements&rdquo; or 
&ldquo;Dedications&rdquo;, 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 &ldquo;Endorsements&rdquo;.  Such a 
section
+</li><li> Delete any section Entitled &ldquo;Endorsements&rdquo;.  Such a 
section
 may not be included in the Modified Version.
 
-          <li>Do not retitle any existing section to be Entitled 
&ldquo;Endorsements&rdquo; or
+</li><li> Do not retitle any existing section to be Entitled 
&ldquo;Endorsements&rdquo; 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&rsquo;s license notice.
 These titles must be distinct from any other section titles.
-
-     <p>You may add a section Entitled &ldquo;Endorsements&rdquo;, provided it 
contains
+</p>
+<p>You may add a section Entitled &ldquo;Endorsements&rdquo;, provided it 
contains
 nothing but endorsements of your Modified Version by various
 parties&mdash;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 
&ldquo;History&rdquo;
+</p>
+<p>In the combination, you must combine any sections Entitled 
&ldquo;History&rdquo;
 in the various original documents, forming one section Entitled
 &ldquo;History&rdquo;; likewise combine any sections Entitled 
&ldquo;Acknowledgements&rdquo;,
 and any sections Entitled &ldquo;Dedications&rdquo;.  You must delete all
 sections Entitled &ldquo;Endorsements.&rdquo;
+</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 &ldquo;aggregate&rdquo; 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&rsquo;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&rsquo;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 
&ldquo;Acknowledgements&rdquo;,
+</p>
+<p>If a section in the Document is Entitled &ldquo;Acknowledgements&rdquo;,
 &ldquo;Dedications&rdquo;, or &ldquo;History&rdquo;, 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 &ldquo;or any later version&rdquo; 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&rsquo;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>&ldquo;Massive Multiauthor Collaboration Site&rdquo; (or &ldquo;MMC 
Site&rdquo;) means any
+<p>&ldquo;Massive Multiauthor Collaboration Site&rdquo; (or &ldquo;MMC 
Site&rdquo;) 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
 &ldquo;Massive Multiauthor Collaboration&rdquo; (or &ldquo;MMC&rdquo;) 
contained in the
 site means any set of copyrightable works thus published on the MMC
 site.
-
-     <p>&ldquo;CC-BY-SA&rdquo; means the Creative Commons Attribution-Share 
Alike 3.0
+</p>
+<p>&ldquo;CC-BY-SA&rdquo; 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>&ldquo;Incorporate&rdquo; means to publish or republish a Document, in 
whole or
+</p>
+<p>&ldquo;Incorporate&rdquo; means to publish or republish a Document, in 
whole or
 in part, as part of another Document.
-
-     <p>An MMC is &ldquo;eligible for relicensing&rdquo; if it is licensed 
under this
+</p>
+<p>An MMC is &ldquo;eligible for relicensing&rdquo; 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 &ldquo;with<small class="dots">...</small>Texts.&rdquo; line with 
this:
+</pre></div>
 
+<p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the &ldquo;with&hellip;Texts.&rdquo; 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> &nbsp; [<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:&nbsp;<a rel="previous" accesskey="p" 
href="Notes-Slot.html#Notes-Slot">Notes Slot</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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 &ldquo;footer&rdquo; 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 &ldquo;translate&rdquo; it as a <tt 
class="key">SPC</tt> if
+you don&rsquo;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">&lt;b&gt;Traduction&lt;/b&gt;: Benjamin Drieu 
+&lt;a 
href=&quot;mailto:address@hidden&quot;&gt;&amp;lt;address@hidden&amp;gt;&lt;/a&gt;,
+2007, 2008.
+</pre></div>
 
-   <p>Like the previous slot, you should &ldquo;translate&rdquo; it as a 
&lt;SPC&gt; 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">     &lt;b&gt;Traduction&lt;/b&gt;: Benjamin Drieu
-     &lt;a 
href="mailto:address@hidden"&gt;&amp;lt;address@hidden&amp;gt;&lt;/a&gt;,
-     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&rsquo;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:&nbsp;<a rel="previous" accesskey="p" 
href="Advantages.html#Advantages">Advantages</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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 &ldquo;no-grace&rdquo;
-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:&nbsp;<a rel="next" accesskey="n" href="PO-Tips.html#PO-Tips">PO Tips</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Migrating.html#Migrating">Migrating</a>,
-Up:&nbsp;<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> &nbsp; [<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 &ldquo;What's 
New&rdquo;, also
+</p>
+<p>The GNU website has infrastructure for supporting &ldquo;What&rsquo;s 
New&rdquo;, also
 known as &ldquo;GNU News&rdquo;.  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:&nbsp;<a rel="next" accesskey="n" 
href="GNUmakefile_002eteam-and-Cron.html#GNUmakefile_002eteam-and-Cron">GNUmakefile.team
 and Cron</a>,
-Up:&nbsp;<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> &nbsp; [<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>&lsquo;<samp><span class="samp">TEAM</span></samp>&rsquo;<dd>Set this to 
the language code, like <code>bg</code> or <code>pt-br</code>.
-
-     <br><dt>&lsquo;<samp><span 
class="samp">wwwdir</span></samp>&rsquo;<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>&lsquo;<samp>TEAM</samp>&rsquo;</dt>
+<dd><p>Set this to the language code, like <code>bg</code> or 
<code>pt-br</code>.
+</p>
+</dd>
+<dt>&lsquo;<samp>wwwdir</samp>&rsquo;</dt>
+<dd><p>The relative or absolute path to the working copy of the master 
&lsquo;www&rsquo;
+repository.  So if you have checked out your project&rsquo;s Sources
+repository at <samp>~/projects/www-<var>lang</var></samp> and the 
&lsquo;www&rsquo; 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>&lsquo;<samp><span class="samp">VERBOSE=yes</span></samp>&rsquo;<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>&lsquo;<samp>VERBOSE=yes</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">VCS=yes</span></samp>&rsquo;<dd>Update both &lsquo;<samp><span 
class="samp">www</span></samp>&rsquo; and &lsquo;<samp><span 
class="samp">www-</span><var>lang</var></samp>&rsquo; repositories, then
+</p>
+</dd>
+<dt>&lsquo;<samp>VCS=yes</samp>&rsquo;</dt>
+<dd><p>Update both &lsquo;<samp>www</samp>&rsquo; and 
&lsquo;<samp>www-<var>lang</var></samp>&rsquo; 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 &ldquo;www&rdquo; 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&mdash;<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&mdash;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:&nbsp;<a rel="previous" accesskey="p" 
href="GNUmakefile_002eteam-Variables.html#GNUmakefile_002eteam-Variables">GNUmakefile.team
 Variables</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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&rsquo;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 &quot;Weekly statistics&quot; \
                             www-<var>lang</var>address@hidden
-</pre>
-   <p><strong>Caution:</strong> Most cron implementations do not allow the 
character
-`\' as a line continuation character&mdash;the example shown is made that
+</pre></div>
+
+<p><strong>Caution:</strong> Most cron implementations do not allow the 
character
+&lsquo;\&rsquo; as a line continuation character&mdash;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:&nbsp;<a rel="next" accesskey="n" 
href="Copying-This-Manual.html#Copying-This-Manual">Copying This Manual</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="Bugs.html#Bugs">Bugs</a>,
-Up:&nbsp;<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> &nbsp; [<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: &nbsp; </th><td><a class="summary-letter" 
href="#Index_cp_letter-A"><b>A</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-B"><b>B</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-C"><b>C</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-D"><b>D</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-E"><b>E</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-F"><b>F</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-G"><b>G</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-I"><b>I</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-L"><b>L</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-M"><b>M</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-N"><b>N</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-O"><b>O</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-P"><b>P</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-R"><b>R</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-S"><b>S</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-T"><b>T</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-V"><b>V</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-W"><b>W</b></a>
+ &nbsp; 
+</td></tr></table>
+<table class="index-cp" border="0">
+<tr><td></td><th align="left">Index Entry</th><td>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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&rsquo; 
credits</a>:</td><td>&nbsp;</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&rsquo; 
credits</a>:</td><td>&nbsp;</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&rsquo; 
notes</a>:</td><td>&nbsp;</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&rsquo; 
notes</a>:</td><td>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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: &nbsp; </th><td><a class="summary-letter" 
href="#Index_cp_letter-A"><b>A</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-B"><b>B</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-C"><b>C</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-D"><b>D</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-E"><b>E</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-F"><b>F</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-G"><b>G</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-I"><b>I</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-L"><b>L</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-M"><b>M</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-N"><b>N</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-O"><b>O</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-P"><b>P</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-R"><b>R</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-S"><b>S</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-T"><b>T</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-V"><b>V</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-W"><b>W</b></a>
+ &nbsp; 
+</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> &nbsp; [<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:&nbsp;<a rel="next" accesskey="n" href="Bugs.html#Bugs">Bugs</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Usage.html#Usage">Usage</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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">&bull; <a href="Scripts.html#Scripts" 
accesskey="1">Scripts</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Helper scripts.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="Rules.html#Rules" 
accesskey="2">Rules</a>:</td><td>&nbsp;&nbsp;</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:&nbsp;<a rel="next" accesskey="n" href="Usage.html#Usage">Usage</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="index.html#Top">Top</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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">&bull; <a href="Overview.html#Overview" 
accesskey="1">Overview</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">What is GNUN and why is necessary?
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="Concepts.html#Concepts" 
accesskey="2">Concepts</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Basic concepts and goals.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="Advantages.html#Advantages" 
accesskey="3">Advantages</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">The goodness GNUN brings.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="Disadvantages.html#Disadvantages" 
accesskey="4">Disadvantages</a>:</td><td>&nbsp;&nbsp;</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> &nbsp; [<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:&nbsp;<a rel="next" accesskey="n" 
href="Main-Variables.html#Main-Variables">Main Variables</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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
+&lsquo;www&rsquo; 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 &lsquo;<samp><span 
class="samp">$(pkgdatadadir)</span></samp>&rsquo; (<samp><span 
class="file">/usr/local/share/gnun</span></samp> with
-the default &lsquo;<samp><span class="samp">prefix</span></samp>&rsquo;) so 
you can just create symlinks pointing to
+installed in &lsquo;<samp>$(pkgdatadadir)</samp>&rsquo; 
(<samp>/usr/local/share/gnun</samp> with
+the default &lsquo;<samp>prefix</samp>&rsquo;) 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 &lsquo;www&rsquo;.)
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a 
href="Runtime-Variables.html#Runtime-Variables" accesskey="1">Runtime 
Variables</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Variables 
to control the build process.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="Special-Targets.html#Special-Targets" accesskey="2">Special 
Targets</a>:</td><td>&nbsp;&nbsp;</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> &nbsp; [<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:&nbsp;<a rel="next" accesskey="n" 
href="Splitting-Long-Passages.html#Splitting-Long-Passages">Splitting Long 
Passages</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Modifying-Boilerplates.html#Modifying-Boilerplates">Modifying 
Boilerplates</a>,
-Up:&nbsp;<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> &nbsp; [<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">     &lt;!-- GNUN: localize URL /philosophy/category.png,
+</p>
+<div class="example">
+<pre class="example">&lt;!-- GNUN: localize URL /philosophy/category.png,
       /licenses/template-diagram.png and /graphics/jesus-cartoon.jpg --&gt;
-</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 
&lsquo;and&rsquo;,
+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&rsquo;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:&nbsp;<a rel="next" accesskey="n" href="PO-Files.html#PO-Files">PO 
Files</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Invoking-GNUN.html#Invoking-GNUN">Invoking GNUN</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo; 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>&lsquo;<samp><span 
class="samp">TEMPLATE_LINGUAS</span></samp>&rsquo;<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>&lsquo;<samp>TEMPLATE_LINGUAS</samp>&rsquo;</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&rsquo;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>&lsquo;<samp><span 
class="samp">extra-templates</span></samp>&rsquo;<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>&lsquo;<samp>extra-templates</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">optional-templates</span></samp>&rsquo;<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>&lsquo;<samp>optional-templates</samp>&rsquo;</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&rsquo;t been converted to PO files won&rsquo;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>&lsquo;<samp><span 
class="samp">FUZZY_DIFF_LINGUAS</span></samp>&rsquo;<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>&lsquo;<samp>FUZZY_DIFF_LINGUAS</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">HOME_LINGUAS</span></samp>&rsquo;<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>&lsquo;<samp><span
 class="samp">ROOT</span></samp>&rsquo;<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>&lsquo;<samp>ROOT</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">ALL_DIRS</span></samp>&rsquo;<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>&lsquo;<samp><span 
class="samp">gnu</span></samp>&rsquo;<dt>&lsquo;<samp><span 
class="samp">philosophy</span></samp>&rsquo;<dt>&lsquo;<samp><span 
class="samp">...directory...</span></samp>&rsquo;<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>&lsquo;<samp>ALL_DIRS</samp>&rsquo;</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>&lsquo;<samp>gnu</samp>&rsquo;</dt>
+<dt>&lsquo;<samp>philosophy</samp>&rsquo;</dt>
+<dt>&lsquo;<samp>&hellip;directory&hellip;</samp>&rsquo;</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&rsquo; 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> &nbsp; [<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:&nbsp;<a rel="next" accesskey="n" href="GNU-News.html#GNU-News">GNU 
News</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="New-Translation.html#New-Translation">New Translation</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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 &ldquo;<code>-C
+<p>If you have no compendium, just omit the &ldquo;<code>-C
 compendium.lang.po</code>&rdquo; 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
 &ldquo;fuzzy&rdquo; (unless you use a compendium); you still should make sure 
that
 the translations correspond to the original and remove those 
&ldquo;fuzzy&rdquo;
 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&eacute;dric Corazza &lt;address@hidden&gt;, 2006, 2008.
+# Jer&ocirc;me Dominguez &lt;address@hidden&gt;, 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&eacute;dric Corazza &lt;address@hidden&gt;, 2006, 2008.
-     # Jer&ocirc;me Dominguez &lt;address@hidden&gt;, 2007.
-</pre>
-   <p>In this example, it is clear that C&eacute;dric made the initial
+<p>In this example, it is clear that C&eacute;dric made the initial
 translation, Jer&ocirc;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> &nbsp; [<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:&nbsp;<a rel="next" accesskey="n" 
href="Localized-URLs.html#Localized-URLs">Localized URLs</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Comments-for-Translators.html#Comments-for-Translators">Comments for 
Translators</a>,
-Up:&nbsp;<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> &nbsp; [<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 &amp; 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&rsquo;s control.  Of course, this does not
 mean that no changes should happen&mdash;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:&nbsp;<a rel="next" accesskey="n" 
href="Migrating.html#Migrating">Migrating</a>,
-Up:&nbsp;<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> &nbsp; [<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 &ldquo;templated&rdquo; (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 &lt;address@hidden&gt;, YEAR.
+#
+#, fuzzy
+msgid &quot;&quot;
+msgstr &quot;&quot;
+&quot;Project-Id-Version: PACKAGE VERSION\n&quot;
+&quot;POT-Creation-Date: 2008-02-06 16:25-0500\n&quot;
+&quot;PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n&quot;
+&quot;Last-Translator: FULL NAME &lt;address@hidden&gt;\n&quot;
+&quot;Language-Team: LANGUAGE &lt;address@hidden&gt;\n&quot;
+&quot;MIME-Version: 1.0\n&quot;
+&quot;Content-Type: text/plain; charset=CHARSET\n&quot;
+&quot;Content-Transfer-Encoding: ENCODING\n&quot;
+</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 &lt;address@hidden&gt;, 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 &lt;address@hidden&gt;\n"
-     "Language-Team: LANGUAGE &lt;address@hidden&gt;\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>&lsquo;<samp><span 
class="samp">Project-Id-Version</span></samp>&rsquo;<dd>Add here the filename 
of the original article, without the
+</p>
+<a name="index-PO-headers"></a>
+<dl compact="compact">
+<dt>&lsquo;<samp>Project-Id-Version</samp>&rsquo;</dt>
+<dd><p>Add here the filename of the original article, without the
 sub-directory, like &ldquo;body-include-1.html&rdquo; or 
&ldquo;free-sw.html&rdquo;.
-
-     <br><dt>&lsquo;<samp><span 
class="samp">POT-Creation-Date</span></samp>&rsquo;<dd>Do not edit this field, 
it is already set when the POT is created.
-
-     <br><dt>&lsquo;<samp><span 
class="samp">PO-Revision-Date</span></samp>&rsquo;<dd>Likewise, do not edit.  
This field is automatically filled in when you
+</p>
+</dd>
+<dt>&lsquo;<samp>POT-Creation-Date</samp>&rsquo;</dt>
+<dd><p>Do not edit this field, it is already set when the POT is created.
+</p>
+</dd>
+<dt>&lsquo;<samp>PO-Revision-Date</samp>&rsquo;</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>&lsquo;<samp><span 
class="samp">Last-Translator</span></samp>&rsquo;<dd>The name and email address 
of the last translator who has edited the
+</p>
+</dd>
+<dt>&lsquo;<samp>Last-Translator</samp>&rsquo;</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 &lt;address@hidden&gt;
-</pre>
-     <br><dt>&lsquo;<samp><span 
class="samp">Language-Team</span></samp>&rsquo;<dd>This field should contain 
the mailing list on which the translation
-team can be reached&mdash;usually <a 
href="mailto:address@hidden";>www-LANG-<small 
class="dots">...</small>@gnu.org</a>. 
+</p>
+<div class="example">
+<pre class="example">Elvis Parsley &lt;address@hidden&gt;
+</pre></div>
+
+</dd>
+<dt>&lsquo;<samp>Language-Team</samp>&rsquo;</dt>
+<dd><p>This field should contain the mailing list on which the translation
+team can be reached&mdash;usually <a 
href="mailto:www-LANG-&hellip;@gnu.org";>www-LANG-&hellip;@gnu.org</a>.
 Example:
-
-     <pre class="example">          Czech &lt;address@hidden&gt;
-</pre>
-     <br><dt>&lsquo;<samp><span 
class="samp">MIME-Version</span></samp>&rsquo;<dd>Leave it like it is.
-
-     <br><dt>&lsquo;<samp><span 
class="samp">Content-Type</span></samp>&rsquo;<dd>Usually this is 
<code>text/plain; charset=UTF-8</code>; change the charset
+</p>
+<div class="example">
+<pre class="example">Czech &lt;address@hidden&gt;
+</pre></div>
+
+</dd>
+<dt>&lsquo;<samp>MIME-Version</samp>&rsquo;</dt>
+<dd><p>Leave it like it is.
+</p>
+</dd>
+<dt>&lsquo;<samp>Content-Type</samp>&rsquo;</dt>
+<dd><p>Usually this is <code>text/plain; charset=UTF-8</code>; change the 
charset
 accordingly.
-
-     <br><dt>&lsquo;<samp><span 
class="samp">Content-Transfer-Encoding</span></samp>&rsquo;<dd>Set this to 
<code>8bit</code>.  Note that the PO file header ends with this
-field, and it should contain a newline (&lsquo;<samp><span 
class="samp">\n</span></samp>&rsquo;).  Unfortunately, some
+</p>
+</dd>
+<dt>&lsquo;<samp>Content-Transfer-Encoding</samp>&rsquo;</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 (&lsquo;<samp>\n</samp>&rsquo;).  
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&rsquo;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 &lt;address@hidden&gt;, 2008.
+#
+msgid &quot;&quot;
+msgstr &quot;&quot;
+&quot;Project-Id-Version: free-sw.html\n&quot;
+&quot;POT-Creation-Date: 2008-02-06 16:25-0500\n&quot;
+&quot;PO-Revision-Date: 2008-02-09 15:23+0200\n&quot;
+&quot;Last-Translator: Yavor Doganov &lt;address@hidden&gt;\n&quot;
+&quot;Language-Team: Bulgarian &lt;address@hidden&gt;\n&quot;
+&quot;MIME-Version: 1.0\n&quot;
+&quot;Content-Type: text/plain; charset=UTF-8\n&quot;
+&quot;Content-Transfer-Encoding: 8-bit\n&quot;
+</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 &lt;address@hidden&gt;, 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 &lt;address@hidden&gt;\n"
-     "Language-Team: Bulgarian &lt;address@hidden&gt;\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 &ldquo;fuzzy&rdquo; marker; you should 
&ldquo;unfuzzy&rdquo; the
+<p>Notice the absence of the &ldquo;fuzzy&rdquo; marker; you should 
&ldquo;unfuzzy&rdquo; the
 header after entering the necessary information (this is done by
-simply pressing &lt;TAB&gt; 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>&rsquo;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>&lsquo;<samp><span class="samp">*GNUN-SLOT: TRANSLATOR'S 
NOTES*</span></samp>&rsquo;<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>&lsquo;<samp>*GNUN-SLOT: TRANSLATOR'S NOTES*</samp>&rsquo;</dt>
+<dd><p>This is for translator&rsquo;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, &lt;SPC&gt;.
-
-     <p><a name="index-credits_002c-translators-68"></a><a 
name="index-translators_0027-credits-69"></a><br><dt>&lsquo;<samp><span 
class="samp">*GNUN-SLOT: TRANSLATOR'S CREDITS*</span></samp>&rsquo;<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>&lsquo;<samp>*GNUN-SLOT: TRANSLATOR'S CREDITS*</samp>&rsquo;</dt>
+<dd><p>This is again optional, and should contain the name (and address) of
 the person who made the translation.  &ldquo;Translate&rdquo; this string as a
-space (&lt;SPC&gt;) 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 &ldquo;normalize&rdquo; 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 ()
+  &quot;Filter current po-mode buffer through `msgcat' tool to wrap all 
lines.&quot;
        (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 &quot;po-wrap.&quot;))
+           (tmp-buf (generate-new-buffer &quot;*temp*&quot;)))
        (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)))
+                   &quot;msgcat&quot; 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&rsquo;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">&bull; <a href="Notes-Slot.html#Notes-Slot" 
accesskey="1">Notes Slot</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">How to handle translator&rsquo;s notes.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="Credits-Slot.html#Credits-Slot" accesskey="2">Credits 
Slot</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">Translator&rsquo;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> &nbsp; [<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:&nbsp;<a rel="next" accesskey="n" 
href="Credits-Slot.html#Credits-Slot">Credits Slot</a>,
-Up:&nbsp;<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> &nbsp; [<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&rsquo;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&rsquo;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 &ldquo;translate&rdquo; the
-<code>msgstr</code> as a space (&lt;SPC&gt;)&mdash;otherwise the PO file will 
be
+translation doesn&rsquo;t have notes, you should &ldquo;translate&rdquo; the
+<code>msgstr</code> as a space (<tt class="key">SPC</tt>)&mdash;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&rsquo; notes in a PO file:
+</p>
+<div class="example">
+<pre class="example"># type: Content of: &lt;p&gt;
+msgid &quot;&quot;
+&quot;To understand the concept, you should think of &lt;q&gt;free&lt;/q&gt; 
&quot;
+&quot;as in &lt;q&gt;free speech,&lt;/q&gt; not as in &lt;q&gt;free 
beer.&lt;/q&gt;&quot;
+msgstr &quot;&quot;
+&quot;Translated message, where you want to clarify beer&lt;sup&gt;&lt;a &quot;
+&quot;href=\&quot;#TransNote1\&quot;&gt;1&lt;/a&gt;&lt;/sup&gt;, presumably 
because the &quot;
+&quot;expression in your language is different&quot;
+&hellip;
+&hellip;
+# type: Content of: &lt;div&gt;
+#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
+msgid &quot;*GNUN-SLOT: TRANSLATOR'S NOTES*&quot;
+msgstr &quot;&quot;
+&quot;&lt;h3&gt;Translator's notes&lt;/h3&gt;\n&quot;
+&quot;&lt;ol&gt;\n&quot;
+&quot;&lt;li id=\&quot;TransNote1\&quot;&gt;Note clarifying the 
text.&lt;/li&gt;\n&quot;
+&quot;&lt;/ol&gt;\n&quot;
+</pre></div>
 
-<pre class="example">     # type: Content of: &lt;p&gt;
-     msgid ""
-     "To understand the concept, you should think of &lt;q&gt;free&lt;/q&gt; "
-     "as in &lt;q&gt;free speech,&lt;/q&gt; not as in &lt;q&gt;free 
beer.&lt;/q&gt;"
-     msgstr ""
-     "Translated message, where you want to clarify beer&lt;sup&gt;&lt;a "
-     "href=\"#TransNote1\"&gt;1&lt;/a&gt;&lt;/sup&gt;, presumably because the "
-     "expression in your language is different"
-     ...
-     ...
-     # type: Content of: &lt;div&gt;
-     #. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
-     msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
-     msgstr ""
-     "&lt;h3&gt;Translator's notes&lt;/h3&gt;\n"
-     "&lt;ol&gt;\n"
-     "&lt;li id=\"TransNote1\"&gt;Note clarifying the text.&lt;/li&gt;\n"
-     "&lt;/ol&gt;\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. &lsquo;<samp><span 
class="samp">TransNote2</span></samp>&rsquo;, &lsquo;<samp><span 
class="samp">TransNote3</span></samp>&rsquo;, etc. and
+incremented number, i.e. &lsquo;<samp>TransNote2</samp>&rsquo;, 
&lsquo;<samp>TransNote3</samp>&rsquo;, etc. and
 you have to add them as more <code>&lt;li&gt;</code> elements accordingly.
-
-   <p>Do not worry about the <code>\n</code> character&mdash;it is inserted
-automatically when you press &lt;RET&gt;.  It is not compulsory that
+</p>
+<p>Do not worry about the <code>\n</code> character&mdash;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&rsquo; 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&mdash;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> &nbsp; [<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:&nbsp;<a rel="next" accesskey="n" 
href="Concepts.html#Concepts">Concepts</a>,
-Up:&nbsp;<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> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html