[NTG-context] unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua
Hi, I wanted to test my earlier example (float placement) also with MKIV, but context ---luatex . give me this error message : unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua How can I make it work? Best, Denis ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Unknown units es and dk
I saw this in (the btw great) bachotex-stepbystep presentation \definepapersize [example] [width=8.5es, height=11es] \setuptextbackground [location=paragraph, backgroundcolor=MyColors:4, backgroundoffset=1dk, frame=off] The units "es" and "dk" are unknown to me. What does they mean? TIA juh ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
Re: [NTG-context] unknown script
On Tue, 16 Nov 2021, skyhorse--- via ntg-context wrote: > > OS: Linux (Ubuntu 20.04.3) > /opt/context-lmtx and all directories and files in it are owned by user > and not root. > > I've had this problem before but forgot how to deal with it and neglected to > make a not of it. > I deleted all old context files and did a fresh install of context-lmtx > without su priveledges today. When attempting to typeset a lmtx source file I > get an 'unknown script' error. > > Here's what pops up on my display screen: > > $ context simple-example.lmtx > resolvers | resolving | configuration files already identified > resolvers | resolving | loading configuration file > 'selfautoparent:/texmf/web2c/texmfcnf.lua' > resolvers | resolving | > resolvers | resolving | locating list of '/opt/context-lmtx/tex/texmf' > (runtime) (tree:opt/context-lmtx/tex/texmf) > resolvers | methods | resolving, method 'locators', how 'uri', handler > 'tree', argument 'tree:opt/context-lmtx/tex/texmf' > resolvers | trees | locator '/opt/context-lmtx/tex/texmf' found > resolvers | resolving | hash '/opt/context-lmtx/tex/texmf' appended > resolvers | resolving | > resolvers | methods | resolving, method 'generators', how 'uri', > handler 'file', argument '/opt/context-lmtx/tex/texmf' > resolvers | expansions | using cached scan of path > '/opt/context-lmtx/tex/texmf', branch '/opt/context-lmtx/tex/texmf' > resolvers | methods | resolving, method 'generators', how 'uri', > handler 'file', argument '/opt/context-lmtx/tex/texmf' > resolvers | expansions | using cached scan of path > '/opt/context-lmtx/tex/texmf', branch '/opt/context-lmtx/tex/texmf' > resolvers | resolving | > resolvers | resolving | not saving runtime tree > '/opt/context-lmtx/tex/texmf' > resolvers | resolving | not saving runtime tree > '/opt/context-lmtx/tex/texmf' > resolvers | resolving | remembered file 'mtx-context.lua' > resolvers | resolving | remembered file 'mtx-contexts.lua' > resolvers | resolving | remembered file 'mtx-context.lua' > resolvers | resolving | remembered file 'mtx-t-context.lua' > resolvers | resolving | remembered file 'mtx-t-contexts.lua' > resolvers | resolving | remembered file 'mtx-t-context.lua' > resolvers | resolving | remembered file 'context.lua' > mtxrun | unknown script 'context.lua' or 'mtx-context.lua' > > # END > > Can anyone shed some light on how this should be handled? mtxrun --generate Aditya ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] unknown script
OS: Linux (Ubuntu 20.04.3) /opt/context-lmtx and all directories and files in it are owned by user and not root. I've had this problem before but forgot how to deal with it and neglected to make a not of it. I deleted all old context files and did a fresh install of context-lmtx without su priveledges today. When attempting to typeset a lmtx source file I get an 'unknown script' error. Here's what pops up on my display screen: $ context simple-example.lmtx resolvers | resolving | configuration files already identified resolvers | resolving | loading configuration file 'selfautoparent:/texmf/web2c/texmfcnf.lua' resolvers | resolving | resolvers | resolving | locating list of '/opt/context-lmtx/tex/texmf' (runtime) (tree:opt/context-lmtx/tex/texmf) resolvers | methods | resolving, method 'locators', how 'uri', handler 'tree', argument 'tree:opt/context-lmtx/tex/texmf' resolvers | trees | locator '/opt/context-lmtx/tex/texmf' found resolvers | resolving | hash '/opt/context-lmtx/tex/texmf' appended resolvers | resolving | resolvers | methods | resolving, method 'generators', how 'uri', handler 'file', argument '/opt/context-lmtx/tex/texmf' resolvers | expansions | using cached scan of path '/opt/context-lmtx/tex/texmf', branch '/opt/context-lmtx/tex/texmf' resolvers | methods | resolving, method 'generators', how 'uri', handler 'file', argument '/opt/context-lmtx/tex/texmf' resolvers | expansions | using cached scan of path '/opt/context-lmtx/tex/texmf', branch '/opt/context-lmtx/tex/texmf' resolvers | resolving | resolvers | resolving | not saving runtime tree '/opt/context-lmtx/tex/texmf' resolvers | resolving | not saving runtime tree '/opt/context-lmtx/tex/texmf' resolvers | resolving | remembered file 'mtx-context.lua' resolvers | resolving | remembered file 'mtx-contexts.lua' resolvers | resolving | remembered file 'mtx-context.lua' resolvers | resolving | remembered file 'mtx-t-context.lua' resolvers | resolving | remembered file 'mtx-t-contexts.lua' resolvers | resolving | remembered file 'mtx-t-context.lua' resolvers | resolving | remembered file 'context.lua' mtxrun | unknown script 'context.lua' or 'mtx-context.lua' # END Can anyone shed some light on how this should be handled? Thanks - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Unknown script 'fonts.lua' or 'mtx-fonts.lua'
On Thu, 30 Jul 2020, Marcus Vinicius Mesquita wrote: Hi, Hans I'm on a linux64 machine, and there is indeed a mtx-fonts.lua file: ~/context/tex/texmf-context/scripts/context/lua/mtx-fonts.lua Am I missing something? Refresh the database: luatools --generate Aditya ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Unknown script 'fonts.lua' or 'mtx-fonts.lua'
Hi, Hans I'm on a linux64 machine, and there is indeed a mtx-fonts.lua file: ~/context/tex/texmf-context/scripts/context/lua/mtx-fonts.lua Am I missing something? Marcus Vinicius -- Todas as coisas fatigam o corpo, salvo a música, que não fatiga nem o corpo nem seus membros, por ser descanso da alma, primavera do coração, distração do aflito, entretenimento do solitário, e viático do viajante. Kunnâsh al-Hâ'ik (Cancioneiro de al-Hâ'ik) ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Unknown script 'fonts.lua' or 'mtx-fonts.lua'
On 7/30/2020 5:03 PM, Marcus Vinicius Mesquita wrote: Dear List, After updating ConTeXt to the last version, the command: mtxrun --script fonts replies: mtxrun | unknown script 'fonts.lua' or 'mtx-fonts.lua' mtxrun --version gives: mtxrun | ConTeXt TDS Runner Tool 1.32 Greetings Marcus Vinicius Directory of t:\texmf\scripts\context\lua 07/30/2020 04:54 PM21,051 mtx-fonts.lua should be there Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] Unknown script 'fonts.lua' or 'mtx-fonts.lua'
Dear List, After updating ConTeXt to the last version, the command: mtxrun --script fonts replies: mtxrun | unknown script 'fonts.lua' or 'mtx-fonts.lua' mtxrun --version gives: mtxrun | ConTeXt TDS Runner Tool 1.32 Greetings Marcus Vinicius -- Todas as coisas fatigam o corpo, salvo a música, que não fatiga nem o corpo nem seus membros, por ser descanso da alma, primavera do coração, distração do aflito, entretenimento do solitário, e viático do viajante. Kunnâsh al-Hâ'ik (Cancioneiro de al-Hâ'ik) ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] unknown references
On 3/30/20 1:41 PM, Hans Hagen wrote: > We've added a tracker: > > \enabletrackers [structures.referencing.show] Many thanks for the implementation, Hans. Pablo -- http://www.ousia.tk ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] unknown references
We've added a tracker:
\enabletrackers [structures.referencing.show]
\starttext
Take a look at \at{page}[unknown:1].
This line has a reference.\pagereference[unknown:2]
Take a look at \at{page}[unknown:2].
\stoptext
Experimental till documented in the interface files.
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] unknown file 'grph-img.lua'
On 12/18/2018 5:03 AM, Henri Menke wrote: Dear devs, In the latest beta building the format fails. resolvers > lua > unknown file 'grph-img.lua' This files seems to have been wrongfully removed. If I restore the file from the previous beta, everything works fine. Please fix! i'll fix it (by not loading that file) - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] unknown file 'grph-img.lua'
Dear devs, In the latest beta building the format fails. resolvers > lua > unknown file 'grph-img.lua' This files seems to have been wrongfully removed. If I restore the file from the previous beta, everything works fine. Please fix! Cheers, Henri ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] unknown library
Do you have a minimal example? Wolfgang Hans van der Meer schrieb am 05.09.18 um 17:12: Mij font setup is nothing more then \setupbodyfont[cambria,12pt] An underfull hbox I can understand but wherefrom these messages about an “unknown library normal”? I guess it is not the font, because substituting lmodern for cambria makes no difference. Does this signify I should change something? If so, then what? Underfull \hbox (badness 1014) in paragraph at lines 7--7 []<15: cambria @ 10.0pt> adres[] fonts > typescripts > unknown library 'normal' fonts > typescripts > unknown library 'normal' pages > flushing realpage 108, userpage 108 dr. 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] unknown library
Mij font setup is nothing more then \setupbodyfont[cambria,12pt] An underfull hbox I can understand but wherefrom these messages about an “unknown library normal”? I guess it is not the font, because substituting lmodern for cambria makes no difference. Does this signify I should change something? If so, then what? Underfull \hbox (badness 1014) in paragraph at lines 7--7 []<15: cambria @ 10.0pt> adres[] fonts > typescripts > unknown library 'normal' fonts > typescripts > unknown library 'normal' pages > flushing realpage 108, userpage 108 dr. 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] unknown script 'context.lua' or 'mtx-context.lua
Hello, This may be a sign of an incorrect PATH, picking-up TeXlive or a system installed context. One solution is to *source* the tex/setuptex script, another is to set your PATH with tex/texmf-ARCH/bin up front. Alan On Thu, 27 Feb 2014 11:08:35 + Tim Li timli2...@outlook.com wrote: Hi guys, I haven't played with ConTeXt for three month because of my examinations. Today, I delete the old version and reinstall a new one from the ConTeXt garden, but it seems that the new one can't run successfully. It says that unknown script 'context.lua' or 'mtx-context.lua. The error messages is the following: mtxrun | forcing cache reload resolvers | resolving | looking for 'texmfcnf.lua' on given path '/home/peng/texmf/web2c' from specification 'home:texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/bin/' from specification 'selfautoloc:' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/share/texmf-local/web2c' from specification 'selfautoloc:/share/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/share/texmf/web2c' from specification 'selfautoloc:/share/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/texmf-local/web2c' from specification 'selfautoloc:/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/texmf/web2c' from specification 'selfautoloc:/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/' from specification 'selfautodir:' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/share/texmf-local/web2c' from specification 'selfautodir:/share/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/share/texmf/web2c' from specification 'selfautodir:/share/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/texmf-local/web2c' from specification 'selfautodir:/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/texmf/web2c' from specification 'selfautodir:/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './../texmf-local/web2c' from specification 'selfautoparent:/../texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on weird path './' from specification 'selfautoparent:' resolvers | resolving | looking for 'texmfcnf.lua' on given path './share/texmf-local/web2c' from specification 'selfautoparent:/share/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './share/texmf/web2c' from specification 'selfautoparent:/share/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './texmf/web2c' from specification 'selfautoparent:/texmf/web2c' resolvers | resolving | resolvers | resolving | warning: no lua configuration files found resolvers | resolving | no texmf paths are defined (using TEXMF) resolvers | resolving | mtxrun | the resolver databases are not present or outdated resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-contexts.lua' resolvers | resolving | remembered file 'mtx-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-t-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-t-contexts.lua' resolvers | resolving | remembered file 'mtx-t-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'context.lua' mtxrun | unknown script 'context.lua' or 'mtx-context.lua' Best wishes, Tim ___ 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 ___
[NTG-context] unknown script 'context.lua' or 'mtx-context.lua'
Hi guys, I haven't played with ConTeXt for three month because of my examinations. Today, I delete the old version and reinstall a new one from the ConTeXt garden, but it seems that the new one can't run successfully. It says that unknown script 'context.lua' or 'mtx-context.lua. The error messages is the following: mtxrun | forcing cache reload resolvers | resolving | looking for 'texmfcnf.lua' on given path '/home/peng/texmf/web2c' from specification 'home:texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/bin/' from specification 'selfautoloc:' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/share/texmf-local/web2c' from specification 'selfautoloc:/share/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/share/texmf/web2c' from specification 'selfautoloc:/share/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/texmf-local/web2c' from specification 'selfautoloc:/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/texmf/web2c' from specification 'selfautoloc:/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/' from specification 'selfautodir:' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/share/texmf-local/web2c' from specification 'selfautodir:/share/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/share/texmf/web2c' from specification 'selfautodir:/share/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/texmf-local/web2c' from specification 'selfautodir:/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/texmf/web2c' from specification 'selfautodir:/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './../texmf-local/web2c' from specification 'selfautoparent:/../texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on weird path './' from specification 'selfautoparent:' resolvers | resolving | looking for 'texmfcnf.lua' on given path './share/texmf-local/web2c' from specification 'selfautoparent:/share/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './share/texmf/web2c' from specification 'selfautoparent:/share/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './texmf/web2c' from specification 'selfautoparent:/texmf/web2c' resolvers | resolving | resolvers | resolving | warning: no lua configuration files found resolvers | resolving | no texmf paths are defined (using TEXMF) resolvers | resolving | mtxrun | the resolver databases are not present or outdated resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-contexts.lua' resolvers | resolving | remembered file 'mtx-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-t-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-t-contexts.lua' resolvers | resolving | remembered file 'mtx-t-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'context.lua' mtxrun | unknown script 'context.lua' or 'mtx-context.lua' Best wishes, Tim ___ 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 ___
[NTG-context] unknown script 'context.lua' or 'mtx-context.lua
Hi guys, I haven't played with ConTeXt for three month because of my examinations. Today, I delete the old version and reinstall a new one from the ConTeXt garden, but it seems that the new one can't run successfully. It says that unknown script 'context.lua' or 'mtx-context.lua. The error messages is the following: mtxrun | forcing cache reload resolvers | resolving | looking for 'texmfcnf.lua' on given path '/home/peng/texmf/web2c' from specification 'home:texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/bin/' from specification 'selfautoloc:' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/share/texmf-local/web2c' from specification 'selfautoloc:/share/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/share/texmf/web2c' from specification 'selfautoloc:/share/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/texmf-local/web2c' from specification 'selfautoloc:/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/texmf/web2c' from specification 'selfautoloc:/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/' from specification 'selfautodir:' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/share/texmf-local/web2c' from specification 'selfautodir:/share/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/share/texmf/web2c' from specification 'selfautodir:/share/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/texmf-local/web2c' from specification 'selfautodir:/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/texmf/web2c' from specification 'selfautodir:/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './../texmf-local/web2c' from specification 'selfautoparent:/../texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on weird path './' from specification 'selfautoparent:' resolvers | resolving | looking for 'texmfcnf.lua' on given path './share/texmf-local/web2c' from specification 'selfautoparent:/share/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './share/texmf/web2c' from specification 'selfautoparent:/share/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './texmf/web2c' from specification 'selfautoparent:/texmf/web2c' resolvers | resolving | resolvers | resolving | warning: no lua configuration files found resolvers | resolving | no texmf paths are defined (using TEXMF) resolvers | resolving | mtxrun | the resolver databases are not present or outdated resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-contexts.lua' resolvers | resolving | remembered file 'mtx-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-t-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-t-contexts.lua' resolvers | resolving | remembered file 'mtx-t-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'context.lua' mtxrun | unknown script 'context.lua' or 'mtx-context.lua' Best wishes, Tim ___ 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 ___
Re: [NTG-context] unknown library 'loc'
Hi Hans, Suppressing the message of a loc that is not needed would be the cleanest method. IMHO, it should not be even causing a warning. regards Keith. Am 12.01.2014 um 23:50 schrieb Hans Hagen pra...@wxs.nl: On 1/12/2014 11:23 AM, Keith J. Schultz wrote: Hi Hans, Am 07.01.2014 um 00:24 schrieb Hans Hagen pra...@wxs.nl: On 1/3/2014 2:33 PM, H. van der Meer wrote: Has someone an idee what causes the unknown library message as in the log below? Is it harmful? fontstypescripts unknown library 'loc' you can add a file type-loc.mkiv someplace in your local tree with % dummy file \endinput this file can be used for local overrides (just some mkii compatible feature). If this is the case, should not the the dummy-file be in the distribution! That way if somebody has local overrides they can modify it if needed, and the rest of have one lees message we need to worry, about? It depends ... there are some more loc files, like cont-loc.mkiv and we don't ship these either. Normally users would put such files in texmf-local nowadays but in the past that tree has changes positions in texlive (loading order) so we make no assumptions i.e. it can even be in the main base path which in turn means that we need to make sure it doesn't get overwritten. Easier is probably to suppress the message (ugly but doable). Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] unknown library 'loc'
Hi Hans, Am 07.01.2014 um 00:24 schrieb Hans Hagen pra...@wxs.nl: On 1/3/2014 2:33 PM, H. van der Meer wrote: Has someone an idee what causes the unknown library message as in the log below? Is it harmful? fontstypescripts unknown library 'loc' you can add a file type-loc.mkiv someplace in your local tree with % dummy file \endinput this file can be used for local overrides (just some mkii compatible feature). If this is the case, should not the the dummy-file be in the distribution! That way if somebody has local overrides they can modify it if needed, and the rest of have one lees message we need to worry, about? regards Keith. ___ 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 ___
Re: [NTG-context] unknown library 'loc'
On 1/12/2014 11:23 AM, Keith J. Schultz wrote: Hi Hans, Am 07.01.2014 um 00:24 schrieb Hans Hagen pra...@wxs.nl: On 1/3/2014 2:33 PM, H. van der Meer wrote: Has someone an idee what causes the unknown library message as in the log below? Is it harmful? fontstypescripts unknown library 'loc' you can add a file type-loc.mkiv someplace in your local tree with % dummy file \endinput this file can be used for local overrides (just some mkii compatible feature). If this is the case, should not the the dummy-file be in the distribution! That way if somebody has local overrides they can modify it if needed, and the rest of have one lees message we need to worry, about? It depends ... there are some more loc files, like cont-loc.mkiv and we don't ship these either. Normally users would put such files in texmf-local nowadays but in the past that tree has changes positions in texlive (loading order) so we make no assumptions i.e. it can even be in the main base path which in turn means that we need to make sure it doesn't get overwritten. Easier is probably to suppress the message (ugly but doable). Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] unknown library 'loc'
On 1/3/2014 2:33 PM, H. van der Meer wrote:
Has someone an idee what causes the unknown library message as in the
log below? Is it harmful?
fontstypescripts unknown library 'loc'
you can add a file type-loc.mkiv someplace in your local tree with
% dummy file
\endinput
this file can be used for local overrides (just some mkii compatible
feature).
(/Users/hansm/tex/context-16/tex/texmf-context/tex/context/base/type-imp-texgyre.mkiv){/Users/hansm/tex/context-16/tex/texmf/fonts/map/dvips/lm/lm-math.map}{/Users/hansm/tex/context-16/tex/texmf/fonts/map/dvips/lm/lm-rm.map}{/Users/hansm/tex/context-16/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map})
ConTeXt ver: 2013.12.26 12:50 MKIV beta fmt: 2013.12.29 int:
english/english
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
___
--
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
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
___
Re: [NTG-context] unknown library 'loc'
On 1/3/2014 2:33 PM, H. van der Meer wrote:
Has someone an idee what causes the unknown library message as in the
log below? Is it harmful?
fontstypescripts unknown library 'loc'
(/Users/hansm/tex/context-16/tex/texmf-context/tex/context/base/type-imp-texgyre.mkiv){/Users/hansm/tex/context-16/tex/texmf/fonts/map/dvips/lm/lm-math.map}{/Users/hansm/tex/context-16/tex/texmf/fonts/map/dvips/lm/lm-rm.map}{/Users/hansm/tex/context-16/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map})
it's a harmless side effect that i need to figure out when i have time
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
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
___
[NTG-context] unknown library 'loc'
Has someone an idee what causes the unknown library message as in the log
below? Is it harmful?
fontstypescripts unknown library 'loc'
(/Users/hansm/tex/context-16/tex/texmf-context/tex/context/base/type-imp-texgyre.mkiv){/Users/hansm/tex/context-16/tex/texmf/fonts/map/dvips/lm/lm-math.map}{/Users/hansm/tex/context-16/tex/texmf/fonts/map/dvips/lm/lm-rm.map}{/Users/hansm/tex/context-16/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map})
ConTeXt ver: 2013.12.26 12:50 MKIV beta fmt: 2013.12.29 int: english/english
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
___
[NTG-context] unknown library lmodern
I spot in the log the following message: fontstypescripts unknown: library 'lmodern' Does this point to a problem? In good faith I believe I have a fairly standard installation. And in /usr/local/texlive/2012 the TeXlive distribution. Neither adding \setupbodyfont[modern,14pt] nor omitting all \setupbodyfont's changes this. 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 ___
Re: [NTG-context] \unknown lost on xml export
On 5-11-2011 15:52, Marco Pessotto wrote:
Hello there.
While exporting the ellipses are completely lost. Is there a workaround
for cases like that (I have the feeling this is the top of the iceberg)?
Not using \unknown but \textellipsis
I'm not sure why you're seeing an iceberg. The \unknown\ commands uses
leaders deep down and those don't get exported. I'll change the
definition to the less efficient variant
\def\doperiods[#1]%
{\dontleavehmode
\hbox\bgroup
\setbox\scratchbox\hbox to \periodswidth{\hss.\hss}%
\dorecurse{\iffirstargument#1\else\periodsdefault\fi}{\copy\scratchbox}%
\egroup}
which does export periods (but spaced, as expected).
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
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
___
Re: [NTG-context] \unknown lost on xml export
Hans Hagen pra...@wxs.nl writes: On 5-11-2011 15:52, Marco Pessotto wrote: Hello there. While exporting the ellipses are completely lost. Is there a workaround for cases like that (I have the feeling this is the top of the iceberg)? Not using \unknown but \textellipsis Thanks. I'm not sure why you're seeing an iceberg. Well, it's the feeling you get when you hit a bug while working on a Hello world document after 5 minutes. :-\ I'm truly sorry if it sounded harsh. -- Marco ___ 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 ___
[NTG-context] \unknown lost on xml export
Hello there.
While exporting the ellipses are completely lost. Is there a workaround
for cases like that (I have the feeling this is the top of the iceberg)?
The following minimal example should be clear enough:
%%% start example
\setupbackend[export=yes]
\starttext
Hello\unknown{} world!
\stoptext
%%% end example
Which leads to:
?xml version='1.0' encoding='UTF-8' standalone='yes' ?
!-- input filename : prova --
!-- processing date : Sat Nov 5 15:45:09 2011 --
!-- context version : 2011.11.02 20:10 --
!-- exporter version : 0.30 --
document language=en file=prova date=Sat Nov 5 15:45:09 2011
context=2011.11.02 20:10 version=0.30
xmlns:m=http://www.w3.org/1998/Math/MathML;
Hello world!
/document
Best regards
--
Marco
___
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
___
[NTG-context] unknown script 'context.lua' or 'mtx-context.lua'
Hans, why don't you add a special-case in this case: context test MTXrun | unknown script 'context.lua' or 'mtx-context.lua' if 'context.lua' cannot be found then either: a) instead of printing out unknown script 'context.lua' print out please run 'luatools --generate' - it will be less confusing for users b) or (may be even better) try to run luatools --generate automatically and then retry I guess that there is some not-too-difficult way to figure out from within mtxrun that no database exists yet. 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] unknown script 'context.lua' or 'mtx-context.lua'
Mojca Miklavec wrote: Hans, why don't you add a special-case in this case: context test MTXrun | unknown script 'context.lua' or 'mtx-context.lua' Coincidence: Hans and I discussed this same thing just this morning. b) or (may be even better) try to run luatools --generate automatically and then retry We decided we want b) but only if there is no database at all yet (to avoid lengthy processing of mtxrun --script fnts) 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] unknown script 'context.lua' or 'mtx-context.lua'
On Wed, May 26, 2010 at 12:25, Taco Hoekwater wrote: Mojca Miklavec wrote: Hans, why don't you add a special-case in this case: context test MTXrun | unknown script 'context.lua' or 'mtx-context.lua' Coincidence: Hans and I discussed this same thing just this morning. Wow, great :) Mindreading. Thanks a lot, Mojca PS (not to be taken too seriously): The second thought probably had to do with if there's format version mismatch in mkii, write out some temporary file or some signal line in tuo file that triggers 'texexec --make' in the 'post-processing step' and thus eliminates the need to do it manually every time or did I misinterpret the signal that came all the way from Netherlands? :) :) :) ___ 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 ___
Re: [NTG-context] unknown script 'context.lua' or 'mtx-context.lua'
On 26-5-2010 12:20, Mojca Miklavec wrote: Hans, why don't you add a special-case in this case: context test MTXrun | unknown script 'context.lua' or 'mtx-context.lua' if 'context.lua' cannot be found then either: a) instead of printing out unknown script 'context.lua' print out please run 'luatools --generate' - it will be less confusing for users and then with any typo a generate? no fun b) or (may be even better) try to run luatools --generate automatically and then retry see email taco - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] unknown script 'context.lua' or 'mtx-context.lua'
On 26-5-2010 12:34, Mojca Miklavec wrote: On Wed, May 26, 2010 at 12:25, Taco Hoekwater wrote: Mojca Miklavec wrote: Hans, why don't you add a special-case in this case: context test MTXrun | unknown script 'context.lua' or 'mtx-context.lua' Coincidence: Hans and I discussed this same thing just this morning. Wow, great :) Mindreading. Thanks a lot, Mojca PS (not to be taken too seriously): The second thought probably had to do with if there's format version mismatch in mkii, write out some temporary file or some signal line in tuo file that triggers 'texexec --make' in the 'post-processing step' and thus eliminates the need to do it manually every time or did I misinterpret the signal that came all the way from Netherlands? :) :) :) that needs a bit of thinking; in mkiv it's easier as there the engine runs context and context then determines it while in pdftex an old format and new engine does not come that far; what could be made to work is auto format making when there is a context update (and forget about the engine) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
[NTG-context] unknown reference fnt:f:50
Hi!
I have compiled my file but it stopped on page 14 with the log file
(bottom of the message) saying unknown reference
I remarked that hyphenation patterns for portuguese do this hypenation
li-gar-am instead of li-ga-ram. How can I correct that?
I remarked that hyphenation for pronominal verbs in portuguese is also
incorrect (though wordprocessors do that as well) because when, say,
this verb amo-te is broken across two lines it should be hyphenated
this way
amo-
-te
A fix will be very welcomed.
armando
i.t., there should be two hyphens sbreaks this ver)
[EMAIL PROTECTED]:~/Documents texexec --xtx augusto_eduardo_nunes31mart.tex
TeXExec | processing document 'augusto_eduardo_nunes31mart.tex'
TeXExec | no ctx file found
TeXExec | tex processing method: context
TeXExec | TeX run 1
TeXExec | writing option file augusto_eduardo_nunes31mart.top
TeXExec | using randomseed 1411
TeXExec | tex engine: xetex
TeXExec | tex format: cont-en
This is XeTeX, Version 3.141592-2.2-0.996 (Web2C 7.5.6)
(WARNING: translate-file natural.tcx ignored)
entering extended mode
(./augusto_eduardo_nunes31mart.tex
ConTeXt ver: 2007.01.12 15:56 MKII fmt: 2007.9.22 int: english/english
language: language en is active
system : cont-new loaded
(/usr/share/texmf/tex/context/base/cont-new.tex
systems : beware: some patches loaded from cont-new.tex
(/usr/share/texmf/tex/context/base/cont-new.mkii))
system : cont-old loaded
(/usr/share/texmf/tex/context/base/cont-old.tex
loading : Context Old Macros
)
system : cont-fil loaded
(/usr/share/texmf/tex/context/base/cont-fil.tex
loading : Context File Synonyms
)
system : cont-sys.rme loaded
(/usr/share/texmf/tex/context/user/cont-sys.rme
(/usr/share/texmf/tex/context/base/type-exa.tex)
(/usr/share/texmf/tex/context/base/type-syn.tex)
(/usr/share/texmf/tex/context/base/type-enc.tex)
(/usr/share/texmf/tex/context/base/type-siz.tex)
(/usr/share/texmf/tex/context/base/type-map.tex)
(/usr/share/texmf/tex/context/base/type-spe.tex)
(/usr/share/texmf/tex/context/base/type-akb.tex)
(/usr/share/texmf/tex/context/base/type-xtx.tex)
fonts : resetting map file list
fonts : using map file: texnansi-public-lm
c \usedmapfile{=}{texnansi-public-lm}
fonts : using map file: original-base
c \usedmapfile{=}{original-base}
fonts : using map file: ec-public-lm
c \usedmapfile{=}{ec-public-lm}
fonts : using map file: ec-base
c \usedmapfile{=}{ec-base}
fonts : using map file: lm-ec
c \usedmapfile{=}{lm-ec}
fonts : using map file: 8r-base
c \usedmapfile{=}{8r-base}
fonts : using map file: t5-base
c \usedmapfile{=}{t5-base}
fonts : using map file: texnansi-base
c \usedmapfile{=}{texnansi-base}
fonts : using map file: qx-base
c \usedmapfile{=}{qx-base}
fonts : using map file: original-ams-base
c \usedmapfile{=}{original-ams-base}
fonts : using map file: original-ams-euler
c \usedmapfile{=}{original-ams-euler}
fonts : using map file: original-public-lm
c \usedmapfile{=}{original-public-lm}
fonts : using map file: qx-public-lm
c \usedmapfile{=}{qx-public-lm}
fonts : using map file: t5-public-lm
c \usedmapfile{=}{t5-public-lm}
c \usedmapline{+}{umvs MarVoSym marvosym.pfb}
)
bodyfont: 12pt rm is loaded
language: patterns en-ec:ec-1-2:3 uk-ec:ec-2-2:3
de-texnansi:tex
nansi-3-2:3 de-ec:ec-4-2:3 fr-texnansi:texnansi-5-2:3
fr-ec:ec-6-2:3
es-ec:ec-7-2:3 pt-texnansi:texnansi-8-2:3 pt-ec:ec-9-2:3
it-texnansi
:texnansi-10-2:3 it-ec:ec-11-2:3 nl-texnansi:texnansi-12-2:3
nl-ec:ec-
13-2:3 cz-il2:il2-14-2:3 cz-ec:ec-15-2:3 sk-il2:il2-16-2:3
sk-ec:ec
-17-2:3 pl-pl0:pl0-18-2:3 pl-ec:ec-19-2:3 pl-qx:qx-20-2:3 loaded
specials: tex,postscript,rokicki loaded
system : augusto_eduardo_nunes31mart.top loaded
(./augusto_eduardo_nunes31mart.top
specials: loading definition file dpx
(/usr/share/texmf/tex/context/base/spec-dpx.tex
specials: loading definition file fdf
(/usr/share/texmf/tex/context/base/spec-fdf.tex
(/usr/share/texmf/tex/context/base/spec-fdf.mkii))
specials: fdf loaded
)
specials: fdf,dpx loaded
) (/usr/share/texmf/tex/context/base/type-pre.tex)
(/usr/share/texmf/tex/context/base/sort-def.tex)
(/usr/share/texmf/tex/context/base/sort-lan.tex)
systems : begin file augusto_eduardo_nunes31mart at line 2
[1.1] [2.2] [3.3] [4.4] [5.5] [6.6] [7.7] [8.8] [9.9]
references : unknown reference [][fnt:t:1]
references : unknown reference [][fnt:f:1]
references : unknown reference [][fnt:t:2]
references : unknown reference [][fnt:f:2]
[10.10] [11.11]
references : unknown reference [][fnt:t:3]
references : unknown reference [][fnt:f:3]
references : unknown reference [][fnt:t:4]
references : unknown reference [][fnt:f:4]
[12.12] [13.13]
references : unknown reference [][fnt:t:5]
Re: [NTG-context] unknown reference fnt:f:50
On Thu, 3 Apr 2008, [EMAIL PROTECTED] wrote: Hi! I have compiled my file but it stopped on page 14 with the log file (bottom of the message) saying unknown reference I think that your file has a missing } somewhere. Run texmfstart concheck filename and it should tell you where the missing } is. Aditya ___ 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] \unknown
Idris Samawi Hamid wrote: Hi Hans... \unknown well, not all fonts have elipses -) i use \unknown as placeholder for something (yet) unknown 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] \unknown
Hi Hans... \unknown is cryptic; why not just... \ellipsis? That's what it is after all, and it's immediately obvious, easier to remember, etc-) (at least as an official synonym...) Note that you could also have \setupellipsis: '...' is the most prevalent but not the only form it can take. '***' and \emdash are apparent alternatives... Bringhurst's discussion on ellipsis rules might help with creating typographical options... French and English have different rules, for example... ...Best ...Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523 -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] \unknown
On Sun, 15 Apr 2007 09:48:39 -0600
Idris Samawi Hamid [EMAIL PROTECTED] wrote:
Hi Hans...
\unknown
is cryptic; why not just...
\ellipsis? That's what it is after all, and it's immediately obvious,
easier to remember, etc-)
(at least as an official synonym...)
Hi Idris,
text \textellipsis
Note that you could also have \setupellipsis: '...' is the most prevalent
but not the only form it can take. '***' and \emdash are apparent
alternatives...
you can use \periods\ or \periods[2] or \periods[5] ...
you can also change the distance of the dots with \def\periodswidth
{...} (default value: 0.5em) and the default number auf dots with the
commands \def\periodsdefault{...} (default value: 3).
Hans, is it possible to make also a definition for the sign used by
\periods to write something like \starts and get ***.
Bringhurst's discussion on ellipsis rules might help with creating
typographical options... French and English have different rules, for
example...
...Best
...Idris
Wolfgang
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
