From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jordi Mas via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Jordi Mas <jmas@softcatala.org>
Subject: Re: [PATCH] l10n: allows to translate diff messages
Date: Wed, 14 Jul 2021 02:18:42 +0200 [thread overview]
Message-ID: <87zgup217d.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqq4kcx24j7.fsf@gitster.g>
On Tue, Jul 13 2021, Junio C Hamano wrote:
> "Jordi Mas via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
>> Subject: Re: [PATCH] l10n: allows to translate diff messages
>
> "allow to translate" would be the right phrasing, but it is too
> vague to say "diff messages". You are only marking 3 messages for
> translation when there are probably a handful more.
>
> You need to explain which ones, not just vague "diff messages".
>
> I think you are focusing on the words on the "git diff --stat" and
> "git diff --shortstat" summary line, so
>
> i18n: mark "git diff --[short]stat" summary for translation
>
> perhaps? And remember, i18n is the act of making the code capable
> of being translated, while l10n is the act of actually translating
> what i18n prepared into a particular language. Here, i18n is more
> appropriate.
What i18n v.s. l10n means is quite the side-discussion, I have not heard
it used like this before, but rather as e.g. defined at :
https://www.w3.org/International/questions/qa-i18n
I.e. in git.git's case that all our gettext-ization would fall under
i18n, but l10n are generally a step beyond that, e.g. if "git status"
output entries were sorted by locale, fsck and other progress.c users
used localized numeric formatting etc.
IOW I agree that i18n is more appropriate here, I just hadn't heard
i18n/l10n used in the way that you describe.
prev parent reply other threads:[~2021-07-14 0:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 12:01 [PATCH] l10n: allows to translate diff messages Jordi Mas via GitGitGadget
2021-07-13 23:11 ` Junio C Hamano
2021-07-14 0:09 ` Bagas Sanjaya
2021-07-14 0:18 ` Ævar Arnfjörð Bjarmason [this message]
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=87zgup217d.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=jmas@softcatala.org \
/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).