Re: [GIT PULL v2] l10n updates for Git 2.54.0

From: Jiang Xin <worldhello.net@gmail.com>
Date: Apr 20, 2026, 11:38 UTC
Message-ID: <CANYiYbGvVh7R3u7AFVFNXK_-cRTsi=6s7sq5hafdJXi8qCs8qA@mail.gmail.com>
In-Reply-To: <xmqqo6jetb1l.fsf@gitster.g>

On Mon, Apr 20, 2026 at 2:12 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 14 quoted lines

> >
> > Here are the v2 l10n updates for Git 2.54.0. Changes since v1 include updates
> > to the Bulgarian (bg) and Traditional Chinese (zh_TW) translations.
> >
> > Changes since v1:
> >
> >     po/bg.po    |   62 +-
> >     po/zh_TW.po | 2699 +++++++++++++++++++++++++++++++++++++++--------------------
> >     2 files changed, 1822 insertions(+), 939 deletions(-)
>
> Thanks, I only pulled v2 and thought about redoing the pull by
> getting v1 first and then v2, but it seems you retracted v1 tag
> already?  I assume that v2 is a superset of v1, in which case we are
> perfectly fine ;-)

I removed the v1 tag this morning (UTC+0800) upon receiving two new pull requests, to prevent you from accidentally pulling it before the updated tag was ready.

During this localization round, `po/.gitattributes` was introduced, which helped detect and prevent a style change in location comments from introducing a large number of unintended diffs. For example:

 - https://github.com/git-l10n/git-po/pull/913

It also caught blank lines and comments left over from deleted obsolete entries that gettext had failed to detect:

 - https://github.com/git-l10n/git-po/pull/909

`po/AGENTS.md` was introduced, and AI-assisted review was used to identify and fix translation quality issues in pull requests. For example:

 - https://github.com/git-l10n/git-po/pull/906
 - https://github.com/git-l10n/git-po/pull/917

-- Jiang Xin