diff options
author | Junio C Hamano <gitster@pobox.com> | 2013-02-05 21:13:21 -0800 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2013-02-05 21:13:21 -0800 |
commit | 076ffcc834f02a4f11d7f4fe8825be3b065020ff (patch) | |
tree | 6f5fa28df80c60c9b0a1dfab028d3db33ae22fa0 /i18n.txt | |
parent | 3f2ed6f9b744f05cf2ad32b0c0c80aa149d9fdcb (diff) | |
download | git-htmldocs-076ffcc834f02a4f11d7f4fe8825be3b065020ff.tar.gz |
Autogenerated HTML docs for v1.8.1.2-545-g2f19ad
Diffstat (limited to 'i18n.txt')
-rw-r--r-- | i18n.txt | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -1,9 +1,9 @@ -At the core level, git is character encoding agnostic. +At the core level, Git is character encoding agnostic. - The pathnames recorded in the index and in the tree objects are treated as uninterpreted sequences of non-NUL bytes. What readdir(2) returns are what are recorded and compared - with the data git keeps track of, which in turn are expected + with the data Git keeps track of, which in turn are expected to be what lstat(2) and creat(2) accepts. There is no such thing as pathname encoding translation. @@ -15,9 +15,9 @@ At the core level, git is character encoding agnostic. bytes. Although we encourage that the commit log messages are encoded -in UTF-8, both the core and git Porcelain are designed not to +in UTF-8, both the core and Git Porcelain are designed not to force UTF-8 on projects. If all participants of a particular -project find it more convenient to use legacy encodings, git +project find it more convenient to use legacy encodings, Git does not forbid it. However, there are a few things to keep in mind. |