May 2018 - ntg-context - NTG Mailing Lists

Missing font features in page header if \feature[-] is used in header text
by Joseph Canedo 30 May '18

30 May '18

Dear list, Provided MWE below I notice that font features seem ignored in page header rendering. Anything I am doing wrong ? Rendering is fine if \headerok is used. Any help would be appreciated. Thanks Best regards Joseph \definefontfeature[base][mode=node, liga=yes, dlig=yes, hlig=yes, kern=yes] \definefontfeature[xvicentury][] \definefontfamily[mainfont][serif][EBGaramond][features=base] \setupbodyfont[mainfont, 9pt] \showfontkerns \def\wrongheader{First book {\feature[-][xvicentury]v} Psalme De David.} %% \feature[-] seems to cause problems in header \def\headerok{First book v Psalme De David.} \setupheadertexts[\wrongheader] %% kern/ligatures missing <--- % \setupheadertexts[\headerok] %% kern/ligatures ok <--- \starttext \wrongheader %% all ok in main text \headerok \stoptext

2 2

Problem defining macro with Lua inside
by Procházka Lukáš Ing. 30 May '18

30 May '18

Hello, I'm trying to define a macro (a MS Word -> clipboard -> Ctx tool), whose simplified form is the following: ---- \def\startWord{% \startluacode context[[ } \def\stopWord{% ]] \stopluacode } \starttext aaa \startWord abc def ghi \stopWord \stoptext ---- Unfortunately, I'm not able to define \startWord and \stopWord in a way that Ctx would accept. How to define it? Any help would be appreciated. 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

3 3

troubles with standalone install on openbsd6.3-amd64
by Damien Thiriet 28 May '18

28 May '18

Hello, I tried to install standalone on my OpenBSD 64-bit. Looks like something went wrong (or I missed something). Here is the output of ./firstsetup.sh (with a change of my home folder name to blablabla for the sake of my paranoia). receiving incremental file list sent 29 bytes received 150 bytes 358.00 bytes/sec total size is 10,447,547 speedup is 58,366.18 mtxrun | forcing cache reload resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/texmf/web2c' from specification 'home:texmf/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on weird path '/home/blablabla/context/bin' from specification 'selfautoloc:' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/context/bin/share/texmf-local/web2c' from specification 'selfautoloc:/share/texmf-local/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/context/bin/share/texmf-dist/web2c' from specification 'selfautoloc:/share/texmf-dist/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/context/bin/share/texmf/web2c' from specification 'selfautoloc:/share/texmf/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/context/bin/texmf-local/web2c' from specification 'selfautoloc:/texmf-local/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/context/bin/texmf-dist/web2c' from specification 'selfautoloc:/texmf-dist/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/context/bin/texmf/web2c' from specification 'selfautoloc:/texmf/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on weird path '/home/blablabla/context' from specification 'selfautodir:' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/context/share/texmf-local/web2c' from specification 'selfautodir:/share/texmf-local/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/context/share/texmf-dist/web2c' from specification 'selfautodir:/share/texmf-dist/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/context/share/texmf/web2c' from specification 'selfautodir:/share/texmf/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/context/texmf-local/web2c' from specification 'selfautodir:/texmf-local/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/context/texmf-dist/web2c' from specification 'selfautodir:/texmf-dist/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/context/texmf/web2c' from specification 'selfautodir:/texmf/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification '$SELFAUTOGRANDPARENT/texmf-local/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on weird path '/home/blablabla' from specification 'selfautoparent:' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/share/texmf-local/web2c' from specification 'selfautoparent:/share/texmf-local/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/share/texmf-dist/web2c' from specification 'selfautoparent:/share/texmf-dist/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/share/texmf/web2c' from specification 'selfautoparent:/share/texmf/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/texmf-dist/web2c' from specification 'selfautoparent:/texmf-dist/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/blablabla/texmf/web2c' from specification 'selfautoparent:/texmf/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/texmf/web2c' from specification 'home:texmf/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on weird path '/home/blablabla/context/bin' from specification 'selfautoloc:' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/context/bin/share/texmf-local/web2c' from specification 'selfautoloc:/share/texmf-local/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/context/bin/share/texmf-dist/web2c' from specification 'selfautoloc:/share/texmf-dist/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/context/bin/share/texmf/web2c' from specification 'selfautoloc:/share/texmf/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/context/bin/texmf-local/web2c' from specification 'selfautoloc:/texmf-local/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/context/bin/texmf-dist/web2c' from specification 'selfautoloc:/texmf-dist/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/context/bin/texmf/web2c' from specification 'selfautoloc:/texmf/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on weird path '/home/blablabla/context' from specification 'selfautodir:' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/context/share/texmf-local/web2c' from specification 'selfautodir:/share/texmf-local/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/context/share/texmf-dist/web2c' from specification 'selfautodir:/share/texmf-dist/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/context/share/texmf/web2c' from specification 'selfautodir:/share/texmf/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/context/texmf-local/web2c' from specification 'selfautodir:/texmf-local/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/context/texmf-dist/web2c' from specification 'selfautodir:/texmf-dist/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/context/texmf/web2c' from specification 'selfautodir:/texmf/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification '$SELFAUTOGRANDPARENT/texmf-local/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on weird path '/home/blablabla' from specification 'selfautoparent:' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/share/texmf-local/web2c' from specification 'selfautoparent:/share/texmf-local/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/share/texmf-dist/web2c' from specification 'selfautoparent:/share/texmf-dist/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/share/texmf/web2c' from specification 'selfautoparent:/share/texmf/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/texmf-dist/web2c' from specification 'selfautoparent:/texmf-dist/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/blablabla/texmf/web2c' from specification 'selfautoparent:/texmf/web2c' resolvers | resolving | resolvers | resolving | warning: no lua configuration files found resolvers | resolving | no texmf paths are defined (using TEXMF) resolvers | resolving | mtxrun | the resolver databases are not present or outdated mtx-update | state, loaded mtx-update | mtx-update | update, start mtx-update | available platforms: freebsd freebsd-amd64 linux linux-64 linux-armhf linuxmusl-64 mswin openbsd6.3 openbsd6.3-amd64 osx-64 solaris-intel solaris-sparc win64 resolvers | tds | no 'texmf-openbsd6.3-amd64' under tree '/home/blablabla/context/tex' Is this all right and what shall I do next or is there a problem, as I think ? Have a nice day, Damien Thiriet

2 1

installing latest stable version
by Jano Kula 26 May '18

26 May '18

Hello, installing latest stable standalone version on Ubuntu 16.04 x64: ./first-setup.sh --context=current --engine=luatex fails with: This is LuaTeX, Version 1.08.0 (TeX Live 2018) (INITEX) system commands enabled. error in callback: ...018/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:194: attempt to call a nil value (upvalue 'isfile') . <insert> <*> ...mf-context/tex/context/base/mkiv/cont-en.mkiv dump Beta on the same machine installs correctly. Jano

2 4

Designsize
by John Grasty 26 May '18

26 May '18

Hello List, Quick question. I have been going through the archives, and I want to make sure I understand this correctly. I want to use the Adobe font Arno Pro. It comes with design sizes (and also has that information in the otf files as shown with otfinfo -z arnopro-subhead.otf for example). To use this font though with the design sizes, do I need to write a goodies file that explains this to ConTeXt? Thanks, John

1 0

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 24 May '18

24 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