From: Junio C Hamano <gitster@pobox.com>
To: Alexander Shopov <ash@kambanaria.org>
Cc: "Git List" <git@vger.kernel.org>,
jmas@softcatala.org, alexhenrie24@gmail.com,
ralf.thielow@gmail.com, matthias.ruester@gmail.com,
phillip.szelat@gmail.com, vyruss@hellug.gr,
christopher.diaz.riv@gmail.com, jn.avila@free.fr,
flashcode@flashtux.org, bagasdotme@gmail.com,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
alessandro.menti@alessandromenti.it, elongbug@gmail.com,
cwryu@debian.org, uneedsihyeon@gmail.com, arek_koz@o2.pl,
dacs.git@brilhante.top, "insolor@gmail.com" <insolor@gmail.com>,
peter@softwolves.pp.se, bitigchi@me.com, ark@cho.red,
kate@kgthreads.com, "vnwildman@gmail.com" <vnwildman@gmail.com>,
pclouds@gmail.com, "dyroneteng@gmail.com" <dyroneteng@gmail.com>,
"oldsharp@gmail.com" <oldsharp@gmail.com>,
"lilydjwg@gmail.com" <lilydjwg@gmail.com>,
me@angyi.io, "Xin Jiang" <worldhello.net@gmail.com>,
"pan93412@gmail.com" <pan93412@gmail.com>,
"franklin@goodhorse.idv.tw" <franklin@goodhorse.idv.tw>
Subject: Re: Is there any interest in localizing term delimiters in git messages?
Date: Tue, 17 Oct 2023 14:49:58 -0700 [thread overview]
Message-ID: <xmqqzg0gx6k9.fsf@gitster.g> (raw)
In-Reply-To: <CAP6f5Mmi=f4DPcFwfvEiJMdKMa0BUyZ019mc8uFXyOufgD4NjA@mail.gmail.com> (Alexander Shopov's message of "Tue, 17 Oct 2023 23:09:50 +0200")
Alexander Shopov <ash@kambanaria.org> writes:
> Typical example:
> ORIGINAL
> msgid " (use \"git rm --cached <file>...\" to unstage)"
>
> TRANSLATION
> msgstr ""
> " (използвайте „git rm --cached %s ФАЙЛ…“, за да извадите ФАЙЛа от индекса)"
>
> The important part are the `<' and `>' delimiters of the term "file"
>
> Instead of using them - I omit them and capitalize the term. As if `<'
> and `>' are declared as localizable and then I translate them as `',
> `'
Is it because it is more common in your target language to omit <>
around the placeholder word, or is it just your personal preference?
Whichever is the case, I am not sure how it affects ...
> So I am asking - is there any interest from other localizers to have
> such a feature? Would the additional maintenance be OK for the
> developers?
... the maintenance burden for developers. Perhaps I am not getting
what you are proposing, but we are not going to change the message
in "C" locale (the original you see in msgid). In untranslated Git,
we will keep the convention to highlight the placeholder word by
having <> around it, so the "(use \"git rm --cached <file>...\" to
unstage)" message will be spelled with "<file>". You can translate
that to a msgstr without <> markings without asking anybody's
permission, and I do not think of a reason why it would burden
developers to do so.
As long as the target audience of your translation wants to see
<file> to be translated to ФАЙЛ without <> around the word, I do
not think there is any problem doing so. I of course am assuming
that using capitalized placeholder is the norm for all users who use
Bulgarian translated Git---if it is not some users want to see <>
around the placeholder word just like "C" locale, then you'd need to
answer your users wish first, or course, but that would not need to
concern the developers who write the "C" locale messages.
Thanks for helping Git easier to use for users with your language.
next prev parent reply other threads:[~2023-10-17 21:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 21:09 Is there any interest in localizing term delimiters in git messages? Alexander Shopov
2023-10-17 21:49 ` Junio C Hamano [this message]
2023-10-18 2:01 ` Jiang Xin
2023-10-18 2:47 ` Junio C Hamano
2023-10-18 3:08 ` [PATCH] commit: do not use cryptic "new_index" in end-user facing messages Junio C Hamano
2023-10-19 5:08 ` Is there any interest in localizing term delimiters in git messages? Jiang Xin
2023-10-19 17:52 ` Junio C Hamano
2023-10-19 18:07 ` Jeff Hostetler
2023-10-19 19:18 ` Junio C Hamano
2023-10-19 19:47 ` Torsten Bögershausen
2023-10-19 20:16 ` Junio C Hamano
2023-10-21 9:30 ` Peter Krefting
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=xmqqzg0gx6k9.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=alessandro.menti@alessandromenti.it \
--cc=alexhenrie24@gmail.com \
--cc=arek_koz@o2.pl \
--cc=ark@cho.red \
--cc=ash@kambanaria.org \
--cc=avarab@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=bitigchi@me.com \
--cc=christopher.diaz.riv@gmail.com \
--cc=cwryu@debian.org \
--cc=dacs.git@brilhante.top \
--cc=dyroneteng@gmail.com \
--cc=elongbug@gmail.com \
--cc=flashcode@flashtux.org \
--cc=franklin@goodhorse.idv.tw \
--cc=git@vger.kernel.org \
--cc=insolor@gmail.com \
--cc=jmas@softcatala.org \
--cc=jn.avila@free.fr \
--cc=kate@kgthreads.com \
--cc=lilydjwg@gmail.com \
--cc=matthias.ruester@gmail.com \
--cc=me@angyi.io \
--cc=oldsharp@gmail.com \
--cc=pan93412@gmail.com \
--cc=pclouds@gmail.com \
--cc=peter@softwolves.pp.se \
--cc=phillip.szelat@gmail.com \
--cc=ralf.thielow@gmail.com \
--cc=uneedsihyeon@gmail.com \
--cc=vnwildman@gmail.com \
--cc=vyruss@hellug.gr \
--cc=worldhello.net@gmail.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.
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 NNTP newsgroup(s).