From: Johannes Sixt <j.sixt@viscovery.net>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Git List" <git@vger.kernel.org>,
"Ævar Arnfjörð" <avarab@gmail.com>
Subject: Re: [PATCH] Update l10n guide
Date: Fri, 02 Mar 2012 11:47:58 +0100 [thread overview]
Message-ID: <4F50A55E.8040705@viscovery.net> (raw)
In-Reply-To: <CANYiYbE7bxz5=h9gaKf6+N6k5cn6mEKnuf_7KPFAnDrC31UL_w@mail.gmail.com>
Am 3/2/2012 8:30, schrieb Jiang Xin:
> Git does not handle multi-bytes character well. Multi-bytes characters
> not convert to UTF-8 when git write tree objects and commit objects.
It does not convert, but it records which encoding the text has. If you
don't specify anything, UTF-8 is assumed, and if your text is actually not
UTF-8, the result is necessarily garbage.
> I think allow multi-bytes characters in commit log would hurt git.git until
> git gives full support UTF-8 (are there any plans for this?).
> I just tested several versions of msysgit:
>
> - Only Git-1.7.8-preview20111229-unicode.exe saves commit objects
> with utf-8 encode.
>
> - Other versions such as Git-1.7.9-preview20120201.exe and
> Git-1.7.8-preview20111206.exe will not convert multi-bytes characters
> in commit log into UTF-8.
Then you haven't set i18n.commitEncoding. Try this:
git config i18n.commitEncoding CP936
(substitute whatever Windows codepage you are using).
-- Hannes
next prev parent reply other threads:[~2012-03-02 10:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 17:40 l10n: the maintaince of git-po repo Jiang Xin
2012-02-29 5:34 ` Junio C Hamano
2012-02-29 8:23 ` [PATCH] Update l10n guide Junio C Hamano
2012-03-01 4:05 ` Jiang Xin
2012-03-01 5:25 ` Junio C Hamano
2012-03-02 7:30 ` Jiang Xin
2012-03-02 10:47 ` Johannes Sixt [this message]
2012-03-02 12:18 ` Jiang Xin
2012-03-02 14:56 ` Jakub Narebski
2012-03-02 16:59 ` Junio C Hamano
2012-03-02 7:41 ` [PATCH] Update l10n guide: change the repository URL, etc Jiang Xin
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=4F50A55E.8040705@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=worldhello.net@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 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).