From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Thomas Guyot" <tguyot@gmail.com>, Yuri <yuri@rawbw.com>,
"Jeff King" <peff@peff.net>,
"Torsten Bögershausen" <tboegi@web.de>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [BUG REPORT] File names that contain UTF8 characters are unnecessarily escaped in 'git status .' messages
Date: Mon, 31 May 2021 10:35:49 +0700 [thread overview]
Message-ID: <ec3adb99-ba20-8db6-4bff-eae7524e6361@gmail.com> (raw)
In-Reply-To: <c1afaf46-0425-110b-6303-f68d3f994b7f@gmail.com>
On 31/05/21 08.14, Thomas Guyot wrote:
> Even if the terminal supports UTF8, will it print it properly? The font
> used could have no or minimal utf8 support. Even when it's supported,
> some characters might look alike and this could have undesired
> consequences (ex accidentally switching from a normal space to a
> non-break space while renaming a file that has spaces...).
On Linux distributions, Noto and DejaVu fonts are often installed as
default fonts, because Noto has almost complete Unicode coverage and
DejaVu Mono become goto monospace font.
And yeah, we steer clear of using non-monospace fonts (either serif or
sans serif), because many terminal-only programs depend on text
alignment which often can be achieved only with monospace fonts, and
reading texts on terminal screen is vertical-oriented as opposed to
horizontal-oriented texts like books.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-05-31 3:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 22:47 [BUG REPORT] File names that contain UTF8 characters are unnecessarily escaped in 'git status .' messages Yuri
2021-05-26 23:32 ` Junio C Hamano
2021-05-26 23:41 ` Yuri
2021-05-27 4:56 ` Torsten Bögershausen
2021-05-27 14:02 ` Jeff King
2021-05-27 20:50 ` Yuri
2021-05-28 4:39 ` Bagas Sanjaya
2021-05-28 4:45 ` Yuri
2021-05-29 9:27 ` Torsten Bögershausen
2021-05-30 21:44 ` Jeff King
2021-05-30 21:55 ` Yuri
2021-05-31 1:14 ` Thomas Guyot
2021-05-31 3:35 ` Bagas Sanjaya [this message]
2021-05-30 22:23 ` Junio C Hamano
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=ec3adb99-ba20-8db6-4bff-eae7524e6361@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=tboegi@web.de \
--cc=tguyot@gmail.com \
--cc=yuri@rawbw.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).