April 2015 - ntg-context - NTG Mailing Lists

new features
by Hans Hagen 22 May '16

22 May '16

Hi, (mostly for Thomas) In the next beta: When you include files in another file (using xmlinclude) we now register what gets included. There are two new commands: \xmlinclusion{#1} : the current inclusion \xmlinclusions{#1} : a list of inclusions the first one backtracks till it find a name and the second one will locate the root if needed. This option can be handy for tracing (i.e. seeing where input comes from). Another addition is that \definemode[something][keep] define an undefined mode; the keep makes sure that the already set value is kept (another option is 'yes'). Using defined modes (that is, set with: \enabledmode, \disablemode or \definemode) can be tested about twice as fast as undefined modes which can make a small difference when modes are tested lots of times. 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 -----------------------------------------------------------------

2 4

bibliography tool
by Gour 22 May '16

22 May '16

I was browsing docs in the contextgarden but not sure what is available for handling bibliography in ConTeXt today? Afaict, RefTeX is for LaTeX only, I recall there was(is). (My dev environment is Debian Linux/Emacs/AUCTeX.) Sincerely, Gour -- Whatever action a great man performs, common men follow. And whatever standards he sets by exemplary acts, all the world pursues.

6 12

MacOsX Mavericks and Luatex
by Pierre Bovet 19 May '16

19 May '16

Hi all! It seems that Luatex (0.76 2013/04/05) don't works with Mavericks? Thank's in advanced for your help and testimonies Best wishes -- Pierre Bovet Documentaliste technique | Chargé de sécurité CFST Tel : +41 (0) 26 401 61 56 Courriel : pierre67(a)me.com

11 27

Overlays as background in textbackground
by Marco Patzer 18 May '16

18 May '16

Hi, overlays are not displayed when used as a background for textbackground. Is this a bug or are overlays not supported? \defineoverlay [myoverlay] [\ssd Foo] \definetextbackground [mybackgroundColour] [background=color, backgroundcolor=gray] \definetextbackground [mybackgroundOverlay] [background=myoverlay] \starttext %% overlay works \framed [background=myoverlay, align=normal] {\input knuth\par} %% background=color works \startmybackgroundColour \input knuth \stopmybackgroundColour %% overlay is missing \startmybackgroundOverlay \input knuth \stopmybackgroundOverlay \stoptext Marco

5 6

halign broken
by Meer, H. van der 16 May '16

16 May '16

There seems something very much amiss with \halign in later ConTeXt versions. This typesets fine in PlainTeX and is an example taken from a textbook. \tabskip=1em\halign{% \hfil\it#\hfil&\hfil#\hfil&#&\hfil#\crA&B&C&D\cr} Also in contextversion 2012.05.30 (from a TeXlive distribution). But it fails at least in ConTeXt ver: 2013.03.20 10:34 MKIV and in ConTeXt ver: 2013.04.16 12:08 MKIV beta with the following error ! Only one # is allowed per tab. system > tex > error on line 5 in file fixedwidth.tex: Only one # is allowed per tab ... 1 \starttext 2 contextversion=\contextversion\par 3 \tabskip=1em 4 \halign{% 5 >> \hfil\it#\hfil&\hfil#\hfil&#&\hfil#\cr 6 A&B&C&D\cr} 7 \stoptext l.5 \hfil\it#\hfil&\hfil# \hfil&#&\hfil#\cr Why? How primitive it may be, I would like to use \halign now and then. Hans van der Meer

5 14

Re: [NTG-context] Hanging punctuation misalignment in footnotes
by Wolfgang Schuster 29 Mar '16

29 Mar '16

Am 22.02.2014 um 01:25 schrieb Jan Tosovsky <j.tosovsky(a)email.cz>: > On 2014-02-22 Jan Tosovsky wrote: >> >> when hanging in footnotes is enabled and the starting character is a >> punctuation, it is not protruded. However, the same character in the >> footnote body works fine. When both cases are close each other, it >> looks weird, see the screenshot: >> >> http://drifted.in/other/footnote_alignment.png >> >> Would it be possible make this behaviour uniform - either do not >> protrude it >> on the starting (left) edge or protrude it everywhere? >> > > A minimal example is available at > http://drifted.in/other/sample.tex There are two things which prevent the protrusion of the opening quote at the begin of the paragraph. One of these can be avoided with a change in the setup for footnotes but not the other without destroying the layout of the footnote text. One problem is the way how context places the footnote number in front of the text, by default context uses the \llap command to move the number into the left margin but this prevents also the protrusion of the opening quote. You can avoid this problem when you change the footnote setup to \setupnotation[footnote][alternative=margin]. <example> \definefontfeature[default][default][expansion=quality,protrusion=quality] \setupbodyfont[modern] \setupalign[hanging] \showframe[text][text] \starttext »Text« \noindent\hbox to 0pt{}»Text« \noindent\hbox to 0pt{\hss}»Text« \stoptext </example> The second problem which prevents the opening quote to protrude are the struts which are added by context at the begin and end of the footnote content and there is no way to disable them because they are needed to have proper spacing between the individual footnote texts on the same page. <example> \definefontfeature[default][default][expansion=quality,protrusion=quality] \setupbodyfont[modern] \setupalign[hanging] \showframe[text][text] \starttext »Text« \strut »Text« \stoptext </example> In the example below where I took care of these two problems (don’t take care of \begstrut in this way in your real document because it will cause many problems, it’s just for educational purpose) to show you this is what caused the unwanted output. <example> \definefontfeature[default][default][expansion=quality,protrusion=quality] \setupbodyfont[modern] \setupalign[hanging] \showframe[text][text] \setupnotation[footnote][alternative=margin,align=hanging] \starttext \let\begstrut\relax First Footnote.\footnote{»\input{ward}«} Second Footnote.\footnote{»\input{ward}«} \stoptext </example> Wolfgang

2 1

metafun
by Herbert Voss 24 Mar '16

24 Mar '16

It is a hard job to understand how all works ... I tried to create the first example of the documentation "Page 257 Anchors and layers", but failed with mkii and iv. The page is created, but without the graphical elements. Not using \startbuffer--\stopbuffer makes no difference. MTXrun | current version: 2010.07.30 11:35 Herbert \starttext \section {Anchors and layers} \startbuffer[a] \setMPpositiongraphic{X-1}{mypos:arrow}{to=X-2} \setMPpositiongraphic{X-2}{mypos:arrow}{to=X-3} \stopbuffer \startbuffer[b] In a previous section we saw that some \hpos {X-1} {words} were \hpos {X-2} {circled} and connected by an \hpos {X-3} {arrow}. As with most things in \CONTEXT, marking these words is separated from declaring what to do with those words. This paragraph is keyed in as: \stopbuffer \getbuffer[a,b] \stoptext

5 5

Re: [NTG-context] Protrusion cancellation by index term
by Hans Hagen 21 Mar '16

21 Mar '16

On 2/22/2014 2:38 PM, Jan Tosovsky wrote: > On 2014-02-22 Jan Tosovsky wrote: >> >> when a punctuated phrase appears at the beginning of the line, it is >> not protruded correctly when preceded by an index term. >> >> ... \index{foo}>Bar< ... >> >> A minimal example is available at >> http://drifted.in/other/sample.tex >> >> I cannot place the space character between these two parts (which >> helps) as I sometimes need to join this and the previous phrase with >> the non-breaking space. >> > > It is more serious issue than expected. Consider next two variants: > > (1) sentence, \index{primary}>Primary< > (2) sentence,\index{primary} >Primary< > > When the line is broken after a comma: > ad 1) starting guillemet is not protruded > ad 2) ending comma is not protruded > > When \index is surrounded by spaces from both sides, the space is rendered > at the beginning of the next line (resulting in 'indenting'). > > :-S > > I'd be grateful for ignoring any non document content preceding punctuation > to avoid its influence on protrusion. well, think of it like this: [something]<text>[something else] with [something] being bound to < ... so that is then the boundary of the word, not < ... i might know a solution (but such -major- changes have to fit into my schedule) 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 -----------------------------------------------------------------

2 1

Setting expansion depth limit for metapost
by Michal Suszko 18 Feb '16

18 Feb '16

I'm preparing quite long presentation -- nearly 3000 sides, 900 figures (500 distinct PNG files). I'm using ConTeXt MkIV installed using minimals (2010.03.12 19:49). Recently I'm hitting MetaPost capacity limit on expansion depth: !mplib : mp terminal: ! MetaPost capacity exceeded, sorry [expansion depth=10000]. Increasing expand_depth in texmf.cnf and regenerating formats with context --make doesn't help. expansion depth is still at 10000 in error message. texmf.cnf in texmf-local I've changed is reported by context as first one in log line starting with "mkiv lua stats : used config path" What am I missing? Michal

3 5

Supported architectures for minimals (any ppc users out there?)
by Mojca Miklavec 06 Feb '16

06 Feb '16

Hi, I would suggest dropping support for linux-ppc for the ConTeXt distribution unless somebody objects. I'm surprised about the number of ppc users on Mac (and would be curious to get more off-list feedback from those still using it). TeX Live planned to drop support this year, but it seems that it's staying for now. We are currently cross-compiling the binaries, but at the moment both luajittex and metapost compilations seem to be broken. We also don't seem to have any kfreebsd or sparc-solaris users, but as long as their builders enjoy supplying the binaries, that's fine by me ;) On the other hand I need to sit down one day and fix support for cygwin. I'm sorry that this didn't happen yet. Mojca

2 3