diff options
| author | Junio C Hamano <junio@hera.kernel.org> | 2007-02-19 05:35:53 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@hera.kernel.org> | 2007-02-19 05:35:53 +0000 |
| commit | 35bb3f600bc6a09085ad895e86a1ffdf6370407a (patch) | |
| tree | 391d8edae965b1d603de4daf79833bba1b959f7c /i18n.txt | |
| parent | 89d4e0f4569738d0b1885879bf6ed88a972cd3da (diff) | |
| download | git-htmldocs-35bb3f600bc6a09085ad895e86a1ffdf6370407a.tar.gz | |
Autogenerated HTML docs for v1.5.0.1-26-gf5a92
Diffstat (limited to 'i18n.txt')
| -rw-r--r-- | i18n.txt | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -25,15 +25,15 @@ mind. an warning if the commit log message given to it does not look like a valid UTF-8 string, unless you explicitly say your project uses a legacy encoding. The way to say this is to - have core.commitencoding in `.git/config` file, like this: + have i18n.commitencoding in `.git/config` file, like this: + ------------ -[core] +[i18n] commitencoding = ISO-8859-1 ------------ + Commit objects created with the above setting record the value -of `core.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. @@ -41,15 +41,15 @@ implies that the commit log message is encoded in UTF-8. header of a commit object, and tries to re-code the log message into UTF-8 unless otherwise specified. You can specify the desired output encoding with - `core.logoutputencoding` in `.git/config` file, like this: + `i18n.logoutputencoding` in `.git/config` file, like this: + ------------ -[core] +[i18n] logoutputencoding = ISO-8859-1 ------------ + If you do not have this configuration variable, the value of -`core.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 |