- ntg-context - Mailing Lists

List of bugs and quirks
by Marco Patzer 27 Mar '13

27 Mar '13

Hi Hans, > maybe after the current is made (which happens sometime within the > next two weeks) > > best make sure that we have no serious bugs (experimental features apart) I think it's better to start a new thread for this issue. I maintain a small list of bugs and quirks which I would like to share. I don't know if the issues are considered bugs or not. I posted most of them to the mailing list at some point, but AFAIK they have not been fixed for whatever reason. Usually there are simple workarounds or I have some code which fixes the issue. Others are still unresolved. Act upon as you see fit. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %% Wrong spacing in \unit when no number is given \starttext \starttabulate \NC wrong spacing \EQ (\unit{micro mol}) \NC\NR \NC spacing OK \EQ (µmol) \NC\NR \NC spacing OK \EQ (3\,µmol) \NC\NR \NC spacing OK \EQ (3 \unit{micro mol}) \NC\NR \NC spacing OK \EQ (\unit{3 micro mol}) \NC\NR \stoptabulate \stoptext %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %% Newline after \placelegend fails \starttext \startplacelegend \startcontent Foo \stopcontent \startcaption Bar \stopcaption \stopplacelegend \stoptext %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %% way setting does not work in \setupcaptions %% The way setting cannot be applied globally to all floats using %% \setupcaptions. For the prefix value it works. \setupblackrules [width=4cm, height=1cm] %% prefix is applied, way is not \setupcaptions [prefix=no, way=bytext] %% prefix and way are applied %% \setupcaption %% [figure, table] %% [prefix=no, %% way=bytext] \starttext \dorecurse{2}{% \startchapter [title=Chapter] \dorecurse{2}{% \startplacefigure \blackrule \stopplacefigure \startplacetable \blackrule \stopplacetable} \stopchapter} \stoptext %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %% Wide descriptions protruding into the margin \definedescription [description] [alternative=hanging, width=broad] \starttext \startdescription{conclusion that} \input knuth \stopdescription \startdescription{conclusion that the designer of a new system must not only be literally} \input knuth \stopdescription \stoptext %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %% interaction mode focus=current does not work for footnotes and floats \setupinteraction [state=start,focus=standard] \starttext \in{figure}[foo] \startplacefigure [reference=foo] \stopplacefigure \stoptext %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %% the \stop… line of database module environment must not be indented, %% spurious line otherwise \usemodule [database] \defineseparatedlist [CSV] [before=\bTABLE, after=\eTABLE, first=\bTR, last=\eTR, left=\bTD, right=\eTD] \starttext %% indentation with spaces works \startCSV alpha, 10 beta, 20 gamma, 30 \stopCSV %% indentation with tabs produces spurious extra line \startCSV alpha, 10 beta, 20 gamma, 30 \stopCSV %% some weird indentation works, but looks awkward \startplacetable \startCSV alpha, 10 beta, 20 gamma, 30 \stopCSV \stopplacetable \stoptext %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %% MetaPost Location throws error \startuseMPgraphic{foo} %% works %% fill Field[Header][Text]; %% error fill Area[Header][Text] shifted Location[Header][Text]; \stopuseMPgraphic \starttext \useMPgraphic{foo} \stoptext %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Marco

2 5

userpagenumber
by Thomas A. Schmitz 27 Mar '13

27 Mar '13

Hi, shouldn't this work? \setupuserpagenumber[number=34] \starttext \dorecurse{20}{\userpagenumber \page} \stoptext I must admit that I'm pretty confused about pagenumbering; there are too many options of \setup...pagenumber and \setup...pagenumbering for my simple brain now, and I often don't know which is supposed to do what. All best Thomas

4 7

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

Hiding text
by Procházka Lukáš Ing. - Pontex s. r. o. 25 Mar '13

25 Mar '13

