Commit 95791be7 authored by Kaartic Sivaraam's avatar Kaartic Sivaraam Committed by Junio C Hamano

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: default avatarKaartic Sivaraam <>
Signed-off-by: default avatarJunio C Hamano <>
parent 08f9c324
......@@ -42,11 +42,11 @@ mind.
commitencoding = ISO-8859-1
commitEncoding = ISO-8859-1
Commit objects created with the above setting record the value
of `i18n.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
implies that the commit log message is encoded in UTF-8.
......@@ -54,15 +54,15 @@ implies that the commit log message is encoded in UTF-8.
`encoding` header of a commit object, and try to re-code the
log message into UTF-8 unless otherwise specified. You can
specify the desired output encoding with
`i18n.logoutputencoding` in `.git/config` file, like this:
`i18n.logOutputEncoding` in `.git/config` file, like this:
logoutputencoding = ISO-8859-1
logOutputEncoding = ISO-8859-1
If you do not have this configuration variable, the value of
`i18n.commitencoding` is used instead.
`i18n.commitEncoding` is used instead.
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
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment