Hello Ben, On Sat, May 31, 2008 at 12:04:17AM +0100, Ben Hutchings wrote: > I asked Simon Tatham about adding support for i18n some time ago, but he > wasn't very enthusiastic about it, partly because it runs on many > platforms with different i18n APIs. This doesn't apply to the
Should I ask on debian-18n about this? Other projects, i.e.
OpenOffice, Firefox, KDE, are multiplatform as well, and at least the
first two I've used in German on W*, MacOSX and of course Unix, so
this is a solvable (read: already solved) issue, even in different
toolkits.
> documentation, of course. Is there anything special I would have to do
> to support translation of documents, other than installing the
> translated documents in appropriate directories?
The workflow essentially is (during build):
Upstream english documents -> po4a-magick -> translated document (build
phase)
And then after installing the english docs you also install the German
ones, including registration if that should be necessary (I haven't
looked, but simply the same as for the english ones).
If the upstream document is changed, then some parts of the translated
document become "fuzzy" and will be not be shown translated. It would
be kind, if you could check for this once in a while (its very easy,
like "grep fuzzy *.po" and then ask the translators to update their
file. Simliarly if upstream adds new content, a simple call will show
you that (or you'll see the information during build in the logs) and
then it would be kind if you call for updates. The entire process is
very well suported by tools in Debian, and I can give you all the
details if you want, or simply look at po-debconf (which is more
generic than the name suggests) and po4a. The po4a maintainer is
currently looking into supporting halibut.
Greetings
Helge
--
Dr. Helge Kreutzmann [EMAIL PROTECTED]
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: Digital signature
