- ntg-context - NTG Mailing Lists

mptopdf problem: he is broken and asking for fix
by Martin Bruchanov 27 Mar '13

27 Mar '13

Hi, I'm using: MPtoPDF 1.4.1 : running 'mpost --mem=mpost linejoin.mp' This is MetaPost, version 1.800 (kpathsea version 6.1.1dev) Attached sources give following error: This is MetaPost, version 1.800 (kpathsea version 6.1.1dev) 26 MAR 2013 22:04 **linejoin.mp (mpost.mp (/mnt/data/tex/texmf/metapost/base/plain.mp Preloading the plain mem file, version 1.004) ) (./linejoin.mp (./line_makro.mp) [1 ! This can't happen (degenerate spec). endfig->scantokens.extra_endfig;shipit; endgroup l.24 endfig ; I'm broken. Please show this to someone who can fix can fix So I hope, there is someone who can fix :) Best regards, BruXy -- Martin Bruchanov Skype : bruxytronics WWW : http://bruxy.regnet.cz/ GPG-Key : http://bruxy.regnet.cz/bruxy-gpg.key (0x8107ED53) Linked-In : http://www.linkedin.com/in/bruxy Google+ : http://gplus.to/BruXy

3 3

\setuphead [bodypartlabel=]
by Alan BRASLAU 27 Mar '13

27 Mar '13

\setuplabeltext [chapter=Chapter ] enables a label in chapter headings. Sometimes, one wants to have an unnumbered chapter-level structure that otherwise appears in the table of contents, bookmarks, marking, etc. without having to make many special definitions. One suggests: \definehead [NOchapter] [chapter] \setuphead [NOchapter] [incrementnumber=no,number=no,bodypartlabel=] \starttext \startNOchapter [title=Introduction] \stopNOchapter \startchapter [title=First chapter] \stopchapter \stoptext And then adding NOchapter to the contents combined list, to the bookmarks, and so on, not to speak about marking. Ugh! Much easier would be the occasional use of \startchapter [title=Introduction,incrementnumber=no,number=no,bodypartlabel=] \stopchapter but this does not work! One gets: "Chapter Introduction". That this does not work I suppose might be somewhat of a bug... Even better, more coherent, more logical, would be \startchapter [title=Introduction,incrementnumber=no,number=no,label=no] \stopchapter (Note that "label=no" is used for lists). This would also have the advantage of allowing the chapter labeltext to be defined for each language, rather than be empty, so that it could then be simply turned on or off. In fact, label=no would be the default setup. Alan

3 4

Rebuilding font cache fails
by Marco Patzer 26 Mar '13

26 Mar '13

Hi, rebuilding the font cache fails in the latest beta. I didn't check the last few beta, though. mtxrun --script fonts --reload ..beta/tex/texmf-context/scripts/context/lua/mtx-fonts.lua:173: attempt to index global 'arguments' (a nil value) Marco

2 1

\setupenumerations, alternative=serried is ignored when setting up multiple enumerations
by Tobias Columbus 26 Mar '13

26 Mar '13

Hi list, While learning the very basics of context, I stumbled upon the following bug: When I try to use \setupenumerations in the latest beta (2013.03.22 12:06) for multiple enumerations, the alternative=... is ignored for all but the first enumeration. A minimal example demonstrating what I mean is attached. This bug, however, seems not to be present in the TL version (2012.05.30) of context. I don't know if this is a well-known bug and apologize in advance if this happens to be the case. Tobias

3 3

\setupheadertexts [section]
by Alan BRASLAU 26 Mar '13

26 Mar '13

Hello, \setupheadertexts [chapter] will center the current chapter title (or abbreviated version using marking=) in the running page headers. However, how can one also put unnumbered chapter-level titles (\starttitle\stoptitle) in the running headers? \setupheadertexts [chapter,title] seems natural but does not work. Also, what seems to be a bug, the running text does *not* get reset to empty upon leaving the chapter. Below is a minimal illustration (nonworking as it is incomplete, only a snippet) \setupheadertexts [chapter] \starttext \startpart % lets have some structure... Some introductory text... \startchapter [title=Getting started] Some text... \stopchapter \page [yes] Some trailing remarks... % the header here still contains "Getting started" \stoppart \stoptext Alan

2 2

Re: [NTG-context] man pages for ConTeXt: looking for volunteers
by Sietse Brouwer 26 Mar '13

26 Mar '13

