Can't add any non-ascii files on mercurial for Windows?

[Matt Mackall]

On Tue, 2012-09-25 at 19:09 -0700, Nathan Davis wrote:
> 10646 seems to be an invalid code page (at least chcp doesn't
> recognize it)

Yeah, Microsoft has their own numbering which has no relation to ISO.

> Also, I tried changing HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
> \Control\Nls\CodePage\ACP from its current value of 1252 to 65001.
> Doing so made the system unable to boot.

Heh. Yes, Windows' internal UTF-8 handling is.. thin.

> You said that cp65001, can be mostly made to work, but I have not had
> success with it.  Can you elaborate?

It's non-trivial and unsupported. You need to set the OEM code page,
then use the magic SetFileAPIsToOEM() kernel call. And then you'll have
a handful of interesting font/console/wincrt bugs to work around. If you
want to become a Windows character encoding guru.. this is one good
starting point.

-- 
Mathematics is the supreme nostalgia of our time.