Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
doc: camelCase the i18n config variables to improve readability
author
Kaartic Sivaraam
<kaarticsivaraam91196@gmail.com>
Mon, 17 Jul 2017 15:39:00 +0000
(21:09 +0530)
committer
Junio C Hamano
<gitster@pobox.com>
Mon, 17 Jul 2017 22:11:26 +0000
(15:11 -0700)
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>
Documentation/i18n.txt
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
08f9c32
)
diff --git
a/Documentation/i18n.txt
b/Documentation/i18n.txt
index 2dd79db5cbf674d3eeeb70c78cc961d0b15503ab..7e36e5b55b1ab89ed67ca02f5327e928c853183d 100644
(file)
--- a/
Documentation/i18n.txt
+++ b/
Documentation/i18n.txt
@@
-42,11
+42,11
@@
mind.
+
------------
[i18n]
+
------------
[i18n]
- commit
e
ncoding = ISO-8859-1
+ commit
E
ncoding = ISO-8859-1
------------
+
Commit objects created with the above setting record the value
------------
+
Commit objects created with the above setting record the value
-of `i18n.commit
e
ncoding` in its `encoding` header. This is to
+of `i18n.commit
E
ncoding` 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.
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
`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.log
outpute
ncoding` in `.git/config` file, like this:
+ `i18n.log
OutputE
ncoding` in `.git/config` file, like this:
+
------------
[i18n]
+
------------
[i18n]
- log
outpute
ncoding = ISO-8859-1
+ log
OutputE
ncoding = 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
-`i18n.commit
e
ncoding` is used instead.
+`i18n.commit
E
ncoding` 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
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