From: Peter Krefting <peter@softwolves.pp.se>
To: Git List <git@vger.kernel.org>
Subject: Re: Is there any interest in localizing term delimiters in git messages?
Date: Sat, 21 Oct 2023 10:30:32 +0100 (CET) [thread overview]
Message-ID: <f6d7e29c-3532-428b-2c1-371eedaa5492@softwolves.pp.se> (raw)
In-Reply-To: <CAP6f5Mmi=f4DPcFwfvEiJMdKMa0BUyZ019mc8uFXyOufgD4NjA@mail.gmail.com>
Alexander Shopov:
> Hello all,
>
> Is there any interest in being able to change the delimiters of the
> changeable terms in git messages?
>
> Typical example:
> ORIGINAL
> msgid " (use \"git rm --cached <file>...\" to unstage)"
I think there should be something indicating the variables, and with
Unicode there are better choices than the ASCII
less-than-greater-than, for instance U+2039/U+203A. In the same way,
we could also fix the quotation marks:
" (use “git rm --cached ‹file›...” to unstage)"
The source should perhaps still be ASCII-only to be compatible with
older systems, but we could create a en_US.UTF-8 localization file
that does the above, and apply similar changes to other localizations
(I have been thinking about doing it to the Swedish translation for a
while, but so far have not come around to; of course quoting differs
from language to language, with different styles for ‘English’,
“American”, „German”, ”Swedish” and «Norwegian», for instance; it is
all very confusing and difficult to get right).
--
\\// Peter - http://www.softwolves.pp.se/
prev parent reply other threads:[~2023-10-21 9:37 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
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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f6d7e29c-3532-428b-2c1-371eedaa5492@softwolves.pp.se \
--to=peter@softwolves.pp.se \
--cc=git@vger.kernel.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.
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).