- ntg-context - Mailing Lists

question about MP drawing with dir
by Pablo Rodriguez 25 May '18

25 May '18

Dear Alan, I have the following sample (as I wrote, this is addictive ;-)): \startMPpage draw fullcircle scaled (.06TextWidth - .05LineHeight); for m=1 step 2 until 10 : path s ; s := (dir30--dir150--dir315--dir90--dir225--cycle) scaled m; n := (m * 50) ; o := (m / 5) ; for i=0 upto n : draw textext("\utfchar{"EB09}") scaled (o * .025) shifted point (i/n*length s) of s ; endfor endfor \stopMPpage dir seems magic to me. I don’t understand how it works, not even how it can be used for drawing not having an origin. Would it be possible that all stars are vertically centered? How should be the path defined? Many thanks for your help, Pablo -- http://www.ousia.tk

3 5

index x-ref problem
by Alan Bowen 25 May '18

25 May '18

IF I am doing this correctly, then, there seems to be problems in the current standalone when there are two x-refs to a single heading. The space after “and” is missing and should the order of the refs not be alphabetical? MWE \starttext \seeindex{animal}{cat} \seeindex{animal}{quadruped} %\seeindex{animal}{whiskers} The \index{cat}cat has \index{whiskers} whiskers. \blank[3*big] \placeindex \stoptext Uncomment the \seeindex{animal}{whiskers} and it gets even messier. Alan

1 1

Re: [NTG-context] Defining command with optional and mandatory arguments
by Christoph Reller 25 May '18

25 May '18

