GTK uses win32 Pango backend directly
GTK3 does that in two places:
PangoFontDescription; contributes to #2495).
gtk_im_context_ime_set_preedit_font()(exploits the fact that a
PangoWin32Fontsubclass of the
PangoFonthas an internal
LOGFONTWfield, which is what
pango_win32_font_logfontw()returns (also - there's a memory leak here, because
pango_win32_font_logfont()is used, but its return value isn't freed), and which GTK then feeds to W32 API as-is).
Personally, i think this is bad. It is technically possible to build Pango without the W32 backend (Pango buildsystem does not have that as an option, but disabling W32 backend requires just a couple of one-line changes to the meson scripts - Pango code itself has no problem with that backend being missing), and except for the two instances above GTK never uses that backend directly. As a test, i built a Pango with no W32 backend, then quickly hacked away these two instances, and was able to successfully build GTK3 and run gtk3-demo.