From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: "Jean-Noël Avila" <avila.jn@gmail.com>
Cc: rsbecker@nexbridge.com, git@vger.kernel.org
Subject: Re: [Question] Translation Dictionary
Date: Thu, 03 Feb 2022 10:54:58 +0100 [thread overview]
Message-ID: <220203.86sft05kzm.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <0c47248d-13b8-9d80-b03f-8ac6fd4ac91e@gmail.com>
On Thu, Feb 03 2022, Jean-Noël Avila wrote:
> Hi Randall,
>
> I guess not all git translators are subscribed to the mailing list, as
> they mostly interact with Jiang. I put them in cc.
>
> For French, I try to maintain a glossary of terms in the header of the
> `fr.po` file, available here:
> https://github.com/git/git/blob/master/po/fr.po
I started trying to come up with something similar for the Icelandic
translation I plan on getting to any day now (for ~11 years and
counting).
I think it would be a really good addition to git to move this list into
a built-in or an option for "git help", something like:
git i18n-terms
Or:
git help --common-terms
It would help users that use a non-English a lot, since they could use
it as a reliable cheatsheet, and it would clearly help translators,
since it could be one of the first things they'd translate, to anchor
themselves when it comes to translating blob/tree/commit/tag etc.
If you're interested I can help you come up with that. Basically it
would be some "static" array with that table as C code with strings
marked with N_(). We could then add optional explanations as in
gitglossary(7) (and even eventually generate that documentation from
that code).
> Le 29/01/2022 à 20:35, rsbecker@nexbridge.com a écrit :
>> To the git translators.
>>
>> I was wondering whether there is an official translation dictionary for
>> git-related terms. At times, I am asked to provide presentations with an
>> initial translation to companies in various parts of the world. It would be
>> nice to be able to follow the official set of terms used in git
>> translations. Does such a thing exist?
>>
>> Thanks,
>> Randall
>>
>> --
>> Brief whoami: NonStop&UNIX developer since approximately
>> UNIX(421664400)
>> NonStop(211288444200000000)
>> -- In real life, I talk too much.
>>
>>
>>
next prev parent reply other threads:[~2022-02-03 9:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 19:35 [Question] Translation Dictionary rsbecker
2022-02-03 9:37 ` Jean-Noël Avila
2022-02-03 9:54 ` Ævar Arnfjörð Bjarmason [this message]
2022-02-03 13:27 ` rsbecker
2022-02-03 18:06 ` Ævar Arnfjörð Bjarmason
2022-02-03 18:15 ` Junio C Hamano
2022-02-03 19:59 ` Jean-Noël AVILA
2022-02-03 21:33 ` Junio C Hamano
2022-02-03 23:45 ` rsbecker
2022-02-03 12:58 ` rsbecker
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=220203.86sft05kzm.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=avila.jn@gmail.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.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).