Another Windows PostScript font issue - Help!

matt_desmond's picture

I'm having an issue with a family of windows postscript fonts that I've generated from Fontographer on the PC. When you go into ATM, only the regular and bold weights show up in the window.

When dragging and dropping the files onto the fonts folder, it says the .PFB is invalid or damaged for each font, but it still installs and I can use the fonts in any application.

Question: What encoding option should I be choosing when I generate the fonts (Windows 95, Windows 3.1, Adobe Standard?). Would that make a difference?

The fonts are named normally like Bold, BoldItalic, Black, BlackItalic etc. So I don't think it's a naming issue.

Any help is appreciated.

as8's picture

Something similar happened to me.
I got the job to develope three fonts a studio
wants to sell its client after the logo they designed.
I used the _ underscore in the font name,
I changed and it worked.
Best,
AS

matt_desmond's picture

Here is a screenshot of the font preview window. The postscript name is correct, but the name is showing up wrong. Weird. Alessandro, I'll try to rename them...

{/image

Thomas Phinney's picture

It seems like you've built the black weight as a style-linked bold to the regular. Windows can only have four-member font families, with only two weights plus italics in a single family. So for example, you might have the following Windows Family, Style (PostScript FontName) combos:

Variable Light, Regular (Variable-Light)
Variable, Regular (Variable-Regular)
Variable Light, Bold (Variable-Semibold)
Variable, Bold (Variable-Bold)
Variable Black, Regular (Variable-Black)

Also, although this couldn't cause the problem at hand, you ought to have a hyphen between the family name and the style in the PostScript FontName.

Cheers,

T

eomine's picture

Regarding the encoding issue: IIRC, PS T1 fonts are supposed to be generated with the Adobe Standard Encoding in Fontographer.

matt_desmond's picture

Thanks for the insight Thomas.

I ended up having to rename the fonts. For some reason, though I had to name the Obliques "Italic" instead or they wouldn't show up. So here's how I ended up naming them:

Variable-Black -Regular
Variable-Black -Italic
Variable-Bold -Regular
Variable-Bold -Italic
Etc...

twardoch's picture

Matthew,

having two dashes in a PostScript font name is a very bad idea. Please refer to http://groups.msn.com/fontlab/tipsandtricks.msnw?action=get_message&mview=0&ID_Message=2843 for font family naming tips.

Adam

matt_desmond's picture

Argh, what a pain this is.

So I'm renaming them as follows:

VariableBlack -Regular
VariableBlack -Italic

Does that look solid?

Thomas Phinney's picture

No, the family name should precede the dash.

Remember, the PostScript FontName is a completely separate issue from the Windows family name stuff.

Family Name, Style (PostScript FontName)

Variable Black, Regular (Variable-Black)
Variable Black, Italic (Variable-BlackOblique)

I should have pointed you at Adam's font naming thingie. It distills most everything he and I know about this stuff.

Cheers,

T

matt_desmond's picture

Adam's page is great, but it applies to FontLab and not FOG. There's no place to put the FOND name anywhere that I can see. I don't seem to have any control over the PostScript name. This is what I have in my font info dialog box:

/image

Maybe I'm just an idiot, but that setting makes the PostScript name end up as VariableBlack-Regular.

Thomas Phinney's picture

The FOND name is a Mac-specific thing, so don't worry about that.

As for the PostScript name, oh well. I suspect that it's Fontographer and not you. I guess there's nothing to be done about that part, then. It's not critical.

Assuming for a moment that there isn't some hidden option, I'll go on to say that Fontographer never did make very good fonts. When you can afford it, you should move to a current-era font editor. FontLab, DTL FontMaster, maybe even TypeTool.

T

matt_desmond's picture

I know, I'm saving up for FontLab. For now, this seems to work, so I'm going to call it a day.

oksidor's picture

My two cents: I'm using FL4.6 to generate several language versions of a typeface. The base names (AfishaGrotesk) are the same, then I put the language ID, say "C" for Cyrillic or "E" for CE. If I separate such suffix with a space (AfishaGrotesk C), a weird error occurs: under MacOS X, Fontbook shows font sample with rearranged alphabet. If I eliminate the space in the name, everything is fine: the sample shows alphabet in the correct order. Seems like a definite bug either in FL, or in MacOS 10.3.4/Fontbook

twardoch's picture

Oleg,

can you please submit a problem report on http://www.fontlab.com/html/support.html? Please include some screenshots showing what you mean by "rearranged alphabet" and "correct order". If possible, please also include the VFB files and the generated fonts for both the incorrect and the correct cases. Please put everything into one ZIP file and attach when submitting the problem. Thank you,
Adam Twardoch
Fontlab Ltd.

pablohoney77's picture

I'm saving up for FontLab

didja know that if you have a registered copy of Fontographer you can save quite a bit on FontLab? I think it's something to the tune of $150! Very nice of those guys at FL, I'll say.

Si_Daniels's picture

Matt, if the upgrade path doesn't work out get in touch with Yuri at FontLab anyhow. I'm sure he'd be willing to provide some other options to help make your move over to FontLab sooner rather than later.

Si

Syndicate content Syndicate content