From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Nicholas Hsiang <xianghongai@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Chinese characters are garbled, setting utf-8 is also garbled
Date: Sun, 2 Aug 2020 01:28:02 +0000 [thread overview]
Message-ID: <20200802012802.GK6540@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CAEcaDL=BrqFf7bwJ0cVWK-+vUKLmuihhKr8m0_w2CCSNfA9LEw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
On 2020-08-01 at 04:36:50, Nicholas Hsiang wrote:
> Hi,
>
> There are some problems here.
>
> I have configured the character encoding in .gitconfig:
>
> ```yaml
> [core]
> quotepath = false
> [gui]
> encoding = utf-8
> [i18n]
> commitencoding = utf-8
> logoutputencoding = utf-8
> ```
>
> and Git Bash configed: Options > Text > Locale: zh_CN, Character set: UTF-8
>
> However, when executing `git pull/reset/status`, Chinese characters
> still appeared garbled.
>
> ```bash
> Xiang@Xiang MINGW64 /c/me/front-end-note (master)
> $ git reset --hard df576e2
> HEAD is now at df576e2 doc: 琛ュ厖 ES5 缁ф壙
> ```
Since this is a Windows issue, you'd be better off reporting this at the
Git for Windows issue tracker at
https://github.com/git-for-windows/git/issues/. As far as what I've
seen in your email, the characters do appear to be in Chinese, although
since I don't speak or read that language, I don't know whether they
make any sense or are garbled.
--
brian m. carlson: Houston, Texas, US
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2020-08-02 1:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 4:36 Chinese characters are garbled, setting utf-8 is also garbled Nicholas Hsiang
2020-08-02 1:28 ` brian m. carlson [this message]
2020-08-02 4:17 ` Nicholas Hsiang
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=20200802012802.GK6540@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=xianghongai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.