Mh, no luck then. I tested your example without problems (log file attached, maybe you see a difference). Do you set any TeX related environmental variables by hand? Am 26.08.2011 13:01, schrieb Hans van der Meer:

This is the requested check:

101 ~: mtxrun --locate lmmath-regular.otf /Users/hans/TeX/context/tex/texmf-fonts/opentype/public/lm/lmmath-regular.otf

The font seems to be there. Hans van der Meer

On 26 aug. 2011, at 12:54, Peter Rolf wrote:

...

Am 26.08.2011 12:36, schrieb Hans van der Meer:

...

I guess I am missing something in my font handling here, but do not know what.

Hans van der Meer

This is the minimal example: \def\fontname{antykwa} \setupbodyfont[\fontname] \starttext Requested font = \fontname.\crlf \showbodyfont \stoptext

This is my setup with respect to fonts: context/tex/texmf-fonts (link to /usr/local/textlive/2011/texmf-dist/fonts

Executed: mtxrun --script fonts --reload Executed: mtxrun --script fonts --list --name antykwa giving as output: antykwatorunskaregular antykwatorunskaregular AntykwaTorunska-Regular.otf

Below is the output of the minimal example. Mark that \showbodyfont names modern, not antykwa. I get the same result with other fonts mentioned in "fonts in context" page 69-71 as preloaded typescripts!

For example calling typeface cambria it even gives an error: ! Math error: parameter \Umathquad\displaystyle is not set.

I don't know if this is related, but I got a similar error message some days ago. The problem here was the missing font 'lmmath-regular.otf'. Can you check that on your installation?

mtxrun --locate lmmath-regular.otf R:/tex/texmf/fonts/opentype/public/lm/lmmath-regular.otf

...

system > tex > error on line 6 in file test.tex: Math error: parameter \Umathquad\displaystyle is not set ...

1 \def\fontname{cambria} 2 \setupbodyfont[\fontname] 3 \starttext 4 Requested font = \fontname.\crlf 5 \showbodyfont 6 >> \stoptext 7

\doshowbodyfont ...mr \languageparameter \c!text $ \quad }\vrule }\cr \noalig... <to be read again> \stoptext

___________________________________________________________________________________ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

___________________________________________________________________________________ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

___________________________________________________________________________________ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

Am 26.08.2011 13:58, schrieb Hans van der Meer:

What is the attached file? Does not open as a text file here.

7zip archive. Attached the log file as zip now..

Hans van der Meer

On 26 aug. 2011, at 13:36, Peter Rolf wrote:

...

Mh, no luck then. I tested your example without problems (log file attached, maybe you see a difference). Do you set any TeX related environmental variables by hand?

___________________________________________________________________________________

___________________________________________________________________________________ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

On Aug 26, 2011, at 2:55 PM, Hans van der Meer wrote:

Still a mystery to me. In your logfile I see the line used files > 16: filename=AntykwaTorunska-Regular | filetype=otf | format=otf | foundname=R:/tex/texmf/fonts/opentype/public/antt/AntykwaTorunska-Regular.otf | usedmethod=database I therefore concluse in your system ConTeXt has found the reference for \setupbodyfont[antykwa].

That typescript is defined in type-otf.mkiv, at least I my context standalone (installed just minutes ago).

The latter shows that antykwa is not found in the context run but mtxrun did! I am completely baffled.

Not booth are looking for the same thing: context looks for a typescript definition, mtxrun for a font. I suspect your problem is not that the font is not found, but that you are inadvertedly mixing the standalone context macros in with the texlive macros somehow. Try removing the symlink in texmf-fonts, rerun mtxrun --script fonts --reload, and see what happens then (all needed files are in the standalone distribution). Best wishes, Taco

Am 26.08.2011 15:43, schrieb Hans van der Meer:

On 26 aug. 2011, at 15:14, Taco Hoekwater wrote:

...

On Aug 26, 2011, at 2:55 PM, Hans van der Meer wrote:

...

Still a mystery to me. In your logfile I see the line used files > 16: filename=AntykwaTorunska-Regular | filetype=otf | format=otf | foundname=R:/tex/texmf/fonts/opentype/public/antt/AntykwaTorunska-Regular.otf | usedmethod=database I therefore concluse in your system ConTeXt has found the reference for \setupbodyfont[antykwa].

That typescript is defined in type-otf.mkiv, at least I my context standalone (installed just minutes ago).

...

The latter shows that antykwa is not found in the context run but mtxrun did! I am completely baffled.

Not booth are looking for the same thing: context looks for a typescript definition, mtxrun for a font. I suspect your problem is not that the font is not found, but that you are inadvertedly mixing the standalone context macros in with the texlive macros somehow.

Try removing the symlink in texmf-fonts, rerun mtxrun --script fonts --reload, and see what happens then (all needed files are in the standalone distribution).

Did this, removed linked, let mtxrun reload the database, then running context. Same result: files > readfile > asked name: 'antykwa', not found

Just to be sure: delete the complete luatex cache files per hand and retry.

