https://bugs.winehq.org/show_bug.cgi?id=52951 Bug ID: 52951 Summary: gdi32:font - test_GetGlyphOutline() fails on "VL Gothic" in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- gdi32:font - test_GetGlyphOutline() fails on "VL Gothic" in Wine: font.c:4885: Test failed: expected 36, got 19 (VL Gothic:136) font.c:4903: Test failed: expected 36, got 19 (VL Gothic:136) https://test.winehq.org/data/patterns.html#gdi32:font This begs two questions: 1. Is this a bug in the font, or a bug in the test? 2. Why does this happen on the debian11 (and debiant) VMs, but not on fg-deb64 (my development machine)? On Debian VL Gothic is brought in by this package dependency chain: libsane -> libpoppler-glib8 -> libpoppler102 -> poppler-data -(suggest)-> fonts-vlgothic Interestingly poppler-data has alternatives to fonts-vlgothic one of which is already installed: fonts-ipaexfont-gothic fonts-ipfont-gothic (installed) fonts-ipafont-nonfree-jisx0208 fonts-mona fonts-takao-gothic fonts-umeplus-cl fonts-vlgothic (installed) But the reason for the difference is that fg-deb64 has the AR PL UMing CN font (from the fonts-arphic-uming package) and not the TestBot VMs. The lack of UMing also causes a test to be skipped on the TestBot VMs: 1: (IPAGothic:128) 2: (NanumGothicCoding:129) font.c:4867: Tests skipped: Fixed-pitch TrueType font for charset 134 is not available 4: (VL Gothic:136) So I'm going to install fonts-arphic-uming on the TestBot VMs which should swipe these two failures under the rug. Note: I don't have information on how much this will increase the runtime (see bug 51367) but it seems like it shouldn't be too bad. -- 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.