mkii and xetex with tl2008: invalid fontname errors

Jesse Alama

17 Jul 2008 17 Jul '08

1:24 p.m.

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? Thanks, Jesse -- Jesse Alama (alama@stanford.edu)

Show replies by date

Mojca Miklavec

17 Jul 17 Jul

2 p.m.

New subject: mkii and xetex with tl2008: invalid fontname errors

On Thu, Jul 17, 2008 at 9:24 PM, Jesse Alama 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. Mojca

Jesse Alama

6:55 p.m.

New subject: mkii and xetex with tl2008: invalid fontname errors

"Mojca Miklavec" writes:

...

On Thu, Jul 17, 2008 at 9:24 PM, Jesse Alama 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. Thanks, Jesse -- Jesse Alama (alama@stanford.edu)

Mojca Miklavec

18 Jul 18 Jul

1:57 a.m.

New subject: mkii and xetex with tl2008: invalid fontname errors

On Fri, Jul 18, 2008 at 2:55 AM, Jesse Alama wrote:

...

"Mojca Miklavec" writes:

...
On Thu, Jul 17, 2008 at 9:24 PM, Jesse Alama 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

Jesse Alama

9:05 p.m.

New subject: mkii and xetex with tl2008: invalid fontname errors

"Mojca Miklavec" writes:

...

On Fri, Jul 18, 2008 at 2:55 AM, Jesse Alama wrote:

...
"Mojca Miklavec" writes:

...
On Thu, Jul 17, 2008 at 9:24 PM, Jesse Alama 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?

\definetypeface [busted] [rm] [serif] [palatino] [default] \setupbodyfont [busted] \starttext \input tufte \stoptext

...

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.

Hmm, perhaps the tex-gyre fonts are incorrectly installed? Jesse -- Jesse Alama (alama@stanford.edu)

Mojca Miklavec

21 Jul 21 Jul

5:26 a.m.

New subject: mkii and xetex with tl2008: invalid fontname errors

On Sat, Jul 19, 2008 at 5:05 AM, Jesse Alama wrote:

...

"Mojca Miklavec" writes:

...
On Fri, Jul 18, 2008 at 2:55 AM, Jesse Alama wrote:

...
"Mojca Miklavec" writes:

...
On Thu, Jul 17, 2008 at 9:24 PM, Jesse Alama 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]

...

...
Can you please send a minimal example that fails?

\definetypeface [busted] [rm] [serif] [palatino] [default] \setupbodyfont [busted] \starttext \input tufte \stoptext

Hmm, perhaps the tex-gyre fonts are incorrectly installed?

Do you have the file texgyrepagella-italic.otf? What does kpsewhich texgyrepagella-italic.otf return you? Or put in other words - do you have fonts/opentype/public/tex-gyre/texgyrepagella-italic.otf? You can also try to reinstall or update packages. I'm not sure how well packaging works, but texgyre has now been added to scheme-context. Mojca

Jesse Alama

30 Jul 30 Jul

7:25 p.m.

New subject: mkii and xetex with tl2008: invalid fontname errors

"Mojca Miklavec" writes:

...

On Sat, Jul 19, 2008 at 5:05 AM, Jesse Alama wrote:

...
"Mojca Miklavec" writes:

...
On Fri, Jul 18, 2008 at 2:55 AM, Jesse Alama wrote:

...
"Mojca Miklavec" writes:

...
On Thu, Jul 17, 2008 at 9:24 PM, Jesse Alama 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]

...
...
Can you please send a minimal example that fails?

\definetypeface [busted] [rm] [serif] [palatino] [default] \setupbodyfont [busted] \starttext \input tufte \stoptext

Hmm, perhaps the tex-gyre fonts are incorrectly installed?

Do you have the file texgyrepagella-italic.otf? What does kpsewhich texgyrepagella-italic.otf return you? Or put in other words - do you have fonts/opentype/public/tex-gyre/texgyrepagella-italic.otf?

