development/git
development/git
1
0
Fork 0
mirror of https://github.com/git/git synced 2024-10-12 11:32:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Documentation/i18n.txt: it is i18n.commitencoding not core.commitencoding

Browse source 
Similarly for i18n.logoutputencoding.

Signed-off-by: Fredrik Kuivinen <frekui@gmail.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
This commit is contained in:
Fredrik Kuivinen 2007-02-18 10:36:51 +01:00 committed by Junio C Hamano
parent 256c3fe6c7
commit 38eb9329ba
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
Documentation/i18n.txt
View file

@ -25,15 +25,15 @@ mind.
an warning if the commit log message given to it does not look an warning if the commit log message given to it does not look
like a valid UTF-8 string, unless you explicitly say your like a valid UTF-8 string, unless you explicitly say your
project uses a legacy encoding. The way to say this is to project uses a legacy encoding. The way to say this is to
have core.commitencoding in `.git/config` file, like this: have i18n.commitencoding in `.git/config` file, like this:
+ +
------------ ------------
[core] [i18n]
commitencoding = ISO-8859-1 commitencoding = ISO-8859-1
------------ ------------
+ +
Commit objects created with the above setting record the value Commit objects created with the above setting record the value
of `core.commitencoding` in its `encoding` header. This is to of `i18n.commitencoding` in its `encoding` header. This is to
help other people who look at them later. Lack of this header help other people who look at them later. Lack of this header
implies that the commit log message is encoded in UTF-8. implies that the commit log message is encoded in UTF-8.
@ -41,15 +41,15 @@ implies that the commit log message is encoded in UTF-8.
header of a commit object, and tries to re-code the log header of a commit object, and tries to re-code the log
message into UTF-8 unless otherwise specified. You can message into UTF-8 unless otherwise specified. You can
specify the desired output encoding with specify the desired output encoding with
`core.logoutputencoding` in `.git/config` file, like this: `i18n.logoutputencoding` in `.git/config` file, like this:
+ +
------------ ------------
[core] [i18n]
logoutputencoding = ISO-8859-1 logoutputencoding = ISO-8859-1
------------ ------------
+ +
If you do not have this configuration variable, the value of If you do not have this configuration variable, the value of
`core.commitencoding` is used instead. `i18n.commitencoding` is used instead.
Note that we deliberately chose not to re-code the commit log Note that we deliberately chose not to re-code the commit log
message when a commit is made to force UTF-8 at the commit message when a commit is made to force UTF-8 at the commit