May 2006 - ntg-context - NTG Mailing Lists

project files searched for using TEXINPUTS
by Sanjoy Mahajan 17 May '06

17 May '06

In experimenting with projects, products, and components, I was tracing file searches (using Linux, teTeX 3.0 and kpathsea). >From the cont-eni.pdf manual (p. 26 of the PDF file), explaining more about components and project structure: > Many TEX implementations look for a file in all directories and > subdirectories when a requested file is not in the current > directory. This is not only time--consuming but may lead to errors when > the wrong file (a file with the same name) is loaded. > For this reason ConTEXt works somewhat differently. A file that is not > available on the working directory is searched for on the parent > directories. I agree with this reasoning. But as implemented, if the current and parent directories fail, ConTeXT will look in the TEXINPUTS search path. Is that the intended behavior when looking for project files? Probably not ideal for the project file, though maybe it is useful for the resulting environment file? For finding figures, the behavior is clear: look in the local (.) and then the global directories, and that's it. For finding files specified by \input, the behavior is also clear (use TEXINPUTS). So I wondered whether the intention for finding project files was also equally clear: look in . and in (grand)parent directories (I've increased the number of levels to three). Here's the test.tex file I used: \startcomponent blah \product null \project abcd \stopcomponent $ texexec -passon="-kpathsea-debug 32" --once test >& log $ grep abcd log | grep kpse_find kdebug:kpse_find_file: searching for ./abcd of type tex (from TEXINPUTS environment variable) kdebug:kpse_find_file: searching for ../abcd of type tex (from TEXINPUTS environment variable) kdebug:kpse_find_file: searching for ../../abcd of type tex (from TEXINPUTS environment variable) kdebug:kpse_find_file: searching for ../../../abcd of type tex (from TEXINPUTS environment variable) kdebug:kpse_find_file: searching for ./abcd of type tex (from TEXINPUTS environment variable) kdebug:kpse_find_file: searching for ../abcd of type tex (from TEXINPUTS environment variable) kdebug:kpse_find_file: searching for ../../abcd of type tex (from TEXINPUTS environment variable) kdebug:kpse_find_file: searching for ../../../abcd of type tex (from TEXINPUTS environment variable) kdebug:kpse_find_file: searching for abcd of type tex (from TEXINPUTS environment variable) The last search, for 'abcd', runs through the entire TEXINPUTS path. The other searches have directories specified, so they will look only in those directories. -Sanjoy `A society of sheep must in time beget a government of wolves.' - Bertrand de Jouvenal

2 3

xetex
by Hans Hagen 17 May '06

17 May '06

Hi, this is what texexec (latest version that i will upload) does with xetex: --xetex --xtx : run xetex and process xdv file afterwards using xdvipdfmx --xdv : run xetex and process xdv file afterwards using xdv2pdf when using dvipdfmx, graphics are analyzed using rlxtools --identify filename.suffix which assumes imagemagick's 'identify' to be present (i can integrate that in the resource log mechanism later); it will be run at runtime when needed, otherwise users need to manually create the associated rli files (i.e. whatever.jpg gets a whatever.jpg.rli file) later i will look into a combination of specials 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 -----------------------------------------------------------------

1 0

A few columnset questions
by Ehrt, Michael 17 May '06

17 May '06

Hi there, I've been experimenting a bit with columnset (thats THE one feature which will make me convert from LaTeX), and a few questions I have I couldn't find explained in the manuals... 1) Is it possible to put a rule between two columns with columnsets? (I know \startcolumns[n=2,distance=15pt,rule=on] does this, but I need certain columnset features). The only thing I came up with so far is \definecolumnset[example][n=3,distance=0pt] %n=3 instead n=2 \setupcolumnset[example][2][width=15pt] and then put the rule in an area defined for column 2. 2) Is there a way to set ny "dynamically" for a columnsetarea, for example, if the text/image/whatever put in the area runs over six lines, tell it to just use six lines automatically? 3) When using columnsetareas, is there a way to link them to a specific columnset? Like, I've got \definecolumnset[set1]... \definecolumnset[set2]... \definecolumnsetarea[one][both][x=2,y=1,nx=1,ny=10] This area pops up in both column sets, and the only way I got it from not showing up in set2 was doing \setupcolumnsetarea[one][both][state=start] \startcolumnset[set1] {...} \stopcolumnset \setupcolumnsetarea[one][both][state=stop] \startcolumnset[set2] {...} \stopcolumnset I would have expected a columnsetarea to be linked to a specific columnset, is this the case? Like in \definecolumnset[set1]... \definecolumnset[set2]... \definecolumnsetarea[set1][one][both][x=2,y=1,nx=1,ny=10] %area for set1 only \definecolumnsetarea[set2][one][both][x=3,y=5,nx=2,ny=5] %area for set2 only Maybe there's a parameter in definecolumnsetarea that does it, but I didn't find anything. And in the columns manual there's just one set being used... Cheers Michael

