March 2013 - ntg-context - NTG Mailing Lists

placefigure
by Hans Hagen 21 Mar '13

21 Mar '13

Hi, while fixing some buglets that showed up in the test suite I ran into: \starttext test \placefigure[somewhere:alpha][whatever]{alpha}{} test \placefigure[somewhere:beta] [whatever]{beta}{} test \placefigure[somewhere:gamma][whatever]{gamma}{} test \placefigure[somewhere:delta][whatever]{delta}{} test \placefigure{}{} in \in{figure}[whatever] bla bla \placenamedfloat[figure][*l*] \placenamedfloat[figure][gamma] \placenamedfloat[figure][beta] \stoptext maybe worth wikifying (bug will be solved in beta) ----------------------------------------------------------------- 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 -----------------------------------------------------------------

2 2

chapter titles
by H. van der Meer 21 Mar '13

21 Mar '13

I would like to put something directly after each chapter number, like so: Chapter 5 <add something everytime> Title of Chapter Is there an option for this? \setuphead? \setupheader? which parameter? I looked up the wiki, but it made me no wiser. Hans van der Meer

4 6

"Missing number, treated as zero" error when using \definefont with \define'd dimension
by Lars Huttar 21 Mar '13

21 Mar '13

Hello, I reported a Missing Number error back in December (thread at http://www.ntg.nl/pipermail/ntg-context/2012/070471.html) but got sidetracked on another issue before finding a resolution. Now I'm back to the Missing Number error, and I have a short example that reproduces it: \define\largefontsize{13pt} % Works fine: \definefont[SerifL][Arial at 13pt] % Leads to error: \definefont[SerifL][Arial at \largefontsize] % "Missing number, treated as zero" error thrown on the following line: \starttext \SerifL{Hello} \stoptext Note that the SerifL font definition works fine (no error) if I hard-code in "13pt" instead of using an intervening \largefontsize definition. But if I hard-code the point size, it would hamper the modularity of our font configuration and the use of modes in which different size fonts are used. Maybe \define is just the wrong command to use when creating an identifier for a specified dimension? I tried changing it to \def and the error went away! I looked up the documentation of \define (http://wiki.contextgarden.net/Command/define) and \def, and couldn't find any obvious difference, except that \def is TeX and \define is ConTeXt. The wiki page I just linked to mentions differences between MkII and MkIV, but this error occurs in both (in XeTeX and LuaTeX). Can someone help me understand why I should not use \define for this case? (Or in general, when I should not use \define?) Or does the problem lie somewhere else? Thanks, Lars

2 1

man pages for ConTeXt: looking for volunteers
by Mojca Miklavec 21 Mar '13

21 Mar '13

Dear users, In preparation of this year's TeX Live release, it would be nice to also revise man pages a bit. Hans just implemented auto-conversion of help into man pages for the lua scripts. So the options are described as they should be, but if there are any volunteers to help polishing out and provide either more extensive descriptions, examples, ... or overall improvements, you are invited to leave some feedback or provide some help (additional text/descriptions or syntax corrections). The old man pages are at http://svn.contextgarden.net/suite/man/ and the new (possibly still experimental) man pages are now part of ConTeXt (see doc/context/scripts). Mojca

4 3

problem with t-gnuplot.tex
by JIN Xiao-Yong 21 Mar '13

21 Mar '13

Using the new beta from context-minimal This is LuaTeX, Version beta-0.75.0-2013030308 (rev 4589) \write18 enabled. (/Users/jin/pkgs/ConTeXt/tex/texmf-context/tex/context/base/cont-yes.mkiv ConTeXt ver: 2013.03.20 21:07 MKIV fmt: 2013.3.21 int: english/english system > 'cont-new.mkiv' loaded (/Users/jin/pkgs/ConTeXt/tex/texmf-context/tex/context/base/cont-new.mkiv system > beware: some patches loaded from cont-new.mkiv ) system > files > jobname 'bulk_trans', input 'bulk_trans', result 'bulk_trans' fonts > latin modern fonts are not preloaded languages > language 'en' is active (bulk_trans.tex resolvers > modules > 'gnuplot' is loaded (/Users/jin/pkgs/ConTeXt/tex/texmf-modules/tex/context/third/gnuplot/t-gnuplot.tex loading > Gnuplot module ! Undefined control sequence. log system > tex > error on line 99 in file /Users/jin/pkgs/ConTeXt/tex/texmf-modules/tex/context/third/gnuplot/t-gnuplot.tex: Undefined control sequence ... <argument> ...:= \@@GNUPLOT@term@context@linejoin ; gp_use_dashed := \@@GNUP... \meta_start_extensions ...extensions("#1",\!!bs #2 \!!es )} l.99 \stopMPextensions ? This happens with context running on a file generated by gnuplot 4.6.1. I have been using context in the texlive 2012 without any problem.

3 2

Re: [NTG-context] Subjects on this list - general request
by Robert Blackstone 21 Mar '13

21 Mar '13

On 20 Mar 2013, at 19:46 , "Keith J. Schultz" <keithjschultz(a)web.de> wrote > > I see no advantage in your suggestion. just search the subject. > > As for the [***Spam***] that is inroduce by mail servers. A user should maybe remove > it to avoid it. But a nuisance, yes, a problem no. > > regards > Keith. and on 20 Mar 2013, at 19:21 , Mica Semrick <paperdigits(a)gmail.com> wrote > > > I would agree with the (no subject) or SPAM titles, but if your search tool > can't tell the difference between "\column, Bug in - " - "\column, Bug in > \column" and "Bug in \column" then you probably need to find a new search > tool. I subscribe to the list in non-digest format, e.g. I get every > email. I used to get it in digest, but I found that made my searching > tougher. I use gmail and have all the list messages skip my inbox and go > directly to a tag. This has helped a ton! > > -Mica > > Am 20.03.2013 um 16:12 schrieb Robert Blackstone <blackstone.robert(a)gmail.com>: > >> …. wouldn't it be a good idea to ask everybody to clearly state the subject of their message, preferably starting with the most important keyword, and in particular to avoid (no subject) or [***SPAM***], and similar things as subjects. ... >> .. Hi Mica and Keith, Thanks for your reaction. It is informative to hear your opninon. I did not want to start a discussion -- it was rather a "cri de coeur" born out of frustration -- so I will leave it at this. Best regards, Robert

1 0

Breaking ligatures
by Idris Samawi Hamid ادريس سماوي حامد 20 Mar '13

20 Mar '13

Dear Knights, What is the canonical way to break a ligature in MkIV? The canonical TeX way, e.g. f{}i does not work if the feature liga=yes. The zero-width joiner or non-joiner will do it but that seems ad hoc or abusive ;-) since those are really for cursive scripts like Arabic and Syriac. Best wishes Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

3 3

date handling maltreated?
by H. van der Meer 20 Mar '13

20 Mar '13

Trying to do some date and time processing myself, I ran into problems caused by ConTeXt makeing it incompatibel with the original plain TeX itself! In the TeX-book, Appendix B one finds <citation> (Some parameters are set by TeX itself as it runs, so it is inappropriate to initialize them: \time, \day, \month, and year are established at the beginning of a job; .. </citation> Now the results in ConTeXT with a minimal example, put into the log for easier copying into the mail: \starttext \writestatus{}{\meaning\date -> \date} \writestatus{}{\meaning\day -> \the\day} \writestatus{}{\meaning\month -> \month WHY NOT monthname?} \writestatus{}{\meaning\year -> \the\year} \writestatus{}{\meaning\time -> \the\time} \stoptext Result: > \time-> \time > \protected macro:->\dodoubleempty \syst_converters_date -> \date > \day-> 20 > macro:#1->\ctxcommand {monthname(#1)}-> \labeltext {unknown}RROR > \year-> 2013 > \time-> 982 I strongly ask that ConTeXt abstains from changing the definition of \month and reverts to the exact result as given by plain TeX, i.e. a number in the range [1-12]. Because the change makes it impossible to do calculations on the month. Hans van der Meer

3 2

etexshow and generation of cont-en.xlm (cont-XX.xml)?
by Jonathan Barchi 20 Mar '13

20 Mar '13

Hi all, I'm using the emacs package etexshow to provide a quick ConTeXt command reference in EMACS. This utility parses the interface file cont-en.xml (for english, in my case) and uses the contents to provide a basic dictionary of available commands. In the documentation for etexshow, there is a reference to being able to generate a complete interface description (the aforementioned xml file) like so: ";; There is still an xml-file shipped with this code. Usually you would ;; generate the xml-file with 'texexec'ing the file setupe.tex. Then you ;; will get the cont-en.xml file that can (could) be used as an input for ;; this etexshow. But for now, this won't work. It will work rsn." It is not clear whether that file (setupe.tex or setup.tex) is/was supposed to be shipped with etexshow or was supposed to be a part of context. I've searched and found a few references to this problem, but never a definitive answer, so if anyone knows the answer to these questions I would love to know!! 1. Is the referenced setup(e).tex a file that was previously shipped with ConTeXt - presumably mkii since the author refers to texexec - or would this be something the author would have included with etexshow itself? 2. Is the interface file, e.g. cont-en.xml, auto-generated from all of the defined macros in ConTeXt, or is that file hand-written as metadata to accompany the source-code definitions? 3. Since self-documentation is a goal of the project, is it possible to generate something akin to the interface file that presents a snapshot of all commands known to context at a given time, for use in things like etexshow or other tools? If so, is it possible to do this with modules loaded to see what they additionally define? Thanks in advance for any help! I'm hoping to use any information I get to update etexshow, if possible, and maybe update the ConTeXt support in AUCTEX as well. I think it would be really cool if AUCTEX could reach out at compile or run time and pull in macro definitions from the installed environment, for example. Best, Jon

4 5

framedtext and margin
by H. van der Meer 20 Mar '13

20 Mar '13

As can be seen in the following example, within an itemized list the framedtext sticks out to the right, instead of having its right edge aligned with the outer ones. Is there a simple remedy or is it an unwanted effect? I would like the right edges line up perfectly. Hans van der Meer \starttext \startframedtext[width=local]\input tufte\stopframedtext Before list. \startitemize \startitem item one\stopitem \startitem item two\startframedtext[width=local]\input tufte\stopframedtext\stopitem \startitem item three\stopitem \stopitemize After list. \startframedtext[width=local]\input tufte\stopframedtext \stoptext

3 2