[Fonts]type1 backend and filenames

[James H. Cloos Jr.]

I just discovered that the Type1 backend errors out if the filename in
fonts.dir matches the glob *.PFB rather than *.pfb.  The current
FreeType backend handles majuscule extensions by including both all
minuscule and all majuscule verisons of the extension in the structure
it passes to FontFileRegisterRenderer().�

The attached patch does the same for the Type1 backend.

-JimC

� Incidently even this is not a perfect solution; many people seem to
  be using an initial-majuscule plus minuscules ...  Perhaps it would
  be better were xc/lib/font/fontfile/renderers.c to match extensions
  case-insensitively?


diff -udNr HEAD/xc/lib/font/Type1/t1funcs.c JHCLOOS/xc/lib/font/Type1/t1funcs.c
--- HEAD/xc/lib/font/Type1/t1funcs.c	Sun Mar 31 05:28:55 2002
+++ JHCLOOS/xc/lib/font/Type1/t1funcs.c	Sun Mar 31 05:29:07 2002
@@ -1446,6 +1446,10 @@
   { ".pfa", 4, NULL, Type1OpenScalable,
         NULL, Type1GetInfoScalable, 0, CAPABILITIES },
   { ".pfb", 4, NULL, Type1OpenScalable,
+    NULL, Type1GetInfoScalable, 0, CAPABILITIES },
+  { ".PFA", 4, NULL, Type1OpenScalable,
+        NULL, Type1GetInfoScalable, 0, CAPABILITIES },
+  { ".PFB", 4, NULL, Type1OpenScalable,
         NULL, Type1GetInfoScalable, 0, CAPABILITIES }
 };