Re: non-US-ASCII file names (e.g. Hiragana) on Windows
- From
- Thomas Singer <thomas.singer@syntevo.com>
- Date
- Nov 29, 2009, 09:18 UTC
- Message-ID
- <4B123C80.30607@syntevo.com>
- In-Reply-To
- <4B11AD43.3070307@gmail.com>
Maximilien Noal wrote:
Show 11 quoted lines
> About the 'boxes' : > > The thing is, Windows' files for Asian languages are _not_ installed by > default. > > They can be installed (even while installing Windows), by checking the > two checkboxes under the "Supplemtal languages support" groupbox in the > "Languages" tab of the "Regional and language options" control panel. > *re-take some breath ;-) * > > It will remove the "boxes" in Explorer and display nice Asian characters.
Thanks, now the characters are showing up fine in the Explorer.
Reece Dunn wrote:
Show 6 quoted lines
> 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?
-- Tom