[NTG-context] \setupmathematics with stylealternative not working

2019-02-21 Thread Mikael P. Sundqvist
Hi, It seems that, with the latest beta, the \setupmathematics with stylealternative is not working. I tried \setupbodyfont[lucidaot] \setupmathematics[stylealternative={calligraphic}] \starttext \startTEXpage[offset=3bp] $\mathcal A$ \stopTEXpage \stoptext and got the attached output lcm.png.

[NTG-context] Latest changes in some size registers

2019-02-21 Thread Martin Bruchanov
Hi all, I have some very condensed documents which should fit on one page: http://gnulinux.guru/bash_cheatsheet.pdf Without any major change in style definition, there is more space around sections or itemize: http://gnulinux.guru/bash_cheatsheet_diff.pdf Source code is here: https://githu

Re: [NTG-context] markdown module vs pandoc

2019-02-21 Thread Gour
On Thu, 21 Feb 2019 18:50:41 +0100 Pablo Rodriguez wrote: > sorry for my delayed reply. No problem - there is no rush here. ;) > I’m still behind the environment itself, although I realized that > these may not be relevant to everybody. I store the new commits in a > private repository. Aha...

Re: [NTG-context] Frame

2019-02-21 Thread Marco Patzer
On Thu, 21 Feb 2019 18:24:29 +0100 Wolfgang Schuster wrote: > > \startprettyblock > >\noindentation > > You don’t need \noindentation when you add “next” to the indenting > options. That's even better (meaning cleaner source). I didn't know that option. Marco

Re: [NTG-context] markdown module vs pandoc

2019-02-21 Thread Pablo Rodriguez
On 2/19/19 2:22 PM, Gour wrote: > On Mon, 18 Feb 2019 17:08:44 +0100 Pablo Rodriguez wrote: > [...] >> I convert Markdown to XHTML and then I compile the XML sources with >> ConTeXt. > > I've tried it and it works nicely. The possibility to have one-source-does-all > is tempting. ;) > > Now I wo

Re: [NTG-context] Frame

2019-02-21 Thread Wolfgang Schuster
Marco Patzer schrieb am 21.02.19 um 12:19: On Thu, 21 Feb 2019 10:50:21 + Ursula Hermann wrote: Here is my example: \setuppapersize[A5] \setupcolors[state=start] This is the default, no need to start the colours any longer. {\framed [width=10cm, background=color,backgroundcolor

Re: [NTG-context] Pretty printer for matlab

2019-02-21 Thread Otared Kavian
Hi Marco, Thanks! I hadn't tries [syntax=scilab], but I just did it and it works exactly as expected! However I could not edit the file scilab.vim which sits (on my machine) in /usr/share/vim/vim80/syntax/scilab.vim Meanwhile, out of curiosity I modified the two files buff-imp-l

Re: [NTG-context] Pretty printer for matlab

2019-02-21 Thread Marco Patzer
On Thu, 21 Feb 2019 15:10:27 +0100 Otared Kavian wrote: > Thanks for pointing to that module, which I didn't know because I > never use vim… I just tested it and seems fine, but I would need to > modify some of the keywords of Matlab in order to adapt them to > Scilab. However I didn't find where

Re: [NTG-context] Pretty printer for matlab

2019-02-21 Thread Otared Kavian
Hi Marco, Thanks for pointing to that module, which I didn't know because I never use vim… I just tested it and seems fine, but I would need to modify some of the keywords of Matlab in order to adapt them to Scilab. However I didn't find where those keywords are defined in the vim module. Best r

Re: [NTG-context] Pretty printer for matlab

2019-02-21 Thread Marco Patzer
On Thu, 21 Feb 2019 14:25:03 +0100 Otared Kavian wrote: > Is there a pretty printer file to typeset Matlab codes? How about Aditya's vim module? It supports Matlab: \usemodule [vim] \definevimtyping [matlab] [syntax=matlab] \starttext \startmatlab … \stopmatlab \stoptext Marco __

[NTG-context] Pretty printer for matlab

2019-02-21 Thread Otared Kavian
Hi all, Is there a pretty printer file to typeset Matlab codes? Actually I would like to modify such a file in order to define a typing environment to typeset portions of codes written for Scilab, which is a sort of free version of Matlab. Thanks for any comment and help: OK ___

Re: [NTG-context] Frame

2019-02-21 Thread Ursula Hermann
Hello Marco! Thanks a lot, that worked. Many regards Uschi -Ursprüngliche Nachricht- Von: ntg-context Im Auftrag von Marco Patzer Gesendet: Donnerstag, 21. Februar 2019 12:19 An: ntg-context@ntg.nl Betreff: Re: [NTG-context] Frame On Thu, 21 Feb 2019 10:50:21 + Ursula Hermann wr

Re: [NTG-context] troubles with \MPinclusions (Taco Hoekwater)

2019-02-21 Thread Damien Thiriet
Thanks for your answers, I could significantly reduce my long timeline code. > 1. Variable names x and y are special and cleared before >every graphic. This is related to the fact that “z" is >defined as a shortcut for "(x,y)”. Both of these are >traditional. > >Every metapos

Re: [NTG-context] Frame

2019-02-21 Thread Marco Patzer
On Thu, 21 Feb 2019 10:50:21 + Ursula Hermann wrote: > Here is my example: > > \setuppapersize[A5] > \setupcolors[state=start] This is the default, no need to start the colours any longer. > {\framed >[width=10cm, >background=color,backgroundcolor=darkblue, >foreground=color,fo

Re: [NTG-context] Frame

2019-02-21 Thread Ursula Hermann
Hello Lars! Here is my example: \setuppapersize[A5] \setupcolors[state=start] {\framed [width=10cm, background=color,backgroundcolor=darkblue, foreground=color,foregroundcolor=white, align={flushleft}] {The Earth, as a habitat for animal life, is in old age and has a fatal illness. S

Re: [NTG-context] troubles with \MPinclusions

2019-02-21 Thread Taco Hoekwater
> On 21 Feb 2019, at 10:03, Damien Thiriet wrote: > > Hi, > > > Why does (1) compile, whereas (2) doesn’t? For me, both compile. However (2) does not work. 1. Variable names x and y are special and cleared before every graphic. This is related to the fact that “z" is defined as a sho

Re: [NTG-context] troubles with \MPinclusions

2019-02-21 Thread Hans Hagen
On 2/21/2019 10:03 AM, Damien Thiriet wrote: Hi, Why does (1) compile, whereas (2) doesn't? I can't understand why can MPinclusions store path and not pairs. (1) %% \setuppapersize[A4,landscape] \startMPinclusions u:=1mm ; %fond path p ; p:= (0,0) --

[NTG-context] troubles with \MPinclusions

2019-02-21 Thread Damien Thiriet
Hi, Why does (1) compile, whereas (2) doesn't? I can't understand why can MPinclusions store path and not pairs. (1) %% \setuppapersize[A4,landscape] \startMPinclusions u:=1mm ; %fond path p ; p:= (0,0) -- (150u,0) -- (150u,95u) -- (0,95u) -- cycle ;