1 0

spurious space before section heading but only in pdf mode
by Sanjoy Mahajan 17 May '06

17 May '06

This file \starttext \section{a} hi \section{b} hi again \stoptext is fine in dvi mode (texexec a.tex). But 'texexec --pdf a.tex' is a bit off, with the "1 a" section heading indented about one character. Is it a pdfetex bug? $ texexec --version TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005 texexec : TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005 texutil : TeXUtil 9.0.1 - ConTeXt / PRAGMA ADE 1992-2006 tex : pdfeTeX, 3.141592-1.21a-2.2 (Web2C 7.5.4) context : ver: 2006.03.25 13:21 cont-en : ver: 2006.03.25 13:21 fmt: 2006.4.8 mes: english The only change from the distributed context version is Taco's suggestion of \def\maxreadlevel{4} in supp-fil.tex. -Sanjoy `A society of sheep must in time beget a government of wolves.' - Bertrand de Jouvenal

3 5

\startlines and whitespace
by frantisek holop 16 May '06

16 May '06

hi there, i am puzzled about the following issue. there's extra whitespace between the centered line and startlines, while when using \crlf, there is not. \startlines is an environment i guess (i come from latex) and some environments sometimes add extra whitespace in latex, if i recall correctly. when i use \nowhitespace between midaligned and startlines, the whitespace is smaller, but still there, depending on where the actual text is on the page. how can i get rid of the whitespace entirely? \starttext \startnarrower[3cm] \midaligned{test} \startlines There snores -- I mean sleeps -- my wife so frail. There snores -- I mean sleeps -- my wife so frail. \stoplines \stopnarrower \startnarrower[3cm] \midaligned{test} There snores -- I mean sleeps -- my wife so frail.\crlf There snores -- I mean sleeps -- my wife so frail. \stopnarrower \stoptext -f -- a kind word and gun gets you more than a kind word alone.

2 2

Reference for the \but command
by Jean Magnan de Bornier 16 May '06

16 May '06

Hello, Where can I find the list of all keywords recognized by the \but command to set up interaction? (Honest, I searched the manual!) thx -- Jean

4 6

ConTeXt, XeTeX for Linux and xdvipdfmx
by Ricard Roca 16 May '06

16 May '06