Hello, is it possible to define a start-stop command to hide text within? Something like: \definestartstop[Hidden][before=\starthiding,after=\stophiding] TIA. Lukas -- Ing. Lukáš Procházka [mailto:LPr@pontex.cz] Pontex s. r. o. [mailto:pontex@pontex.cz] [http://www.pontex.cz] Bezová 1658 147 14 Praha 4 Tel: +420 244 062 238 Fax: +420 244 461 038

4 6

Nabla operator appears italic in formula
by Xenia 24 Mar '13

24 Mar '13

Dear context list, using the nabla symbol ∇ in formulas, I wondered why it looks italic and not upright as for example in [1]. I attach an example. Thanks, Xenia [1] https://en.wikipedia.org/wiki/Nabla_symbol

3 4

setupinterlinespace in \startquotation\stopquotation
by Alan BRASLAU 24 Mar '13

24 Mar '13

Hello, It can be quite common to typeset long quotations in a smaller typeface. The following minimal example is somewhat problematic: ------------------------------------------------------ \setupquotation [style=\tfx\setupinterlinespace] \starttext \startquotation \input tufte \input tufte \input tufte \stopquotation \stoptext ------------------------------------------------------ The interline spacing is wrong for the last paragraph. Adding a \par in the input before \stopquotation puts the right quotation closing mark on a newline. I suppose that the common practice is *not* to use explicit quotation marks when typesetting such long quotations in smaller typeface. In this case, setting left=,right= and explicitly putting a \par would work. However, if one wants to have quotation marks, this is no good. And placing an explicit \par is not very elegant, either. Nor does it seem that \switchtobodyfont[] does any better. Maybe the solution is simple but I have not found it... Alan

2 1

setupquotation and setupquote
by Alan BRASLAU 24 Mar '13

24 Mar '13

Hello, quotation is linked to quote. Indeed, we have in typo-del.mkiv \definedelimitedtext [\v!quote][\v!quotation] However, when the user then changes options using \setupquotation, \startquote\stopquote also gets modified. In the minimal example below, it is necessary to uncomment \setupquote in order to restore normal quote text. I believe that this to be a bug (and not a feature). \setupquotation [style=slanted] %\setupquote [style=normal] \starttext Tufte: \startquotation \input tufte \stopquotation Ward: \startquote \input ward \stopquote \stoptext

1 0

Framed: Individual background offsets
by Marco Patzer 23 Mar '13

23 Mar '13

Hi, how can I set individual offsets for the background, similar to loffset, roffset, etc.? \defineframedtext [foo] [frame=off, offset=none, backgroundoffset=1cm, %% backgroundloffset=1cm, %% there is no backgroundloffset background=screen] \starttext %% backgroundoffset is applied on all four sides \startfoo \input ward \stopfoo \input knuth %% this is what I'm aiming for \startnarrower [-1cm] \startfoo [backgroundoffset=0cm, loffset=1cm] \input ward \stopfoo \stopnarrower \stoptext Marco

2 2

different page background for chapter title page
by Thomas A. Schmitz 23 Mar '13

23 Mar '13

Hi all, I'm sure there must be a solution for this, but I haven't been able to find it yet: I want my chapter titles typeset in a sort of frame which will span the entire page, not only the text area, so I guess the easiest way to do that would be a page background. How can I set up a background that will appear only on the title page, in addition to the regular background? Bonus question: I also want the color schemes of both backgrounds to be different in every chapter, so the solution should make this possible. The example is a bit silly, but it shows what I'm looking for, I hope. Thanks, and all best Thomas \setuplayout [header=0cm, topspace=1.625cm, footer=0cm, width=fit, height=fit] \definecolor [color:background] [r=0.86,g=0.61,b=0.54] \definecolor [color:title] [r=0.91,g=0.75,b=0.7] \startuseMPgraphic{background:normal} StartPage ; numeric h ; h = 10mm ; z[1] = ulcorner Page ; z[2] = urcorner Page ; z[3] = z[2] shifted (0, -h) ; z[4] = z[1] shifted (0, -h) ; path p ; p = z[1] -- z[2] -- z[3] -- z[4] -- cycle ; fill p withcolor \MPcolor{color:background} ; StopPage ; \stopuseMPgraphic \defineoverlay [background:normal] [\useMPgraphic{background:normal}] \startuseMPgraphic{background:title} StartPage ; numeric h ; h = 10mm ; z[1] = ulcorner Page shifted (0, -1.5*h) ; z[2] = urcorner Page shifted (0, -1.5*h); z[3] = z[2] shifted (0, -h) ; z[4] = z[1] shifted (0, -h) ; path p ; p = z[1] -- z[2] -- z[3] -- z[4] -- cycle ; fill p withcolor \MPcolor{color:title}; StopPage ; \stopuseMPgraphic \defineoverlay [background:title] [\useMPgraphic{background:title}] \setupbackgrounds[page][background={background:normal,background:title}] \starttext \startchapter[title=One] \input tufte \page \input knuth \stopchapter \startchapter[title=Two] \definecolor [color:background] [r=0.82,g=0.85,b=0.68] \definecolor [color:title] [r=0.86,g=0.88,b=0.76] \input tufte \page \input knuth \stopchapter \stoptext

2 2

cc-icons
by Hans Hagen 23 Mar '13

23 Mar '13

Hi, new in the distribution \usesymbols[cc] \starttext \showsymbolset[cc] \symbol[cc][cc-by-sa-nc] \stoptext ----------------------------------------------------------------- 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 -----------------------------------------------------------------

1 0

synctex problem
by Ulrike Fischer 23 Mar '13

23 Mar '13

Is it possible to tell context to create a .synctex file instead of a .synctex.gz? (Or alternativly does someone know how to get sumatra (on windows) to handle a synctex.gz?) -- Ulrike Fischer http://www.troubleshooting-tex.de/

2 2

redone language frequencies
by Hans Hagen 23 Mar '13

23 Mar '13

Hi, As I needed it for a (long-term) manual I redid \averagewidth: \mainlanguage[de] \hsize65\averagecharwidth \normalexpanded{\inleft{\the\hsize}} (not that german but anyway) \input ward \par Frequency tables are now in lang-frq-<code>.lua so feel free to come up with more. (no beta uploaded yet) 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 -----------------------------------------------------------------

1 0

bibliography (interaction)
by Alan BRASLAU 23 Mar '13

23 Mar '13

Hello, 1. Is there some way to enable interaction with bibliographies? (i.e. hyperlinks from the citations to the list.) 2. Can one create an index of author names, for example, listing the pages of citations? Alan

3 6

\recurselevel inside \bTABLE\eTABLE
by Willi Egger 22 Mar '13

22 Mar '13

Dear all, I should prepare a form with a table. The table rows should be numbered. How can I get get this done by using \recurselevel. In the attached minimal example all rows are numbered with 0. \starttext \subject{bTABLE--eTABLE: recurse creates rows} \bTABLE \dorecurse{3} {\bTR \bTD \recurselevel \eTD \eTR} \eTABLE What do i do wrongly here? knd regards Willi

5 9

Fwd: [NTG-leden] Fwd: EuroBachoTeX 2013: Communication and typography
by Willi Egger 22 Mar '13

22 Mar '13

Dear friends! It looks likely that we will have again a great conference in Bachotek: the Euro-BachoTeX 2013. -- So please to consider the community there! Kind regards Willi Egger Secretetary CG Begin forwarded message: > From: Willi Egger <w.egger(a)boede.nl> > Subject: [NTG-leden] Fwd: EuroBachoTeX 2013: Communication and typography > Date: March 22, 2013 9:44:15 PM GMT+01:00 > To: NTG-leden <ntg-leden(a)ntg.nl> > Reply-To: ntg-secretaris(a)ntg.nl > > Besten allemaal, > > hm, dat lijkt weer een fijne conferentie te worden! Meld je aan! > > Vriendelijke groeten > > Willi Egger > > Begin forwarded message: > >> From: org-ebt2013 <president(a)gust.org.pl> >> Subject: EuroBachoTeX 2013: Communication and typography >> Date: March 21, 2013 11:38:12 PM GMT+01:00 >> To: Willi Egger <w.egger(a)boede.nl> >> Reply-To: Jerzy.Ludwichowski(a)umk.pl >> >> AND NOW IN ENGLISH :-) (SORRY!) >> >> Dear Friend-in-TeX, >> >> >> coming soon is the 2013 EuroTeX conference, numbered 21, joint with the >> 21st BachoTeX conference. At this wiriting, it is the 21st of March, the >> first full day of spring in the northern hemisphere. >> This must be a meanigful coincidence! >> >> At the moment the weather outside doesn't support let's-have-some-fun-time >> at the lake kind of thinking but you definitely should do so. We give you the >> organizers weather guarantee for BachoTeX. >> >> The conference theme is “Communication and Typography”, for the motivation >> see the call for papers (http://www.gust.org.pl/bachotex/2013/cfp) >> >> We already have promises of presentations which will deal with various >> aspects of the theme, but as always, there will be presentations with >> interesting TeX-and-friends as well as fonts-related content plus >> a lot of fun events. >> >> Building on last year's success, we plan hands-on workshops: calligraphy >> applied to initials, linocut with color prints and making boxes with bookbinding >> techniques. >> >> Of course, we will have a concert (flamenco!) and a bonfire with singing and music, >> and surely – the conference dinner. >> >> The current conference info is available at http://gust.org.pl/bachotex/2013. >> >> Please do respond to the call for papers mentioned above with a contribution, >> however small. Many thanks in advance! >> >> Additional information, including the presentation abstracts and schedule, >> will be posted on the conference page as it will become available. >> >> See you in Bachotek! >> >> Jerzy Ludwichowski >> (for the organizers) >> >> P.S. Apologies if that reached you more than once or if you are already >> registered. > > _______________________________________________ > NTG-leden mailing list > NTG-leden(a)ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-leden

1 0

widowpenalty
by Meer H. van der 22 Mar '13

22 Mar '13

Is the \widowpenalty for avoiding short single lines at the top of the page functional in ConTeXt? Or is there another setup to be done? I find a situation where \widowpenalty=10000 doesn't make a difference. But it is not easily decided if the TeX-engine could have done nothing in this special case or if the parameter is not functional. Hans van der Meer

2 1