Hey all, but especially Win, Mac and Adobe gurus:
How do operating systems and apps respond differently to an OTF or TTF font which declares Unicode ranges but no codepages at all are supported?
If you have minimal glyph set or weird glyph set, is it better for the font to not claim any codepages supported? Or to claim codepage 2525 (WinANSI) ?
Since I've not heard otherwise, I believe it is also still a procurement requirement from Microsoft for any fonts they license or purchase to have coverage for at least one Windows 8-bit codepage, usually CP1252 (not, as you typed, 2525).
2525? Not sure how I made that typo on my number pad. Weird.
Are you sure you didn't have Zager and Evans playing in the background?