From: Junio C Hamano <gitster@pobox.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Philip Oakley via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Philip Oakley <philipoakley@iee.email>
Subject: Re: [PATCH v2] README.md: add CodingGuidelines and a link for Translators
Date: Mon, 17 Jan 2022 10:49:35 -0800 [thread overview]
Message-ID: <xmqqtue2uri8.fsf@gitster.g> (raw)
In-Reply-To: <6271ff4b-1821-0086-167c-b273ab252eb9@gmail.com> (Bagas Sanjaya's message of "Mon, 17 Jan 2022 16:00:32 +0700")
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> On 16/01/22 23.11, Philip Oakley via GitGitGadget wrote:
>> +Those wishing to help with error message translation (localization L10)
>> +should see [po/README.md][] (a `po` file is a Portable Object file that
>> +holds the translations).
>> +
>
> I mean not just error messages are in po/*.po, but also usage and informational
> strings. We can say "Those wishing to help translating message strings
> (localization or l10n)...".
Yup, that sounds more correct.
Thanks.
next prev parent reply other threads:[~2022-01-17 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 17:50 [PATCH] README.md: add CodingGuidelines and a link for Translators Philip Oakley via GitGitGadget
2022-01-14 20:54 ` Junio C Hamano
2022-01-15 0:08 ` Philip Oakley
2022-01-15 0:47 ` Junio C Hamano
2022-01-16 16:11 ` [PATCH v2] " Philip Oakley via GitGitGadget
2022-01-16 22:47 ` Junio C Hamano
2022-01-17 18:08 ` Philip Oakley
2022-01-17 9:00 ` Bagas Sanjaya
2022-01-17 17:52 ` Philip Oakley
2022-01-17 18:49 ` Junio C Hamano [this message]
2022-01-17 18:18 ` [PATCH v3] " Philip Oakley via GitGitGadget
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqtue2uri8.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=philipoakley@iee.email \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.