I've renamed plenty of my fonts to reflect foundries/designers before, so that I can have (for example) different Helveticas on my system at the same time, and so that "Adobe Garamond" is under "Garamond" where it belongs, not alphabetized with the "A"s. I also converted some of my old postscript fonts to Opentype with Fontlab and named them so that I would know they were my conversions, should enhanced OT versions become available in the future from the vendor. I also have an aesthetic disagreement with vendors putting a trademark symbol in the font name.

But Fontlab/Fontographer are certainly overkill for that task alone -- I'm curious what suggestions people have, as well.

Not with mine:

"You may also modify the Font for your own personal or internal business use, but you may not distribute, or transfer your adaptations..."

Try TTF_edit - a freeware TrueType editing tool.

http://www.truetex.com/ttf_edit.htm

Allan Murray

Converting a font also voids and support or assistance you might receive from a foundry in the event of a problem. As someone who troubleshoots font issues regularly, I would have to say that "converted" fonts often cause a disproportionate amount of problems. Font naming is just one issue. As mentioned in other threads, FontLab's "green gem" auto-naming icon is not sufficient to ensure fonts will work in all applications or across operating systems. A converted font is just like a piece of software that has not been tested. It might work, but the probability of failure is higher. That's why, for example, you can have confidence in Adobe's fonts--the same files I'm using have been tested by hundreds of thousands of users. In the case of small vendors like Mr. Shinn, there may be relatively fewer customers. However the foundry takes personal responsibility for making the product function correctly.

A lot of fonts that people think are "corrupt" or "damaged" didn't damage themselves...

Thanx for all your comments. I really appreciate all the feedback.