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

From: Jakub Narebski <jnareb@gmail.com>
Date: Jan 18, 2008, 17:24 UTC
Message-ID: <fmqncq$5sf$1@ger.gmane.org>
In-Reply-To: <Pine.LNX.4.64.0801181631150.817@ds9.cixit.se>

Peter Karlsson wrote:

Show 8 quoted lines

> Dmitry Potapov:
> 
>> because Microsoft C library does not work with encoding that requires
>> more than two bytes per character.
> 
> Indeed. On Windows, you should avoid using UTF-8 and instead use UTF-16
> everywhere. That usually works better, and if you run on an NT-based
> system it will convert all the data to WinAPI to UTF-16 anyway.

Errr... doesn't UTF-16 (as compared to USC-2) sometimes (for some exotic characters) require more than two bytes per character?

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.