git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/3] po/README: document PO helper

From
Bagas Sanjaya <bagasdotme@gmail.com>
Date
Mar 12, 2021, 11:56 UTC
Message-ID
<2600d078-9ba0-2ebc-4611-c414ef8b12dd@gmail.com>
In-Reply-To
<xmqqa6r8c3i0.fsf@gitster.g>
On 12/03/21 13.03, Junio C Hamano wrote:
Show 51 quoted lines
> 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.

-- 
An old man doll... just what I always wanted! - Clara
Previous: Junio C HamanoNext: Jiang Xin
Message 9 of 13 in “po/README: document miscellaneous topics mentioned by l10n coordinator”
  1. 0/3 po/README: document miscellaneous topics mentioned by l10n coordinatorBagas Sanjaya, Mar 11, 2021
  2. 3/3 po/README: document l10n conventionsBagas Sanjaya, Mar 11, 2021
  3. Bagas SanjayaMar 11, 2021
  4. Jiang XinMar 12, 2021
  5. Bagas SanjayaMar 12, 2021
  6. 1/3 po/README: document PO helperBagas Sanjaya, Mar 11, 2021
  7. Jiang XinMar 12, 2021
  8. Junio C HamanoMar 12, 2021
  9. Bagas SanjayaMar 12, 2021
  10. Jiang XinMay 13, 2021
  11. Jiang XinMay 27, 2021
  12. 2/3 po/README: document "core translation"Bagas Sanjaya, Mar 11, 2021
  13. Jiang XinMar 12, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.