On Thu, 24 May 2018 14:50:36 +0200, Hans Hagen <j.hagen(a)xs4all.nl> wrote: > On 5/24/2018 11:21 AM, Christoph Reller wrote: >> On Wed, 23 May 2018 16:01:05 +0200, Hans Hagen <j.hagen(a)xs4all.nl> wrote: >>> On 5/23/2018 3:39 PM, Christoph Reller wrote: >>>> >>>> What is the right way to define a command with both mandatory and >>>> optional arguments, e.g: >>>> >>>> \MyCommand[optional][mandatory] >>>> >>>> Consider the following MWE: >>>> >>>> \unexpanded\def\MyCommand[#1]{ >>>> \dosingleempty{\doMyCommand[#1]}} >>>> \def\doMyCommand[#1][#2]{ >>>> \doifsomething{#1}{number 1: #1\par} >>>> \doifsomething{#2}{number 2: #2}\blank[big]} >>>> \starttext >>>> \MyCommand[A][B] >>>> \MyCommand[A] >>>> \stoptext >>>> >>>> In last year's versions of ConTeXt the output was >>>> >>>> number 1: A >>>> number 2: B >>>> number 1: A >>>> >>>> In the latest version of ConTeXt the output is >>>> >>>> number 1: A >>>> number 2: B >>>> number 2: A >>>> >>>> Is this behavior intended? How can I make a definition whose behavior >>>> does not change in new versions of ConTeXt? >>> i'm not sure wht happens at your end but this is the best way: >>> >>> \unexpanded\def\MyCommand >>> {\dodoubleempty\doMyCommand} >>> >>> \def\doMyCommand[#1][#2]% >>> {\iffirstargument >>> number 1: #1% >>> \par >>> \fi >>> \ifsecondargument >>> number 2: #2% >>> \fi >>> \blank[big]} >>> >>> \starttext >>> \MyCommand[A][B] >>> \MyCommand[A] >>> \stoptext >> >> Thank you Hans for this information. My question is rather about error >> handling. I want: >> >> \MyCommand[A][B] % <- succeeds with #1->A, #2->B >> \MyCommand[A] % <- succeeds with #1->A >> \MyCommand % <- fails with "! Use of \MyCommand doesn't match its definition" >> >> I just wanted to ask whether there is a standard way to achieve this >> with \do<whatever>empty. If not, then this is also okay. > just use \dodoubleempty instead Thank you for your hint, Hans. \dodoubleempty renders both arguments optional and hence the command can be used without any argument, which is not what I intended. Of course I can still test in the command's definition whether at least one argument is given and generate an error myself. In i-context.pdf, many arguments are documented as being optional and I assume that all the others are mandatory. A quick test has, however, shown that when omitting mandatory arguments, either no error is generated (e.g., nothing is setup or defined) or an obscure error emerges other than "! Use of \<command> doesn't match its definition". So I take it as a design decision that reporting missing mandatory arguments as errors is not part of the interface implementation, and that is a perfectly acceptable decision for me. It is just good to know. Thank you all for your highly valued feedback! Cheers, Christoph

1 0

question about followtext in MP
by Pablo Rodriguez 24 May '18

24 May '18

Dear list, I have the following sample: \starttext \startMPcode path p ; p := reverse halfcircle scaled 5cm; path q ; q := reverse halfcircle rotatedaround (origin, 180) scaled 5cm ; draw p; draw q; draw followtext(p, "·Just follow the tokens") ; draw followtext(q, "Just follow the tokens·") ; draw followtext(reverse q, "Just follow the tokens·") ; \stopMPcode \stoptext Is there any way to followtext in q without changing text direction? I need to write the text counter-clockwise, but on outside of the path. Reverse changes both text direction and side of the text (related to the path) and I don’t want to change text direction. Many thanks for your help, Pablo -- http://www.ousia.tk

3 12

Re: [NTG-context] Defining command with optional and mandatory arguments
by Christoph Reller 24 May '18

24 May '18

On Wed, 23 May 2018 17:54:39 +0200, Henning Hraban Ramm <texml(a)fiee.net> wrote: > Date: Wed, 23 May 2018 17:54:39 +0200 > From: Henning Hraban Ramm <texml(a)fiee.net> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > Subject: Re: [NTG-context] Defining command with optional and > mandatory arguments > Message-ID: <A21D40D2-E607-47A4-BAB0-C437DC9150DA(a)fiee.net> > Content-Type: text/plain; charset=windows-1252 > > Am 2018-05-23 um 16:01 schrieb Hans Hagen <j.hagen(a)xs4all.nl>: > >> On 5/23/2018 3:39 PM, Christoph Reller wrote: >>> Hi, >>> What is the right way to define a command with both mandatory and >>> optional arguments, e.g: >> i'm not sure wht happens at your end but this is the best way: > > Also, there’s documentation at > http://wiki.contextgarden.net/Commands_with_optional_arguments > > If there’s something wrong, please fix it yourself or come back to this list ;) > Thank you Hraban for pointing me to the wiki. I was aware of this page but it contains only the case of mandatory arguments in curly braces {} not in brackets []. Cheers, Christoph

4 3

Defining command with optional and mandatory arguments
by Christoph Reller 24 May '18

24 May '18

On Wed, 23 May 2018 16:01:05 +0200, Hans Hagen <j.hagen(a)xs4all.nl> wrote: > > On 5/23/2018 3:39 PM, Christoph Reller wrote: >> Hi, >> >> What is the right way to define a command with both mandatory and >> optional arguments, e.g: >> >> \MyCommand[optional][mandatory] >> >> Consider the following MWE: >> >> \unexpanded\def\MyCommand[#1]{ >> \dosingleempty{\doMyCommand[#1]}} >> \def\doMyCommand[#1][#2]{ >> \doifsomething{#1}{number 1: #1\par} >> \doifsomething{#2}{number 2: #2}\blank[big]} >> \starttext >> \MyCommand[A][B] >> \MyCommand[A] >> \stoptext >> >> In last year's versions of ConTeXt the output was >> >> number 1: A >> number 2: B >> number 1: A >> >> In the latest version of ConTeXt the output is >> >> number 1: A >> number 2: B >> number 2: A >> >> Is this behavior intended? How can I make a definition whose behavior >> does not change in new versions of ConTeXt? > i'm not sure wht happens at your end but this is the best way: > > \unexpanded\def\MyCommand > {\dodoubleempty\doMyCommand} > > \def\doMyCommand[#1][#2]% > {\iffirstargument > number 1: #1% > \par > \fi > \ifsecondargument > number 2: #2% > \fi > \blank[big]} > > \starttext > \MyCommand[A][B] > \MyCommand[A] > \stoptext Thank you Hans for this information. My question is rather about error handling. I want: \MyCommand[A][B] % <- succeeds with #1->A, #2->B \MyCommand[A] % <- succeeds with #1->A \MyCommand % <- fails with "! Use of \MyCommand doesn't match its definition" I just wanted to ask whether there is a standard way to achieve this with \do<whatever>empty. If not, then this is also okay. Cheers, Christoph

2 1

\showgrid not working right
by Marcus Vinicius Mesquita 24 May '18

24 May '18

Dear list, The frame around text area is appearing way below where it should be. Minimal working example: \setuplayout[grid=yes] \showgrid \starttext \input knuth.tex \stoptext My context version: mtx-context | current version: 2018.05.19 21:46 mkiv lua stats > used platform: linux-64, type: unix, binary subtree: texmf-linux-64 mkiv lua stats > used engine: luatex version 1.08 with functionality level 6731, banner: this is luatex, version 1.08.0 (tex live 2018) Marcus Vinicius

1 0

Defining command with optional and mandatory arguments
by Christoph Reller 23 May '18

23 May '18

Hi, What is the right way to define a command with both mandatory and optional arguments, e.g: \MyCommand[optional][mandatory] Consider the following MWE: \unexpanded\def\MyCommand[#1]{ \dosingleempty{\doMyCommand[#1]}} \def\doMyCommand[#1][#2]{ \doifsomething{#1}{number 1: #1\par} \doifsomething{#2}{number 2: #2}\blank[big]} \starttext \MyCommand[A][B] \MyCommand[A] \stoptext In last year's versions of ConTeXt the output was number 1: A number 2: B number 1: A In the latest version of ConTeXt the output is number 1: A number 2: B number 2: A Is this behavior intended? How can I make a definition whose behavior does not change in new versions of ConTeXt? Cheers, Christoph

3 2

Trim blank space of a PDF page
by Procházka Lukáš Ing. 23 May '18

23 May '18

Hello, just curious - is threre a way how to crop a page of a PDF via ConTeXt? Ideally - to process a single page PDF into another file, with the one page cropped... Best regards, Lukas -- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz | IDDS:nrpt3sn Bezová 1658 147 14 Praha 4 Mob.: +420 702 033 396

5 5

referenceprefix=+ not working
by Henri Menke 23 May '18

23 May '18

Dear list, the option referenceprefix=+ for setuphead seems to not work. https://tex.stackexchange.com/questions/432844 It works however if you put an explicit prefix. See MWE below. Reproducible on TL2018 and latest beta. Cheers, Henri --- \setuphead [section] [referenceprefix=+] % when I put "test" it works \starttext \startsection[reference=test,title={Test}] \startplacefigure[reference=cow] \externalfigure[cow] \stopplacefigure \stopsection \in[test:cow] % ?? \stoptext

2 1