FWIU no matter what UPM you use in the design space, once you make a Type1 font it is converted to a 1000 UPM so by working at 5000, you will introduce rounding errors.

If the logo is that detailed that 1000 UPM wokspace make it distorted, it may be best to keep in in an importable eps format.

Or make a TrueType version of the logo, working at 2048 and with FontLab you can hint the Bejeezes out of it to control its small size rendering.

James

Huh. That's an unfortunate limitation. The Type 1 format itself supports arbitrary UPM values (though 1000 is what people almost universally use).

T

So maybe I'm wrong. I've just always found that font deitors export Type1 at 1000 upm. Is there a work around.

I have a logo font here, that I created a while back when I was on Mac OS 9.2 or 8.5. Never had troubles with it until I moved to OS X. I was using it principaly for my invoices in FileMaker. I would then output the FileMaker invoice to a PDF file, where my Logo Font was embedded. This, gave a more interesting finish than importing an eps in FileMaker. It was a question of antialiasing. I did many tests and never succeeded to import a vector graphic in FileMaker that would output as vectors. It seems it always convert the file to a pict.

Since I moved to OS X, that font is not working anymore and I don't understand why. Wish someone could explain me why.

To make a test, I just opened in FontLab 4.6 this working Type 1 LogoFont (the PS file) I created a while back, and in the Info, the UPM shows to be 5882.

I have the feeling that something has changed in OS X and I don't know what and why...?

What I liked, and that was sort of usefull, is the negative kerning, where the combination of different keys was giving me the possibility to use a mask underneath the logo, and to color differently each parts, depending on the visual application.

If anyone interested... give me a ring and I'll send you the LogoFont to check.

I feel I have been struggling with this issue since too long now. I discovered this forum yesterday and said to myself: "If no one has the answer here... you will never have any".

This forum seems to be the good place to ask for help.

Kind Regards,

Yves

Actually, this was reported as a bug to the FontLab folks a while back. I just tested it in FontLab 4.6.1 and it seems to work fine!

I took Myriad Pro Italic, set the em square to 2200, didn't scale the glyphs, and exported as a (renamed) Type 1. The resulting font behaves as I would expect.

Cheers,

T

Hello Thomas,

Are you on Mac OS X ?
You tested it on Mac OS X ?

Yves

I don't think this is realted to OS X, but to the tool itself....

T

Here I post a Type 1 -- LogoFont -- UPM 5882 -- I created for a customer to ease the visual identity usage for PDF files.

Download for testing:

Atlante-LogoFont-ForTestsOnly Atlante_Mac.zip (104.0 k)

I created it in 2001 with FontLab 3.1.
Never had trouble using it, before the move to OS X and Suitcase 10.

I used to be able to use it in FreeHand but now in FreeHand MX... no way. Samething in FileMaker. Can't use it. It shows up as bitmap, and when trying to convert it to paths in FreeHand, it seems it can't find the PS file even if it is located in the same folder as the suitcase file.

Questions, Questions, Questions...

There seems to be some Gremlins under the OS X hood.

Regards,

Yves

Nope, I'm not on OS X myself. Sorry for missing this point earlier. So two questions:

- does the tool support making such fonts?
- do they work in OS X?

If they don't work in OS X, that would be an OS X bug. It would not be the first significant OS X problem that causes perfectly good fonts to not work.

T

You may try re-generating your font in FontLab 4.6 or 4.6.1 (as it is released).
Adam

Years ago, when I first tried making Type 1 fonts with arbitrary UPM values, I did find that some PS emulations in printers gagged on anything other than 1000. Not sure whether this would be a live issue.