Sietse wrote: > 5. Lastly, I think it would be good to include a standard SEE ALSO > block at the end of each man page, to list all the scripts we have man > pages for. Hans wrote: >> sure, we can add stuff How about this? <seealsos> <seealso name="context">Compile a ConTeXt file or recompile ConTeXt.</seealso> <seealso name="mtx-babel">Convert LaTeX Babel codes for Greek into UTF-8</seealso> <seealso name="mtx-base">ConTeXt TDS Management Tool (aka luatools)</seealso> <seealso name="mtx-cache">Manage the ConTeXt and MetaTeX cache</seealso> <seealso name="mtx-chars">Generate MkII character tables</seealso> <seealso name="mtx-check">Check ConTeXt file for syntax errors</seealso>  <seealso name="mtx-colors">Show International Color Consortium table for a file</seealso> <seealso name="mtx-context"> (See `context`)</seealso> <seealso name="mtx-epub">Create ePub zip file</seealso> <seealso name="mtx-fcd">Convenience script for fast directory-changing</seealso> <seealso name="mtx-flac">Collect Flac albums in XML file</seealso> <seealso name="mtx-fonts">Inspect and manage the ConTeXt font database</seealso> <seealso name="mtx-grep">A simple Lua-based grep</seealso> <seealso name="mtx-interface">Lists of ConTeXt commands (for text editors)</seealso> <seealso name="mtx-metapost">Compile MetaPost to PDF</seealso>  <seealso name="mtx-metatex">MetaTeX process management</seealso> <seealso name="mtx-modules">Extract `%D`-style documentation from ConTeXt module source files</seealso> <seealso name="mtx-package">Merge: replace loadmodule(...) calls with module contents</seealso> <seealso name="mtx-patterns">Produce files for ConTeXt describing hyphenation patters</seealso> <seealso name="mtx-pdf">Inspect metadata and font info of PDFs</seealso>  <seealso name="mtx-profile">LuaTeX profiler</seealso> <seealso name="mtx-rsync">Rsync helper script</seealso> <seealso name="mtxrun">MetaTeX factotum: run scripts and get info</seealso> <seealso name="mtx-scite">Convert spelling dictionaries to SciTE Lua format</seealso> <seealso name="mtx-server">Simple webserver</seealso> <seealso name="mtx-texworks">TeXworks startup script</seealso> <seealso name="mtx-timing">Process timing data after `context --timing` run</seealso> <seealso name="mtx-tools">Tools to glob directories into XML</seealso> <seealso name="mtx-unzip">Simple unzipper</seealso> <seealso name="mtx-update">Updating script for ConTeXt minimals, used by first-setup.sh</seealso>  <seealso name="mtx-watch">Watch a file for changes</seealso> </seealsos>

2 2

Suggestion for bibtex: command to switch between upper and lower case for title
by Xenia 25 Mar '13

25 Mar '13

Dear context folks, I would like to have the possibility to change between upper and lower case in titles for bibliography items, e.g. for English and German items. This is controlled by the bst-files as described in [1]. But changing these files after an update is rather annoying. Is there maybe even such a function that I do not know? Thanks, Xenia [1] http://www.ntg.nl/pipermail/ntg-context/2011/059359.html

2 2

setups in the latest Context release
by Devendra Ghate 25 Mar '13

25 Mar '13

Hello Everyone I have been using the following setup (provided by Wolfgang on this list) to format my chapter headings till now. However, it does not work since I upgraded by context installation today. If the entire *\startlinealignment .... \stoplinealignment* block is copied outside the setups then it works fine. So the change must have been in the interface for *setups*. Please let me know if there has been a change OR I have made some kind of mistake. Thank you, Devendra Ghate ----------------------------- \startsetups[head:margin] \startlinealignment[left] \startframed [width=1cm, height=3cm, frame=on, align={flushleft,nothyphenated,verytolerant,low}] \headtextcontent \stopframed % \inmargin[location=outer,align={right}]{% \framed[% width=3cm, height=3cm, align={bottom,middle}, frame=on]{\headnumbercontent} } \stoplinealignment \stopsetups \defineheadalternative[margin][renderingsetup=head:margin] \definehead[dchapter][chapter] \setuphead[dchapter][alternative=margin] \starttext \dchapter{Inexpensive Monte Carlo} \stoptext -------------------------------- -- Cheers, Devendra.

2 1

structure: project, product, structureresetset, ...
by Alan BRASLAU 25 Mar '13

25 Mar '13

