Weird Windows 10 font issue: installs fine, previews fine, defaults to Arial in Word

Saga Söderback
Posts: 44
Hi all –
Is Windows 10 goofy with TTFs in some way? I am testing out a font I hinted but I'm getting a wacky issue. The font installs fine. It looks correct in the small preview of an Explorer window of the Fonts directory. It is correct in the small drop-down font selection preview in Word. Type with it, though, and you get Arial. Never seen anything like this before.
The font passes validation (including rasterization). I deleted the font cache and restarted. impallari.com show it fine. There are zero issues with it working properly on the Mac side.
Any ideas? I am stumped. I have diffed with properly working files pre-hints and the only differences are:
- a few glyph list changes, making glyf, loca, and UnicodeRange & ulCodePageRange diffs in OS/2
- checksum and date modified in head
(besides the obvious diffs one would create due to hinting in VDMX, LTSH, gasp, hdmx, prep, fpgm, cvt, maxp)
Thanks for any thoughts...
Micah
Is Windows 10 goofy with TTFs in some way? I am testing out a font I hinted but I'm getting a wacky issue. The font installs fine. It looks correct in the small preview of an Explorer window of the Fonts directory. It is correct in the small drop-down font selection preview in Word. Type with it, though, and you get Arial. Never seen anything like this before.
The font passes validation (including rasterization). I deleted the font cache and restarted. impallari.com show it fine. There are zero issues with it working properly on the Mac side.
Any ideas? I am stumped. I have diffed with properly working files pre-hints and the only differences are:
- a few glyph list changes, making glyf, loca, and UnicodeRange & ulCodePageRange diffs in OS/2
- checksum and date modified in head
(besides the obvious diffs one would create due to hinting in VDMX, LTSH, gasp, hdmx, prep, fpgm, cvt, maxp)
Thanks for any thoughts...
Micah
Tagged:
0
Comments
-
Other random things I have tried:
fsType in OS/2 to Installable, Editable, etc
different versions of the OS/2 table (3, 4)0 -
Latest test: using the "Ship Font" function in VTT instead of deleting the TSI tables by hand (my usual workflow). No luck.0
-
My guess is the changes in UnicodeRange & ulCodePageRange may be responsible for the behaviour.3
-
Jens is probably right. Word is likely deciding it doesn't support Latin when you start typing. Happy to take a look if you want to send it my way. Cheers, Si2
-
Well, wouldn't you know it: ulCodePageRange was wrong in the new files. I wonder if Glyphs introduced that error when I was subsetting there...? Strange. I'll see if I can duplicate it.
Thanks very much, gentlemen. Enjoy your weekends.1 -
Hmm, but font validator checks ulCodePageRange, about bits set and missing glyphs and also bits clear but glyphs present. Did the warnings not happen?1
-
For checking and altering also the consistency checker of OTM can be used.0
-
Hin-Tak Leung said:Hmm, but font validator checks ulCodePageRange, about bits set and missing glyphs and also bits clear but glyphs present. Did the warnings not happen?0
Categories
- All Categories
- 46 Introductions
- 3.8K Typeface Design
- 478 Type Design Critiques
- 558 Type Design Software
- 1.1K Type Design Technique & Theory
- 645 Type Business
- 836 Font Technology
- 29 Punchcutting
- 512 Typography
- 119 Type Education
- 318 Type History
- 75 Type Resources
- 110 Lettering and Calligraphy
- 31 Lettering Critiques
- 79 Lettering Technique & Theory
- 538 Announcements
- 87 Events
- 111 Job Postings
- 168 Type Releases
- 171 Miscellaneous News
- 274 About TypeDrawers
- 53 TypeDrawers Announcements
- 119 Suggestions and Bug Reports