- ntg-context - Mailing Lists

What is the replacement for the 'stop_run' callback?
by Tad Ashlock 19 Oct '10

19 Oct '10

Hi All, I'm trying to update a ConTeXt module of mine. It does some data gathering during the ConTeXt run, and then processes it after the run is complete. This used to work last year: local id, err = callback.register('stop_run', new_stop_run_function) But now err is set to "callback 'stop_run' is frozen (actions performed at the end of a run)". I see from the mailing list archive that registering user callbacks was disallowed in February of this year (2010). I also saw some advice for installing other new user processing (like 'pre_linebreak_filter'), but no general advice for adapting to the lack of callbacks. ( http://archive.contextgarden.net/message/20100219.130524.b3857a0a.en.html) After trying various approaches for a couple of hours, I'm calling for help. :) Here's what I ended up with: \startluacode print('%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% TEST1') local function after_run (head, groupcode) print('%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% TEST2') return head, true end nodes.tasks.appendaction('finalizers','after','after_run') \stopluacode \starttext \input knuth \stoptext In the output, I see the TEST1 line, but not the TEST2 line. I don't know what "head" and "groupcode" are, but those seem to be the expected parameters for an action. I don't know why it returns "head, true", but that was recommended in a posting ( http://archive.contextgarden.net/message/20100410.005025.76ac9efd.en.html) I have no idea if 'finalizers' is the right parameter, but I didn't see any others that looked like it could be synonymous with 'stop_run'.

2 2

itemize
by Herbert Voss 19 Oct '10

19 Oct '10

An example from the documentation: \starttext \startitemize[1,packed] \head supported image formats in \PDFTEX \par \startitemize[a] \item png \item eps \item pdf \stopitemize \head non supported image formats in \PDFTEX \par \startitemize[continue] \item jpg \item gif \item tif \stopitemize \stopitemize \stoptext I get with mkIV (TeXLive2010) [...] systems : begin file zzzz.tex at line 3 ! Math error: parameter \Umathquad\displaystyle is not set. \mathematics ... #1\else \Ustartmath #1\Ustopmath \fi \dodosymbol ...bol \csname \??ss :#1:#2\endcsname [...] Herbert

5 11

entries in registerentry
by Steffen Wolfrum 19 Oct '10

19 Oct '10

Hi, I don't understand the concept of entries in registerentry :o( Say, you have this example: \starttext \placeregister[index] \page page 1 \setregisterentry[index] [entries:1={eins}, entries:2={zwei}, entries:3={drei}, label=range] \page page 2 text \page page 3 \finishregisterentry[index][label=range] text \stoptext Why does only have entries:3 the index range "2-4", both entries:1 and 2 are emtpy? What should I write in order to have all of those entries referering to the same "2-4"? Best, Steffen

2 1

How to wirte a registered trademark in mkiv?
by seasoul 19 Oct '10

19 Oct '10

Is there a built-in module to write a registered trademark: a R in a circle; or a TM in a circle?

2 1

quoted environment arguments
by Philipp Gesang 18 Oct '10

18 Oct '10

Hi, there’s a behaviour concerning how context handles forced quotes in command line arguments that I do not understand. ··· <example> ··················································· for i=-1,#environment.rawarguments do print(i, environment.rawarguments[i], environment.originalarguments[i]) end ·· </example> ··················································· Now run this as ‘test.lua’ with mtxrun: # mtxrun --script test.lua \"simple\" \"more complex\" Here I get the following output: ··· <result> ···················································· -1 texlua texlua 0 /home/kokytos/context/tex/texmf-linux/bin/mtxrun /home/kokytos/context/tex/texmf-linux/bin/mtxrun 1 --script --script 2 test.lua test.lua 3 "simple" simple" 4 "more more complex 5 complex" nil ·· </result> ···················································· Number 3 indicates that a quoted argument is fully unquoted iff it gets parsed into multiple arguments. It also leads to ‘Unbalanced quotes in argument ./simple"’ when used with the main ‘context’ script. It would make sense if you expect only args containing spaces to be explicitly quoted, though. I would propose a patch like the one I attached but I’m having difficulties testing locally modified copies of the core Lua files, so it remains untested. Philipp

1 0

