Re: [BUG REPORT] File names that contain UTF8 characters are unnecessarily escaped in 'git status .' messages
- From
Bagas Sanjaya <bagasdotme@gmail.com>
- Date
- May 31, 2021, 03:35 UTC
- Message-ID
- <ec3adb99-ba20-8db6-4bff-eae7524e6361@gmail.com>
- In-Reply-To
- <c1afaf46-0425-110b-6303-f68d3f994b7f@gmail.com>
On 31/05/21 08.14, Thomas Guyot wrote:
Show 5 quoted lines
> 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