On Fri, Jul 18, 2008 at 2:55 AM, Jesse Alama <[EMAIL PROTECTED]> wrote: > "Mojca Miklavec" <[EMAIL PROTECTED]> writes: > >> On Thu, Jul 17, 2008 at 9:24 PM, Jesse Alama <[EMAIL PROTECTED]> wrote: >>> Using XeTeX and ConTeXt MkII with the TeX Live 2008 developer snapshot >>> (as of a few days ago), I run into a bunch of "invalid fontname" errors >>> when compiling some documents: >>> >>> $ texmfstart texexec --xtx file.tex >>> TeXExec | processing document 'file.tex' >>> TeXExec | no ctx file found >>> TeXExec | tex processing method: context >>> TeXExec | TeX run 1 >>> TeXExec | writing option file file.top >>> TeXExec | using randomseed 518 >>> TeXExec | tex engine: xetex >>> TeXExec | tex format: cont-en >>> This is XeTeXk, Version 3.1415926-2.2-0.999.2 (Web2C 7.5.7) >>> %&-line parsing enabled. >>> entering extended mode >>> (./file.tex >>> >>> ConTeXt ver: 2008.07.14 18:07 MKII fmt: 2008.7.15 int: english/english >>> [snip] >>> kpathsea: Invalid fontname >>> `texgyrepagella-italic:+liga;+kern;mapping=tlig;+trep;', contains ':' >>> kpathsea: Invalid fontname >>> `texgyrepagella-italic:+liga;+kern;mapping=tlig;+trep;', contains ':' >>> kpathsea: Invalid fontname >>> `texgyrepagella-italic:+liga;+kern;mapping=tlig;+trep;', contains ':' >>> kpathsea: Invalid fontname >>> `texgyrepagella-italic:+liga;+kern;mapping=tlig;+trep;', contains ':' >>> kpathsea: Invalid fontname >>> `texgyrepagella-italic:+liga;+kern;mapping=tlig;+trep;', contains ':' >>> kpathsea: Invalid fontname >>> `texgyrepagella-bolditalic:+liga;+kern;mapping=tlig;+trep;', contains ':' >>> kpathsea: Invalid fontname >>> `texgyrepagella-bolditalic:+liga;+kern;mapping=tlig;+trep;', contains ':' >>> [many more errors like that] >>> >>> Any idea what might be going on? >> >> You probably need to install "tex-gyre" package. It might make sense >> to add the fonts to scheme-context. > > The tex-gyre package is installed. > > Is this just a typo somewhere? Apparently the only problem is the colon > in the font name.
Can you please send a minimal example that fails? XeTeX has multiple ways of finding fonts (by name, by filename for modern fonts, by filename for tfm fonts), and that's probably the fallback (looking for tfm fonts). Colon needs to stay, it's just the wrong "algorithm" that looks for fonts. Mojca ___________________________________________________________________________________ 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 ___________________________________________________________________________________