Hi, It seems that some things doesn't work well with ConTeXt and XeTeX for Linux. For example image inclusion (jpg, png, pdf) with \externalfigure or \useexternalfigure doesn't work, but does with xdvipdfmx \special's (\special{pdf: image ...}). Also, \setuppapersize doesn't work (e. g. \setuppapersize[A5][A5] does the same as \setuppapersize[A5][A4], being A4 the default). But \color seems to work well. Are these ConTeXt bugs (related to \special's) or Linux XeTeX-xdvipdfmx bugs? Thanks in advance, Ricard

2 1

Re: [NTG-context] some patches
by Dalyoung 16 May '06

16 May '06

> for xetex you really need to update because the backend driver has changed to xpdfmx Hans Dear Hans, Thank you for the reply. I'll upgrade to the latest version soon. By the way, I noticed one thing in the process of XeTeX-ConTeXt. In the previous version before may, "texexec --xtx file.tex" run and made file.xdv, and then finally produced file.pdf. But in the current version "texmfstart texexec --xetex file.tex" run and file.tuo - file.dvi - file.pdf are produced in the log file but file.pdf is not produced in the folder. "texexec --xtx file.tex" also produced pdf via *.tuo - *.dvi - *.pdf but figures in pdf format are appeared as blank space. Doesn't ConTeXt-XeTeX use *.xdv anymore? I'd like to upgrade from the beginning, TeX+ConTeXt update + XeTeX and test the same file. It makes me a little bit nervous. Thank you again. Dalyoung

2 1

Re: [NTG-context] some patches (clever ConTeXt installation)
by Maurice Diamantini 16 May '06

16 May '06

Le 16 mai 06 à 01:14, Hans Hagen a écrit : > Maurice Diamantini wrote:nment. >> >> Usually, one can build dynamicaly (default) variable environment >> at the start of a programm >> (i.e. in the same process and sub-process), then let the original >> environment untouch >> while ending the programm. > this is what > > texmfstart --tree=.... texexec .... > > does; it sets env vars specified in either setuptex.tmf in the path > mentioned as tree, or some specific tmf file; those tmf files are > platform independent. this is how i run multiple (different trees) > on one machine (say a web server); Thank you very much. So I can do a little "texexec" script, add its path in front of the global path (so that it will be found before any standard old ConTeXt distrib) and use the new "texexec" shell script as the main context executable as usualy. The main avantage over my previous proposal is that it doesn't even require adding a new path in the PATH environment variable (which already is quite accectable!). >> I don't know much about context, but if you use some texmfstart >> laucher, it could have >> the responsability of that job). >> In fact, I'd like to only have to add some PATH for using a >> personnal full ConTeXt >> distribution near another standard LaTeX (containing obolate Context) > this is what in regular distributions texmf-local is for Yes, but the texmf-local is part of a particular directory from a particular network or host. And I like to separate my own (full, independant, robust, ...) ConTeXt environmement from the several LaTeX distrib I use (e.g. my unix/osX account is mirror via rsync between hom, work, and another network. >> LaTeX will probably become again my main xTeX environment, but I'd >> like to be able >> to switch ponctualy to a recent ConTeXt distro, without hacking >> and breaking >> my main TeX environment. > in that case, just put the latest context in your main tree (unzip > cont-tmf in > texmf-local or so); that should work as always No, because of recent font (lm) probleme, I decided to keep a full context distrib (linuxtex.zip + macosxtex.zip + justtex.zip) in my personnal home directory. I positionned this environment with some "setuptex" variante before using context program (with all previous problems when comming back to LaTeX) >> Because the Makefile should work on all plateform (and in a year >> or two also if possible!) >> I use only the standard texexec (instead of texmfstart and path >> argument). >> But if you say texmfstart become the standard way: I'd switch to! > well, you can still use texexec.rb instead of texexec.pl and avoid > texmfstart; > it's just that then you need to keep an eye on when texexec changes Do you mean that "texexec.rb" is clever enought to guess its ows directory tree ? Great, that what I asked for ;-) (and if "texexec.rb"" becomme the standard texexec tool the problem is solved (no more need to do a small texexec" shell script) but... ... for context programme only, but what about other tools (metapost, mp2pdf...) >> Just a remark in that case: texmfstart seems a bad name, bacause >> not related to "ConTeXt" >> Why not simply "context" or "ctx" as the main ConTeXt tool?) > because i use it to run anything organized in a tree (e.g. > xsltproc); running context > progies i just part of the game Ok, I can always make an alias "ctx" for "texmfstart --tree=..." alias ctx=texmfstart --tree=/home/myHome/myLocl/fullcontext perhaps it solves all problem at a time! I'll try that in the next two week. Thank you very much, Maurice

1 0

Re: [NTG-context] new release
by nico 16 May '06

16 May '06

