GNUN 0.3 is out, exactly in time for this year's Slavonic Literature
and Culture Day (for those who care, of course). As it is becoming a
tradition, all of the fancy new features are postponed for subsequent
releases. Highlights in this version include (in no particular
order): two important bugfixes, configuration & documentation
improvements, support for `msgmerge --previous' and out-of-the-box
support for GNU Arch repositories in GNUmakefile.team. Read the NEWS
extract below for details.
GNUnited Nations is a build system for gnu.org translations and a
collection of tools to help translators (and occasionally webmasters).
As of version 0.2 it also contains the web-translators manual, the
canonical documentation for all participants in the gnu.org
translation process. GNUN is still entirely dependent on gnu.org's
structure/layout and not useful for other sites without non-trivial
modifications.
See its homepage <http://gnu.org/software/gnun/> and
<http://gnu.org/software/trans-coord/> for more information.
Translators do not have to install this package to do their work; an
official build instance is running at fencepost.gnu.org which
automatically updates all translations in the `www' CVS repository.
However, it is still recommended to install GNUN localy in order to
check easily incomplete translations, and for info-browsable
documentation.
GNUN can be downloaded from ftp.gnu.org and its mirrors; the easiest
way to get it is
wget http://ftpmirror.gnu.org/gnun/gnun-latest.tar.gz
which will pick the closest mirror to your location.
Here are the compressed sources:
ftp://ftp.gnu.org/gnu/gnun/gnun-0.3.tar.gz (352KB)
Here are the GPG detached signatures[*]:
ftp://ftp.gnu.org/gnu/gnun/gnun-0.3.tar.gz.sig
Here are the MD5 and SHA1 checksums:
76568252fd9e42f27c7fb6bee72c119c gnun-0.3.tar.gz
c0cfcadc680f3b0385afa594698d1249e4072660 gnun-0.3.tar.gz
[*] You can use either of the above signature files to verify that
the corresponding file (without the .sig suffix) is intact. First,
be sure to download both the .sig file and the corresponding tarball.
Then, run a command like this:
gpg --verify gnun-0.3.tar.gz.sig
If that command fails because you don't have the required public key,
then run this command to import it:
gpg --keyserver keys.gnupg.net --recv-keys A49EF0C0
and rerun the `gpg --verify' command.
This release was bootstrapped with the following tools:
Autoconf 2.63
Automake 1.11
NEWS
* Changes in GNUnited Nations 0.3 (2009-05-24)
** GNU gettext >= 0.16 is required for `msgmerge --previous' support.
This feature copies the entire old string above the new `msgid',
enabling translators to compare what precisely changed in the
original. Currently, it is not very useful for large messages as
it is hard to detect a small change in a long paragraph. Po4a 0.36
comes with an example script `compare-msgids.pl' which can be used
to print the differences in wdiff format. A separate GNUN program
with better output is planned for the very near future.
** Improved configuration.
The `configure' tests have been improved, and a short summary with
enabled/disabled features is printed at the end.
** Notifications are sent about errors during POT generation.
If NOTIFY is enabled, errors from the .pot files generation are
mailed to `web-addr' (i.e. www-discuss for the official build).
Usually they are about non-ASCII characters in the original .html.
** GNUmakefile.team supports GNU Arch repositories.
** Bugs fixed in 0.3.
*** Empty .LANG.html files are no longer committed.
In previous releases, an empty .LANG.html was committed when
1) The newly added .LANG.po does not pass PO validation, or
2) The translation was based on an old version of the .pot,
so msgmerge introduced "fuzzy" strings in the .LANG.po prior
to the generation of the HTML translation.
The behavior now is the following: 1) The build halts with an
error and a message is sent (if NOTIFY is enabled) while no .html
file is created; 2) The value of GRACE is ignored, so the
resulting .LANG.html contains English text. This proved to be a
better alternative than an empty file which may remain unnoticed
by the translator during the whole GRACE period.
*** PO files for the homepage and whatsnew are always msgmerge'd.
Previously, only PO files for ordinary articles were updated
unconditionally prior to HTML generation, to cater for the case
when a translator commits a "complete" translation but it's not
actually complete as the PO file is based on an old POT. Now this
is done for the homepage and whatsnew (aka "gnunews") and as a
consequence, fuzzy strings are always marked as such.