Type Managers.
Straight_Man
Geeky, in my own wayNaples, FL Icrontian
There are two major families of vector type that come with Office Suites and specialty graphics apps-- for Windows per se.
WordPerfect Office in modern versions, like 10 and 11, comes with Bitstream fonts and manager, and also the CorelDraw family comes this way. ATM (Adobe's Type Manager) is very good at what it does, but XP's type manager can handle TrueType fonts also. I use almost totally Bitstream fonts, except for what the XP system font handlers want to prefer, which is Adobe fonting licensed from Adobe back when, then customized into specific custom built fonts over time.
Funny thing is, the latest Bitsteam type manager-- releases within last 18 months-- can also handle Adobe TrueType fonts robustly, and does not often hang when it encounters a bad TT1 or Bitstream vector font-- instead it bad-marks it and will not load it for view of font sampling but can delete it. It does not get along with ATM, though, ATM protects it TT font associations. A lot of folks run into issues with ATM when Btistream fonting managers and ATM are present, MIME associations get fubarred by being either accientally or automatically associated when you run the manager concerned. So, run one or the other on any one O\S instance with especially Windows up through XP and back to 98-- not both on same box unless you are willing to restrict Bitstream's font manager to only Bitstream fonts-- it can be so set up at install time and in registry.
I started this thread this way, simply to be able to answer questions about the font handling in Windows and apps for Windows, and the tools for handling same. Figured would start with the cause of major conflicts between the two most major 3rd party type managers
John D.
WordPerfect Office in modern versions, like 10 and 11, comes with Bitstream fonts and manager, and also the CorelDraw family comes this way. ATM (Adobe's Type Manager) is very good at what it does, but XP's type manager can handle TrueType fonts also. I use almost totally Bitstream fonts, except for what the XP system font handlers want to prefer, which is Adobe fonting licensed from Adobe back when, then customized into specific custom built fonts over time.
Funny thing is, the latest Bitsteam type manager-- releases within last 18 months-- can also handle Adobe TrueType fonts robustly, and does not often hang when it encounters a bad TT1 or Bitstream vector font-- instead it bad-marks it and will not load it for view of font sampling but can delete it. It does not get along with ATM, though, ATM protects it TT font associations. A lot of folks run into issues with ATM when Btistream fonting managers and ATM are present, MIME associations get fubarred by being either accientally or automatically associated when you run the manager concerned. So, run one or the other on any one O\S instance with especially Windows up through XP and back to 98-- not both on same box unless you are willing to restrict Bitstream's font manager to only Bitstream fonts-- it can be so set up at install time and in registry.
I started this thread this way, simply to be able to answer questions about the font handling in Windows and apps for Windows, and the tools for handling same. Figured would start with the cause of major conflicts between the two most major 3rd party type managers
John D.
0