IMPORTANT
=========
There has been a major commit for the English version of the manual. You
will find some tips on how efficiently update your translation later in
this mail.
Recent and planned changes
==========================
Important recent updates:
- Add conditions so that post-Sarge changes can be documented while still
keeping the same source for Sarge and post-Sarge (Etch).
- Various commits documenting post-Sarge changes.
- New section documenting localechooser (post-Sarge).
- Major end-of-line whitespace cleanup.
In line with the first change, the build system used for the daily builds
published on alioth [1] has now been set to build the Etch version of the
manual. The Sarge version is still regularly updated for all translations
and is published on the official website [2].
The index page for the manual on alioth [1] has also been updated,
including some more information for editors and translators. Comments are
welcome.
Planned updates:
- There will be another fairly big commit in about 10 days that fixes
quoting and the use of dashes (see also "Whitespace cleanup").
New translations
================
Since RC3 several new translations have been added, most using PO files
for translation: Korean, Simplified Chinese, Traditional Chinese.
A Tagalog translation was started, but no real progress was made.
The Greek translation has been revived.
Whitespace cleanup
==================
A long time ago a cleanup patch (bug #279927) was submitted by our current
DPL. Because of its invasiveness, it has been ignored until after the
release of Sarge, but now the time has come to apply it.
The patch has been updated by Christian Weisel (thanks!) and will be
committed in two parts:
- whitespace cleanup only (already committed in r28672)
there were _no_ textual changes in this commit;
- textual changes (mainly use of quotes and dashes).
The first commit has most impact for translators who do not use PO files
as they will have to update revision comments and make sure that all
changes before this commit are correctly translated.
Translators using PO files will see a few fuzzies, but not many. Most
fuzzies will be in <example>'s where whitespace is preserved.
For translators _not_ using PO files who use revision comments and thus
can use the "doc-check" scripts, the following procedure is recommended
to update your translations.
- Check and update changes before the whitespace commit. The following
command will show these changes:
$ ./scripts/doc-check -r 28671 -d <language>
(the option -r was added recently and lists changes up to r28671!)
- Commit these updates.
- Run the following command to update your revision comments to 28672:
$ ./scripts/rev-update -u
- IMPORTANT! If any revision comments were updated to a revision greater
than 28672, you should manually change the revision comment to 28672.
If you do not, you may miss textual updates in the original version!!!
- If you want to also perform the whitespace cleanup for your translation,
use:
$ cd <language>
$ for i in $(find . -name "*.xml"); do \
cp $i $i.old; sed "s/[[:space:]]*$//" $i.old >$i; rm $i.old; done
- Check using 'svn diff' and commit.
- Check for updates after 28672 and update your translation as normal.
If you need help doing this, feel free to ask!
VACATION
========
I'll be on vacation next week (a pre-Debconf hike through Finland :-)
This means there will be no builds for the manual next week.
[1] http://d-i.alioth.debian.org/manual/
[2] http://www.debian.org/releases/stable/installmanual
Attachment:
pgpLjFZGbv21X.pgp
Description: PGP signature