Re: [NTG-context] mkii and xetex with tl2008: invalid fontname errors
On Sat, Aug 2, 2008 at 4:48 AM, Jesse Alama [EMAIL PROTECTED] 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 ___ 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 ___
Re: [NTG-context] mkii and xetex with tl2008: invalid fontname errors
Mojca Miklavec [EMAIL PROTECTED] 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 ([EMAIL PROTECTED]) ___ 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 ___
Re: [NTG-context] 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
___
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
___
Re: [NTG-context] 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 ___ 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 ___
Re: [NTG-context] mkii and xetex with tl2008: invalid fontname errors
Taco: ... does it actually work, and can you explain why? I don't get the error any more with that fix (and it's not an error anyway). The problem is that if there is no file: prefix in font synonyms, then ConTeXt asks for \font\whatever=texgyre-whatever:options and XeTeX first asks fontconfig, font not there, and then asks kpathsea and kpathsea complains about font not present. With minimals I don't get that complaint printed out. It used to complain in some other way some time ago, but let's forget that for a moment. Then, since ConTeXt figures out that font doesn't exist, it asks for \font\whatever=[texgyge-whatever]:options and then XeTeX finds the font and ConTeXt uses it. There's a third iteration asking for a font without quotes, but I should check the exact order of those three attempts, and maybe attempt without quotes is not needed any more since Jonathan fixed the behaviour of quoted filenames to also look for kpathsea fonts, not only system fonts if I recall correctly. If there is file: prefix, the first iteration is skipped, so it's more efficient to load fonts. We have fixed that (added file: in front of names) in number of font definitions some time ago (most important being LM since it's really used each time when one compiles a XeTeX document), but those palatino/times synonyms were not fixed at the time of major changes for some reason (overseen, me being lazy, it worked anyway?, ... I don't quite remember). However, there is still problem with +trep (a missing/unneeded mapping, depends on how you treat it) in this font call: texgyrepagella-italic:+liga;+kern;mapping=tlig;+trep; trep and tlig both happened to map to tex-text some time ago. Then I asked Hans to optimize the behaviour a bit since some mappings of and ` were really cruel and lead to inability to use grave accents at all. He removed some mappings, but left both tlig and trep there. In luatex, tlig does a mapping of -- and --- and trep does a mapping of apostrophe. In XeTeX +tlig option in features=default gets replaced by mapping=tlig which has all the three replacements (--, --- and ') font-ini.tex:\remapfontfeature tlig yes mapping=tlig while +trep is passed unmodified to xetex. So the behaviour is inconsistent in LuaTeX and XeTeX (no reason why it should be), but it just happens that nobody cares/complains. The second option would be useful if one really wanted to recall all the other TeX ligatures and replacements back (`, ``, , , , `, ` or whatever else is there), else I think that having two options is really not needed. tlig and trep used to have all the other old TeX replacements ligatures there, but I asked Hans to remove most of them exactly for the reason mentioned above (grave accents were gone). XeTeX just happens not to complain about +trep, but that +trep should be removed one day. Maybe just font-ini.tex:\remapfontfeature trep yes [empty] 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 ___
Re: [NTG-context] mkii and xetex with tl2008: invalid fontname errors
Mojca Miklavec [EMAIL PROTECTED] writes: On Sat, Jul 19, 2008 at 5:05 AM, Jesse Alama [EMAIL PROTECTED] wrote: Mojca Miklavec [EMAIL PROTECTED] writes: 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] 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 ([EMAIL PROTECTED]) ___ 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 ___
Re: [NTG-context] mkii and xetex with tl2008: invalid fontname errors
On Sat, Jul 19, 2008 at 5:05 AM, Jesse Alama [EMAIL PROTECTED] wrote: Mojca Miklavec [EMAIL PROTECTED] writes: 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] 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 ___ 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 ___
Re: [NTG-context] mkii and xetex with tl2008: invalid fontname errors
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 ___
Re: [NTG-context] mkii and xetex with tl2008: invalid fontname errors
Mojca Miklavec [EMAIL PROTECTED] writes: 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? \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 ([EMAIL PROTECTED]) ___ 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 ___
[NTG-context] mkii and xetex with tl2008: invalid fontname errors
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 ([EMAIL PROTECTED]) ___ 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 ___
Re: [NTG-context] mkii and xetex with tl2008: invalid fontname errors
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. 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 ___
Re: [NTG-context] mkii and xetex with tl2008: invalid fontname errors
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. Thanks, Jesse -- Jesse Alama ([EMAIL PROTECTED]) ___ 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 ___
