German translation unusable

Martin Geisler mg at aragost.com
Wed Sep 22 04:02:07 CDT 2010


Christoph <christoph at webvariants.de> writes:

> Hi,
>
> two days ago i ran msgmerge to update the German .po file. After that
> (and even to some extend before that) the translation is now in large
> parts unusable. For example, the documentation for the convert
> extension has been split into many little texts instead of one large
> block. msgmerge copied the large translated block to every single
> little unit, so when someone runs 'hg help convert', they would get
> the same text over and over again.

Ak, that's of course very annoying. When we split the big docstrings
into paragraphs, the idea was to insert the full original text so that
translators could easily delete the extra parts and thus sync things.

> I started updating the translations, but more than two thirds are
> still missing. But I already pushed the current results into the i18n
> repo, so they will eventually end up in the next release and all
> German users would be very annoyed.
>
> What would be the best way to handle this? As Mark mentioned in IRC,
> the next freeze for 1.6.4 will be in 8 days, and I don't think I can
> update all missing translations in this time.
> So should we go with the old translation file (the one before
> msgmerge) or use the current one, except removing all those over and
> over repeatd messages?

I was contacted by Martin Roppelt on IRC today and he also wants to help
with the German translation. I hope the two of you can work together to
update it, or at least remove the duplicated messages.

Using the English texts is of course better than a German translation
with tons of duplicates, so I think one of you should roll the
translation back in the stable branch if you cannot fix it before the
release of 1.6.4.

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://aragost.com/mercurial/


More information about the Mercurial-devel mailing list