on filenames

Signed-off-by: Mattias Andrée <maandree@operamail.com>

1 files changed, 29 insertions, 1 deletions

diff --git a/using-git.texinfo b/using-git.texinfo
index f753fce..7ce98d0 100644
--- a/using-git.texinfo
+++ b/using-git.texinfo
@@ -1308,6 +1308,10 @@ is annoying.
 * Git and shared build caches::
 * Git and keyword expansion::
 * Git and links::
+* Git and filenames::
+@c TODO * Git and merge tracking::
+@c TODO * git and file renames::
+@c TODO * Git and atomic commits::
 @end menu
 
 
@@ -1447,6 +1451,30 @@ in your symlinks.
 
 
 
+@node Git and filenames
+@section Git and filenames
+
+Git treats file names as byte sequences,
+meaning that if it supports all characters
+supported by your file system, including
+one developers operativing systems uses
+UTF-8 and the other's uses UTF-16, or
+only ASCII, there will be problems. Will
+it is true that systems really should use
+UTF-8, be case sensitive and support
+the entire Unicode, even characters that
+are not yet defined with use of all 31
+bits@footnote{Yes Unicode supports only
+up to 31 bits, so negative ordinals can
+be considered process private use.}
+except the NUL control character, you
+may consider just using lower case ASCII
+and be friendly to other systems on use
+a very restricted set of punctuation
+and no control characters.
+
+
+
 @node Beyond Git
 @chapter Beyond Git
 
@@ -1846,7 +1874,7 @@ distribution. To make possible for everyone
 to build your program you can use GNU Autotools
 or just a simple handwritten make file.
 
-Additionall such a build system lets you
+Additionally such a build system lets you
 provide means to configure and customise the
 build process as well as installing and
 uninstalling (without using package management)