Re: git on MacOSX and files with decomposed utf-8 file names

From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date: Jan 18, 2008, 09:42 UTC
Message-ID: <200801181042.37391.robin.rosenberg.lists@dewire.com>
In-Reply-To: <alpine.LFD.1.00.0801171716310.2957@woody.linux-foundation.org>

fredagen den 18 januari 2008 skrev Linus Torvalds:

Show 12 quoted lines

> > > translation to UTF-8, and since we use C strings, I'd assume/hope Windows 
> > > actually uses that unambiguous translation for any filenames).
> > 
> > It uses the local 8-bit codepage, which is not UTF-8, often some latin-inspired
> > thingy, but in Asia multi-byte encodings are used. In western Europe it is
> > Windows-1252, which is almost, but not exactly iso-8859-1. Oh, and then we
> > have the cmd prompt which has another encoding in 8-bit mode.
> 
> Well, if it uses a 8-bit codepage, then that means that as far as the 
> POSIX filename interface is concerned, it has nothing what-so-ever to do 
> with Unicode (ie unicode is just a totally invisible internal encoding 
> issue, not externally visible).

I just had to investigate this a bit, so on a Vista machine I started a cmd prompt and typed mode con: cp select=65001, selected the lucida font and then echo å >x.txt and opened it in notepad and it was UTF-8 encoded. So there might be some hope after all. I don't know how to change the encoding for non-console apps. I leave that as an excercise for the list.

-- robin