[Bug 52902] New: gdi32:font has specific failures on Windows 10 with the UTF-8 codepage

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52902

Bug ID: 52902
           Summary: gdi32:font has specific failures on Windows 10 with
                    the UTF-8 codepage
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdi32
          Assignee: [e-mail]
          Reporter: [e-mail]

The following gdi32:font failures are specific to UTF-8 on Windows 10:

--- test_RealizationInfo():
font.c:4356: Test failed: info[0] = 103 for the system font

--- test_GetCharacterPlacement():
font.c:4998: Test failed: Unexpected first glyph L":"
font.c:5012: Test failed: GetCharacterPlacementA returned different result:
1048638 vs 1048637
font.c:5016: Test failed: GetCharacterPlacementA returned different result:
1048638 vs 1048637
font.c:5023: Test failed: GetCharacterPlacementA returned different result:
1048638 vs 1048637
font.c:5025: Test failed: Unexpected first glyph L":"

--- test_GetCharWidthInfo():
font.c:7396: Test failed: expected 0, got -8
font.c:7397: Test failed: expected 0, got -9
font.c:7398: Test failed: expected 0, got 1

https://test.winehq.org/data/patterns.html#gdi32:font

They can be reproduced on w10pro64-hi-u8.
Note that w10pro64-hi which uses the Hindi locale too but not UTF-8 (so the
system locale is English) has its own set of totally unrelated failures.