https://bugs.winehq.org/show_bug.cgi?id=39297
--- Comment #6 from Hin-Tak Leung htl10@users.sourceforge.net --- (In reply to Nikolay Sivov from comment #5)
The question is does this tool work on Windows for same fonts? (please name them if it's possible, I can test it if you don't have access to Windows machine).
Of course it does - it is a microsoft tool!
e.g. on Windows 8.1 (which comes with this code page) - if you use the tool to analyse window 8.1's tahoma.ttf, in the generated report it would say something like:
A CodePage bit is set in ulCodePageRange, but the font is missing some of the printable characters from that codepage, bit #61, Arabic; ASMO 708 (49 missing, first ten missing chars are: U2502 U2524 U2561 U2562 U2556 U2555 U2563 U2551 U2557 U255D)
but running under wine + dotnet 2, it would say something about code page not installed.
Note that:
1. for some unknown reason, it does not want to navigate to c:\windows\fonts on windows 8.1 - but you can copy tahoma.ttf onto desktop to test.
2. some part of it does not work with wine + wine-mono, though this part does. You should de-select all of the table tests except OS/2, and also choose to "save report file" to a location of your choice, rather than the default "open after analyis" (from temp location), if you are testing under wine + wine-mono or wine + dotnet .
Another easy thing to try is to add test with this cp number for GetCPInfoEx for example, to see if it works at all and if it does see what's returned as a name.
What is the purpose of this test? I already told you what the problem is, and where the bulk of new code need to be added - there needs to be a new "wine/libs/wine/c_708.c" file, and an extra line "wine/libs/wine/cptable.c" to register the new code page table, just like any of the others!