Re: [1/2] mlang: Add implementation of fnIMLangFontLink_GetCharCodePages

[Dmitry Timoshkov]

"Vitaly Perov"  wrote:
> @@ -1855,8 +1855,56 @@ static HRESULT WINAPI fnIMLangFontLink_GetCharCodePages(
>          WCHAR chSrc,
>          DWORD* pdwCodePages)
>  {
> - FIXME("\n");
> - return E_NOTIMPL;
> - /* codepages, supported by Windows */
> - static const unsigned int processCP[] = {1250, 1251, 1252, 1253, 1254, 1255,
> -
>    1256, 1257, 1258, 874, 932, 936, 949, 950, 0};

It doesn't really matter what code pages Windows supports, it does
matter though what code pages are valid. You need to use Win32 APIs
EnumSystemCodePages/GetCPInfo/MultiByteToWideChar instead of accessing
Wine internals directly.

[1/2] mlang: Add implementation offnIMLangFontLink_GetCharCodePages

[Dmitry Timoshkov]

"Dmitry Timoshkov"  wrote:
> It doesn't really matter what code pages Windows supports, it does
> matter though what code pages are valid. You need to use Win32 APIs
> EnumSystemCodePages/GetCPInfo/MultiByteToWideChar instead of accessing
> Wine internals directly.

... or rather use mlang internal mlang_data structures.

[1/2] mlang: Add implementation of fnIMLangFontLink_GetCharCodePages

[Vitaly Perov]

Hi! Thank you for your comments
> It doesn't really matter what code pages Windows supports, it does
> matter though what code pages are valid. You need to use Win32 APIs
> EnumSystemCodePages/GetCPInfo/MultiByteToWideChar instead of accessing
> Wine internals directly.

I used EnumSystemCodePages before, but in this case GetCharCodePages set some 
extra bits in result. So the result differ from Windows
> ... or rather use mlang internal mlang_data structures.

I's good idea! Thank you!