- dev-context - NTG Mailing Lists

should texexec abort if write18, \runMP* needed but not set?
by Sanjoy Mahajan 12 Jun '09

12 Jun '09

In testing a recent ConText (with texlive2008) using my math textbook, I noticed that the problem backgrounds were not placed correctly. Below is a minimal test file where no background shows up. Eventually I figured out the cause: The defaults are \runMPgraphicsfalse and \runMPTEXgraphicsfalse and shell_escape = f (in texmf.cnf). Setting them all true fixed the backgrounds. This is with ConTeXt ver: 2009.06.04 22:20 MKII (texlive 2008). Could/should texexec abort if runtime metapost is needed but write18 and \runMP* are not true? That way seems safer than silently producing a document different from what the user expects. The long-term solution is probably that it all work even if those variables are not true, but it is probably tricky to implement all the subprocess communication and coordination. -Sanjoy \setupcolors[state=start] % sly textbackground method from Aditya Mahajan (2006), "Homework % Assignments in CONTEXT", PracTEX Journal, No. 4. \definetextbackground [problembackground] [ mp=background:random, location=paragraph, width=local, ] \startuseMPgraphic{background:random} path p; for i = 1 upto nofmultipars : p = (multipars[i]); fill p withcolor 0.90white; endfor; \stopuseMPgraphic \chardef\kindofpagetextareas\plusone \starttext \startproblembackground \input tufte \stopproblembackground \stoptext

2 1

particular mpost label fails with recent ConTeXt
by Sanjoy Mahajan 12 Jun '09

12 Jun '09

