Re: [PATCH v2] Documentation/i18n.txt: clarify character encoding support

From: Torsten Bögershausen <tboegi@web.de>
Date: Jul 2, 2015, 05:25 UTC
Message-ID: <5594CB33.7020108@web.de>
In-Reply-To: <55943B37.40101@gmail.com>

On 07/01/2015 09:10 PM, Karsten Blees wrote:

Show 6 quoted lines

>
> Of course, it would be nice to hear other opinions as well - this
> probably shouldn't be a discussion between the two of us :-)
>
> Karsten
>

I like this paragraf from your previous mail, I think it can go into i18n.txt "as is":

ISO-8859-x file names may be fine if you won't ever need to:
- use git-web, JGit, gitk, git-gui...
- exchange repos with "normal" (UTF-8) Unices, Mac and Windows systems
- publish your work on a git hosting service (and expect file and
   ref names to show up correctly in the web interface)
- store the repo on Unicode-based file systems (JFS, Joliet, UDF,
   exFat, NTFS, HFS+, CIFS...)