Frustration working with i18n/l10n
Hey folks,
Yesterday I worked on the rescue package, fixing #823612. That
involved making some changes to some of the templates, mainly
parameterising stuff to change "/boot" to "${FILESYSTEM}" is a few
places.
I also found that quite a few of the existing translations here were
terrible, including the string "/home" in translations that should be
talking about "/boot". Some others mention PReP in similar places,
which I know is used in powerpc booting but is not mentioned directly
at all in the rescue package. There are clearly some problems in the
translations here.
I naively fixed up all the references to "/home" in the existing po
files, and then switched from "/boot" to "${FILESYSTEM}" so things
would match the new template changes I'd made. Yay, everything
worked. Then the l10n cron jobs last night went and undid a lot of
these fixes. :-(
KiBi pointed me at the Debian Installer Internationalization and
Localization Guide [1], and I've been reading through that without
much joy. In particular, I'm concerned about the text:
When working on "core" Debian Installer packages, developers should
not care about the debian/po directory contents. They even don't
need running the debconf-updatepo utility, except the first time
they create the package (so that the debian/po/templates.pot file is
created).
When I can see that the changes I've made can be very easily
mechanically updated in po files too, I *want* to be able to make
those updates too. Especially in cases where the existing translations
are obvious going to be wrong/incorrect, I'd like to be able to update
them where I can. How exactly do I do that?
[1] http://d-i.alioth.debian.org/doc/i18n/
--
Steve McIntyre, Cambridge, UK. steve@einval.com
< sladen> I actually stayed in a hotel and arrived to find a post-it
note stuck to the mini-bar saying "Paul: This fridge and
fittings are the correct way around and do not need altering"
Reply to: