doc: camelCase the i18n config variables to improve readability
The i18n config variable used weren't readable as they were in the crude form of how git stores/uses it's config variables. Improve it's readability by replacing them with camelCased versions of config variables as it doesn't have any impact on it's usage. Signed-off-by: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Kaartic Sivaraam committed
Jul 17, 2017 at 21:09 UTC
95791be750c43fed878b965480d14cf5f995585c
1 file changed
+5
-5
Documentation/i18n.txt
+5
-5
@@ -42,11 +42,11 @@ mind.
42
+
43
------------
44
[i18n]
45
- commitencoding = ISO-8859-1
45
+ commitEncoding = ISO-8859-1
46
------------
47
+
48
Commit objects created with the above setting record the value
49
-of `i18n.commitencoding` in its `encoding` header. This is to
49
+of `i18n.commitEncoding` in its `encoding` header. This is to
50
help other people who look at them later. Lack of this header
51
implies that the commit log message is encoded in UTF-8.
52
@@ -54,15 +54,15 @@ implies that the commit log message is encoded in UTF-8.
54
`encoding` header of a commit object, and try to re-code the
55
log message into UTF-8 unless otherwise specified. You can
56
specify the desired output encoding with
57
- `i18n.logoutputencoding` in `.git/config` file, like this:
57
+ `i18n.logOutputEncoding` in `.git/config` file, like this:
58
+
59
------------
60
[i18n]
61
- logoutputencoding = ISO-8859-1
61
+ logOutputEncoding = ISO-8859-1
62
------------
63
+
64
If you do not have this configuration variable, the value of
65
-`i18n.commitencoding` is used instead.
65
+`i18n.commitEncoding` is used instead.
66
67
Note that we deliberately chose not to re-code the commit log
68
message when a commit is made to force UTF-8 at the commit