From: Thomas Singer <thomas.singer@syntevo.com>
Date: Tue, 01 Dec 2009 07:49:13 GMT
Subject: Re: non-US-ASCII file names (e.g. Hiragana) on Windows
Message-ID: <4B14CA79.6040408@syntevo.com>
In-Reply-To: <4B123C80.30607@syntevo.com>

Thomas Singer wrote:
> Reece Dunn wrote:
>> This is a bug in git's character encoding/conversion logic. It looks
>> like git is taking the source string and converting it to ascii to be
>> displayed on the console output (e.g. by using the WideCharToMultiByte
>> conversion API) -- these APIs will use a '?' character for characters
>> that it cannot map to the target character encoding (like the Hiragana
>> characters that you are using).
> 
> I have a screenshot from a SmartGit user where 1) the console can show the
> far-east-characters and 2) Git *can* show the characters escaped. Are there
> two versions of Git available or does Gits behaviour depends somehow on the
> system locale?

Does no Git expert know what to do to get it working?

-- 
Tom