Re: [PATCH 0/1] handling mistranslation reports (resend)

From: Jiang Xin <worldhello.net@gmail.com>
Date: Aug 2, 2015, 15:50 UTC
Message-ID: <CANYiYbGbMvPOerwQHSKRzqR8HfsTm-6fV6R+gefiX4hr1d4=SA@mail.gmail.com>
In-Reply-To: <1438522955-6076-1-git-send-email-philipoakley@iee.org>

2015-08-02 21:42 GMT+08:00 Philip Oakley <philipoakley@iee.org>:

Show 14 quoted lines

> [Resent as first email was not picked up by vger, apologies for any duplicates]
>
> Hi Jiang,
>
> Recently, on the 'Git for human beings' list, a user reported a
> mistranslation and asked if/what could be done, with a suggested
> alternate text [1].
>
> I pointed the user at the po/README for general guidance.
> Unfortunately the user was noting a Spanish (es) translation error which
> is not held in your tree, but the README does include how to start a new
> translation. This led to a misunderstanding with regard to which aspect
> of the README was being referred to (private discussion with Junio).
>

Some linux distribution, such as Ubuntu, has its own l10n workflow for each package (including git.git), and not works well with the upstream. For example, Ubuntu makes a one-time import from our Git translations (from some obsoleted version) into their l10n databases, and their contributors will start to translate using their web UI, and never sync with our upstream again. They ubuntu may have more languages support, but they may also have more bugs. Sometime, their bugs will be reported to our upstream, for example:

* http://thread.gmane.org/gmane.comp.version-control.git/239130/focus=239130

We could add some clues for this case if the user can not find the resource to contribute.

-- Jiang Xin