If an acl file specifies accounts whose name contains national letters, MSLogonACL cannot import such permissions (it reports "Garbled-Account-Name: SID not valid."). The same applies to export: if you specify such an account using the UI and then try to export the ACL, you get the text file with garbled account names, and this file cannot be imported either. This applies to unicode version of MSLogonACL (non-unicode version untested, may work properly).

This is fixed by the following patch:
[syntax="c"]
*** UltraVNC/winvnc/ms-logon/MSLogonACL/MSLogonACL.cpp Sun Feb 17 02:04:21 2008
--- UltraVNC/winvnc/ms-logon/MSLogonACL/MSLogonACL.cpp Tue May 25 14:55:07 2010
***************
*** 19,24 ****
--- 19,25 ----
// If the source code for the program is not available from the place from
// which you received this file, check
// http://ultravnc.sourceforge.net/+ #include <locale.h>
#include <wchar.h>
#include <tchar.h>
#include "MSLogonACL.h"
***************
*** 28,33 ****
--- 29,35 ----

It was commited by Rudi right after the last stable version was released.
However, this is just a partial patch, that will cover most, but not all, cases. E.g., it will not be able to handle cases when there are accounts that consist of non-english AND non-current-user-locale characters. The only way to handle this is to rewrite the code to use Unicode. It must be done in MSLogonACL as well as in the authSSP (and thus change the UVNC MSLogon protocol to transmit Unicode).

did you try enable japanese keyboard at vncviewer and winvnc ... options or this not effect anything with mslogon ?

normally uvnc 2.0.x should be full unicode and backward compatible.standby now for bug fix to uvnc 1.0.9.5.1adzm developer working for unicode as priority for next major version for non english people and non latin keyboard

uvnc 2.0, not yet started, next version 1.0.9.7 with multi monitor fix and some others feature, shame fix of multi monitor NOT include to 1.0.9.6.1, hope would be honored.should not effect to all other code, seperate code.