Just a quick reply:

having the afm is already very good. The file without an extension looks suspiciously like a Mac font resource. Can you try running the utility "fondu" on it (from the command line)? That will usually produce the pfbs (very likely, there's more than one: roman, italics, bold ...). Texfont, btw, can equally well work with truetype fonts, so if you have a proper tryetype font with extension .ttf. you might as well use this. texfont will produce a map entry that you will have to modify a bit (so it points to a .ttf instead of the default .pfb), but that's not too difficult. As to names: don't bother, ConTeXt is happy with whatever name you throw at it.



On Feb 21, 2005, at 1:58 AM, David Wooten wrote:

Greetings all,

I've been having a lot of fun struggling with the installation of a newly purchased font, and wanted to double check a preliminary question before I give in and ask a more thorough question ;)

I'm working with Mac OS X, so I bought a font-set with both Mac TTF and Postscript files. The Postscript folders have 2 types of file for each fontname: .afm and another without a suffix. The names also have uppercase letters, such as AndulBooBol (a.k.a. Andulka Book Bold).

For the texfont script, it apparently needs the .afm files and .pfb files. Thus:

1) Are these non-suffixed files the .pfb files in question? If so, should I rename (add .pfb to) them before trying to install them? (I could convert the TTF files to .pfb?)

2) Should I take away the UpperCaseLettering as well? Rename them to something more Berry-like?

In fact, I've tried these things with no success, but before I spell out the details of my failure I thought I would get this straight.

Kind regards,
David Wooten

ntg-context mailing list

_______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context

Reply via email to