Quote:
Originally Posted by Doitsu
1. Generate MD5 checksum of the font(s) and ask the font designer and the font reseller to send you the checksums for the font files.
[...]
3. Open the font files with FontForge and resave them. (If FontForge can't open the fonts they're definitely corrupted.)
|
I second this... could be when the site packaged the collection, they accidentally stored a corrupt file.
Quote:
Originally Posted by Hitch
I can't "select" the font in Windows File Explorer. I mean, simply, left-clicking it in the Dir. I can't even run Font Doctor on it. Nada, zip, zein zilch. When I try to click the face, to preview it--it FREEZES Windows File Explorer, and then crashes it.
[...]
And that's not opening it--it's just trying to SELECT it. (n.b.: I do have the file preview window open, in File Explorer. Again, however, thousands of other font files have never had an issue with that.).
|
I am also thinking it could potentially be at the Windows level instead.
1. Is it even crashing if you use a different View (Details, List, Large Icon, [...])?
Maybe Windows is trying to generate a thumbnail and that is causing the issue. (I know sometimes this occurs when you have a corrupt/not properly built video file for instance).
Side Note: I have run across this problem with Windows Explorer not liking some video files... but the way Windows generates thumbnails for Fonts is probably a different beast.
2. What about the good ol' commandline?
What happens if you cd to the directory and dir to get a list of files? Maybe there are funky non-visible characters in the filename?
I know that Windows explodes if there is a reserved character in there (like a colon).
Maybe you would be able to install it via commandline (although if the font itself is corrupt, I probably wouldn't want to do that... if Windows Explorer explodes just CLICKING on it, who knows what that would do if it was sitting in your Font folder.
)
3. Do you have access to a Linux machine (or a Live USB)? If you could install the font there and use it, then you know it might not be the font file itself.