mirror of
https://github.com/git/git
synced 2024-08-25 02:35:46 +00:00
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>
This commit is contained in:
parent
08f9c32463
commit
95791be750
|
@ -42,11 +42,11 @@ mind.
|
|||
+
|
||||
------------
|
||||
[i18n]
|
||||
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:
|
||||
+
|
||||
------------
|
||||
[i18n]
|
||||
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
|
||||
|
|
Loading…
Reference in a new issue