It was a corporate font they were required to use for their government contract work and had to get it fixed. Sent it back to them and they were extremely happy. I rearranged the entire thing to put glyphs where they were supposed to be, assigned Unicode values to them and saved it as an OpenType PostScript font. Looking at it in FontLab (as above) I couldn't believe the font ever worked. It would display correctly, but print alphabet soup. One was so bad, a person sent me the font to look at because it no longer worked for them. Many of the extended glyphs shown here line up well with the OpenType version, but I've seen some horribly jumbled fonts. Basically, there were no rules or conformity of any kind for extended glyphs. But in an older font like the T1 PS version, they can be wherever the vendor making the font felt like putting it. Those have predefined Unicode positions and will always be in the same ordinal position. 1/2, 1/4 and others are before that in the T1 PS version. The most obvious difference is there are no glyphs before the space character in the OpenType version. Type 1 PostScript first, OpenType second. The problem with old fonts and up-to-date Unicode aware apps is the position of less commonly used glyphs. No real issue there since all fonts should have these glyphs in the same spots whether then have an assigned Unicode value or not. It then runs through all upper case letters, followed by a few more standard glyphs and then all lower case. After that the most standard punctuation marks and numbers. If you're counting glyph cells starting at zero, the space character is at ordinal position 32. The biggest being placement of the non-Latin characters. The fonts likely (but not necessarily) already have family names so the typefaces would group together, but the further we get away from the old styles of fonts into Unicode, the more of these odd issues seem to be appearing. It also gives the option of converting to off and can group them in families so FEX gives you a more concise selection in the Adobe CC apps.Ĭan't quite guess how "converting to off" was supposed to read. There a couple of other translators that also do good job. When you convert a T1 PS font to OpenType, it has to do that from the outline printer fonts (where the actual vector outline glyphs are). You can't do anything with only the suitcase of bitmap screen fonts. Type 1 PostScript suitcase: Useless without the printer outlines. Or, if you want, convert them to OpenType. TrueType suitcase: There's nothing necessary to extract. Whether the suitcase has an extension or not, here's what you have:
#TRANSTYPE FONT HINTING MAC#
But by then of course, there were hundreds, or more likely thousands of Mac TrueType fonts out there with a.
#TRANSTYPE FONT HINTING UPGRADE#
Macromedia stopped doing that with the next major upgrade of Fontographer. suit extension normally meant it was the suitcase for a Type 1 PostScript font, and now you had to look for the missing outline printer fonts. It didn't hurt anything to do so since the extension meant nothing anyway, but it confused the heck out of users since a. One version of Fontographer was responsible for creating Mac legacy TrueType suitcase fonts with a. Truetype fonts WERE commonly sold by vendors as families packaged in suitcases with the. Several threads on this and font management suffer contributors apparently from not having lived in the classic environment, I suppose.
I'm think the best solution is to convert the old files into. suitĪs mentioned elsewhere, I've seen these font files file-typed with random suffixes (often the font vendors abbreviation) and still work fine. True-type fonts in suitcase with the type/creator of TFIL / DMOV. Type-1 screen fonts in suitcases with the type/creator of FFIL / DMOV. Surprisingly little to find about management of old type-1 fonts (.bmap suitcases & needed laserwriter postscript files) and the truetype fonts (some in.
#TRANSTYPE FONT HINTING PRO#
Are there really NO programs that can extract screen fonts from suitcase files in a modern High Sierra environment? I have random screen fonts with no printer files and vice versa, and it makes for a messy FontExplorer X Pro experience.