Hello, I have a *project* that consists of a book in 3 volumes. Each volume is a *part*. Each volume or part has a (recto-verso) title page. Each volume or part also has front and back matter: table of contents, bibliography, index, ... Each volume or part also has *appendices* Thus, I have 3 *products* corresponding to the three volumes. Each product has *components*: chapters, appendices, ... Now, I would like the second volume to know that it is Part II and the third volume to know that it is Part III. I would also like to continue the chapter numbering in succession in each volume: i.e. 1, 2, 3 in Part I; 4, 5, 6 in Part II; 7, 8, 9 in Part III. Furthermore, I would like the appendices to do likewise: i.e. A, B in Part I; C, D, and E in Part II; F in Part III. Of course, I need to specify in my *environment* \definestructureresetset [default] [0,0] [1] \setuphead [part] [sectionresetset=default,conversion=Romannumerals] But... how do I propagate the numbering from product to product, that is part to part? Everything was just fine when all of the parts were collected into a single product having a unique front and back matter and all of the appendices at the end... It should be simple, but sometimes I fail to see the obvious! :) Alan

2 1

upto current
by Hans Hagen 25 Mar '13

25 Mar '13

Hi, One these days there will be a first iteration of this years 'current' release. This has to do with the texlive code freeze. As usual the current is paired with a version of luatex and mplib, of which there also will be a frozen version soon. This year we also have luajittex. Among the biggest differences between this and the previous current are: - More low level tex code has been made mkiv compliant. This had a side effect of introducing bugs. As expected more flexibility an potential for extensions has not resulted in slower runs. - Some mechanisms have been rewritten, some even from scratch (a new table mechanism, multi columns). We tried to remain compatible but where possible inconsistencies have been removed. - Of course bugs have been removed also thanks to Wolfgang and others. Like before users have been very patient and willing to test. The updated wiki and good examples that show up on sites are an indication that mkiv has mostly replaced mkii. - There is some new math magic under the hood. We switched to tex gyre and latin modern open math as defaults. - Lua code has been optimized: leaner, meaner, less dependent, version 5.2 etc. There is more helper code available pending future extensions to mkiv. Basic code can be used in stock Lua. - The 2013 current performs significantly faster than previous versions and (certainly) on complex jobs mkiv outperforms mkii. Lots of time went into identifying and removing bottlenecks. - When luajittex is used, thanks to the faster virtual machine, mkiv benefits a lot: 20-490% faster runs are possible. I usually test with manuals I'm working on, but a nice base test is \dorecurse {1000} {test\page} which now runs 20% faster with stock luatex and 50% faster with luajittex. - The font database generator is made more efficient and unless you do a full reload take hardly any time to regenerate after an update. This means that updating betas is more convenient. In general all logging to the terminal and log file is faster due to several optimizations. - Some mtx scripts have been extended, some more will show up. - We ship a set of advanced scite lexers (tex, lua, cld, mp, w, xml, etc. plus a context setup) that can serve as benchmark for syntax highlighting context code. To some extent this also determines the way mkiv is coded. I probably forgot a lot. After the current is done, we can start thinking of what to do next. Here are some thoughts: - Improving the output routines. This is non-trivial. Maybe I'll rewrite the columnsets code. The mixed column figure placement can be improved too. - Some mechanism will get support for setups alongside commands, like sections and list related mechanisms already has. - Parts of the xml handling can be cleaned up, although the current code performs rather well already. - Support for sql might get more integrated into the core (a side effect of projects I'm working on). - I might pickup the metatex thread: a generic base with special purpose subsets of code. It might not be worth the trouble, but it's good to have a proper dependency tree. - I will continue making some of the Lua code more generic (maybe by introducing some additional namespaces). - I need to cleanup all the s-* files: namespaces, mkii->mkiv, etc. A tedious job. Clean up all mkiv presentation styles. (Something for rainy days or cold winter nights with stacks of new cd's to make that effort bearable.) - Play with a partial css simulator (relates to export), but only when I'm really bored or need it (getting css itself right is already enough of a challenge). - Pick up on ideas with respect to math dictionaries. Add some support for breaking large math formulas. Kick out more old code. - Play with alternative par builders, i.e. finally add the mkiv Lua parbuilder that I have around for years into the distribution. This relates to a drastic cleanup of expansion code in the luatex front- and backend. - Include some third party modules into the core distribution. - Remove bottlenecks in mkiv where possible (user input is needed for this). Then there are the documents: - Update the xml descriptions (Wolfgang has been working on this, and there is the wiki). - Finish the 'cld' manual (mostly done). - Update the 'xml' mkiv manual (doable, maybe users have examples too). - Finish the updated 'mathml' manual (done but needs checking but then I might overhaul the whole lot again). - Finish the more technical 'mkiv font' manual (tedious job but okay). - Pickup the 'stylistics' manual (also nice to do but a bit tedious). - Turn 'hybrid' into a more finished document (the second part of the history of mkiv/luatex). - Add more to the 'about' series (the third part). Of course this is too ambitious but it's good to remind myself that some work needs to be done. And ... users might have ideas of what needs to be done as well. 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 -----------------------------------------------------------------

14 32