(w32font_has_char): Always return -1.

diff --git a/src/ChangeLog b/src/ChangeLog
index 95cbce4dbb0d263fd4c9b47ea51d7da769920d55..b3b5f3371f75589507178c5e1aac49c00b14a0c2 100644 (file)
--- a/src/ChangeLog
+++ b/src/ChangeLog
@@ -1,3 +1,7 @@
+2008-12-17  Jason Rumney  <jasonr@gnu.org>
+
+       * w32font.c (w32font_has_char): Always return -1.
+
 2008-12-16  Kenichi Handa  <handa@m17n.org>
 
        * font.c (font_open_entity): Fix previous change.

diff --git a/src/w32font.c b/src/w32font.c
index f892adeb6365b777c1c69eb8e797e7b7e10d1b56..c5546ee937923b72de623e2f181dea3c24325f05 100644 (file)
--- a/src/w32font.c
+++ b/src/w32font.c
@@ -308,6 +308,12 @@ w32font_has_char (entity, c)
      Lisp_Object entity;
      int c;
 {
+  /* We can't be certain about which characters a font will support until
+     we open it.  Checking the scripts that the font supports turns out
+     to not be reliable.  */
+  return -1;
+
+#if 0
   Lisp_Object supported_scripts, extra, script;
   DWORD mask;
 
@@ -333,8 +339,11 @@ w32font_has_char (entity, c)
     return -1;
 
   /* Font reports what scripts it supports, and none of them are the script
-     the character is from, so it is a definite no.  */
-  return 0;
+     the character is from. But we still can't be certain, as some fonts
+     will contain some/most/all of the characters in that script without
+     claiming support for it.  */
+  return -1;
+#endif
 }
 
 /* w32 implementation of encode_char for font backend.