How difficult would it be to adapt the typescript for Gentium (at http://wiki.contextgarden.net/TypeScripts) to use the new Gentium Basic for headings & Gentium Book Basic for text weights (both have Roman, Bold Roman, Italic, & Bold Italic) -- but with reverting to Gentium for characters that aren't in the Basic fonts? --Joel
Guess I asked for too much at once. I've downloaded the Gentium Basic/Basic Book set of fonts from http://scripts.sil.org/Gentium_basic, and I'd like to use them with ConTeXt. I ran texfont (with the command line texfont --fontroot=c:\users\chesky\programs\context\tex\texmf-local --sourcepath=... --vendor=sil --collection=gentium --makepath --install), and now running texexec on the newly generated texnansi-sil-gentium.tex produces some sort of glyph list. Now I'm trying to adapt the typescript from http://wiki.contextgarden.net/TypeScripts for the new set of fonts. (I intend to use only utf-8 input files, if that matters any.) I'd like to use Gentium Basic as the titling font and Gentium Book Basic as the text font, with regular, italic, bold, & bold-italic all available in the normal fashion. But I find I don't know what I'm doing. Has anyone yet tried to use the new fonts with ConTeXt? --Joel
Joel C. Salomon wrote:
Guess I asked for too much at once.
I've downloaded the Gentium Basic/Basic Book set of fonts from http://scripts.sil.org/Gentium_basic, and I'd like to use them with ConTeXt. I ran texfont (with the command line texfont --fontroot=c:\users\chesky\programs\context\tex\texmf-local --sourcepath=... --vendor=sil --collection=gentium --makepath --install), and now running texexec on the newly generated texnansi-sil-gentium.tex produces some sort of glyph list.
Now I'm trying to adapt the typescript from http://wiki.contextgarden.net/TypeScripts for the new set of fonts. (I intend to use only utf-8 input files, if that matters any.) I'd like to use Gentium Basic as the titling font and Gentium Book Basic as the text font, with regular, italic, bold, & bold-italic all available in the normal fashion. But I find I don't know what I'm doing.
Has anyone yet tried to use the new fonts with ConTeXt?
these are open type fonts ... use luatex or xetex ... Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 11/19/07, Joel C. Salomon wrote:
Guess I asked for too much at once.
I've downloaded the Gentium Basic/Basic Book set of fonts from http://scripts.sil.org/Gentium_basic, and I'd like to use them with ConTeXt. I ran texfont (with the command line texfont --fontroot=c:\users\chesky\programs\context\tex\texmf-local --sourcepath=... --vendor=sil --collection=gentium --makepath --install), and now running texexec on the newly generated texnansi-sil-gentium.tex produces some sort of glyph list.
Rather than using texfont (half-broken anyway), use XeTeX or LuaTeX. (If you're using MikTeX and are willing to upgrade to MikTeX 2.7, you can process your documents with "texexec --xtx filename"; if you're using the standalone ConTeXt, you can process it with "--xtx" or "--lua".) Depending on whether you want to install those fonts or keep them in the tree there are slightly different approaches, but this should work for both LuTeX and XeTeX if you keep your files in the working directory or in texmf/fonts/opentype/...[somewhere here]... \starttypescript[serif][gentium-basic] \definefontsynonym[GentiumBasic] [file:GenBasR] [features=default] \definefontsynonym[GentiumBasicItalic] [file:GenBasI] [features=default] \definefontsynonym[GentiumBasicBold] [file:GenBasB] [features=default] \definefontsynonym[GentiumBasicBoldItalic][file:GenBasBI][features=default] \stoptypescript \starttypescript[serif][gentium-basic][name] \definefontsynonym[Serif] [GentiumBasic] \definefontsynonym[SerifItalic] [GentiumBasicItalic] \definefontsynonym[SerifBold] [GentiumBasicBold] \definefontsynonym[SerifBoldItalic][GentiumBasicBoldItalic] \stoptypescript \definetypeface[mygentium][rm][serif][gentium-basic][default] \setupbodyfont[mygentium,13pt] I don't know how you plan to mix those fonts, but "reverting to another typeface in case a glyph is missing" is a bad idea in this particular case, at least in my opinion (although it's conditionally doable) - how are you going to handle missing characters in bold typeface? One possibility would be to use: - Gentium for Roman & Italic - Gentium Basic for Bold & Bold Italic (and hope that you won't need any special characters for titles) Mojca
Hi Mojca, I tried your example below and struggled in path error: %\starttypescript[serif][gentium-basic] %\definefontsynonym[GentiumBasic] [file:GenBasR] [features=default] %\definefontsynonym[GentiumBasicItalic] [file:GenBasI] [features=default] %\definefontsynonym[GentiumBasicBold] [file:GenBasB] [features=default] %\definefontsynonym[GentiumBasicBoldItalic][file:GenBasBI] [features=default] %\stoptypescript %\starttypescript[serif][gentium-basic][name] %\definefontsynonym[Serif] [GentiumBasic] %\definefontsynonym[SerifItalic] [GentiumBasicItalic] %\definefontsynonym[SerifBold] [GentiumBasicBold] %\definefontsynonym[SerifBoldItalic][GentiumBasicBoldItalic] %\stoptypescript %\definetypeface[mygentium][rm][serif][gentium-basic][default] %\setupbodyfont[mygentium,36pt] \font\rom="Gentium Basic" at 36pt \starttext Test WQG 0196 \rom Test WQG 0196 \stoptext Doing it like this works OK. But uncommenting the lines above ends up in ... kpathsea: Running mktexmf GenBasR ! I can't find file `GenBasR'. But isn't it the same font/file adressed in both cases? (sorry, I am an absolute beginner in xetex) Yours, Steffen Am 20.11.2007 um 01:57 schrieb Mojca Miklavec:
On 11/19/07, Joel C. Salomon wrote:
Guess I asked for too much at once.
I've downloaded the Gentium Basic/Basic Book set of fonts from http://scripts.sil.org/Gentium_basic, and I'd like to use them with ConTeXt. I ran texfont (with the command line texfont --fontroot=c:\users\chesky\programs\context\tex\texmf-local --sourcepath=... --vendor=sil --collection=gentium --makepath --install), and now running texexec on the newly generated texnansi-sil-gentium.tex produces some sort of glyph list.
Rather than using texfont (half-broken anyway), use XeTeX or LuaTeX.
(If you're using MikTeX and are willing to upgrade to MikTeX 2.7, you can process your documents with "texexec --xtx filename"; if you're using the standalone ConTeXt, you can process it with "--xtx" or "--lua".)
Depending on whether you want to install those fonts or keep them in the tree there are slightly different approaches, but this should work for both LuTeX and XeTeX if you keep your files in the working directory or in texmf/fonts/opentype/...[somewhere here]...
\starttypescript[serif][gentium-basic] \definefontsynonym[GentiumBasic] [file:GenBasR] [features=default] \definefontsynonym[GentiumBasicItalic] [file:GenBasI] [features=default] \definefontsynonym[GentiumBasicBold] [file:GenBasB] [features=default] \definefontsynonym[GentiumBasicBoldItalic][file:GenBasBI] [features=default] \stoptypescript
\starttypescript[serif][gentium-basic][name] \definefontsynonym[Serif] [GentiumBasic] \definefontsynonym[SerifItalic] [GentiumBasicItalic] \definefontsynonym[SerifBold] [GentiumBasicBold] \definefontsynonym[SerifBoldItalic][GentiumBasicBoldItalic] \stoptypescript
\definetypeface[mygentium][rm][serif][gentium-basic][default]
\setupbodyfont[mygentium,13pt]
I don't know how you plan to mix those fonts, but "reverting to another typeface in case a glyph is missing" is a bad idea in this particular case, at least in my opinion (although it's conditionally doable) - how are you going to handle missing characters in bold typeface?
One possibility would be to use: - Gentium for Roman & Italic - Gentium Basic for Bold & Bold Italic (and hope that you won't need any special characters for titles)
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 ______________________________________________________________________ _____________
On Nov 22, 2007 12:01 PM, Steffen Wolfrum wrote:
Hi Mojca,
I tried your example below and struggled in path error:
%\starttypescript[serif][gentium-basic] %\definefontsynonym[GentiumBasic] [file:GenBasR] [features=default] %\definefontsynonym[GentiumBasicItalic] [file:GenBasI] [features=default] %\definefontsynonym[GentiumBasicBold] [file:GenBasB] [features=default] %\definefontsynonym[GentiumBasicBoldItalic][file:GenBasBI] [features=default] %\stoptypescript
%\starttypescript[serif][gentium-basic][name] %\definefontsynonym[Serif] [GentiumBasic] %\definefontsynonym[SerifItalic] [GentiumBasicItalic] %\definefontsynonym[SerifBold] [GentiumBasicBold] %\definefontsynonym[SerifBoldItalic][GentiumBasicBoldItalic] %\stoptypescript
%\definetypeface[mygentium][rm][serif][gentium-basic][default]
%\setupbodyfont[mygentium,36pt]
\font\rom="Gentium Basic" at 36pt
\starttext
Test WQG 0196
\rom Test WQG 0196
\stoptext
Doing it like this works OK. But uncommenting the lines above ends up in ...
kpathsea: Running mktexmf GenBasR
! I can't find file `GenBasR'.
But isn't it the same font/file adressed in both cases?
(sorry, I am an absolute beginner in xetex)
No, my typescripts defile the font to be GenBasR.otf or GenBasR.ttf Apparently you have installed the font (I provided the example for the case when one puts fonts in TEXMF tree). In that case you need (for LuaTeX you might need to provide other names - not sure) \starttypescript[serif][gentium-basic] \definefontsynonym[GentiumBasic] [name:Gentium Basic] [features=default] \definefontsynonym[GentiumBasicItalic] [name:Gentium Basic/I] [features=default] \definefontsynonym[GentiumBasicBold] [name:Gentium Basic/B] [features=default] \definefontsynonym[GentiumBasicBoldItalic][name:Gentium Basic/BI] [features=default] \stoptypescript or, even more simple would be the following one-liner: \definetypeface[mygentium][rm][Xserif][Gentium Basic][default] Mojca
Am 22.11.2007 um 12:30 schrieb Mojca Miklavec:
or, even more simple would be the following one-liner: \definetypeface[mygentium][rm][Xserif][Gentium Basic][default]
So do you mean like this? \definetypeface[mygentium][rm][Xserif][Gentium Basic][default] %\setupbodyfont[mygentium,36pt] \starttext Test WQG 0196 \stoptext When I uncomment the second line the typesetting process stops after the log entry (/usr/local/texlive/2007/../texmf-local/tex/context/base/type-xtx.tex) for about 13 seconds and finally ends up in Output written on xetex_gentium_1.xdv (1 page, 1672 bytes). Transcript written on xetex_gentium_1.log. TeXExec | runtime: 18.589679 Now I am curious what else I am missing ... Steffen
On Thu, 22 Nov 2007 13:52:16 +0100
Steffen Wolfrum
Am 22.11.2007 um 12:30 schrieb Mojca Miklavec:
or, even more simple would be the following one-liner: \definetypeface[mygentium][rm][Xserif][Gentium Basic][default]
So do you mean like this?
\definetypeface[mygentium][rm][Xserif][Gentium Basic][default] %\setupbodyfont[mygentium,36pt]
\starttext
Test WQG 0196
\stoptext
When I uncomment the second line the typesetting process stops after the log entry (/usr/local/texlive/2007/../texmf-local/tex/context/base/type-xtx.tex)
for about 13 seconds and finally ends up in
Output written on xetex_gentium_1.xdv (1 page, 1672 bytes). Transcript written on xetex_gentium_1.log. TeXExec | runtime: 18.589679
Now I am curious what else I am missing ...
Steffen
The following works for me with LuaTeX and XeTeX. I had my test file in the same directory as the fonts, can you try this or you forgot to call "fc-cache -v -r". \starttypescript[serif][gentium-basic] \definefontsynonym[Serif] [GentiumBasic] \definefontsynonym[SerifItalic] [GentiumBasicItalic] \definefontsynonym[SerifBold] [GentiumBasicBold] \definefontsynonym[SerifBoldItalic][GentiumBasicBoldItalic] \stoptypescript \starttypescript[serif][gentium-basic] \definefontsynonym[GentiumBasic] [file:GenBasR] [features=default] \definefontsynonym[GentiumBasicItalic] [file:GenBasI] [features=default] \definefontsynonym[GentiumBasicBold] [file:GenBasB] [features=default] \definefontsynonym[GentiumBasicBoldItalic][file:GenBasBI][features=default] \stoptypescript \starttypescript[gentium-basic] \definetypeface[gentium][rm][serif][gentium-basic][default] \stoptypescript \usetypescript[gentium-basic] \setupbodyfont[gentium] \starttext \rm\input knuth\par \it\input knuth\par \bf\input knuth\par \bi\input knuth \stoptext Wolfgang
Am 22.11.2007 um 19:31 schrieb Wolfgang Schuster:
\starttypescript[serif][gentium-basic] \definefontsynonym[Serif] [GentiumBasic] \definefontsynonym[SerifItalic] [GentiumBasicItalic] \definefontsynonym[SerifBold] [GentiumBasicBold] \definefontsynonym[SerifBoldItalic][GentiumBasicBoldItalic] \stoptypescript
\starttypescript[serif][gentium-basic] \definefontsynonym[GentiumBasic] [file:GenBasR] [features=default] \definefontsynonym[GentiumBasicItalic] [file:GenBasI] [features=default] \definefontsynonym[GentiumBasicBold] [file:GenBasB] [features=default] \definefontsynonym[GentiumBasicBoldItalic][file:GenBasBI] [features=default] \stoptypescript
\starttypescript[gentium-basic] \definetypeface[gentium][rm][serif][gentium-basic][default] \stoptypescript
\usetypescript[gentium-basic] \setupbodyfont[gentium]
\starttext
\rm\input knuth\par \it\input knuth\par \bf\input knuth\par \bi\input knuth
\stoptext
Wolfgang
very, very strange. your file as above works perfectly ... but have no font size specified?! when I change \setupbodyfont[gentium] to \setupbodyfont[gentium,12pt] it works nevertheless. same for 11pt, 10pt, 9pt, 8pt, 7pt, 6pt, 5pt, 4pt. BUT: with all other font-sizes I end up in the same freeze process and no output!! what the hell is going on? steffen [XeTeXk, Version 3.141592-2.2-0.996 (Web2C 7.5.6), ConTeXt ver: 2007.10.03 12:52 MKII fmt: 2007.11.22 int: english/english]
On Nov 22, 2007 8:57 PM, Steffen Wolfrum wrote:
Am 22.11.2007 um 19:31 schrieb Wolfgang Schuster:
\starttypescript[serif][gentium-basic] \definefontsynonym[Serif] [GentiumBasic] \definefontsynonym[SerifItalic] [GentiumBasicItalic] \definefontsynonym[SerifBold] [GentiumBasicBold] \definefontsynonym[SerifBoldItalic][GentiumBasicBoldItalic] \stoptypescript
\starttypescript[serif][gentium-basic] \definefontsynonym[GentiumBasic] [file:GenBasR] [features=default] \definefontsynonym[GentiumBasicItalic] [file:GenBasI] [features=default] \definefontsynonym[GentiumBasicBold] [file:GenBasB] [features=default] \definefontsynonym[GentiumBasicBoldItalic][file:GenBasBI] [features=default] \stoptypescript
\starttypescript[gentium-basic] \definetypeface[gentium][rm][serif][gentium-basic][default] \stoptypescript
\usetypescript[gentium-basic] \setupbodyfont[gentium]
\starttext
\rm\input knuth\par \it\input knuth\par \bf\input knuth\par \bi\input knuth
\stoptext
Wolfgang
very, very strange. your file as above works perfectly ... but have no font size specified?!
12pt is the default size.
when I change \setupbodyfont[gentium] to \setupbodyfont[gentium,12pt] it works nevertheless. same for 11pt, 10pt, 9pt, 8pt, 7pt, 6pt, 5pt, 4pt.
BUT: with all other font-sizes I end up in the same freeze process and no output!!
ConTeXt has some weird ideas about how font sizes should work because of CMR (still better than LaTeX which only supports 10, 11 and 12pt though), so you might need sometning like \definebodyfontenvironment[15.5pt] before using that size. Don't ask me how it works though. Mojca
Am 22.11.2007 um 21:23 schrieb Mojca Miklavec:
On Nov 22, 2007 8:57 PM, Steffen Wolfrum wrote:
Am 22.11.2007 um 19:31 schrieb Wolfgang Schuster:
\starttypescript[serif][gentium-basic] \definefontsynonym[Serif] [GentiumBasic] \definefontsynonym[SerifItalic] [GentiumBasicItalic] \definefontsynonym[SerifBold] [GentiumBasicBold] \definefontsynonym[SerifBoldItalic][GentiumBasicBoldItalic] \stoptypescript
\starttypescript[serif][gentium-basic] \definefontsynonym[GentiumBasic] [file:GenBasR] [features=default] \definefontsynonym[GentiumBasicItalic] [file:GenBasI] [features=default] \definefontsynonym[GentiumBasicBold] [file:GenBasB] [features=default] \definefontsynonym[GentiumBasicBoldItalic][file:GenBasBI] [features=default] \stoptypescript
\starttypescript[gentium-basic] \definetypeface[gentium][rm][serif][gentium-basic][default] \stoptypescript
\usetypescript[gentium-basic] \setupbodyfont[gentium]
\starttext
\rm\input knuth\par \it\input knuth\par \bf\input knuth\par \bi\input knuth
\stoptext
Wolfgang
very, very strange. your file as above works perfectly ... but have no font size specified?!
12pt is the default size.
when I change \setupbodyfont[gentium] to \setupbodyfont[gentium,12pt] it works nevertheless. same for 11pt, 10pt, 9pt, 8pt, 7pt, 6pt, 5pt, 4pt.
BUT: with all other font-sizes I end up in the same freeze process and no output!!
ConTeXt has some weird ideas about how font sizes should work...
but why do I have no problems to use: \usetypescript[postscript][\defaultencoding] \setupencoding[default=texnansi] \setupbodyfont[postscript,10.75pt] \starttext \rm\input knuth\par \it\input knuth\par \bf\input knuth\par \bi\input knuth \stoptext Is it "only" a problem of third-party-fonts? Or ConTeXt documents typeset with XeTeX? Steffen
As this strange error makes me a bit nervous I checked an older file for its behavior: same result! A file that without problems was typeset in April now ends up with the same kind of freezing: \usetypescriptfile[type-gyr] \usetypescript[times][ec] \mainlanguage[de] \enableregime[utf] \setupbodyfont[times,10pt] \setupinterlinespace[line=12pt] \starttext Wort und Tat in 1906 \stoptext When this is set with pdftext all is fine. With xetex (or xtx) the process stop at this line: (/usr/local/texlive/2007/../texmf-local/tex/context/base/type- gyr.tex))! unknown encoding "utf"; reading as raw bytes for 29 second (!) and ends up without producing the pdf: Output written on test_1.xdv (1 page, 1628 bytes). Transcript written on test_1.log. TeXExec | runtime: 30.596294 What went wrong? Help! Steffen
On Nov 23, 2007 11:53 AM, Steffen Wolfrum wrote:
As this strange error makes me a bit nervous I checked an older file for its behavior: same result!
A file that without problems was typeset in April now ends up with the same kind of freezing:
\usetypescriptfile[type-gyr]
you don't need that one for XeTeX, I think.
\usetypescript[times][ec]
It's still not clear to me how to make these definition engine-independent, but for XeTeX use \usetypescript[times] else you'll get the old ec-encoded fonts instead of OpenType.
\mainlanguage[de] \enableregime[utf]
\setupbodyfont[times,10pt] \setupinterlinespace[line=12pt]
\starttext
Wort und Tat in 1906
\stoptext
When this is set with pdftext all is fine. With xetex (or xtx) the process stop at this line:
(/usr/local/texlive/2007/../texmf-local/tex/context/base/type- gyr.tex))! unknown encoding "utf"; reading as raw bytes
Sorry, my fault again. For you: to solve the problem temporary, remove \enableregime, or use \beginOLDTEX \enableregime[utf] \endOLDTEX or try to fix this line in regi-ini.mkii (and test the behavior): \def\mkenableregime#1{\doifnot{#1}{utf}{\XeTeXinputencoding "#1"\relax}} For Hans: There's a little problem in regi-ini: \def\mkenableregime#1{\XeTeXinputencoding "#1"\relax} \def\enableregime[#1]% {\edef\currentregime{\trueregimename{#1}}% \doifelsenothing\currentregime {\disableregime} {\douseregime\currentregime \mkenableregime\currentregime}} This passes \XeTeXinputencoding "utf" to XeTeX, even is someone says \enableregime[utf-8], but XeTeX doesn't know what "utf" encoding is (it expects at least "utf-8" or nothing). The following fix helps, but is not the final answer: \def\mkenableregime#1{\doifnot{#1}{utf}{\XeTeXinputencoding "#1"\relax}} This has one weak point though: \enableregime[cp1250] \enableregime[utf-8] will leave the current regime at cp1250, so perhaps \def\mkenableregime#1{\doifelse{#1}{utf}% {\XeTeXinputencoding "utf-8"\relax}{\XeTeXinputencoding "#1"\relax}} Another option would be to rename utf to utf-8 internally (or to adapt \trueregimename or regi-syn), but that would probably do more harm than good unless tested well, and it's not worth the effort. ... Hmmm .... when thinking agin ... I know that you asked me which regime name to pass to XeTeX and I said "don't worry, it should be more or less the same", but "8859-1" isn't valid regime name either. I'll take a look and report back. Mojca
... Hmmm .... when thinking agin ... I know that you asked me which regime name to pass to XeTeX and I said "don't worry, it should be more or less the same", but "8859-1" isn't valid regime name either. I'll take a look and report back.
The recent archives from the XeTeX list seem to yield \XeTeXinputencoding{utf8} or \XeTeXinputencoding "ISO-8859-1". I assume that both syntaxes are recognized by XeTeX (with curly braces or double quotes). Arthur
On Nov 23, 2007 3:11 PM, Arthur Reutenauer wrote:
... Hmmm .... when thinking agin ... I know that you asked me which regime name to pass to XeTeX and I said "don't worry, it should be more or less the same", but "8859-1" isn't valid regime name either. I'll take a look and report back.
The recent archives from the XeTeX list seem to yield \XeTeXinputencoding{utf8} or \XeTeXinputencoding "ISO-8859-1". I assume that both syntaxes are recognized by XeTeX (with curly braces or double quotes).
No, it's not about the syntax, but rather about the list of accepted names for input encodings. Apart from those three in regi-syn (only left for backward-compatibility): \defineregimesynonym [windows] [cp1252] \defineregimesynonym [grk] [8859-7] \defineregimesynonym [iso88595] [8859-5] and maybe some others in regi-cyp/cyr, XeTeX seems to accept a wide variety of names, so I would suggest the following fix in regi-ini.mkii: \beginXETEX % no idea what these do, but may be left if needed: \let\mkloadregime \gobbleoneargument \let\mkenableregime \gobbleoneargument \let\mkwalkregime \gobbleoneargument \let\mkautosetregime\gobbletwoarguments % sets input encoding to whatever the user asks for. utf is mapped to utf-8 \def\enableregime[#1]% {\doifelse{#1}{utf}% {\message{Specifying UTF-8 input encoding/regime is not needed in XeTeX, but if you do it,}% \message{please use [backslash] enableregime[utf-8] instead of [utf].}% \edef\currentregime{utf-8}}{\edef\currentregime{#1}}% \doifnot{\currentregime}{utf-8}{\message{You are highly encouraged to switch over to UTF-8 input encoding.}}% \XeTeXinputencoding{\currentregime}% \message{Using input encoding/regime \currentregime}} \endXETEX Mojca
OK, so I followed Mojca's tip and used this: \usetypescriptfile[times] \usetypescript[times] \mainlanguage[de] \setupbodyfont[times,10pt] \setupinterlinespace[line=12pt] \starttext Wort und Tat in 1906 \stoptext But this takes about 95 (!) seconds to typeset with a lot of strange log entries: )kpathsea: Illegal fontname `texgyretermes- regular:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- regular:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- regular:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- bold:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- bold:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- bold:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- italic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- italic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- italic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- italic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- italic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- italic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- bolditalic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- bolditalic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- bolditalic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- bolditalic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- bolditalic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- bolditalic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- regular:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;+smcp;': contains ':' kpathsea: Illegal fontname `texgyretermes- regular:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;+smcp;': contains ':' kpathsea: Illegal fontname `texgyretermes- regular:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;+smcp;': contains ':' kpathsea: Illegal fontname `texgyretermes- regular:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- regular:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- bold:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- bold:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- italic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- italic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- italic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- italic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- bolditalic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- bolditalic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- bolditalic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- bolditalic:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':' kpathsea: Illegal fontname `texgyretermes- regular:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;+smcp;': contains ':' kpathsea: Illegal fontname `texgyretermes- regular:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;+smcp;': contains ':' Thers MUST be something wrong/missing!!! Steffen
On Nov 23, 2007 5:33 PM, Steffen Wolfrum wrote:
OK, so I followed Mojca's tip and used this:
\usetypescriptfile[times] \usetypescript[times] \mainlanguage[de] \setupbodyfont[times,10pt] \setupinterlinespace[line=12pt] \starttext Wort und Tat in 1906 \stoptext
But this takes about 95 (!) seconds to typeset with a lot of strange log entries:
)kpathsea: Illegal fontname `texgyretermes- regular:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':'
Thers MUST be something wrong/missing!!!
Wait ... I have been reading in the wrong order: so it does work, only too slow? Actually, being slow and those weird lines in log are "normal" for the current imlementation - it's a price for flexibility over efficiency, but being so inefficient that its flexibility is nearly "useless". What happens if you: - use the latest xetex (http://minimals.contextgarden.net/current/bin/xetex/) - use the attached fixed file (it has been fixed a while ago, but Hans hasn't released a new version yet) - make sure that you have termes otf files - only use \usetypescript[times] \mainlanguage[de] \setupbodyfont[times,10pt] \setupinterlinespace[line=12pt] \starttext Wort und Tat in 1906 \stoptext Mojca
It stays exactly the same: no improvement! (see below) Am 24.11.2007 um 01:25 schrieb Mojca Miklavec:
On Nov 23, 2007 5:33 PM, Steffen Wolfrum wrote:
OK, so I followed Mojca's tip and used this:
\usetypescriptfile[times] \usetypescript[times] \mainlanguage[de] \setupbodyfont[times,10pt] \setupinterlinespace[line=12pt] \starttext Wort und Tat in 1906 \stoptext
But this takes about 95 (!) seconds to typeset with a lot of strange log entries:
)kpathsea: Illegal fontname `texgyretermes- regular:script=latn;language=dflt;+liga;+kern;mapping=tex- text;mapping=tex-text;': contains ':'
Thers MUST be something wrong/missing!!!
Wait ... I have been reading in the wrong order: so it does work, only too slow?
Actually, being slow and those weird lines in log are "normal" for the current imlementation - it's a price for flexibility over efficiency, but being so inefficient that its flexibility is nearly "useless".
What happens if you: - use the latest xetex (http://minimals.contextgarden.net/current/ bin/xetex/)
I did.
- use the attached fixed file (it has been fixed a while ago, but Hans hasn't released a new version yet)
I had already (is exactly the same as in the distro).
- make sure that you have termes otf files
I have texgyretermes...
- only use
\usetypescript[times] \mainlanguage[de] \setupbodyfont[times,10pt] \setupinterlinespace[line=12pt] \starttext Wort und Tat in 1906 \stoptext
Ok did it, but nothing changes ... Steffen
On Nov 24, 2007 10:33 PM, Steffen Wolfrum wrote:
- use the attached fixed file (it has been fixed a while ago, but Hans hasn't released a new version yet)
I had already (is exactly the same as in the distro).
I'm sorry. Something weird is happenning. You need to change these lines (add "file:" prefix): \definefontsynonym [Times-Roman] [file:texgyretermes-regular] [features=default] \definefontsynonym [Times-Italic] [file:texgyretermes-italic] [features=default] \definefontsynonym [Times-Bold] [file:texgyretermes-bold] [features=default] \definefontsynonym [Times-BoldItalic] [file:texgyretermes-bolditalic] [features=default] \definefontsynonym [Times-Caps] [file:texgyretermes-regular] [features=smallcaps] and possibly remake the formats. Does that change anything? (Needs to be changed in the distpibution as well.) Mojca
Am 25.11.2007 um 02:30 schrieb Mojca Miklavec:
On Nov 24, 2007 10:33 PM, Steffen Wolfrum wrote:
- use the attached fixed file (it has been fixed a while ago, but Hans hasn't released a new version yet)
I had already (is exactly the same as in the distro).
I'm sorry. Something weird is happenning. You need to change these lines (add "file:" prefix):
\definefontsynonym [Times-Roman] [file:texgyretermes-regular] [features=default] \definefontsynonym [Times-Italic] [file:texgyretermes-italic] [features=default] \definefontsynonym [Times-Bold] [file:texgyretermes-bold] [features=default] \definefontsynonym [Times-BoldItalic] [file:texgyretermes-bolditalic] [features=default] \definefontsynonym [Times-Caps] [file:texgyretermes-regular] [features=smallcaps]
and possibly remake the formats. Does that change anything? (Needs to be changed in the distpibution as well.)
Yes and No: it makes no improvement, it just changes the point where
the typesetting process pauses/freezes.
Now it is after the line:
(/usr/local/texlive/2007/../texmf-local/tex/context/base/spec-xet.tex)
specials : fdf,dpx loaded
After doing this the process stops for about 90 seconds (while Mac's
processor shows heavy work!), afterwards TeXShop's console prints
dozens of empty line and finally ends in:
(./test_1.tuo) (./test_1.tuo) (./test_1.tuo) (./test_1.tuo) (./
test_1.tuo)
(./test_1.tuo) (./test_1.tuo) (./test_1.tuo) (./test_1.tuo) (./
test_1.tuo)
(/usr/local/texlive/2007/../texmf-local/tex/context/base/sort-lan.tex
loading : Context Sorting Macros (languages)
(/usr/local/texlive/2007/../texmf-local/tex/context/base/sort-lan.mkii))
(./test_1.tuo) (./test_1.tuo)
systems : begin file test_1 at line 9
fonts : resetting map file list
fonts : using map file: original-base
fonts : using map file: lm-math
fonts : using map file: lm-rm
fonts : using map file: original-youngryu-tx
[1.1]
** WARNING ** This .map file looks like a dvips format fontmap file.
** WARNING ** -- Current input buffer is: HoeflerTextOrnaments
hoeflertextornaments
On Nov 25, 2007 12:21 PM, Steffen Wolfrum wrote:
Am 25.11.2007 um 02:30 schrieb Mojca Miklavec:
On Nov 24, 2007 10:33 PM, Steffen Wolfrum wrote:
- use the attached fixed file (it has been fixed a while ago, but Hans hasn't released a new version yet)
I had already (is exactly the same as in the distro).
I'm sorry. Something weird is happenning. You need to change these lines (add "file:" prefix):
\definefontsynonym [Times-Roman] [file:texgyretermes-regular] [features=default] \definefontsynonym [Times-Italic] [file:texgyretermes-italic] [features=default] \definefontsynonym [Times-Bold] [file:texgyretermes-bold] [features=default] \definefontsynonym [Times-BoldItalic] [file:texgyretermes-bolditalic] [features=default] \definefontsynonym [Times-Caps] [file:texgyretermes-regular] [features=smallcaps]
and possibly remake the formats. Does that change anything? (Needs to be changed in the distpibution as well.)
Yes and No: it makes no improvement, it just changes the point where the typesetting process pauses/freezes.
Now it is after the line: (/usr/local/texlive/2007/../texmf-local/tex/context/base/spec-xet.tex) specials : fdf,dpx loaded
After doing this the process stops for about 90 seconds (while Mac's processor shows heavy work!), afterwards TeXShop's console prints dozens of empty line and finally ends in:
Empty lines highly resemble the old XeTeX. Can you try to put \suppressfontnotfounderror\plusone at the top of your document (only to see if your XeTeX is recent enough to recognise the command).
systems : begin file test_1 at line 9 fonts : resetting map file list fonts : using map file: original-base fonts : using map file: lm-math fonts : using map file: lm-rm fonts : using map file: original-youngryu-tx [1.1] ** WARNING ** This .map file looks like a dvips format fontmap file. ** WARNING ** -- Current input buffer is: HoeflerTextOrnaments hoeflertextornaments
What does locate dvipdfm.map say? Can you send a few lines from that file? (It's weird ...)
(The one-liner pdf that was produced in this 95 second looks ok, though. What will happen when some typesets a regular 400 pages book??)
The problem raises only once per typescript change, so unless one is planning to switch typeface regularly, typesetting 400 pages would take 95 seconds+normal processing time for 400 pages. I don't say that is OK, but I don't experience that problem at the moment (though I completely believe you, I only don't know where exactly it stops), so I don't know how exactly to help. Take a look into font-ini, uncomment the following lines and remake the formats: \ifx\xetextempfont\nullfontname \writestatus\m!fonts{fails #1: #2 (\xetextempfont)}% \expandafter\secondoftwoarguments \else \writestatus\m!fonts{succeeds #1: #2 (\xetextempfont)}% \expandafter\firstoftwoarguments (Perhaps uncommenting these lines shold be done in the distro for some period to make debugging easier.) Mojca
No, it's not about the syntax, but rather about the list of accepted names for input encodings.
Yes, I know, I only mentioned it in passing. Now for completeness' sake, the complete list of encodings accepted by XeTeX's \XeTeXinputencoding seems to be: - A couple of special encodings handled by XeTeX internally (from xetexdir/XeTeX_ext.c in the source tree): auto utf8 utf16 <- This one's meaning depends on the host platform's endianness utf16be utf16le bytes - A rather lengthly list of encodings handled by ICU, to be found at http://demo.icu-project.org/icu-bin/convexp with their complete conversion tables to Unicode (quite interesting and useful!). Arthur
Hi Arthur, can you tell me then what is wrong in my minimal example here (it work like a charm in April!)? \usetypescriptfile[times] \usetypescript[times] \mainlanguage[de] \setupbodyfont[times,10pt] \setupinterlinespace[line=12pt] \font\Arab="Baghdad" at 10pt \starttext Zinedine Yazid Zidane (in arab {\Arab زين الدين يزيد زيدان,}), nicknamed Zizou \stoptext Steffen Am 23.11.2007 um 20:28 schrieb Arthur Reutenauer:
No, it's not about the syntax, but rather about the list of accepted names for input encodings.
Yes, I know, I only mentioned it in passing.
Now for completeness' sake, the complete list of encodings accepted by XeTeX's \XeTeXinputencoding seems to be:
- A couple of special encodings handled by XeTeX internally (from xetexdir/XeTeX_ext.c in the source tree):
auto utf8 utf16 <- This one's meaning depends on the host platform's endianness utf16be utf16le bytes
- A rather lengthly list of encodings handled by ICU, to be found at http://demo.icu-project.org/icu-bin/convexp with their complete conversion tables to Unicode (quite interesting and useful!).
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 ______________________________________________________________________ _____________
Hello Steffen, Yes, it seems we have forgotten your original problem in the discussion ;-) I'm not sure I can really help, though, but:
can you tell me then what is wrong in my minimal example here (it work like a charm in April!)?
Nothing is wrong with your input file, really, it's an (admittedly annoying) side-effect of changes that have been made recently in XeTeX-specific font selection options. I have the same problem here and, as frightening as XeTeX's messages may look, the output looks right. One thing: if you wish to typeset Arabic, you really have to say \font\Arab="Baghdad:script=arab", and not only \font\Arab="Baghdad", otherwise character shaping is not correctly done and the output is just messy. This behaviour needs to be fixed in ConTeXt but it's been around for a while now so it's really not that easy (fixing some things will break others, etc.). It's quite unfortunate that you had to experience all XeTeX+ConTeXt font problems at the same time, though, but judging from the other recent mails to the list I have the impression that you're not the only one today with weird problems and that everything seems to have gone astray ;-) I don't know, maybe it's just Weird Encoding Day; just this morning I was experimenting with yet another variation on ispell called hunspell, and I had the following extremely interesting crash which I would like to call the Locale-of-Death: [Current locale is fr_FR.UTF-8] $ hunspell -d morph Hunspell 1.2.1 [blah blah blah spell-checking ...] ^C $ unset LC_ALL $ hunspell -d morph zsh: bus error (core dumped) hunspell -d morph :-) Arthur
On Nov 23, 2007 8:36 PM, Steffen Wolfrum wrote:
Hi Arthur,
can you tell me then what is wrong in my minimal example here (it work like a charm in April!)?
\usetypescriptfile[times]
What exactly is written in type-times.tex? And what does log say? Typescripts in XeTeX have been broken between February and September, so ... :) Mojca PS: also try to use XeTeX 0.997 (http://minimals.contextgarden.net/current/bin/xetex/) PPS: I'm replying to the other thread on the XeTeX list with a slightly longer explanation about the recent changes, but I'm experiencing some problems with the keyboard, so it might take a while before I finish it
Mojca Miklavec wrote:
.... Hmmm .... when thinking agin ... I know that you asked me which regime name to pass to XeTeX and I said "don't worry, it should be more or less the same", but "8859-1" isn't valid regime name either. I'll take a look and report back.
ok, probably some trueregimename kind of mapping is needed ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Thu, 22 Nov 2007 21:23:44 +0100
"Mojca Miklavec"
On Nov 22, 2007 8:57 PM, Steffen Wolfrum wrote:
Am 22.11.2007 um 19:31 schrieb Wolfgang Schuster:
\starttypescript[serif][gentium-basic] \definefontsynonym[Serif] [GentiumBasic] \definefontsynonym[SerifItalic] [GentiumBasicItalic] \definefontsynonym[SerifBold] [GentiumBasicBold] \definefontsynonym[SerifBoldItalic][GentiumBasicBoldItalic] \stoptypescript
\starttypescript[serif][gentium-basic] \definefontsynonym[GentiumBasic] [file:GenBasR] [features=default] \definefontsynonym[GentiumBasicItalic] [file:GenBasI] [features=default] \definefontsynonym[GentiumBasicBold] [file:GenBasB] [features=default] \definefontsynonym[GentiumBasicBoldItalic][file:GenBasBI] [features=default] \stoptypescript
\starttypescript[gentium-basic] \definetypeface[gentium][rm][serif][gentium-basic][default] \stoptypescript
\usetypescript[gentium-basic] \setupbodyfont[gentium]
\starttext
\rm\input knuth\par \it\input knuth\par \bf\input knuth\par \bi\input knuth
\stoptext
Wolfgang
very, very strange. your file as above works perfectly ... but have no font size specified?!
12pt is the default size.
when I change \setupbodyfont[gentium] to \setupbodyfont[gentium,12pt] it works nevertheless. same for 11pt, 10pt, 9pt, 8pt, 7pt, 6pt, 5pt, 4pt.
BUT: with all other font-sizes I end up in the same freeze process and no output!!
ConTeXt has some weird ideas about how font sizes should work because of CMR (still better than LaTeX which only supports 10, 11 and 12pt though), so you might need sometning like \definebodyfontenvironment[15.5pt] before using that size. Don't ask me how it works though.
Mojca
ConTeXt has a few pedefined font size, they are 4pt, 5pt, 6pt, 7pt, 8pt, 9pt, 10pt, 11pt, 12pt, 14.4p and 17.3pt (taken from type-size) but I thought they are only used to take care of the the relative font sizes like small, big, \tfx ... I can choose on my system any font size I like with XeTeX and LuaTeX but XeTeX seems to have a problem with Latin Modern Typewriter in nonstandard sizes. Wolfgang
Am 22.11.2007 um 21:23 schrieb Mojca Miklavec:
ConTeXt has some weird ideas about how font sizes should work because of CMR (still better than LaTeX which only supports 10, 11 and 12pt though), so you might need sometning like \definebodyfontenvironment[15.5pt] before using that size. Don't ask me how it works though.
No, fortunately ConTeXt is better than we feared :o) Now this works perfect: \starttypescript[serif][gentium-basic] \definefontsynonym[GentiumBasic] [name:Gentium Basic] [features=default] \definefontsynonym[GentiumBasicItalic] [name:Gentium Basic/I] [features=default] \definefontsynonym[GentiumBasicBold] [name:Gentium Basic/B] [features=default] \definefontsynonym[GentiumBasicBoldItalic][name:Gentium Basic/BI] [features=default] \stoptypescript \starttypescript[serif][gentium-basic][name] \definefontsynonym[Serif] [GentiumBasic] \definefontsynonym[SerifItalic] [GentiumBasicItalic] \definefontsynonym[SerifBold] [GentiumBasicBold] \definefontsynonym[SerifBoldItalic][GentiumBasicBoldItalic] \stoptypescript \definetypeface[mygentium][rm][serif][gentium-basic][default] \setupbodyfont[mygentium,36.85pt] \starttext Test WQG 0196 \stoptext What I did was: 1) use XeTeX 0.997 (http://minimals.contextgarden.net/current/bin/ xetex/) 2) set MKTEXTFM = 0 in texmf.cnf 3) comment the HoeflerTextOrnaments line in dvipdfm.map Now the killer-combo XeConTeXt is back to life, Halleluja!!! Thank you all for your help, and Good Night. Steffen
On Nov 22, 2007 1:31 PM, Wolfgang Schuster
The following works for me with LuaTeX and XeTeX. I had my test file in the same directory as the fonts, can you try this or you forgot to call "fc-cache -v -r".
I ran "fc-cache -v -r", and that typescript worked for me, but I couldn't make the one-liner work. Does it require some ConTeXt magic that I'm not calling? --Joel
Now I also tried the first version that Moija mentioned (put the font in the tree), same result - 13 seconds pause, no output. I am running ConTeXt ver: 2007.10.03 12:52 MKII fmt: 2007.11.22 int: english/english st.
participants (6)
-
Arthur Reutenauer -
Hans Hagen -
Joel C. Salomon -
Mojca Miklavec -
Steffen Wolfrum -
Wolfgang Schuster