From: Bastien Traverse <bastien@traverse.email>
To: Charles Bailey <charles@hashpling.org>
Cc: git@vger.kernel.org
Subject: Re: [Question] Is it normal for accented characters to be shown as decomposed Unicode on GNU/Linux?
Date: Mon, 22 Jun 2015 18:13:40 +0200 [thread overview]
Message-ID: <55883434.8040406@traverse.email> (raw)
In-Reply-To: <20150622150428.GA14100@hashpling.org>
Le 22/06/2015 17:04, Charles Bailey a écrit :
> Note that these aren't "decomposed" (in the unicode decomposition
> sense) but are merely octal escaped representations of the utf-8
> encoded file names.
Thanks, I had read that term in similar context (German umlaut) and
thought it was correctly describing the phenomenon. Key words "octal
escape" return more precise results :)
> My understanding that this is normal and probably dates back (at least
> for status as far as:
>
> commit a734d0b10bd0f5554abb3acdf11426040cfc4df0
> Author: Dmitry Potapov <dpotapov@gmail.com>
> Date: Fri Mar 7 05:30:58 2008 +0300
>
> Make private quote_path() in wt-status.c available as
> quote_path_relative()
>
> [...]
>
> The behaviour can be changed by setting the git config variable
> "core.quotePath" to false.
This is awesome, thank you. Indeed I just tried my test case with this
config option set to false and accented characters appear normally.
Thank you!
prev parent reply other threads:[~2015-06-22 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 13:17 [Question] Is it normal for accented characters to be shown as decomposed Unicode on GNU/Linux? Bastien Traverse
2015-06-22 15:04 ` Charles Bailey
2015-06-22 16:13 ` Bastien Traverse [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=55883434.8040406@traverse.email \
--to=bastien@traverse.email \
--cc=charles@hashpling.org \
--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).