That's right; use fondu. Fontforge can read a .dfont (data fork resource) but it cannot specify something within that to load without user input. The only files that use .dfont are from Apple for Apple. The Mac knows what is basically coded into these files and works with them accordingly. That presents the design decision of whether to support an alien font scheme that only exists in Steve Jobs' universe, not in the rest of the 95% of computers out there. Then there is the whole issue of encoding because especially the Apple .dfont files tend to have a number of named glyphs that Fontforge thinks are misplaced. Fontforge also will not open a font in a ~/.fonts dir, at least on Ubuntu Hardy. It does not appear to handle special cases of pathnames very well. You can, however, use Fontforge and fondu to get at the fonts in the resource fork; fondu looks like it is better for the task Charles On Tue, 2008-07-15 at 21:19 +0200, Thomas A. Schmitz wrote:
On Jul 15, 2008, at 6:27 PM, Mojca Miklavec wrote:
I'm not sure, but ".dfont" looks like AAT format and no extension like Mac-specific way of storing Type 1. Both doable, but someone needs to do that.
You can run "fondu" on .dfont files and then use the resulting files (ttf or pfb, I guess) for use with whatever flavor of TeX you want.
Thomas ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________