Documentation/i18n.txt: it is i18n.commitencoding not core.commitencoding
Similarly for i18n.logoutputencoding. Signed-off-by: Fredrik Kuivinen <frekui@gmail.com> Signed-off-by: Junio C Hamano <junkio@cox.net>
Fredrik Kuivinen committed
Feb 18, 2007 at 10:36 UTC
38eb9329babb49e5bed52f4e2a577ac01c8d2fcb
1 file changed
+6
-6
Documentation/i18n.txt
+6
-6
@@ -25,15 +25,15 @@ mind.
25
an warning if the commit log message given to it does not look
26
like a valid UTF-8 string, unless you explicitly say your
27
project uses a legacy encoding. The way to say this is to
28
- have core.commitencoding in `.git/config` file, like this:
28
+ have i18n.commitencoding in `.git/config` file, like this:
29
+
30
------------
31
-[core]
31
+[i18n]
32
commitencoding = ISO-8859-1
33
------------
34
+
35
Commit objects created with the above setting record the value
36
-of `core.commitencoding` in its `encoding` header. This is to
36
+of `i18n.commitencoding` in its `encoding` header. This is to
37
help other people who look at them later. Lack of this header
38
implies that the commit log message is encoded in UTF-8.
39
@@ -41,15 +41,15 @@ implies that the commit log message is encoded in UTF-8.
41
header of a commit object, and tries to re-code the log
42
message into UTF-8 unless otherwise specified. You can
43
specify the desired output encoding with
44
- `core.logoutputencoding` in `.git/config` file, like this:
44
+ `i18n.logoutputencoding` in `.git/config` file, like this:
45
+
46
------------
47
-[core]
47
+[i18n]
48
logoutputencoding = ISO-8859-1
49
------------
50
+
51
If you do not have this configuration variable, the value of
52
-`core.commitencoding` is used instead.
52
+`i18n.commitencoding` is used instead.
53
54
Note that we deliberately chose not to re-code the commit log
55
message when a commit is made to force UTF-8 at the commit