From: Junio C Hamano <gitster@pobox.com>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: [PATCH 1/3] po/README: document PO helper
Date: Thu, 11 Mar 2021 22:03:51 -0800 [thread overview]
Message-ID: <xmqqa6r8c3i0.fsf@gitster.g> (raw)
In-Reply-To: <CANYiYbH_U=3gN+LH7e-LBdRdcE0geAuUzoBX4O09qego0xKX-Q@mail.gmail.com> (Jiang Xin's message of "Fri, 12 Mar 2021 09:32:39 +0800")
Jiang Xin <worldhello.net@gmail.com> writes:
> Bagas Sanjaya <bagasdotme@gmail.com> 于2021年3月11日周四 下午8:56写道:
>>
>> Document about PO helper script (po-helper.sh). It covers about
>> installing the script and short usage examples.
>>
>> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
>> ---
>> po/README | 22 ++++++++++++++++++++++
>> 1 file changed, 22 insertions(+)
>>
>> diff --git a/po/README b/po/README
>> index efd5baaf1d..9beffc2954 100644
>> --- a/po/README
>> +++ b/po/README
>> @@ -286,3 +286,25 @@ Testing marked strings
>>
>> Git's tests are run under LANG=C LC_ALL=C. So the tests do not need be
>> changed to account for translations as they're added.
>> +
>> +
>> +PO Helper
>> +---------
>> +
>> +To make maintaining XX.po file easier, the l10n coordinator created
>> +po-helper.sh script. It is wrapper to gettext suite, specifically
>
> It's better to rename the script to other name without the suffix
> ".sh", so we can reimplement it in other programming language. Maybe
> we can rename it to `git-po-helper`, and host this helper in a
> separate project on GitHub.
It might be a good move in the longer term, but if the po-helper.sh
is working well enough to fill the need of i18n/l10n team right now,
I think documenting the status quo would be a good way to help the
contributors immediately.
And when we reimplement it (if that is desirable---I have no opinion
myself), we certainly would want to update this part of the doc to
use the name of the rewritten tool.
In any case, I expect that you to be the main reviewer on this topic
and you will feed me the final commits, just like any other change
in the po/* area via a pull request. In other words, I may have
input to the discussion on list, but I won't be applying the result
myself---I'll be pulling from git://github.com/git-l10n/git-po.git
repository instead.
Thanks.
next prev parent reply other threads:[~2021-03-12 6:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 12:55 [PATCH 0/3] po/README: document miscellaneous topics mentioned by l10n coordinator Bagas Sanjaya
2021-03-11 12:55 ` [PATCH 1/3] po/README: document PO helper Bagas Sanjaya
2021-03-12 1:32 ` Jiang Xin
2021-03-12 6:03 ` Junio C Hamano [this message]
2021-03-12 11:56 ` Bagas Sanjaya
2021-05-13 15:40 ` Jiang Xin
2021-05-27 3:11 ` Jiang Xin
2021-03-11 12:55 ` [PATCH 2/3] po/README: document "core translation" Bagas Sanjaya
2021-03-12 1:32 ` Jiang Xin
2021-03-11 12:55 ` [PATCH 3/3] po/README: document l10n conventions Bagas Sanjaya
2021-03-11 13:13 ` Bagas Sanjaya
2021-03-12 1:33 ` Jiang Xin
2021-03-12 11:47 ` Bagas Sanjaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqa6r8c3i0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=worldhello.net@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).