# [L10N] Kickoff of translation for Git 2.15.0 round 2

3 messages from 2017-10-17 to 2017-10-17. Participants: Jiang Xin, Junio C Hamano, Ralf Thielow.
Thread: https://gitlist.dev/t/46980

## Jiang Xin, 2017-10-17 02:09

Subject: [L10N] Kickoff of translation for Git 2.15.0 round 2
Message-ID: <CANYiYbEojz6P5BmN4bmQ-VuwsVf7RX1sDqiwnEsXN+M4-PXZtg@mail.gmail.com>
URL: https://gitlist.dev/e/CANYiYbEojz6P5BmN4bmQ-VuwsVf7RX1sDqiwnEsXN%2BM4-PXZtg%40mail.gmail.com

```
Hi,

Git v2.15.0-rc1 released with a typo fix from commit dfab1eac23
("i18n: add a missing space in message", Sun Oct 8 14:18:39 2017 +0200).
This time there are 2 updated messages need to be translated since last
update.  Let's start new round of translation for Git 2.15.0.

You can get it from the usual place:

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

As how to update your XX.po and help to translate Git, please see
"Updating a XX.po file" and other sections in “po/README" file.

--
Jiang Xin

```

## Junio C Hamano, 2017-10-17 06:53

Subject: Re: [L10N] Kickoff of translation for Git 2.15.0 round 2
Message-ID: <xmqqr2u2nu37.fsf@gitster.mtv.corp.google.com>
URL: https://gitlist.dev/e/xmqqr2u2nu37.fsf%40gitster.mtv.corp.google.com
In-Reply-To: <CANYiYbEojz6P5BmN4bmQ-VuwsVf7RX1sDqiwnEsXN+M4-PXZtg@mail.gmail.com>

```
Jiang Xin <worldhello.net@gmail.com> writes:

> Git v2.15.0-rc1 released with a typo fix from commit dfab1eac23
> ("i18n: add a missing space in message", Sun Oct 8 14:18:39 2017 +0200).
> This time there are 2 updated messages need to be translated since last
> update.  Let's start new round of translation for Git 2.15.0.

Today's pushout included 3247edbb ("sequencer.c: fix and unify error
messages in rearrange_squash()", 2017-10-15), which unfortunately
added this to the mix:

    error_errno(_("could not write '%s'"), todo_file);

There is another one "could not truncate '%s'" added by the same
commit, but the codebase already had another instance of the same
string, so it won't cause trouble.

Regarding the "could not write" thing, there are quite a few
instances of "coulld not write to '%s'" with %s set to the filename,
and I strongly suspect that this new one should be further updated
to match them (Ralf promoted from Cc: to To: for this).  That would
have a nice side effect of making today's last-minute merges a
non-event from translators' point of view ;-)




```

## Ralf Thielow, 2017-10-17 07:30

Subject: Re: [L10N] Kickoff of translation for Git 2.15.0 round 2
Message-ID: <CAN0XMOKFsHhCSbsWKGg3a84euqkfHA+0dt=snTejqcMQYnAK_A@mail.gmail.com>
URL: https://gitlist.dev/e/CAN0XMOKFsHhCSbsWKGg3a84euqkfHA%2B0dt%3DsnTejqcMQYnAK_A%40mail.gmail.com
In-Reply-To: <xmqqr2u2nu37.fsf@gitster.mtv.corp.google.com>

```
2017-10-17 8:53 GMT+02:00 Junio C Hamano <gitster@pobox.com>:
> Jiang Xin <worldhello.net@gmail.com> writes:
>
>> Git v2.15.0-rc1 released with a typo fix from commit dfab1eac23
>> ("i18n: add a missing space in message", Sun Oct 8 14:18:39 2017 +0200).
>> This time there are 2 updated messages need to be translated since last
>> update.  Let's start new round of translation for Git 2.15.0.
>
> Today's pushout included 3247edbb ("sequencer.c: fix and unify error
> messages in rearrange_squash()", 2017-10-15), which unfortunately
> added this to the mix:
>
>     error_errno(_("could not write '%s'"), todo_file);
>
> There is another one "could not truncate '%s'" added by the same
> commit, but the codebase already had another instance of the same
> string, so it won't cause trouble.
>
> Regarding the "could not write" thing, there are quite a few
> instances of "coulld not write to '%s'" with %s set to the filename,
> and I strongly suspect that this new one should be further updated
> to match them (Ralf promoted from Cc: to To: for this).  That would
> have a nice side effect of making today's last-minute merges a
> non-event from translators' point of view ;-)
>
>
>

I didn't expect this message to be a new one for translation. I'll send
a patch later to update the message to match the other instances.

```