On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen <pragma(a)wxs.nl> wrote: > Hi, > > Today i'll upload a new release. Got big problems with the fonts that are no more found when using the ruby stuff. Since the unix stubs are crappy, I do this: ruby /usr/local/share/texmf-local/scripts/context/ruby/texmfstart.rb texexec.rb --pdf typefile.tex What's wrong? Here is the log: This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=cont-en 2006.5.8) 8 MAY 2006 19:55 entering extended mode (/usr/local/share/texmf-local/web2c/natural.tcx) **typefile.tex emergencyend (./typefile.tex ConTeXt ver: 2006.05.08 12:59 fmt: 2006.5.8 int: english mes: english language : language en is active <protectionstate 0> system : cont-new loaded (/usr/local/share/texmf-local/tex/context/base/cont-new.tex systems : beware: some patches loaded from cont-new.tex color : palette rollover is available ) system : cont-old loaded (/usr/local/share/texmf-local/tex/context/base/cont-old.tex loading : Context Old Macros ) system : cont-fil loaded (/usr/local/share/texmf-local/tex/context/base/cont-fil.tex loading : Context File Synonyms ) system : cont-sys loaded (/usr/local/share/texmf-dist/tex/context/user/cont-sys.tex (/usr/local/share/texmf-local/tex/context/base/type-exa.tex) (/usr/local/share/texmf-local/tex/context/base/type-syn.tex) (/usr/local/share/texmf-local/tex/context/base/type-enc.tex) (/usr/local/share/texmf-local/tex/context/base/type-siz.tex) (/usr/local/share/texmf-local/tex/context/base/type-map.tex) (/usr/local/share/texmf-local/tex/context/base/type-spe.tex) (/usr/local/share/texmf-local/tex/context/base/type-akb.tex)) bodyfont : 12pt rm is loaded language : patterns nl->texnansi:texnansi->1->2:3 nl->ec:ec->2->2:3 fr-> texnansi:texnansi->3->2:3 fr->ec:ec->4->2:3 de->texnansi:texnansi->5->2:3 de->e c:ec->6->2:3 it->texnansi:texnansi->7->2:3 it->ec:ec->8->2:3 pt->texnansi:texna nsi->9->2:3 pt->ec:ec->10->2:3 hr->ec:ec->11->2:3 pl->pl0:pl0->12->2:3 pl->ec:e c->13->2:3 pl->qx:qx->14->2:3 cz->il2:il2->15->2:3 cz->ec:ec->16->2:3 sk->il2:i l2->17->2:3 sk->ec:ec->18->2:3 sl->ec:ec->19->2:3 en->ec:ec->21->2:3 uk->ec:ec- > 22->2:3 us->ec:ec->23->2:3 agr->agr:agr->24->2:3 da->ec:ec->25->2:3 > sv->ec:ec- > 26->2:3 af->ec:ec->27->2:3 no->ec:ec->28->2:3 deo->ec:ec->29->2:3 > es->ec:ec->3 0->2:3 ca->ec:ec->31->2:3 la->ec:ec->32->2:3 ro->ec:ec->33->2:3 tr->ec:ec->34-> 2:3 fi->ec:ec->36->2:3 hu->ec:ec->37->2:3 loaded specials : tex,postscript,rokicki loaded \openout2 = `typefile.tui'. system : typefile.top loaded (./typefile.top specials : loading definition file tpd (/usr/local/share/texmf-local/tex/context/base/spec-tpd.tex specials : loading definition file fdf (/usr/local/share/texmf-local/tex/context/base/spec-fdf.tex) specials : fdf loaded ) specials : fdf,tpd loaded ) \openout0 = `typefile-mpgraph.mp'. \openout0 = `mpgraph.mp'. (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) systems : begin file typefile at line 146 (/usr/local/share/texmf-local/tex/context/base/pdfr-ec.tex) verbatim : file ./test-001.tex does not exist verbatim : file joke does not exist fonts : resetting map file list fonts : using map file: original-base fonts : using map file: ec-public-lm fonts : using map file: ec-base fonts : using map file: 8r-base fonts : using map file: t5-base fonts : using map file: original-ams-base fonts : using map file: original-ams-euler fonts : using map file: original-public-lm [1.1 Warning: pdfetex (file original-empty.map): cannot open font map file Warning: pdfetex (file original-base.map): cannot open font map file Warning: pdfetex (file ec-public-lm.map): cannot open font map file Warning: pdfetex (file ec-base.map): cannot open font map file Warning: pdfetex (file 8r-base.map): cannot open font map file Warning: pdfetex (file t5-base.map): cannot open font map file Warning: pdfetex (file original-ams-base.map): cannot open font map file Warning: pdfetex (file original-ams-euler.map): cannot open font map file Warning: pdfetex (file original-public-lm.map): cannot open font map file ] [2.2] systems : end file typefile at line 167 ) Here is how much of TeX's memory you used: 1168 strings out of 58787 21094 string characters out of 563686 4585586 words of memory out of 5529308 39652 multiletter control sequences out of 10000+100000 75349 words of font info for 38 fonts, out of 500000 for 2000 232 hyphenation exceptions out of 1000 47i,18n,54p,252b,773s stack positions out of 1500i,500n,5000p,200000b,5000s PDF statistics: 10 PDF objects out of 300000 0 named destinations out of 131072 5 words of extra memory for PDF output out of 65536 Warning: pdfetex (file ec-lmtt12): Font ec-lmtt12 at 600 not found Warning: pdfetex (file ec-lmr12): Font ec-lmr12 at 600 not found Output written on typefile.pdf (2 pages, 3101 bytes). Regards, BG

3 13