RE: Issues with chrome.manifest when installed in path having japanese characters

> This is correct and intentional: see the comment at
>
http://mxr.mozilla.org/mozilla-central/source/xpcom/build/nsXULAppAPI.h#155
>  We do this because on Windows the native charset doesn't represent
unicode. So we use a wmain entry point and wchar, and convert to UTF8
immediately so that we can use a shared 
> char* interface with all the other platforms.

Indeed, and this behaviour is (probably) the best to adopt. However it is a
problem if the embedder is itself an MBCS application.