From dbffa4c83d29c689ee4cd8a1c53e84521028c711 Mon Sep 17 00:00:00 2001
From: Behdad Esfahbod <behdad@behdad.org>
Date: Fri, 8 Jun 2012 14:08:32 -0400
Subject: [PATCH] Fix Uniscribe charset matching

Previously was failing to match fonts that didn't support CHARSET_ANSI.

There still remains a problem with the Uniscribe backend, in that if a
font with the same family name is installed, and is newer, the native
one is preferred over the font we provide.  Fixing it requires rewriting
the name table with a unique family name...
---
 src/hb-uniscribe.cc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/hb-uniscribe.cc b/src/hb-uniscribe.cc
index 42721ec10..17d0acc78 100644
--- a/src/hb-uniscribe.cc
+++ b/src/hb-uniscribe.cc
@@ -64,6 +64,7 @@ populate_log_font (LOGFONTW  *lf,
 {
   memset (lf, 0, sizeof (*lf));
   lf->lfHeight = -font->y_scale;
+  lf->lfCharSet = DEFAULT_CHARSET;
 
   hb_blob_t *blob = Sanitizer<name>::sanitize (hb_face_reference_table (font->face, HB_TAG ('n','a','m','e')));
   const name *name_table = Sanitizer<name>::lock_instance (blob);