Trouble with ConTeXt's project structure
by Stefan Müller 18 Oct '10

18 Oct '10

Dear list, I tried to set up a project of mine using the project structure propagated in the wiki [1]. Because I ran into some trouble I made the following small example (using MkIV, minimals 2010.10.14 13:14). %% project_mymag.tex \startproject project_mymag \environment env_mymag \product prd_year2004-01 \completecontent[criterium=all] \stopproject %% EOF %% env_mymag.tex \startenvironment env_mymag \setupindenting[medium, yes] %some random setup \stopenvironment %% EOF %% prd_year2004-01 \startproduct prd_year2004-01 \project project_mymag \component c_editorial \component c_article01 \stopproduct %% EOF %% c_editorial.tex \startcomponent c_editorial \product prd_year2004-01 \project project_mymag \chapter{Editorial} Dear reader... \stopcomponent %% EOF %% c_article01.tex \startcomponent c_article01 \product prd_year2004-01 \project project_mymag \chapter{First Article} This will be awesome... \stopcomponent %% EOF When I translate the project file I get what I want, e.g. 3 pages: first page "Editorial", second page "First Article", third page "Content". When I translate the product file I don't get "Editorial", "First Article" as expected, but "Content", "Editorial", "First Article". It seems as if context first typesets the project file without going down inside the products again, before typesetting the originally called project. When I translate one of the component files, lets say c_editorial.tex, I get "Contents", "Editorial" instead of just one page "Editorial". Again, it seems as if context first looks inside the project file (without going down) and only then typesets the component. Another case, same problem. If I drop the "product", i.e. I only have a project file including several components, the individual component files and an environment file, kind of the same problems appear. Translating the project file works well. Translating the component file c_editorial.tex results in a PDF with 4 pages (instead of one with "Editorial"): "Editorial", "First Article", "Contents", "Editorial". Context puts the whole project in the PDF and appends the component c_editorial... All this seems very strange to me, especially since a friend told me project structure works pretty well in his projects. I tested on two different machines (Windows Vista and Linux). Am I doing something wrong? Is this a bug or a feature? Thanks for your help in advance. Best wishes, Stefan. [1] http://wiki.contextgarden.net/Project_structure

2 2

MKIV on miktex
by luigi scarso 18 Oct '10

18 Oct '10

http://blog.miktex.org/post/2010/10/ConTeXt.aspx -- luigi

1 0

pictures in tabulate
by Thomas A. Schmitz 18 Oct '10

18 Oct '10

Hi all, I'm looking for a way to use pictures inside a tabulate environment. Unfortunately, newer versions of ConTeXt don't take the picture height into account. The following code gives a somewhat disappointing result both in mkii and mkiv: \starttext \starttabulate[|rw(3em)|p|] \NC YYY \NC ZZZ \NC \NR \NC XXX \NC \dontleavehmode \externalfigure[cow][frame=on,width=0.5\textwidth] \NC \NR \NC YYY \NC ZZZ \NC \NR \stoptabulate \stoptext Interestingly, this used to work a couple of years ago (last time I used this was 2008), but something must have changed. I tried putting the externalfigure into a \tbox, but no dice. Bug or feature? All best Thomas

2 2

\ReadFile in MkII vs MkIV
by Aditya Mahajan 18 Oct '10

18 Oct '10

Hi, In MkII, I can say \ReadFile{/tmp/filename} to read a file in /tmp directory. However, in MkIV, that fails because ReadFile is defined as \unexpanded\def\ReadFile #1{\doreadfile{any} {.}{#1}\donothing\donothing} so it explicitly searches in the . (current) directory. Bug or feature? Aditya

4 12

title settings
by Herbert Voss 17 Oct '10

17 Oct '10

If I understand the documentations correct, then the first command should set _all_ titles to slanted except the subsection. When I run this example the titles are always upright. \setupheads[textstyle=slanted] \setuphead[part][placehead=yes,color=blue] \setuphead[subsection][numberstyle=bold,textstyle=cap] \starttext \part{Teilebene} \chapter{Kapitelebene} \section{Abschnittsebene 1} \subsection{Abschnittsebene 2} \subsubsection{Abschnittsebene 3} \stoptext running TeXLive2010 with mkiv Herbert

3 4