On Sunday, Aug 8, 2004, at 10:09 America/Vancouver, Andrew Stiller wrote:

But it looks like the other solutions mentioned (TypeTool, Font Doctor, etc.) might be better for your purposes. TTConvertor is only good for TrueType fonts. I think it would give an error if there was an encoding problem though (which is what I think you are running into).

The problem is that I don't *know* whether, or in what fonts, I have an encoding problem unless my eye happens to fall on a misprint--this in scores which I am offering for sale to the public, some of wh. have been in print for years.

What I'd like to do is "simply" go through *all* my fonts and make sure they're OK. It sounds to me as if all the solutions suggested have the same problem as Fontographer, wh. I already have: they would require me to open each font individually and go through multiple steps to identify and correct any encoding problem. Doing this for hundreds of fonts would take me weeks!

Indeed. That's why scripting was invented and probably why the Adobe geek tools could be of some use. I would first check into the AppleScript dictionaries of the font utility applications you will be working with though before diving into shell scripting.


If you are going to have to eyeball them anyway, the "Text Editor" plugin for Finale 2K2/2K3 has some font listing menu items. It can itemize the characters with the slot number (both hex and decimal) and save them to a file on disk. Since you have so many fonts, I'd limit the output file size to 32K unless you have an OS 9 editor which can handle larger than 32K Simple Text format files (there are free ones like Tex-Edit). If you open up those listings on OS 9 then they should give you the expected characters in the expected slot and you can probably print them to PDF on OS 9. Those listings can serve as a reference.

For OS X, there is an AppleScript example for the TextEdit application which show how to create a "Font Sample" for several fonts in one shot. I'm sure it can be adapted for the listing purposes such that it would coordinate with the OS 9 listings and allow comparison. If the AppleScript errors during execution for a particular font, I'd expect it to be one of the ones that will need adjusting. Don't know about anyone else, but if I had to compare the character slots for 100 fonts, I think I'd prefer a printout.

For the actual adjusting, I'd see if I could utilize AppleScript to batch process the changes in the fonts.


Philip Aker http://www.aker.ca

_______________________________________________
Finale mailing list
[EMAIL PROTECTED]
http://lists.shsu.edu/mailman/listinfo/finale

Reply via email to