https://bugs.winehq.org/show_bug.cgi?id=39297
--- Comment #4 from Hin-Tak Leung htl10@users.sourceforge.net --- The list of functions which FontValidator tries to access are:
BOOL kernel32.GetCPInfo( UINT CodePage, LPCPINFO lpCPInfo ) BOOL kernel32.IsValidCodePage( UINT CodePage ) BOOL kernel32.IsDBCSLeadByteEx( UINT CodePage, BYTE TestChar ) int kernel32.MultiByteToWideChar( UINT CodePage, DWORD dwFlags, LPCSTR lpMultiByteStr, int cbMultiByte, LPWSTR lpWideCharStr, int cchWideChar )
As one can see, all of them contains a codepage argument.
For most (all?) codepages, these eventually traces to one of wine/libs/wine/c_*.c .
for example, for code page 950 (traditional chinese), there is a file wine/libs/wine/c_950.c .
Whereas c_950.c and friends are derived from public sources on www.unicode.org, I cannot (yet) find an authoritative source of what code page 708 is, although both glibc and mono claims to supports this code page in their internationalization support.