You said: (all needed files are in the standalone distribution). But is it possible that somehow the relevant files did not reach my computer? Searching for antykwa gives only these files in the context setup downloaded by me: 113 context: find . -name "*antykwa*" ./tex/texmf-context/tex/context/fonts/antykwa-math.lfg ./tex/texmf-context/tex/context/fonts/antykwapoltawskiego.lfg That's all.

Same here, but 'find' is case sensitive. If you search for "*Antykwa*" you will also find the related otf files.

And finally, the unexplained cambria crash?

As I wrote, you get this cryptic error message if no default math font is found.

For the sake of completeness here the script I call inside the directory context where the distribution must be placed. Assuming that the installation procedure leaves present materials like texmf-local etc. intact: curl -o first-setup.sh http://minimals.contextgarden.net/setup/first-setup.sh chmod a+x ./first-setup.sh mkdir tex sh ./first-setup.sh >first-setup.log exit

Hans van der Meer

___________________________________________________________________________________ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

On 26 aug. 2011, at 16:34, Taco Hoekwater wrote:

On 08/26/2011 03:43 PM, Hans van der Meer wrote:

...

Did this, removed linked, let mtxrun reload the database, then running context. Same result: files> readfile> asked name: 'antykwa', not found

Which is already wrong, afaik. It should *not* be looking for a typescript file, because the typescript 'antykwa' has already been set up in type-otf.mkiv (it *did* load that file, I trust?).

The file type-otf.mkiv is in the base directory and contains typescriptcollection antykwa.

...

You said: (all needed files are in the standalone distribution). But is it possible that somehow the relevant files did not reach my computer? Searching for antykwa gives only these files in the context setup downloaded by me: 113 context: find . -name "*antykwa*" ./tex/texmf-context/tex/context/fonts/antykwa-math.lfg ./tex/texmf-context/tex/context/fonts/antykwapoltawskiego.lfg That's all.

Sure. As I wrote above, there should not *be* any typescript file, and the actual fonts are named *antt*, not '*antykwa*'

changing to \setupbodyfont[antt] now produces: files > readfile > asked name: 'antt', not found I did context --make en: no type-otf.mkiv touched. Then after that: context test and I find the lines: fonts > latin modern fonts are not preloaded languages > language en is active (/Users/hans/TeX/context/tex/texmf-context/tex/context/base/type-siz.mkiv) (/Users/hans/TeX/context/tex/texmf-context/tex/context/base/type-otf.mkiv) files > readfile > asked name: 'loc', not found files > readfile > asked name: 'antykwa', not found fonts > preloading latin modern fonts (third stage) Thus I take it for granted that typeset.mkiv has been found by ConTeXt.

...

And finally, the unexplained cambria crash?

Not looked at that yet, and it is usually unwise to attempt to fix two problems at the same time, but my first guess in that case is simply that you have not installed the font. I get:

$ mtxrun --script fonts --list --name cambria\* --all

Hm… Running this one gives an empty return. That sounds bad I guess. But why, isn't it in the distribution? I guessed ConTeXt will find it automatically in the system in case it is in the /usr/local/texlive location. But I agree, best solve the problems one by one. I append a compressed log, having ran make, context, and for completeness sake again the font reload. Hans van der Meer

cambria cambria cambria.ttc index: 1 cambriamath cambriamath cambria.ttc index: 0 cambriamathnormal cambriamath cambria.ttc index: 0 cambrianormal cambria cambria.ttc index: 1

$ luatools cambria.ttc /home/taco/texmf/fonts/truetype/cambria.ttc

...

For the sake of completeness

Have you posted a full log yet? If not, perhaps that is wise (otherwise I missed it).

On 26 aug. 2011, at 17:09, Wolfgang Schuster wrote:

Am 26.08.2011 um 16:57 schrieb Hans van der Meer:

...

On 26 aug. 2011, at 16:34, Taco Hoekwater wrote:

...

Sure. As I wrote above, there should not *be* any typescript file, and the actual fonts are named *antt*, not '*antykwa*'

changing to \setupbodyfont[antt] now produces: files > readfile > asked name: 'antt', not found

\setupbodyfont expects the name of a typeface.

I saw from your terminal output that your context version is from july and a while ago you needed \usetypescript to use “Antykwa Torunska”.

\usetypescript[antykwa-torunska] \setupbodyfont[antykwa]

O, how wonderful is the internet-community. Indeed, that \usetypescript does the trick. Thanks, one problem less here! I guess from Wolfgang's comment that newer vrsions of ConTeXt can do without the \usetypescript? As for the cambria, I now see its name is has been typeset in boldface in the font book. And that solves that problem also, because the font is not here. Hans van der Meer

Hi, On 08/26/2011 04:57 PM, Hans van der Meer wrote:

files> readfile> asked name: 'loc', not found files> readfile> asked name: 'antykwa', not found

solved by Wolfgang :)

But why, isn't it in the distribution?

Because Microsoft is not in the habit of giving stuff away for free. As with all commercial fonts, there is a simple rule: do not use the typescript if you do not own the font. Best wishes, Taco