[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
trans-coord/gnun/server/gnun ChangeLog doc/gnun... [sr-hr]
|
From: |
Yavor Doganov |
|
Subject: |
trans-coord/gnun/server/gnun ChangeLog doc/gnun... [sr-hr] |
|
Date: |
Mon, 05 Jul 2010 15:21:03 +0000 |
CVSROOT: /sources/trans-coord
Module name: trans-coord
Branch: sr-hr
Changes by: Yavor Doganov <yavor> 10/07/05 15:21:03
Modified files:
gnun/server/gnun: ChangeLog
gnun/server/gnun/doc: gnun.texi web-trans.texi
Log message:
* doc/web-trans.texi (Introduction, Submitting as PO)
(Submitting as Plain Text, New Team, Commits, Migrating, SSI)
(Priorities, Mailing Lists, Savannah Projects):
* doc/gnun.texi (Top, Introduction, Overview, Concepts)
(Advantages, Usage, Invoking GNUN, Runtime Variables, sync)
(triggers, Main Variables, PO Files, New Translation)
(Notes Slot, Credits Slot, Migrating, GNU News, PO Tips)
(PO Files and Team, GNUmakefile.team Variables, Webmaster Tips)
(Internals, Scripts, make-prototype, gnun-validate-html)
(mailfail, validate-html-notify, gnun-clear-previous, Bugs): Get
rid of @acronym, for simplicity.
Suggested by Karl Berry in
http://thread.gmane.org/gmane.comp.sysutils.automake.bugs/4869.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/ChangeLog?cvsroot=trans-coord&only_with_tag=sr-hr&r1=1.157.2.17&r2=1.157.2.18
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/gnun.texi?cvsroot=trans-coord&only_with_tag=sr-hr&r1=1.9.2.9&r2=1.9.2.10
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/web-trans.texi?cvsroot=trans-coord&only_with_tag=sr-hr&r1=1.6.2.3&r2=1.6.2.4
Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/ChangeLog,v
retrieving revision 1.157.2.17
retrieving revision 1.157.2.18
diff -u -b -r1.157.2.17 -r1.157.2.18
--- ChangeLog 1 Jul 2010 15:06:43 -0000 1.157.2.17
+++ ChangeLog 5 Jul 2010 15:21:03 -0000 1.157.2.18
@@ -1,6 +1,22 @@
+2010-07-05 Yavor Doganov <address@hidden>
+
+ * doc/web-trans.texi (Introduction, Submitting as PO)
+ (Submitting as Plain Text, New Team, Commits, Migrating, SSI)
+ (Priorities, Mailing Lists, Savannah Projects):
+ * doc/gnun.texi (Top, Introduction, Overview, Concepts)
+ (Advantages, Usage, Invoking GNUN, Runtime Variables, sync)
+ (triggers, Main Variables, PO Files, New Translation)
+ (Notes Slot, Credits Slot, Migrating, GNU News, PO Tips)
+ (PO Files and Team, GNUmakefile.team Variables, Webmaster Tips)
+ (Internals, Scripts, make-prototype, gnun-validate-html)
+ (mailfail, validate-html-notify, gnun-clear-previous, Bugs): Get
+ rid of @acronym, for simplicity.
+ Suggested by Karl Berry in
+ http://thread.gmane.org/gmane.comp.sysutils.automake.bugs/4869.
+
2010-07-01 Yavor Doganov <address@hidden>
- Bail out when bulding homepage/whatsnew if the lang is undefined.
+ Bail out when building homepage/whatsnew if the lang is undefined.
* GNUmakefile ($(template-dir)/po/whatsnew.%.html)
($(rootdir)/home.$(1).shtml): For robustness, check if the
language is defined in TEMPLATE_LINGUAS and exit with an error if
Index: doc/gnun.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/gnun.texi,v
retrieving revision 1.9.2.9
retrieving revision 1.9.2.10
diff -u -b -r1.9.2.9 -r1.9.2.10
--- doc/gnun.texi 1 Jul 2010 15:06:08 -0000 1.9.2.9
+++ doc/gnun.texi 5 Jul 2010 15:21:03 -0000 1.9.2.10
@@ -14,20 +14,19 @@
@copying
-This manual (updated @value{UPDATED}) is for @acronym{GNU}nited Nations
-(version @value{VERSION}),
-a suite for maintaining translations of www.gnu.org essays and other
address@hidden
+This manual (updated @value{UPDATED}) is for GNUnited Nations (version
address@hidden), a suite for maintaining translations of www.gnu.org
+essays and other address@hidden
@sp 1
Copyright @copyright{} 2008, 2009, 2010 Free Software Foundation, Inc.
@quotation
Permission is granted to copy, distribute and/or modify this document
-under the terms of the @acronym{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 address@hidden Free Documentation License.''
+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.''
@end quotation
@end copying
@@ -57,61 +56,57 @@
@menu
* Introduction:: Overview of GNUnited Nations.
* Usage:: Basic usage, invocation and tips.
-* Internals:: Dive into @acronym{GNUN}.
+* Internals:: Dive into GNUN.
* Bugs:: How to report bugs.
* Index::
* Copying This Manual:: The GNU Free Documentation License.
@end menu
@node Introduction
address@hidden Introduction to @acronym{GNU}nited Nations
address@hidden Introduction to GNUnited Nations
address@hidden Nations (abbreviated @acronym{GNUN}) is a
-collection of makefiles and scripts that are supposed to make the life
-of @url{http://gnu.org} translators easier. Although it is
-specifically developed for the @acronym{GNU} Project's website, it
-could be customized, at least in theory, to fit the needs of other
-internationalized sites. @acronym{GNUN} is in early stage of
+GNUnited Nations (abbreviated GNUN) is a collection of makefiles and
+scripts that are supposed to make the life of @url{http://gnu.org}
+translators easier. Although it is specifically developed for the GNU
+Project's website, it could be customized, at least in theory, to fit
+the needs of other internationalized sites. GNUN is in early stage of
development, but if it proves useful, and if there is sufficient
interest (and time), it is possible to develop a robust configuration
interface that would be appropriate for general usage.
-It is vitally important to understand that @acronym{GNUN} is
address@hidden a silver bullet that solves all problems. If we have to be
-honest, deploying @acronym{GNUN} in fact even does create some
-(@pxref{Disadvantages}).
+It is vitally important to understand that GNUN is @emph{not} a silver
+bullet that solves all problems. If we have to be honest, deploying
+GNUN in fact even does create some (@pxref{Disadvantages}).
address@hidden Nations is free software, available under the
address@hidden General Public License.
+GNUnited Nations is free software, available under the GNU General
+Public License.
This manual is organized in way that is suitable both for translators
-and @acronym{GNU} Web Translation managers (plus eventually interested
address@hidden Webmasters, if any). It may also serve as an
-introductory material and reference for new @acronym{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.
+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.
This manual is free documentation, and you can modify and redistribute
-it under the terms of the @acronym{GNU} Free Documentation License.
address@hidden This Manual, ,GNU Free Documentation License}.
+it under the terms of the GNU Free Documentation License. @xref{Copying
+This Manual, ,GNU Free Documentation License}.
@menu
-* Overview:: What is @acronym{GNUN} and why is necessary?
+* Overview:: What is GNUN and why is necessary?
* Concepts:: Basic concepts and goals.
-* Advantages:: The goodness @acronym{GNUN} brings.
+* Advantages:: The goodness GNUN brings.
* Disadvantages:: Staying on firm ground.
@end menu
@node Overview
address@hidden Why @acronym{GNUN} is Being Developed
address@hidden Why GNUN is Being Developed
-The @acronym{GNU} Project's website, @uref{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, @uref{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
@@ -120,50 +115,46 @@
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
-keeping their translation in line with the changing original
-articles. As a consequence, the @acronym{GNU} Project is facing the
-problem of maintaining them in suboptimal ways, in order to keep the
-information updated.
-
-The reasons for developing @acronym{GNU}nited Nations are very similar
-to those that lead to the inception of @acronym{GNU} gettext, or
address@hidden Documentation Utilities (@code{gnome-doc-utils}) some
-years later.
+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.
+
+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}) some years later.
@node Concepts
address@hidden What @acronym{GNU}nited Nations is and Should be
address@hidden What GNUnited Nations is and Should be
-The basic concept behind @acronym{GNUN} is that localization of HTML
-articles is similar to localization of computer
address@hidden, it is much more closer to localization of
-software documentation, where typically strings (also known as
-``messages'' in gettext's context) are longer than strings in
-programs. Nevertheless, all points raised still apply.}. 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.
-
-The @acronym{GNU} @code{gettext} package already provides the needed
-infrastructure for maintaining translations using PO files.
address@hidden, , Introduction, gettext, GNU gettext tools}, for a basic
-overview. @acronym{GNU}nited Nations fills the gaps to apply this
-infrastructure to articles in @url{http://gnu.org} web
address@hidden process of converting HTML to PO and the other way
-around is performed using po4a (``po for anything''), see
address@hidden://po4a.alioth.debian.org}.}
-
-The following diagram summarizes the relation between the files
-handled by @acronym{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.
+The basic concept behind GNUN is that localization of HTML articles is
+similar to localization of computer address@hidden, it is
+much more closer to localization of software documentation, where
+typically strings (also known as ``messages'' in gettext's context) are
+longer than strings in programs. Nevertheless, all points raised still
+apply.}. 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.
+
+The GNU @code{gettext} package already provides the needed
+infrastructure for maintaining translations using PO files. @xref{Top,
+, Introduction, gettext, GNU gettext tools}, for a basic overview.
+GNUnited Nations fills the gaps to apply this infrastructure to articles
+in @url{http://gnu.org} web address@hidden process of converting
+HTML to PO and the other way around is performed using po4a (``po for
+anything''), see @uref{http://po4a.alioth.debian.org}.}
+
+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.
@example
@group
@@ -179,27 +170,25 @@
@end group
@end example
-The indication @samp{*} appears in two places in this picture, and
-means that the corresponding file is intended to be edited by humans.
-The author or web maintainer edits the original
address@hidden@var{article}.html}, and translators edit
address@hidden@address@hidden All other files are regenerated
-by @acronym{GNUN} and any manual changes on them will be lost on the
-next run.
+The indication @samp{*} appears in two places in this picture, and means
+that the corresponding file is intended to be edited by humans. The
+author or web maintainer edits the original @address@hidden,
+and translators edit @address@hidden@var{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 @samp{make -C server/gnun}. This is the primary way to invoke
address@hidden, since it is implemented as a set of recipes for
address@hidden @code{make}.
+GNUN, since it is implemented as a set of recipes for GNU @code{make}.
-First, @acronym{GNUN} extracts all translatable strings from the
-original English article @address@hidden into
address@hidden@var{article}.pot}. The resulted file is suitable for
-manipulation with the various @acronym{GNU} @samp{gettext} utilities.
-It contains all original article strings and all translations are set
-to empty. The letter @code{t} in @file{.pot} marks this as a Template
-PO file, not yet oriented towards any particular language.
+First, GNUN extracts all translatable strings from the original English
+article @address@hidden into @address@hidden The
+resulted file is suitable for manipulation with the various GNU
address@hidden utilities. It contains all original article strings and
+all translations are set to empty. The letter @code{t} in @file{.pot}
+marks this as a Template PO file, not yet oriented towards any
+particular language.
The first time though, there is no @address@hidden@var{lang}.po}
yet, so a translator must manually copy @address@hidden to
@@ -225,23 +214,22 @@
for more information.
When the PO file actually exists (hopefully populated with initial
-translations), @acronym{GNUN} generates
address@hidden@address@hidden file. It takes its structure
-from the original @address@hidden, but all translatable
-strings are replaced with their translations specified in
address@hidden@address@hidden
-
-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, @acronym{GNUN} will
-automatically rebuild @address@hidden, and will merge the
-changes to @address@hidden@var{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
+translations), GNUN generates @address@hidden@var{lang}.html} file.
+It takes its structure from the original @address@hidden, but
+all translatable strings are replaced with their translations specified
+in @address@hidden@var{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 @address@hidden, and will merge the changes to
address@hidden@address@hidden 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
@address@hidden@var{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
+strings in the translation will be substituted with the original English
+text, until the translation teams update them in
@address@hidden@var{lang}.po}.
Those changes in the original article that do not affect the
@@ -254,13 +242,13 @@
@c that explains those details like exact paths in www, diagram with
@c the basic directory layout, additional files like .translinks, etc.
-The POT for every article under @acronym{GNUN}'s control is kept in
-the `www' repository under a special directory @file{po/}, which is a
+The POT for every article under GNUN's control is kept in the `www'
+repository under a special directory @file{po/}, which is a
sub-directory of the relevant directory in the `www' tree. So, for
@indicateurl{http://www.gnu.org/philosophy/free-sw.html} that is
address@hidden/po/}. Except @file{free-sw.pot}, this directory
-holds the canonical source of every translation, like
address@hidden, @file{free-sw.ca.po}, etc.
address@hidden/po/}. Except @file{free-sw.pot}, this directory holds
+the canonical source of every translation, like @file{free-sw.bg.po},
address@hidden, etc.
Several additional features are implemented, like automatic update of
the list of the available translations. For example, if a new
@@ -273,14 +261,14 @@
improvement. Translators' credits are also handled, as well as
translators' notes, if any.
address@hidden 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.
+GNUN can be extended, and new features will certainly be added. The
address@hidden 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.
@node Advantages
address@hidden Major Advantages of @acronym{GNUN}
address@hidden Major Advantages of GNUN
Here is a simple list of situations where we hope this suite would
prove to be useful.
@@ -322,10 +310,10 @@
@item
Markup consistency site-wide---it would be substantially easier to
update the site to a future standard, because translations will
-naturally follow the changes in the original articles. This also
-means that translation teams do not have to undergo the boring process
-of converting their articles to the new @acronym{SSI}-based layout;
-this will be done automatically.
+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.
@item
Easy updates by translators. Modified paragraphs, links, etc. will
@@ -376,8 +364,8 @@
@end flushright
@sp 1
address@hidden currently consists of a few makefiles, scripts and
-optional @address@hidden files, intended to contain
+GNUN currently consists of a few makefiles, scripts and optional
address@hidden@var{lang}.html} files, intended to contain
article-independent but team-specific information. They are designed to
reside in the @file{server/gnun} directory, but this may change. In all
examples in this manual, ``invoking'' means executing on the command
@@ -407,15 +395,15 @@
@cindex invoking
@cindex triggering, build
-The central part of @acronym{GNU}nited Nations is a makefile; actually a
+The central part of GNUnited Nations is a makefile; actually a
@file{GNUmakefile} since it heavily relies on features and extensions
-available in @acronym{GNU} Make. Thus, invoking a build consists of
-typing @command{make} on the command line, or within cron. If you are
-deploying the software on a non-GNU machine, probably @acronym{GNU} Make
-is installed and available as @command{gmake} or @command{gnumake}. If
+available in GNU Make. Thus, invoking a build consists of typing
address@hidden 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 @command{gmake} or @command{gnumake}. If
not, you should consider installing it, since the build will fail
otherwise. See @uref{http://www.gnu.org/software/make} for information
-how to download and install @acronym{GNU} Make.
+how to download and install GNU Make.
If you don't specify a target, @command{make} by default builds the
target @code{all}, which in this case is to rebuild all translations
@@ -465,12 +453,12 @@
@code{template-files} variable.
@item VCS=always
-Because @acronym{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 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.
+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
+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.
@cindex VALIDATE
@cindex validation
@@ -500,11 +488,11 @@
Do not send email notifications about errors. This is the default.
@item 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
+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{web-addr} and @code{transl-addr} control the
-recipients; normally they should be set to the @acronym{GNUN}
-maintainers, webmasters and translators accordingly.
+recipients; normally they should be set to the GNUN maintainers,
+webmasters and translators accordingly.
@cindex VERBOSE
@cindex output, detailed
@@ -617,13 +605,13 @@
@code{files-to-sync} variable during a subsequent invocation.
In addition, @code{sync} synchronizes all ``verbatim'' server templates
-that are not under @acronym{GNUN}'s control, such as
address@hidden/header.html}, @file{server/banner.html},
address@hidden/footer.html} and their translations, as defined in the
address@hidden 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.
+that are not under GNUN's control, such as @file{server/header.html},
address@hidden/banner.html}, @file{server/footer.html} and their
+translations, as defined in the @code{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.
@code{VCS=always} has no effect on this target, as well as
@code{VALIDATE}.
@@ -657,14 +645,14 @@
@c FIXME: Check how Subversion behaves with keywords and update the
@c paragraph below.
-When a @acronym{GNUN} build completes and some translations fail at the
-XHTML validation stage, the result is checked in the repository, as
-explained earlier (@pxref{Runtime Variables}). Thus, CVS updates the
address@hidden 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
+When a GNUN build completes and some translations fail at the XHTML
+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.
@@ -675,7 +663,7 @@
based on the timestamp of the target that must be rebuilt. Finally, it
deletes all those @file{*.hook} files.
-To summarize, for effective operation @acronym{GNUN} should be invoked
+To summarize, for effective operation GNUN should be invoked
automatically as @code{make ; cvs|svn commit -m @dots{} ; make
triggers}. To illustrate this, here is a concrete example showing the
official job running at fencepost.gnu.org:
@@ -717,12 +705,12 @@
order to make translators' life easier: variables that translators are
free to modify and variables that are modified by the web-translators
address@hidden because presumably, they are more familiar with
address@hidden Nations' internals. From a purely technical point
-of view, there is no difference.}, ideally after performing some local
-tests. A translation team leader should update only
address@hidden and @code{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.
+GNUnited Nations' internals. From a purely technical point of view,
+there is no difference.}, ideally after performing some local tests. A
+translation team leader should update only @code{TEMPLATE_LINGUAS} and
address@hidden; everything else is supposed to be built
+automagically, without manual intervention. If not, that is a bug that
+should be reported and fixed.
@table @samp
@cindex TEMPLATE_LINGUAS
@@ -730,14 +718,14 @@
@cindex defining templates
@item TEMPLATE_LINGUAS
A space-separated list with languages. Add here your language code
address@hidden and only if} you have all the @acronym{SSI} templates
-translated, and have already committed in the repository all these
-template files: @file{server/@/po/@/address@hidden,
address@hidden and only if} you have all the SSI templates translated, and
+have already committed in the repository all these template files:
address@hidden/@/po/@/address@hidden,
@file{server/@/po/@/address@hidden,
@file{server/@/po/@/address@hidden,
@file{server/@/po/@/address@hidden, as well as the templates
-that are not under @acronym{GNUN}'s control and are translated manually,
-like @file{server/address@hidden,
+that are not under GNUN's control and are translated manually, like
address@hidden/address@hidden,
@file{server/address@hidden and
@file{server/address@hidden
@@ -774,7 +762,7 @@
A space-separated list of basenames for articles residing in
@var{directory}, 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 @acronym{GNUN}.
+way its translations to be maintained via GNUN.
@end table
@node PO Files
@@ -796,25 +784,25 @@
@itemize
@cindex PO editors
@item
-PO mode. We recommend using @acronym{GNU} Emacs in PO mode, because
-Emacs is the program that is suitable for performing any task when it
-comes to maintaining the @acronym{GNU} Project's website. Provided
-that you have @acronym{GNU} gettext installed, any @file{.po} file you
-visit should automatically switch to PO mode. You can enable/disable
-it by @code{M-x po-mode @key{RET}}. On some @acronym{GNU}/Linux
-distros such as gNewSense, PO mode is available in a separate package,
address@hidden See @uref{http://www.gnu.org/software/gettext}.
+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 @file{.po} file you visit should automatically
+switch to PO mode. You can enable/disable it by @code{M-x po-mode
address@hidden On some GNU/Linux distros such as gNewSense, PO mode is
+available in a separate package, @code{gettext-el}. See
address@hidden://www.gnu.org/software/gettext}.
@item
-gTranslator---the @acronym{GNOME} PO editor. See
+gTranslator---the GNOME PO editor. See
@uref{http://gtranslator.sourceforge.net}.
@item
-Lokalize---the @acronym{KDE} 4 editor. See
+Lokalize---the KDE 4 editor. See
@uref{http://userbase.kde.org/@/Lokalize}.
@item
-KBabel---the @acronym{KDE} 3 editor. See @uref{http://kbabel.kde.org}.
+KBabel---the KDE 3 editor. See @uref{http://kbabel.kde.org}.
@item
Poedit---another popular editor that is based on the @code{wxWidgets}
@@ -841,7 +829,7 @@
@menu
* New Translation:: How to start a new translation.
* Migrating:: How to migrate an existing translation to a PO
- format under @acronym{GNUN}'s control.
+ format under GNUN's control.
* GNU News:: How to handle ``whatsnew'' (a.k.a. ``gnunews'').
* PO Tips:: Tips and hints for translators.
* generic.LANG.html:: Specifying information that will propagate in
@@ -862,10 +850,9 @@
@code{cd philosophy/po ; cp free-sw.pot address@hidden and then
edit the latter. If @file{free-sw.pot} does not exist it is because
either the article is not yet ``templated'' (i.e. migrated to the new
-style), or the @acronym{GNUN} maintainers have not yet added it to the
-value of the appropriate variable in @file{server/gnun/gnun.mk}. In
-that case, just ask them to do the necessary in order the POT to be
-generated.
+style), or the GNUN maintainers have not yet added it to the value of
+the appropriate variable in @file{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 @command{msginit} utility that would populate
the PO file header with the right information, provided your
@@ -923,11 +910,11 @@
@end example
@item Language-Team
-This field should contain the mailing list on which the translation
-team can be reached---sometimes this is the alias
+This field should contain the mailing list on which the translation team
+can be reached---sometimes this is the alias
@email{web-translators-LANG@@gnu.org}, but in some cases it is a
-separate, address@hidden list. It could be a URL of the team's
-homepage, provided that it contains contact details. Example:
+separate, non-GNU list. It could be a URL of the team's homepage,
+provided that it contains contact details. Example:
@example
French <trad-gnu@@april.org>
@@ -944,7 +931,7 @@
Set this to @code{8bit}. Note that the PO file header ends with this
field, and it should contain a newline (@samp{\n}). Unfortunately, some
PO editors remove the newline, which causes an unnecessary revision when
-the file is automatically modified by @acronym{GNUN}'s rules.
+the file is automatically modified by GNUN's rules.
@end table
Here is an example of a properly edited header:
@@ -1103,7 +1090,7 @@
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 @acronym{CSS} class for them, and also to convert the
+a special CSS class for them, and also to convert the
translations in other formats such as Texinfo---when these features
are implemented.
@@ -1131,8 +1118,8 @@
It is highly desirable to use this form, but you may omit the email
address or add the homepage of the translator, provided that the
translation team leader ensures that it constantly meets the linking
-criteria for gnu.org. Please follow the @acronym{FSF} HTML Style
-Sheet when adding @acronym{URI}s or other information.
+criteria for gnu.org. Please follow the FSF HTML Style Sheet when
+adding URIs or other information.
@node Migrating
@subsection Transforming existing translation in PO format
@@ -1159,14 +1146,14 @@
you are confident that the translation you have been yanking strings
from is a completely up-to-date translation.
-There is no need to delete the existing HTML translation,
address@hidden will automatically overwrite it. The only thing a
-translator should do is to commit the PO file in the repository.
+There is no need to delete the existing HTML translation, GNUN will
+automatically overwrite it. The only thing a translator should do is to
+commit the PO file in the repository.
When an essay has been translated by several people through the years,
it is important that this information is recorded and reflected in the
-PO file. In the future, special targets may be added to enable the
address@hidden to check who translated a particular article, and when.
+PO file. In the future, special targets may be added to enable the FSF
+to check who translated a particular article, and when.
A recommended way to do this is as follows:
@@ -1185,13 +1172,13 @@
translator returned in 2008 and continued maintaining it.
@node GNU News
address@hidden Special Handling For @acronym{GNU} News
address@hidden Special Handling For GNU News
@cindex gnunews
@cindex whatsnew
@cindex gnusflashes
-The @acronym{GNU} website has infrastructure for supporting ``What's
-New'', also known as address@hidden News''---see
+The GNU website has infrastructure for supporting ``What's New'', also
+known as ``GNU News''---see
@uref{http://www.gnu.org/@/server/@/standards/@/README.webmastering.html#polnews}
for details. Entries are added in a special plain text file,
@file{server/whatsnew.txt} and are used to build
@@ -1199,8 +1186,8 @@
former is used by @file{server/whatsnew.html}, while the latter is
included in the homepage.
address@hidden has additional rules for building @file{whatsnew.pot},
-which contains a combination of all necessary strings for
+GNUN has additional rules for building @file{whatsnew.pot}, which
+contains a combination of all necessary strings for
@file{server/address@hidden,
@file{server/address@hidden and
@address@hidden There is nothing unusual in this
@@ -1211,9 +1198,9 @@
generated for the first time in order the translated homepage to include
it instead of @file{gnusflashes.include}.
-Note that localized @acronym{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.
+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.
@node PO Tips
@subsection Useful Hints For Editing PO Files
@@ -1238,13 +1225,12 @@
In the next build, your @address@hidden@var{lang}.html} will be
built and the link to it will propagate to all translations, provided
-that they are under @acronym{GNUN}'s control.
+that they are under GNUN's control.
@item
If you don't feel comfortable editing @file{gnun.mk}, do not worry.
-Someone from the @acronym{GNUN} maintainers will notice and will amend
address@hidden or @code{HOME_LINGUAS} for you, as
-appropriate.
+Someone from the GNUN maintainers will notice and will amend
address@hidden or @code{HOME_LINGUAS} for you, as appropriate.
@item
Dealing with obsolete strings. Elements which are removed from the
@@ -1299,13 +1285,13 @@
@item
Wrapping of @code{msgstr} using @kbd{M-q} in Emacs (or other means) is
-considered harmful. It is best to leave @acronym{GNUN} (or more
-precisely, Po4a) to do the wrapping---that way all generated HTML
-translations will have predictable results. This will help tremendously
-for the conversion to other formats, like Texinfo. Also, note that not
-all elements are wrapped by default, so deliberately wrapping the text
-inside the @code{msgstr} could lead to an invalid page or a page that is
-valid, but is rendered incorrectly by the web browser.
+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
address@hidden could lead to an invalid page or a page that is valid, but
+is rendered incorrectly by the web browser.
@end itemize
@node generic.LANG.html
@@ -1344,11 +1330,11 @@
@cindex repository, translation project
@cindex team maintenance
address@hidden operates on the ``official'' Web repository of the
-Savannah project `www', where normally only the coordinators of
-translation teams have write access. However, all translation teams
-have their own projects, so it is possible to take advantage of Savannah
-as a hosting facility to make the team work more comfortable.
+GNUN operates on the ``official'' Web repository of the Savannah project
+`www', where normally only the coordinators of translation teams have
+write access. However, all translation teams have their own projects,
+so it is possible to take advantage of Savannah as a hosting facility to
+make the team work more comfortable.
The PO files provide an excellent and natural way to review each other's
translations, because the translation appears right below the original
@@ -1468,8 +1454,8 @@
Update both `www' and address@hidden' 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, @acronym{GNU}
-Bzr, @acronym{GNU} Arch and Mercurial (Hg) repositories are supported.
+determined automatically; currently only CVS, Subversion, GNU Bzr, GNU
+Arch and Mercurial (Hg) repositories are supported.
@strong{Caution:} The makefile rule will commit all local changes, not
only those that resulted from running @command{msgmerge}. Thus, it is
@@ -1497,9 +1483,9 @@
@item format
A convenience rule to rewrap all files upto the standard length. Most
PO editors leave the @code{msgstr} as a single long line after it has
-been edited, but @acronym{GNUN} will automatically rewrap the file to
-the standard line length when it is processed. Wrapping long lines in
-PO files is a good pracice as it avoids unnecessary revisions.
+been edited, but GNUN will automatically rewrap the file to the standard
+line length when it is processed. Wrapping long lines in PO files is a
+good pracice as it avoids unnecessary revisions.
This rule checks for all translations that have lines longer than 80,
and runs @command{msgcat} accordingly to reformat them. For that
@@ -1614,10 +1600,10 @@
you don't have to make titanic efforts to help.
If you plan to edit a certain page extensively, please do so within the
-period between two adjacent @acronym{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.
+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.
Use @emph{only} US-ASCII characters and HTML entities for the others.
This is required because the English text in the articles serves as a
@@ -1666,20 +1652,19 @@
after the beginning of the HTML comment (@code{<!--}), since this will
unnecessarily indent the comment in the POT.
address@hidden:} Any structural diversion from
address@hidden in a specific article is likely to result in
-errors from @acronym{GNUN}. Any unexpected updates to the server
-templates (such as changing the entire look & feel of the site) will
-most probably break @emph{all} translations under @acronym{GNUN}'s
-control. Of course, this does not mean that such changes should not
-happen---only that they must be applied in our sandbox first, to
-ensure a smooth transition.
address@hidden:} Any structural diversion from @file{boilerplate.html}
+in a specific article is likely to result in errors from GNUN. Any
+unexpected updates to the server templates (such as changing the entire
+look & feel of the site) will most probably break @emph{all}
+translations under GNUN's control. Of course, this does not mean that
+such changes should not happen---only that they must be applied in our
+sandbox first, to ensure a smooth transition.
@node Internals
address@hidden Unexciting Information for @acronym{GNUN}'s Operation
address@hidden Unexciting Information for GNUN's Operation
-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
+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.
@menu
@@ -1696,7 +1681,7 @@
useful on their own.
The @command{gnun-clear-previous} script is an exception---it is not
-used in @acronym{GNUN}'s rules at all.
+used in GNUN's rules at all.
@menu
* make-prototype::
@@ -1713,11 +1698,11 @@
@cindex generation, POT, .proto
This is a Guile script which makes the ``prototype'' file,
address@hidden@var{lang}.proto}, from which the POT is generated.
address@hidden 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.
address@hidden@var{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.
In addition, @command{make-prototype} guards the timestamp (the
@w{$}Date$ RCS keyword) in order the timestamp of the translation to
@@ -1757,7 +1742,7 @@
@itemx address@hidden
The file containing the translation links. This makes sense only for
articles, since the homepage has its own @file{translations.include}
-which gets included via an @acronym{SSI} directive.
+which gets included via an SSI directive.
@c FIXME: This should be improved, it is not clear.
@item --version
@@ -1771,13 +1756,12 @@
@subsection The @command{gnun-validate-html} Script
@cindex validation, XHTML
-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 @acronym{W3C} standard. Sometimes webmasters make
-mistakes, and translators too, so this tool is useful to catch errors
-of that kind.
+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.
address@hidden enforces XHTML validation at build time if invoked with
+GNUN enforces XHTML validation at build time if invoked with
@code{VALIDATE=yes}.
The script expects only one @var{file} as an argument and will exit
@@ -1791,7 +1775,7 @@
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.
address@hidden depends on @acronym{GNU} Mailutils, or a compatible
address@hidden depends on GNU Mailutils, or a compatible
implementation, such as BSD's mailx.
Usage:
@@ -1821,8 +1805,7 @@
The arguments of @code{CMD}, if any.
@end table
-Here is a typical example, similar to the way it is used in
address@hidden:
+Here is a typical example, similar to the way it is used in GNUN:
@example
mailfail translators@@example.org "Bad PO" msgfmt -cv -o /dev/null bg.po
@@ -1859,8 +1842,8 @@
The recipient of the message.
@item FILE
-The HTML file that has to be validated for compliance with the
address@hidden standard.
+The HTML file that has to be validated for compliance with the W3C
+standard.
@end table
The subject of the message is hardcoded in the script, since this
@@ -1871,9 +1854,9 @@
@subsection The @command{gnun-clear-previous} Script
@cindex previous, manipulating PO files
-This simple script is not used internally in @acronym{GNUN}. It is
-merely for convenience only, for those who find it hard to remember the
-various @samp{gettext} tools and their options.
+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
address@hidden tools and their options.
@command{gnun-clear-previous} deletes the @dfn{previous} messages in a
PO file, which is a good thing to do after the corresponding translation
@@ -1904,10 +1887,10 @@
@cindex bugs, reporting
@cindex reporting bugs
address@hidden Nations, like any other software, is not bug free.
-There are some known bugs and annoyances, which are listed in the
address@hidden file, but it is absolutely certain that there are more
-which we know nothing about.
+GNUnited Nations, like any other software, is not bug free. There are
+some known bugs and annoyances, which are listed in the @file{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 @email{bug-gnun@@gnu.org} or
Index: doc/web-trans.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/web-trans.texi,v
retrieving revision 1.6.2.3
retrieving revision 1.6.2.4
diff -u -b -r1.6.2.3 -r1.6.2.4
--- doc/web-trans.texi 10 Jan 2010 09:08:37 -0000 1.6.2.3
+++ doc/web-trans.texi 5 Jul 2010 15:21:03 -0000 1.6.2.4
@@ -5,7 +5,7 @@
@settitle GNU Web Translators Manual
@c FIXME: Would be nice to have it in the format `%:b %:d, %:y', but
@c in English.
address@hidden lastupdate 10.11.2009
address@hidden lastupdate 05.07.2010
@afourpaper
@c %**end of header
@@ -14,19 +14,18 @@
@copying
-This manual is a guide for the @acronym{GNU} Web address@hidden
-Last updated on @value{lastupdate}, for @acronym{GNU}nited Nations
-version @value{VERSION}.
+This manual is a guide for the GNU Web address@hidden Last updated on
address@hidden, for GNUnited Nations version @value{VERSION}.
@sp 1
Copyright @copyright{} 2009, 2010 Free Software Foundation, Inc.
@quotation
Permission is granted to copy, distribute and/or modify this document
-under the terms of the @acronym{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 address@hidden Free Documentation License.''
+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.''
@end quotation
@end copying
@@ -72,10 +71,10 @@
This manual is an attempt to describe in detail the process of
translating www.gnu.org articles---how to join a team, or start a new
one, the responsibilities of the team members and leaders, as well as
-some peculiarities of the @acronym{GNU} Project's website when it comes
-to localization.
+some peculiarities of the GNU Project's website when it comes to
+localization.
-The @acronym{GNU} website contains hundreds of documents, most of them
+The GNU website contains hundreds of documents, most of them
philosophical articles (essays) and technical documents which need to be
translated to make them available to a broader audience. This is
especially important for the philosophy-related materials, as many
@@ -83,20 +82,20 @@
read such articles in their native language. Dealing with the task of
translating a website this large is a hard job, and too often people
volunteering as translators get frustrated or lose interest in keeping
-up with that work. Reading this manual, and the related @acronym{GNUN}
-manual (@pxref{Top, , GNUnited Nations, gnun, The GNUnited Nations
-Manual}), is just the tip of the iceberg. This is not meant to
-discourage any potential volunteer; rather, we prefer to be honest and
-to give preliminary estimation of the work/responsibility involved---if
-you feel you are not in a position to help you may move on to a smaller
-project before going through all procedures.
-
-It is important to realize that being a @acronym{GNU} Web Translator is
-a hard job at all levels, but your help is much appreciated and is
-invaluable contribution to the society. While there are many people who
-contribute to our community by writing free software (and their number
-is constantly increasing), the ones actively engaged in teaching others
-to appreciate and defend their freedom are only a few. Consequently and
+up with that work. Reading this manual, and the related GNUN manual
+(@pxref{Top, , GNUnited Nations, gnun, The GNUnited Nations Manual}), is
+just the tip of the iceberg. This is not meant to discourage any
+potential volunteer; rather, we prefer to be honest and to give
+preliminary estimation of the work/responsibility involved---if you feel
+you are not in a position to help you may move on to a smaller project
+before going through all procedures.
+
+It is important to realize that being a GNU Web Translator is a hard job
+at all levels, but your help is much appreciated and is invaluable
+contribution to the society. While there are many people who contribute
+to our community by writing free software (and their number is
+constantly increasing), the ones actively engaged in teaching others to
+appreciate and defend their freedom are only a few. Consequently and
rather unfortunately, there are not so many volunteers willing to
maintain on the long term translations of the various essays that
describe the fundamental values of the free software movement.
@@ -105,16 +104,16 @@
language teams. Each team has one or more co-ordinators, who are
responsible for the respective team. The co-ordinators participate in
the Savannah @samp{trans-coord} organizational project, which is managed
-by the @acronym{GNU} Web Translation Managers. The manual is organized
-in chapters that follow the organizational structure of the whole
+by the GNU Web Translation Managers. The manual is organized in
+chapters that follow the organizational structure of the whole
translation project.
If you wish to join a translation team or contribute a translation or
-two, @pxref{Members}. If your intention is to form a translation
-team, @pxref{Leaders}. The chapter about the @samp{trans-coord}
-administrators (a.k.a. @address@hidden Translation Managers})
-describes all the responsibilities and procedures involved in performing
-this duty. @xref{Translation Managers}.
+two, @pxref{Members}. If your intention is to form a translation team,
address@hidden The chapter about the @samp{trans-coord}
+administrators (a.k.a. @dfn{GNU Translation Managers}) describes all the
+responsibilities and procedures involved in performing this duty.
address@hidden Managers}.
@node Members
@chapter Team Members
@@ -207,7 +206,7 @@
@subsection How To Submit a Translation in PO Format
All address@hidden really, but the goal is to maintain
-all of them.} are maintained via @acronym{GNUN} (see
+all of them.} are maintained via GNUN (see
@uref{http://www.gnu.org/@/software/@/gnun/}), which significantly eases
maintenance and avoids the unpleasant situation where a translation is
lagging behind the original. @xref{Advantages, , , gnun, The GNUnited
@@ -249,8 +248,8 @@
ability) the translation and will install it in the repository.
@item
-In order @acronym{GNUN} to be able to generate (and subsequently update)
-a gettextized translation, the language should have the server templates
+In order GNUN to be able to generate (and subsequently update) a
+gettextized translation, the language should have the server templates
available as PO files. These templates are short, and translating them
shouldn't take much time. If the language code is present in the
@code{TEMPLATE_LINGUAS} variable at @file{server/gnun/gnun.mk}, then you
@@ -281,9 +280,9 @@
If you feel the procedure described in the previous section is too
burdensome and unfeasible for you to follow, you can still submit a
translation in plain text. It will be manually converted to PO file by
-the @acronym{GNU} Web Translation Managers, which can be tricky
-sometimes, and naturally, means more work for them and slower processing
-of your request.
+the GNU Web Translation Managers, which can be tricky sometimes, and
+naturally, means more work for them and slower processing of your
+request.
You should @emph{never} translate the HTML markup---i.e. @emph{do not}
use the ``View Source'' functionality of your browser to translate the
@@ -419,9 +418,9 @@
new canonical source format of the translations is stored.
@item
-Assuming you have already read the @acronym{GNUN} manual entirely (as
-recommended in the beginning of this section), check if your language
-code is present in the variable @code{TEMPLATE_LINGUAS} at
+Assuming you have already read the GNUN manual entirely (as recommended
+in the beginning of this section), check if your language code is
+present in the variable @code{TEMPLATE_LINGUAS} at
@file{server/gnun/gnun.mk}. If it is not, the first thing to do is to
translate and submit to @email{web-translators@@gnu.org} the following
files (all in the @file{server/po/} directory):
@@ -526,8 +525,8 @@
@end itemize
You'll have to request subscription to @samp{www-discuss}
-yourself---this list is managed by the @acronym{GNU} Webmasters, but all
-team leaders are required to subscribe in order to receive important
+yourself---this list is managed by the GNU Webmasters, but all team
+leaders are required to subscribe in order to receive important
site-wide announcements.
@end enumerate
@@ -740,8 +739,8 @@
If you wish to volunteer as webmaster and help with generic webmaster
work and RT tickets, that is perfectly fine---please follow the
-established (by the @acronym{GNU} Webmasters) procedure. If you are
-approved, you can modify such pages wearing your ``webmaster's hat''.
+established (by the GNU Webmasters) procedure. If you are approved, you
+can modify such pages wearing your ``webmaster's hat''.
If a particular page has issues with the markup which create problems
for your language, please inform @email{trans-coord-discuss@@gnu.org}.
@@ -1173,11 +1172,11 @@
@section Migration To The New Style
Migration to the new style should be straightforward, and this is one of
-the problems @acronym{GNUN} set out to solve. If you have to migrate
-old-style translations, @pxref{Migrating, , , gnun, The GNUnited Nations
-Manual}. If the old translation is HTML 2.0 (or 3.2), you still have to
-take care about the inner markup. Overall, it is substantially easier
-than doing all of it manually.
+the problems GNUN set out to solve. If you have to migrate old-style
+translations, @pxref{Migrating, , , gnun, The GNUnited Nations Manual}.
+If the old translation is HTML 2.0 (or 3.2), you still have to take care
+about the inner markup. Overall, it is substantially easier than doing
+all of it manually.
Subsequent migrations to newer (X)HTML standards and newer look and feel
of the website are supposed to happen semi-automatically, although this
@@ -1186,11 +1185,11 @@
@node SSI
@section Summary of SSI @code{#include}s
-The GNU Project's website uses @acronym{SSI} (Server Side Includes) to
-manage some common parts that are the same in many of the articles.
-With the help of @acronym{GNUN} their handling should be behind the
-scenes, but for some of them manual intervention is needed. Here is a
-(possibly incomplete) list of the @code{#include}'s used:
+The GNU Project's website uses SSI (Server Side Includes) to manage some
+common parts that are the same in many of the articles. With the help
+of GNUN their handling should be behind the scenes, but for some of them
+manual intervention is needed. Here is a (possibly incomplete) list of
+the @code{#include}'s used:
@table @file
@item server/banner.html
@@ -1212,14 +1211,14 @@
@item server/footer-text.html
This is a very short file currently containing the ``back to top'' link.
-Also translatable via @acronym{GNUN}.
+Also translatable via GNUN.
@item server/header.html
The declaration that is included in literally every file. It is
maintained manually, as it does not make much sense to put it under
address@hidden's control (there are no translatable strings). Remember
-to specify the proper @code{xml:lang} and @code{lang} attributes, and
-for RTL languages, the @code{dir} attribute. For example, the file
+GNUN's control (there are no translatable strings). Remember to specify
+the proper @code{xml:lang} and @code{lang} attributes, and for RTL
+languages, the @code{dir} attribute. For example, the file
@file{header.ar.html} should contain this line:
@example
@@ -1271,8 +1270,8 @@
HTML version of the license without the gnu.org style; 2) to prevent
strings sneaking in the @file{.pot} files, as licenses have only
unofficial translations, hosted elsewhere. Nothing special should be
-done about these SSI directives; the files generated by @acronym{GNUN}
-include them verbatim as they should not be translated.
+done about these SSI directives; the files generated by GNUN include
+them verbatim as they should not be translated.
@item server/sidebar*.html
These files are deprecated---they are remnants from an older design that
@@ -1290,9 +1289,9 @@
files are included in almost every article, translated or not. They are
somewhat important, as an error made in translating them propagates
everywhere. The server templates, the homepages, and whatsnew
-(a.k.a. ``GNU News'') are being rebuilt by @acronym{GNUN} whenever there
-is a change in the original English files; the @code{GRACE} variable has
-no effect for them. @xref{Runtime Variables, , , gnun, The GNUnited
+(a.k.a. ``GNU News'') are being rebuilt by GNUN whenever there is a
+change in the original English files; the @code{GRACE} variable has no
+effect for them. @xref{Runtime Variables, , , gnun, The GNUnited
Nations Manual}.
@node CSS
@@ -1426,14 +1425,14 @@
@table @file
@item software/@var{pkg}/
These pages are maintained by the respective @var{pkg} maintainers.
address@hidden does not support them for the time being, as they reside
-in separate repositories. The procedures for contributing translations
-of such articles are not yet settled.
+GNUN does not support them for the time being, as they reside in
+separate repositories. The procedures for contributing translations of
+such articles are not yet settled.
@item brave-gnu-world
The Brave GNU World initiative has been abandoned long time ago, and
-it's in a separate repository---thus not supported by the automatic
address@hidden build job.
+it's in a separate repository---thus not supported by the automatic GNUN
+build job.
@item home.shtml
There is not problem to translate this page, but don't make the mistake
@@ -1509,8 +1508,8 @@
@table @email
@item www-discuss@@gnu.org
-The basic discussion list of the @acronym{GNU} Webmasters. All team
-leaders are required to subscribe.
+The basic discussion list of the GNU Webmasters. All team leaders are
+required to subscribe.
This is a private mailing list.
@@ -1524,40 +1523,39 @@
archives. The @samp{www} CVS repository is also public.
@item trans-coord-discuss@@gnu.org
-The main discussion list for the @acronym{GNU} Web Translators. Team
-leaders must subscribe, as errors from @acronym{GNUN} are mailed here.
-Team members are welcome to join as well, provided they are already
-members of @address@hidden If they want to subscribe with a
-different email address, a verification from the team leader is
-required.
+The main discussion list for the GNU Web Translators. Team leaders must
+subscribe, as errors from GNUN are mailed here. Team members are
+welcome to join as well, provided they are already members of
address@hidden@var{lang}}. If they want to subscribe with a different email
+address, a verification from the team leader is required.
This is a private mailing list, although there is no absolute reason for
that. It may become public in the future.
@item trans-coord-news@@gnu.org
-This is a list for notifications about gnunews and @acronym{GNU}nited
-Nations releases. It is not mandatory to subscribe to it, although the
-traffic is very low. If you want to track only @acronym{GNUN} release
-announcements, subscribe to the @samp{gnun} topic via Mailman's user
-interface. Likewise, if you want to recieve only @dfn{What's New}
-updates, subscribe to the @samp{whatsnew} topic. In the near future,
-there will be automatic announcements for newly available English
-articles and translations.
+This is a list for notifications about gnunews and GNUnited Nations
+releases. It is not mandatory to subscribe to it, although the traffic
+is very low. If you want to track only GNUN release announcements,
+subscribe to the @samp{gnun} topic via Mailman's user interface.
+Likewise, if you want to recieve only @dfn{What's New} updates,
+subscribe to the @samp{whatsnew} topic. In the near future, there will
+be automatic announcements for newly available English articles and
+translations.
This is a public mailing list.
@item trans-coord-devel@@gnu.org
-All development of @acronym{GNUN} happens here. Commits to the
address@hidden repository are also sent to this list.
+All development of GNUN happens here. Commits to the @samp{trans-coord}
+repository are also sent to this list.
This is a public list, and @email{bug-gnun@@gnu.org} is an alias.
@item trans-coord-logs@@gnu.org
-All build logs from the various @acronym{GNUN} automatic builds are sent
-to this list, so it is not a very pleasant thing to be subscribed,
-especially if you are not interested in @acronym{GNUN}'s internals.
-However, everyone can use the web archives to check the log why a
-particular article was not built at expected.
+All build logs from the various GNUN automatic builds are sent to this
+list, so it is not a very pleasant thing to be subscribed, especially if
+you are not interested in GNUN's internals. However, everyone can use
+the web archives to check the log why a particular article was not built
+at expected.
This is a public list.
@end table
@@ -1586,8 +1584,7 @@
to be members, as bugs reported to @email{web-translators@@gnu.org} are
often redirected to the @samp{trans-coord} @samp{Bugs} tracker.
-The admins of this project are the @acronym{GNU} Web Translation
-Managers.
+The admins of this project are the GNU Web Translation Managers.
@item address@hidden
All translation team leaders of the language @var{lang} should be
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- trans-coord/gnun/server/gnun ChangeLog doc/gnun... [sr-hr],
Yavor Doganov <=