That seems to work. I just renamed the fontname and family (removing the colon), generated a new ttf and loaded that into the system. So this works: \definetypeface[MaraFontNFPlain][rm][Xserif][MaraFontNFPlain] \starttext \startfont[MaraFontNFPlain] This is a test. \stoptext And yes, the url is correct as far as where I got the font from. And yes, there were other errors (or warnings) when I generated the font; however, it does work. One quick question (again expressing my ignorance). Why can't I take the code above and change it to the following: \definetypeface[Mara][rm][Xserif][MaraFontNFPlain] \starttext \startfont[Mara] This is a test. \stoptext Thanks, Bart On Tuesday 18 November 2008 01:13:02 pm Arthur Reutenauer wrote:
Is the colon at the end of the name a problem?
No, the message says the problem is with the space character, but it is of little concern here (XeTeX doesn't use PostScript font names at all).
Is it the font from http://www.perry.com/disney/indy/marafont.html? It seems to have quite a number of other problems actually (xdvipdfmx protests heavily when I try loading it with plain XeTeX). You could try saving it again from FontForge, and installing that modified font (you of course need to uninstall the original one from your system, or more problems will likely happen). While doing so, you can of course modify whatever seems suspicious (like the trailing colon, etc.).
Arthur ___________________________________________________________________________ ________ 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 ___________________________________________________________________________ ________