$ kpsewhich texgyrepagella-italic.otf /usr/local/texlive/2008/texmf-dist/fonts/opentype/public/tex-gyre/texgyrepagella-italic.otf

...

You can also try to reinstall or update packages. I'm not sure how well packaging works, but texgyre has now been added to scheme-context.

The package seems to be installed just fine, so I'm stumped. Thanks, Jesse -- Jesse Alama (alama@stanford.edu)

Mojca Miklavec

31 Jul 31 Jul

4:23 a.m.

New subject: mkii and xetex with tl2008: invalid fontname errors

On Thu, Jul 17, 2008 at 9:24 PM, Jesse Alama wrote:

...

\definetypeface [busted] [rm] [serif] [palatino] [default] \setupbodyfont [busted] \starttext \input tufte \stoptext

...

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?

Does it only complain or does it fail to work? I suspect what the error could be (harmless, though it makes sense to fix it), but I only think that error reporting got more verbose since it works here despite many warnings. Outside of TL (probably some branch of xetex trunk + latest context) I don't get that warning. Maybe Jonathan knows more. The enteresting thing is that those messages don't even show up in log file. But log does show that some files like sort-lan.mkii (and some others) are a bit problematic in respect to (not being) UTF-8. % \enableregime[utf] % \mainlanguage[sl] % \starttext % \ccaron\index{\ccaron\space 1} % \Ccaron\index{\Ccaron\space 1} % Ä<8d>\index{Ä<8d> 2} % Ä<8c>\index{Ä<8c> 2} % \v c\index{\v c 3} % \v C\index{\v C 3} % \placeindex % \stoptext That should be % č\index{č 2} % Č\index{Č 2} Mojca

Taco Hoekwater

4:44 a.m.

New subject: mkii and xetex with tl2008: invalid fontname errors

Mojca Miklavec wrote:

...

I suspect what the error could be (harmless, though it makes sense to fix it), but I only think that error reporting got more verbose since it works here despite many warnings. Outside of TL (probably some branch of xetex trunk + latest context) I don't get that warning.

Looks like a change in kpathsea itself could be the 'cause. The searches for these tfms are supposed to fail, so I guess there is no actual problem, just more verbose complaining from kpathsea. Best wishes, Taco

Jesse Alama

1 Aug 1 Aug

8:48 p.m.

New subject: mkii and xetex with tl2008: invalid fontname errors

"Mojca Miklavec" writes:

...

On Thu, Jul 17, 2008 at 9:24 PM, Jesse Alama wrote:

...
\definetypeface [busted] [rm] [serif] [palatino] [default] \setupbodyfont [busted] \starttext \input tufte \stoptext

...
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?

Does it only complain or does it fail to work?

As far as I can tell this is only a complaint, in the sense that the XeTeX run finishes and produces a PDF. Is that what you mean? I'm not sure whether those invalid fontnames errors are having an effect.

...

I suspect what the error could be (harmless, though it makes sense to fix it), but I only think that error reporting got more verbose since it works here despite many warnings. Outside of TL (probably some branch of xetex trunk + latest context) I don't get that warning.

Thanks, Jesse -- Jesse Alama (alama@stanford.edu)

Mojca Miklavec

2 Aug 2 Aug

3:41 a.m.

New subject: mkii and xetex with tl2008: invalid fontname errors

On Sat, Aug 2, 2008 at 4:48 AM, Jesse Alama wrote:

...

"Mojca Miklavec" writes:

As far as I can tell this is only a complaint, in the sense that the XeTeX run finishes and produces a PDF. Is that what you mean?

Yes. Though this should be fixed now anyway. Mojca

5827

Age (days ago)

5843

Last active (days ago)

List overview

Download

10 comments

3 participants

participants (3)

Jesse Alama
Mojca Miklavec
Taco Hoekwater

mkii and xetex with tl2008: invalid fontname errors

tags

participants (3)