[Bug 52967] New: gdi32:font - test_text_metrics() fails on Windows with en-AE-u8 and plain Hindi

[WineHQ Bugzilla]

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

            Bug ID: 52967
           Summary: gdi32:font - test_text_metrics() fails on Windows with
                    en-AE-u8 and plain Hindi
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdi32
          Assignee: wine-bugs at winehq.org
          Reporter: fgouget at codeweavers.com

gdi32:font - test_text_metrics() has a set of failures on Windows that only
happen with the English Arab Emirates + UTF-8 locale (en-AE-u8), and in Hindi
but without UTF-8 (hi):

font.c:3441: Test failed: BIZ UDGothic: expected family 30 got 26. panose
2-11-4-0-...
font.c:3441: Test failed: BIZ UDGothic: expected family 30 got 26. panose
2-11-4-0-...
font.c:3441: Test failed: @BIZ UDGothic: expected family 30 got 26. panose
2-11-4-0-...
font.c:3441: Test failed: @BIZ UDGothic: expected family 30 got 26. panose
2-11-4-0-...
font.c:3441: Test failed: BIZ UDMincho Medium: expected family 30 got 16.
panose 2-2-5-0-...
font.c:3441: Test failed: BIZ UDMincho Medium: expected family 30 got 16.
panose 2-2-5-0-...
font.c:3441: Test failed: @BIZ UDMincho Medium: expected family 30 got 16.
panose 2-2-5-0-...
font.c:3441: Test failed: @BIZ UDMincho Medium: expected family 30 got 16.
panose 2-2-5-0-...
font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho N-B got a5
expected 1f
font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho N-B got ff65
expected 1f
font.c:3441: Test failed: UD Digi Kyokasho N-B: expected family 30 got 16.
panose 2-2-7-0-...
font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho N-B got a5
expected 1f
font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho N-B got ff65
expected 1f
font.c:3441: Test failed: @UD Digi Kyokasho N-B: expected family 30 got 16.
panose 2-2-7-0-...
font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho NP-B got a5
expected 1f
font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho NP-B got ff65
expected 1f
font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho NP-B got a5
expected 1f
font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho NP-B got ff65
expected 1f
font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho NK-B got a5
expected 1f
font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho NK-B got ff65
expected 1f
font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho NK-B got a5
expected 1f
font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho NK-B got ff65
expected 1f
font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho N-R got a5
expected 1f
font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho N-R got ff65
expected 1f
font.c:3441: Test failed: UD Digi Kyokasho N-R: expected family 30 got 16.
panose 2-2-4-0-...
font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho N-R got a5
expected 1f
font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho N-R got ff65
expected 1f
font.c:3441: Test failed: @UD Digi Kyokasho N-R: expected family 30 got 16.
panose 2-2-4-0-...
font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho NP-R got a5
expected 1f
font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho NP-R got ff65
expected 1f
font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho NP-R got a5
expected 1f
font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho NP-R got ff65
expected 1f
font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho NK-R got a5
expected 1f
font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho NK-R got ff65
expected 1f
font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho NK-R got a5
expected 1f
font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho NK-R got ff65
expected 1f

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

So it's not UTF-8 that causes the failures (still fails in Hindi). It seems to
be something that English Arab Emirates and Hindi have in common and that goes
away in Hindi + UTF-8.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.