Page 1 of 1

Fonts installed using MainType don't show as resources in MainType

Posted: Thu Nov 10, 2016 3:01 pm
by nabsltd
If you install a font using MainType, it only shows the resource from the original location on disk, not the font file in the Windows font folder. But, if you install the exact same font file using Control Panel, you see both resources.

This is misleading, because when you install fonts using MainType, it still copies them to the Windows font folder (usually C:\Windows\Fonts), and doesn't just link them to the original files (which is a perfectly valid way to install fonts on WIndows 7 and beyond). Copying the files to the Windows directory is absolutely the best and most reliable way to install fonts, but does result in another copy of the fonts being created, and this should be reflected in the MainType "Resources" display. It's also misleading in that MainType names the font file copied to the Windows directory with the "Font Name" (which might be the PostScript font name), so it often no longer matches what is on disk in the original location.

Also, for people with small system disks but larger data disks where they keep all their font files, they might like the option of just linking to the font files where they reside on disk. This is how most other font managers work, because it keeps from having to copy lots of files when you change font groups for different projects.

Re: Fonts installed using MainType don't show as resources in MainType

Posted: Thu Nov 10, 2016 3:53 pm
by Erwin Denissen
We did change the way MainType installs fonts. Several users reported issues with installing fonts from a network or shared folder. I think this change is the cause of this bug.

We've added this to the bug list.