From: Jiang Xin <worldhello.net@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Git List" <git@vger.kernel.org>,
"Alexander Shopov" <ash@kambanaria.org>,
"Jordi Mas" <jmas@softcatala.org>,
"Matthias Rüster" <matthias.ruester@gmail.com>,
"Jimmy Angelakos" <vyruss@hellug.gr>,
"Christopher Díaz" <christopher.diaz.riv@gmail.com>,
"Jean-Noël Avila" <jn.avila@free.fr>,
"Alessandro Menti" <alessandro.menti@alessandromenti.it>,
"Gwan-gyeong Mun" <elongbug@gmail.com>, Arusekk <arek_koz@o2.pl>,
"Daniel Santos" <hello@brighterdan.com>,
"Dimitriy Ryazantcev" <DJm00n@mail.ru>,
"Peter Krefting" <peter@softwolves.pp.se>,
"Emir SARI" <bitigchi@me.com>,
"Trần Ngọc Quân" <vnwildman@gmail.com>,
"Jiang Xin" <worldhello.net@gmail.com>,
"Yi-Jyun Pan" <pan93412@gmail.com>
Subject: Re: [PATCH 1/3] po/README: document PO helper
Date: Thu, 13 May 2021 23:40:11 +0800 [thread overview]
Message-ID: <CANYiYbEVyUc6gsjb4=+8x8m64zpkTo4vYSLAB+au-Rz5xsEVaA@mail.gmail.com> (raw)
In-Reply-To: <2600d078-9ba0-2ebc-4611-c414ef8b12dd@gmail.com>
Bagas Sanjaya <bagasdotme@gmail.com> 于2021年3月12日周五 下午7:57写道:
>
>
> On 12/03/21 13.03, Junio C Hamano wrote:
> > 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.
> >
>
> Grazie Junio. However, I'm more of writing documentation rather than
> contributing code, so I will help for the documentation and usage
> testing. But anyways, we can ask for help from other l10n contributors
> who are more proficient at coding.
>
Hi Bagas,
I created a new repository at
https://github.com/git-l10n/git-po-helper that contains a new helper
program `git-po-helper` to replace the obsolete `po-helper.sh` script.
The new `git-po-helper` program can check character encoding of the
commit log, check author/committer datetime, and check format of
`po/TEAMS`, etc., in addition to the conventions listed in README of
the new project "git-l10n/git-po-helper".
You can update your patches according to this change.
All l10n contributors can use this new helper to check their l10n contributions.
BTW, with the help of Daniel, a google group named git-l10n is created
for discussion on git-l10n. This mail is also cc to this email
address: git-l10n@googlegroups.com .
--
Jiang Xin
next prev parent reply other threads:[~2021-05-13 15:40 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
2021-03-12 11:56 ` Bagas Sanjaya
2021-05-13 15:40 ` Jiang Xin [this message]
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='CANYiYbEVyUc6gsjb4=+8x8m64zpkTo4vYSLAB+au-Rz5xsEVaA@mail.gmail.com' \
--to=worldhello.net@gmail.com \
--cc=DJm00n@mail.ru \
--cc=alessandro.menti@alessandromenti.it \
--cc=arek_koz@o2.pl \
--cc=ash@kambanaria.org \
--cc=bagasdotme@gmail.com \
--cc=bitigchi@me.com \
--cc=christopher.diaz.riv@gmail.com \
--cc=elongbug@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hello@brighterdan.com \
--cc=jmas@softcatala.org \
--cc=jn.avila@free.fr \
--cc=matthias.ruester@gmail.com \
--cc=pan93412@gmail.com \
--cc=peter@softwolves.pp.se \
--cc=vnwildman@gmail.com \
--cc=vyruss@hellug.gr \
/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).