[NTG-context] can Context render complex scripts?
My first experiments aren't going well. For example: using the free font, BNBDOT0N.ttf, from Deutsche Welle here: http://www.dw-world.de/dw/article/0,,3219221,00.html and the following typescript, type-bidisha.tex: \starttypescript [serif] [dwbangla] \definefontsynonym[DWbangla][name:BNBIDISHAOpentypeNormal][features=body] \stoptypescript \starttypescript [serif] [dwbangla] \definefontsynonym[Serif][DWbangla][features=body] \stoptypescript \starttypescript [dwbangla] \definetypeface [dwbangla] [rm] [serif] [dwbangla] [default] [script=beng,features=body] \stoptypescript I try the following test: \definefontfeature[default][mode=node,language=dflt,script=latn,kern=yes,liga=yes,tlig=yes,trep=yes] \definefontfeature[body][default][mode=node,script=latn,onum=yes,pnum=yes,calt=yes,protrusion=quality,expansion=quality] %just to be sure: \definefontfeature[indic][body][nukt=yes,akhn=yes,rphf=yes,blwf=yes,half=yes,pstf=yes,vatu=yes,pres=yes,blws=yes,abvs=yes,psts=yes, haln=yes,blwm=yes,abvm=yes,dist=yes] \usetypescriptfile[type-bidisha] \starttypescript [MTbook] \definetypeface [dwbangla] [rm] [serif] [dwbangla] [default] [script=beng,language=ben,features=body] \stoptypescript \def\bengali#1{{\switchtobodyfont[dwbangla]\addff{indic}\language[ben]#1}} \usetypescript[MTbook] \starttext \bengali{সত্যজিৎ রায়} \stoptext সত্যজিৎ isn't rendered correctly in the output---after a the first two characters, things go wrong. Yet, with the same font, it is rendered correctly everywhere else I look in windows---notepad, Firefox, TexnicCenter, etc., etc. To see what a correct rendering should look like, google সত্যজিৎ রায় or see here: http://bn.wikipedia.org/wiki/%E0%A6%B8%E0%A6%A4%E0%A7%8D%E0%A6%AF%E0%A6%9C%E0%A6%BF%E0%A7%8E_%E0%A6%B0%E0%A6%BE%E0%A6%AF%E0%A6%BC or here (first word in text, in bold): http://i367.photobucket.com/albums/oo113/andbipul/All%20about%20JJ/JJ%20Torjoma%20Works/Work-11Post-1.jpg I tried this with several other free and MS fonts (e.g., arial Unicode MS) and got the same results. Am I doing something wrong? ___ 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] problem with 'kpse.find_file'
On 11-6-2010 3:03, Li Yanrui (李延瑞) wrote: 'kpse.find_file' now can not work in MkIV (beta 2010.06.10 15:24). The attachment is a minimal example for this. When I compile it, I got the following error: LuaTeX errormain ctx instance:2: attempt to call field 'find_file' (a nil value) stack traceback: main ctx instance:2: in main chunk. }inserted text ...(kpse.find_file (a, lua)) \dodostartluacode ...d \directlua \zerocount {#1}} l.4 \stopluacode i need to check it as i though that i overloades kpse vi ametatables but i didn't check it ... as taco mentioned kpse is not to be used in mkiv 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] can Context render complex scripts?
On Fri, Jun 11, 2010 at 02:14:12AM -0500, Michael Saunders wrote: My first experiments aren't going well. For example: AFAIK, there no Indic specific support yet, Hans will probably need more information about Indic shaping, some test files, the expected output etc. Also, AFAIK, Indic support in OpenType is a bit messy, as there are two specification by MS, one deprecating the other, and there are fonts in the wild that implement this or that, there isn't any free implementation of the new specification, BTW. Digging MS typography site for more information would be a good start, I guess. -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer ___ 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] Irregularity in a topspace a bottomspace?
Am 11.06.10 07:45, schrieb Jaroslav Hajtmar: Hi all. I was surprised that when I set up (in the MKII and MKIV too) topspace parameter to a nonzero value and the value of the bottomspace parameter to zero value, then the size of bottomspace is the same as topspace size. On the other side, if I set topspace to zero value and the bottomspace to nonzero value, ConTeXt behaves as I expected. Is this a normal behavior ConTeXt? Ie. when bottomspace is zero, then the paper has only the tops and not bottoms? When you set 'width=fit' or 'width=middle' context looks at the bottomspace value and if the bottomspace height is 0pt it assign to the bottomspace the height of the topspace. The only thing you can do it to assign a domension ti height, e.g. 'height=15cm'. @Hans: How about a 'height=auto' key which calculates the textheight like 'height=middle' but doen't change the bottomspace value even if the value is 0pt? Wolgang ___ 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] Irregularity in a topspace a bottomspace?
Am 11.06.10 07:45, schrieb Jaroslav Hajtmar: Hi all. I was surprised that when I set up (in the MKII and MKIV too) topspace parameter to a nonzero value and the value of the bottomspace parameter to zero value, then the size of bottomspace is the same as topspace size. On the other side, if I set topspace to zero value and the bottomspace to nonzero value, ConTeXt behaves as I expected. Is this a normal behavior ConTeXt? Ie. when bottomspace is zero, then the paper has only the tops and not bottoms? As told in my other mail that's not possible with a calculated text height but here is a patch: \unprotected\def\dorecalculatelayout {%\the\everybeforelayout \setups[\layoutparameter\c!preset]% \global\leftmarginwidth \layoutparameter\c!leftmargin \global\rightmarginwidth\layoutparameter\c!rightmargin \global\leftedgewidth \layoutparameter\c!leftedge \global\rightedgewidth \layoutparameter\c!rightedge \global\headerheight\layoutparameter\c!header \global\footerheight\layoutparameter\c!footer \global\bottomheight\layoutparameter\c!bottom \global\topheight \layoutparameter\c!top \global\backspace \layoutparameter\c!backspace \global\topspace\layoutparameter\c!topspace \setlayoutdimensions % the rest of the `dimensions' \docheckgridsnapping \doprocesslocalsetups{\layoutparameter\c!setups}% depends on gridsnapping ! \simplesetupwhitespace \simplesetupblank \setupinterlinespace[\v!reset]% \synchronizegloballinespecs \global\cutspace\layoutparameter\c!cutspace \relax \doifelse{\layoutparameter\c!width}\v!middle {\ifdim\cutspace=\zeropoint \global\cutspace\backspace \fi \global\makeupwidth\dimexpr\paperwidth-\backspace-\cutspace\relax} {\doifelse{\layoutparameter\c!width}\v!auto {\global\makeupwidth\dimexpr\paperwidth-\backspace-\cutspace\relax} {\doifelse{\layoutparameter\c!width}\v!fit {\ifdim\cutspace=\zeropoint \global\cutspace\backspace \fi \global\makeupwidth\dimexpr\paperwidth-\cutspace\relax \scratchdimen\dimexpr\backspace -\leftedgewidth -\leftedgedistance -\leftmarginwidth-\leftmargindistance\relax \ifdim\scratchdimen\zeropoint \scratchdimen\zeropoint \fi \global\advance\makeupwidth\dimexpr -\rightmargindistance-\rightmarginwidth -\rightedgedistance -\rightedgewidth -\scratchdimen\relax} {\global\makeupwidth\layoutparameter\c!width\relax \ifdim\cutspace=\zeropoint \global\cutspace\dimexpr\paperwidth-\makeupwidth-\backspace\relax % \else % A kind of inconsistent specification, but used % in for instance s-pre-19.tex; the cutspace is % used only for determining some kind of right % margin; don't use this in doublesided mode \fi}}}% \scratchdimen\layoutparameter\c!bottomspace\relax %\ifdim\scratchdimen=\zeropoint % \scratchdimen\topspace %\fi \global\bottomspace\layoutparameter\c!bottomspace\relax \global\layoutlines0\number\layoutparameter\c!lines\relax % may be empty \ifcase\layoutlines \doifelse{\layoutparameter\c!height}\v!middle {\ifdim\bottomspace=\zeropoint \global\bottomspace\topspace \fi \global\makeupheight\dimexpr\paperheight-\topspace-\bottomspace\relax} {\doifelse{\layoutparameter\c!height}\v!auto {\global\makeupheight\dimexpr\paperheight-\topspace-\bottomspace\relax} {\doifelse{\layoutparameter\c!height}\v!fit {\ifdim\bottomspace=\zeropoint \global\bottomspace\topspace \fi \global\makeupheight\dimexpr\paperheight-\bottomspace\relax \scratchdimen\dimexpr\topspace-\topheight-\topdistance\relax \ifdim\scratchdimen\zeropoint \scratchdimen\zeropoint \fi \global\advance\makeupheight\dimexpr-\bottomdistance-\bottomheight-\scratchdimen\relax} {\global\makeupheight\layoutparameter\c!height\relax \ifdim\bottomspace=\zeropoint \global\bottomspace\dimexpr\paperheight-\makeupheight-\topspace\relax \else % inconsistent specification \fi}}}% \else % beware, when the bodyfont changes (switched) this will change as well; implementing % a global lineheight is tricky: should we take the bodyfont interlinespace or the one set % independent of the bodyfont (before or after a layout spec); way too fuzzy, so we % stick to the current method (after a night of experimenting ...2003/10/13) \global\makeupheight\dimexpr \layoutparameter\c!lines\lineheight-\strutheight+\topskip+ \headerdistance+\headerheight+\footerdistance+\footerheight\relax \fi
Re: [NTG-context] Irregularity in a topspace a bottomspace?
Ok. Thanx. I see that you are due my ignorance revealed a problem that I did not report :-) Jaroslav Dne 11.6.2010 11:50, Wolfgang Schuster napsal(a): Am 11.06.10 07:45, schrieb Jaroslav Hajtmar: Hi all. I was surprised that when I set up (in the MKII and MKIV too) topspace parameter to a nonzero value and the value of the bottomspace parameter to zero value, then the size of bottomspace is the same as topspace size. On the other side, if I set topspace to zero value and the bottomspace to nonzero value, ConTeXt behaves as I expected. Is this a normal behavior ConTeXt? Ie. when bottomspace is zero, then the paper has only the tops and not bottoms? As told in my other mail that's not possible with a calculated text height but here is a patch: \unprotected\def\dorecalculatelayout {%\the\everybeforelayout \setups[\layoutparameter\c!preset]% \global\leftmarginwidth \layoutparameter\c!leftmargin \global\rightmarginwidth\layoutparameter\c!rightmargin \global\leftedgewidth \layoutparameter\c!leftedge \global\rightedgewidth \layoutparameter\c!rightedge \global\headerheight\layoutparameter\c!header \global\footerheight\layoutparameter\c!footer \global\bottomheight\layoutparameter\c!bottom \global\topheight \layoutparameter\c!top \global\backspace \layoutparameter\c!backspace \global\topspace\layoutparameter\c!topspace \setlayoutdimensions % the rest of the `dimensions' \docheckgridsnapping \doprocesslocalsetups{\layoutparameter\c!setups}% depends on gridsnapping ! \simplesetupwhitespace \simplesetupblank \setupinterlinespace[\v!reset]% \synchronizegloballinespecs \global\cutspace\layoutparameter\c!cutspace \relax \doifelse{\layoutparameter\c!width}\v!middle {\ifdim\cutspace=\zeropoint \global\cutspace\backspace \fi \global\makeupwidth\dimexpr\paperwidth-\backspace-\cutspace\relax} {\doifelse{\layoutparameter\c!width}\v!auto {\global\makeupwidth\dimexpr\paperwidth-\backspace-\cutspace\relax} {\doifelse{\layoutparameter\c!width}\v!fit {\ifdim\cutspace=\zeropoint \global\cutspace\backspace \fi \global\makeupwidth\dimexpr\paperwidth-\cutspace\relax \scratchdimen\dimexpr\backspace -\leftedgewidth -\leftedgedistance -\leftmarginwidth-\leftmargindistance\relax \ifdim\scratchdimen\zeropoint \scratchdimen\zeropoint \fi \global\advance\makeupwidth\dimexpr -\rightmargindistance-\rightmarginwidth -\rightedgedistance -\rightedgewidth -\scratchdimen\relax} {\global\makeupwidth\layoutparameter\c!width\relax \ifdim\cutspace=\zeropoint \global\cutspace\dimexpr\paperwidth-\makeupwidth-\backspace\relax % \else % A kind of inconsistent specification, but used % in for instance s-pre-19.tex; the cutspace is % used only for determining some kind of right % margin; don't use this in doublesided mode \fi}}}% \scratchdimen\layoutparameter\c!bottomspace\relax %\ifdim\scratchdimen=\zeropoint % \scratchdimen\topspace %\fi \global\bottomspace\layoutparameter\c!bottomspace\relax \global\layoutlines0\number\layoutparameter\c!lines\relax % may be empty \ifcase\layoutlines \doifelse{\layoutparameter\c!height}\v!middle {\ifdim\bottomspace=\zeropoint \global\bottomspace\topspace \fi \global\makeupheight\dimexpr\paperheight-\topspace-\bottomspace\relax} {\doifelse{\layoutparameter\c!height}\v!auto {\global\makeupheight\dimexpr\paperheight-\topspace-\bottomspace\relax} {\doifelse{\layoutparameter\c!height}\v!fit {\ifdim\bottomspace=\zeropoint \global\bottomspace\topspace \fi \global\makeupheight\dimexpr\paperheight-\bottomspace\relax \scratchdimen\dimexpr\topspace-\topheight-\topdistance\relax \ifdim\scratchdimen\zeropoint \scratchdimen\zeropoint \fi \global\advance\makeupheight\dimexpr-\bottomdistance-\bottomheight-\scratchdimen\relax} {\global\makeupheight\layoutparameter\c!height\relax \ifdim\bottomspace=\zeropoint \global\bottomspace\dimexpr\paperheight-\makeupheight-\topspace\relax \else % inconsistent specification \fi}}}% \else % beware, when the bodyfont changes (switched) this will change as well; implementing % a global lineheight is tricky: should we take the bodyfont interlinespace or the one set % independent of the bodyfont (before or after a layout spec); way too fuzzy, so we % stick to the current method (after a night of experimenting ...2003/10/13) \global\makeupheight\dimexpr
Re: [NTG-context] marginrules vs. papersize
luigi == luigi scarso luigi.sca...@gmail.com writes: luigi A bug in mkii ? This is ok, btw luigi \setuppapersize[letter][letter] \setupoutput[pdftex] Great, that did the trick! Thanks, Martin ___ 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] \pdfcatalog broken in MkIV
Hello, as suggested in the thread about PDF Page Labels, \pdfcatalog can be used to manually modify the PDF Stream. However it seems that this does not currently work in MkIV (from the minimals, beta branch). In MkII it does exactly as I though (the resulting PDF contains a Catalog section with the content I passed to \pdfcatalog). In the PDF produced by MkIV however no Catalog can be found. Best Regards, Andreas. ___ 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] status message of mtxrun --ifchanged
Hi, When I run mtxrun --ifchanged, it echoes the status messages on stdout. This makes it impossible to use mtxrun --ifchanged as part of a standard unix pipe. What is the right way to resolve this? * Output these messages to stderr rather than stdout? * Provide a --silent option mtxrun that suppresses all output? I can parse the generated output and remove the lines starting with MTXrun, but that is no fun. 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] problem with \ref[t][...]
Hello, \ref[t][...] does not work as expected, or I expect the wrong thing: \starttext \startsection[title=Problem here, reference=sec1] Section text: \ref[t][sec1] \stopsection \startsection[title=Workaround] \reference[sec2]{Workaround} Section text: \ref[t][sec2] \stopsection \stoptext A related question: how can I get rid of the quotation marks of \about[]? Test file: \starttext \startsection[title=Section, reference=sec] Title: \about[sec] \stopsection \stoptext TIA for any help! Cheers, Peter -- Contact information: http://pmrb.free.fr/contact/ ___ 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] failure with luatools --generate
Hi, I ran into trouble compiling beta of June 10. It seems to me that luatools is now a script run under mtxrun. Under linux I made executable the scripts scripts/context/stubs/unix/{mtxrun,context, luatools}. Now when I run luatools --generate I get MTXrun | forcing cache reload MTXrun | fileio: warning: no lua configuration files found MTXrun | MTXrun | MTXrun | the resolver databases are not present or outdated MTXrun | fileio: using suffix based filetype 'lua' MTXrun | fileio: using suffix based filetype 'lua' MTXrun | fileio: remembering file 'mtx-base.lua' MTXrun | fileio: using suffix based filetype 'lua' MTXrun | unknown script 'base.lua' or 'mtx-base.lua' MTXrun | MTXrun | runtime: 0.008 seconds What does it mean? I had no trouble with earlier versions of luatools Thank you. Eythan ___ 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] failure with luatools --generate
On 11-6-2010 5:21, Eythan Weg wrote: Hi, I ran into trouble compiling beta of June 10. It seems to me that luatools is now a script run under mtxrun. Under linux I made executable the scripts scripts/context/stubs/unix/{mtxrun,context, luatools}. Now when I run luatools --generate use mtxrun --generate 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] failure with luatools --generate
Thank you. I ran mtxrun --generate MTXrun | fileio: variable 'SELFAUTOLOC' set to '/usr/bin' MTXrun | fileio: variable 'SELFAUTODIR' set to '/usr' MTXrun | fileio: variable 'SELFAUTOPARENT' set to '/' MTXrun | fileio: variable 'TEXMFCNF' set to '/etc/texmf/texmf.cnf' MTXrun | fileio: variable 'TEXMF' set to '' MTXrun | fileio: variable 'TEXOS' set to '/usr' MTXrun | MTXrun | fileio: warning: no lua configuration files found MTXrun | I have manually exported the TEXMFCNF. Here are the commands: w...@fermat:~$ ls -l `which mtxrun` lrwxrwxrwx 1 root root 56 2010-06-11 10:15 /usr/bin/mtxrun - /usr/local/share/texmf/scripts/context/stubs/unix/mtxrun w...@fermat:~$ ls -l `which luatools` lrwxrwxrwx 1 root root 58 2010-06-11 11:03 /usr/bin/luatools - /usr/local/share/texmf/scripts/context/stubs/unix/luatools w...@fermat:~$ ls -l `which context` lrwxrwxrwx 1 root root 57 2010-06-11 10:14 /usr/bin/context - /usr/local/share/texmf/scripts/context/stubs/unix/context Eythan Hans Hagen pra...@wxs.nl Fri, 11 Jun 2010 17:43:43 +0200 On 11-6-2010 5:21, Eythan Weg wrote: Hi, I ran into trouble compiling beta of June 10. It seems to me that luatools is now a script run under mtxrun. Under linux I made executable the scripts scripts/context/stubs/unix/{mtxrun,context, luatools}. Now when I run luatools --generate use mtxrun --generate Hans ___ 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] Strange nieuw directory after updating with first-setup.sh
I just only can tell, that it happens. Yesterday I updated twice, the second time after removing the suspicious part of the tree. But after the second update it was there again. I will update again today...tonight. Willi On 10 Jun 2010, at 21:35, Mojca Miklavec wrote: On Thu, Jun 10, 2010 at 18:32, Willi Egger w.eg...@boede.nl wrote: Hi, I just updated the minimals and I see a strange directory: This is LuaTeX, Version beta-0.60.1-2010042810 Current version: 2010.06.10 15:24 .../lua60.1 is the texroot. ../lua60.1/tex/lua60.1 ^^^ How can I reproduce that? 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 ___ ___ 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] reference, ref, label, id, etc.
Hello, We have now \startsection[reference=...] and \reference[]{} and perhaps other such commands. Wouldn't it be better to call this label or identifier or id or similar instead of reference ? Cheers, Peter -- Contact information: http://pmrb.free.fr/contact/ ___ 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] Strange nieuw directory after updating with first-setup.sh
After the update of this evening the suspicious directory did not appear again. -- So this is solved. However I can not generate the formats, nor did the first-setup.sh produce formats. It looks like there is something fundamentally changed: All exports of environment variables are commented in setuptex. - Also with uncommenting TEXMFCONTEXT, reopening the terminal and running setuptex will not result in the generation of the formats with context --make --all: MTXrun | format path: /Applications/lua60.1/tex/texmf-cache/luatex-cache/context/b71615c5b9a2778e9dcc7d2eff3a04e6/formats MTXrun | no tex source file with name: cont-en.tex I am running this with MacOSX 10.6.3. Kind regards Willi On 10 Jun 2010, at 21:35, Mojca Miklavec wrote: On Thu, Jun 10, 2010 at 18:32, Willi Egger w.eg...@boede.nl wrote: Hi, I just updated the minimals and I see a strange directory: This is LuaTeX, Version beta-0.60.1-2010042810 Current version: 2010.06.10 15:24 .../lua60.1 is the texroot. ../lua60.1/tex/lua60.1 ^^^ How can I reproduce that? 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 ___ ___ 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 ___