PangoWin32: Make font discovery thread-safe

Make font discovery using GDI/Unicscribe on Windows thread-safe, by:

-Making the alias HashTable a part of the _PangoWin32FontMap struct, so
 that we only need to initialize this once when we initialize the
 PangoFontMap on Win32.  Make sure that we fill in that hash table with
 the fonts items we ask from the system once and only once as we
 initialize the PangoWin32FontMap.

-Make the warned_fonts HashTable a part of the _PangoWin32FontMap struct
 as well, and create the HashTable when we init the PangoWin32FontMap.

-Make the access to the common HDC in pangowin32.c where Alex mentioned
 that could be thread-unsafe done through pango_win32_get_dc().

At this point the test-pangocairo-threads will pass in Meson, tested for
20 successive rounds using 'meson test test-pangocairo-threads'.  Note
that we still get the
"Pango-WARNING **:hh:mm:ss.sss: All font fallbacks failed!!!", but at
least we are doing much better on PangoWin32 in terms of thread-safety.

0 files changed, 0 insertions, 0 deletions