With a recent ConTeXt, the following file (run with "mpost -mem=metafun test.mp") % use ConTeXt to typeset labels (needs -mem=metafun option) verbatimtex %&cont-en etex beginfig(100) % flow arrow label(btex $\displaystyle\buildrel \rm Flow \over {=\joinrel=\joinrel\Longrightarrow}$ etex, origin); endfig; end fails with: ! Unable to make mpx file. l.7 label(btex $\displaystyle\buildrel \rm Flow \over Transcript written on fig.log. The error in mpxerr.log is: ! Illegal unit of measure (pt inserted). <to be read again> = <argument> = \joinrel =\joinrel \Longrightarrow \buildrel ...mathrel {\mathop {\kern \zerocount #2 }\limits ^{#1}} l.14 {=\joinrel=\joinrel\Longrightarrow} $% It works with ConTeXt 2008.10.31. It fails with ConTeXt 2009.06.04 (with texlive2007 from Debian or with vanilla texlive2008).

3 3

setupbodyfont
by Wolfgang Schuster 11 Jun '09

11 Jun '09

Hi Hans, I run with my simplefonts module in two problems when I try to set the bodyfont, the regard math and fallback fonts and I was only to solve them by redefining of a few values. 1. I have to set the bodyfont at the same time when I set a individual font for serif, sans or mono. This works fine for the the three text style but not when I try to switch to a different math font, which is frozen with the first \setupbodyfont command and can only be changed when I the main fontclass (created with \registerfontclass in \definetypeface) and the style value for rm (I need the 'rm' style to allow e.g. ss as document style). Here is a example to illustrate the problem: \definetypeface[mainface][rm][serif][times][default] \setupbodyfont[mainface,ss,12pt] \definetypeface[mainface][ss][sans][helvetica][default] \definetypeface[mainface][tt][mono][courier][default] \definetypeface[mainface][mm][math][palatino][default] % comment/uncomment the following two lines to see how % the math font changes with/without these redefinitions \letvalueempty{@@tfmainfacedefault}% \undefinevalue{@f@st@rm}% \setupbodyfont[mainface,ss,12pt] %\definetypeface[mainface][mm][math][cambria][default] %\letvalueempty{@@tfmainfacedefault}% %\undefinevalue{@f@st@rm}% %\setupbodyfont[mainface,ss,12pt] \starttext text \rmtf regular \it italic \bf bold \bi bolditalic \sstf regular \it italic \bf bold \bi bolditalic \tttf regular \it italic \bf bold \bi bolditalic $$ c^2 = a^2 + b^2 $$ \stoptext 2. The fallback for the main style (i.e. \rmtf) is frozen too with the first \setupbodyfont line in the document with can be only reset when I undefine \newfontidentifier, a example for this is: \starttypescript [serif] [mainfont] \setups[font:fallback:serif] \definefontsynonym [Serif] [name:texgyrepagellaregular] [fallbacks=mainfont,features=default] \stoptypescript \definetypeface [mainfont] [rm] [serif] [mainfont] [default] \setupbodyfont[mainfont,rm] \definefontfallback [mainfont] [name:texgyretermesregular] [0x0065-0x0070] [force=yes] % The following line is necessary to enable the fallback font for the main % style after the bodyfont is set, if this isn't done the complete text % below is typeset in Pagella whereas e-p should be in Times \undefinevalue\newfontidentifier \setupbodyfont[mainfont,rm] \starttext abcdefghijkmnopqrstuvwxyz \stoptext I would prefer something documented (e.g. \setupbodyfont[reload,...]) which can be used to get the same effect as I did with my hacks because I like now my new font module, it's lot easier than direct method to set fallback fonts. TIA Wolfgang

2 5

Crash with luatex-fonts
by Khaled Hosny 10 Jun '09

10 Jun '09

The following sample would crash luatex using context distriputed luatex-plain format: %%% \font\arab="SimpleNaskhi.ttf:script=arab;language=dflt;mode=node;+init;+medi;+fina;+rlig;+liga;+mark"\arab \textdir TRT اللهِ \bye %%% (the font used http://code.google.com/p/raqm/source/browse/trunk/fonts/simplenaskhi/Simple…) With the message: %%% error: ...texmf/tex/plain/luatex-plain/luatex-fonts-merged.lua:7765: attempt to call field 'register_message' (a nil value) %%% It seems that fonts.register_message is not defined. Pressing enter after that will crash luatex: %%% luatex: ../../../source/texk/web2c/luatexdir/tex/linebreak.c:1660: ext_do_line_break: Assertion `varmem[((cur_p)+1)].hh.v.RH == 0+4+4+4+4+4+4+2+2+2' failed. Aborted %%% Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer

3 6

luatex beta 0.40.5
by Taco Hoekwater 10 Jun '09

10 Jun '09

Hi, I have just uploaded luatex 0.40.5 to the foundry server, and have committed the source code to texlive. What's new: * One of the internal print functions accidentally encoded its argument string to UTF-8 even though it was already UTF-8. * Some of the log and terminal UTF-8 output was gibberish. The archives can be downloaded from supelec as usual: http://foundry.supelec.fr/gf/project/luatex/ You could also check out the sources via anonymous svn: svn co http://foundry.supelec.fr/svn/luatex/tags/beta-0.40.5 Bugs and feature requests can be added to the issue tracker at http://tracker.luatex.org Have fun, Taco

1 0

removing BibTeX auxiliary files with --purgeall
by Oliver Buerschaper 10 Jun '09

10 Jun '09

Hello Hans and Taco, may I also add the request that temporary files created by BibTeX are deleted automatically by --purgeall? That is, *.blg *.aux It'll probably be wise to keep the *.bbl file :-) Although it is created automatically by the BibTeX run I need to tweak it manually at times ... Best wishes, Oliver P.S. I cannot test this with MkIV at the moment but MkII doesn't delete those files for sure ...

1 0

luatex beta 0.40.4
by Taco Hoekwater 09 Jun '09

09 Jun '09

Hi, I have just uploaded luatex 0.40.4 to the foundry server, and have committed the source code to texlive. What's new: * \the\textfont0 returned a number instead of doing a font switch. * The embedded MPlib is now 1.203. The archives can be downloaded from supelec as usual: http://foundry.supelec.fr/gf/project/luatex/ You could also check out the sources via anonymous svn: svn co http://foundry.supelec.fr/svn/luatex/tags/beta-0.40.4 Bugs and feature requests can be added to the issue tracker at http://tracker.luatex.org Have fun, Taco

2 1

MetaPost 1.203 announcement
by Taco Hoekwater 09 Jun '09

09 Jun '09

The MetaPost team is happy to announce a new release of MetaPost: ---------------------------------------------------------------------- MetaPost 1.203 ---------------------------------------------------------------------- The standalone distribution package and a win32 binary can be downloaded immediately from http://foundry.supelec.fr/gf/project/metapost/ This release will also be available from CTAN soon, and it will be included in the next TeXLive. The source package should compile normally on all systems that are capable of compiling a modern web2c-based TeX distribution. The win32 binary is intended for texlive or a similar web2c-based installation, this executable will *not* work for miktex. Of course, we welcome any comments (either good or bad) that you may have. Simply replying to this message is fine, but see the bottom of the message for a more formal way to report bugs and feature requests. ---------------------------------------------------------------------- What is new in MetaPost version 1.203: ---------------------------------------------------------------------- * Building version 1.202 for source required X11 headers to be installed. * Another infinite recursion trap added, now for erroneous vardefs with suffixes (reported by Nicola Vitacolonna). * Fix infinite loop recursion on integer overflow (reported by Nicola Vitacolonna, fix based on a hint from Dan Luecking). * In version 1.202, setting "job_name" from lua code caused a crash. * The "filename" field on the lua figure object in 1.202 was just the extension, instead of the whole file name. ---------------------------------------------------------------------- Legal notice / license / bug reports ---------------------------------------------------------------------- MetaPost is a system for producing graphics developed by John Hobby at AT&T, based on Donald Knuth's Metafont. The MetaPost home page is http://tug.org/metapost. MetaPost is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. The MetaPost development project is currently hosted at Supelec, http://foundry.supelec.fr/gf/project/metapost; please report bugs and request enhancements through there if possible. Alternatively, you can reach us through the <metapost(a)tug.org> mailing list as well. Have fun! Taco Hoekwater, for the MetaPost team, June 9, 2009.

1 0

luatex beta 0.40.3
by Taco Hoekwater 08 Jun '09

08 Jun '09

Hi, I have just uploaded luatex 0.40.3 to the foundry server, and have committed the source code to texlive. What's new: * A set of portability fixes for the AIX compiler from Vladimir Volovich. * A set of fixes to the synctex support. * A patch to the build script to prevent installed X11 headers from being required. * Some weave (web syntax) fixes from Manuel Pégourié-Gonnard. * A simplification in luatex.ch (it is now less verbose about the web2c-specific extensions) from Karl Berry. * A fix in the handling of UTF-8 (input) file names. * Hyphenation exceptions were case sensitive in 0.40.2. The archives can be downloaded from supelec as usual: http://foundry.supelec.fr/gf/project/luatex/ You could also check out the sources via anonymous svn: svn co http://foundry.supelec.fr/svn/luatex/tags/beta-0.40.3 Bugs and feature requests can be added to the issue tracker at http://tracker.luatex.org Have fun, Taco

1 0

use of \phantombox doesn't match its definition
by Sanjoy Mahajan 06 Jun '09

06 Jun '09

In trying to install the latest context on my system, I installed texlive 2008, then the 2009.06.04 context, and rebuilt the formats. Using texlive 2008 solved my problems with the Palatino fonts not being found (compared to when I was using the latest context with texlive 2007). However, the following file fails on my laptop, and on the live Context (also 2009.06.04, texlive 2008): \newbox\phantombox \def\lowest#1{\setbox\phantombox=\vbox{\vphantom{$\displaystyle{#1}$}}} \def\support{\copy\phantombox} \starttext \startformula \lowest{Q} \underbrace{\support Q}_{dx} \stopformula \stoptext The error is: ! Use of \phantombox doesn't match its definition. \lowest #1->\setbox \phantombox = \vbox {\vphantom {$\displaystyle {#1}$}} l.8 \lowest{Q} Changing all uses of \phantombox to \phantomboxff fixes the problem, so maybe there's a name clash, but I couldn't find it in the context source code. -Sanjoy

2 2