Re: [NTG-context] TeX Live 2019: attempt to call a nil value (upvalue 'isfile')

2019-03-01 Thread luigi scarso
On Fri, Mar 1, 2019 at 12:01 PM Mojca Miklavec < mojca.miklavec.li...@gmail.com> wrote: > On Fri, 1 Mar 2019 at 08:50, luigi scarso wrote: > > > ( forget the time, it's a zero-optimized binary (fast to compile)) > > It takes even longer for me with the binary from the distribution. > I know, but

Re: [NTG-context] How to define a new language?

2019-03-01 Thread Arthur Reutenauer
On Thu, Feb 28, 2019 at 01:23:51PM -0500, Paul Hoffman wrote: > It's an invented language, so no one else will ever need to use it. Maybe so -- though you can’t know that for sure -- but if you’re down the path of requesting a change in a ConTeXt script to add it locally, you might as well

Re: [NTG-context] em-dash ligature is converted to en-dash in the generic fontloader

2019-03-01 Thread Hans Hagen
On 2/28/2019 12:38 PM, Marcel Krüger wrote: On 2/23/2019 1:50 PM, Ulrike Fischer wrote: As reported on the dev-luatex list --- is converted to an en-dash (instead of em-dash) if there are no spaces around the ---. We could now reproduce the problem also with the generic fontloader: it appears

Re: [NTG-context] TeX Live 2019: attempt to call a nil value (upvalue 'isfile')

2019-03-01 Thread Mojca Miklavec
On Fri, 1 Mar 2019 at 08:50, luigi scarso wrote: > > $> context luatex > mkiv lua stats > used platform: linux-64, type: unix, binary subtree: > texmf-linux-64 > mkiv lua stats > used engine: luatex version 1.1 with functionality level > 7088, banner: this is luatex, version 1.10.0 (tex live

Re: [NTG-context] TeX Live 2019: attempt to call a nil value (upvalue 'isfile')

2019-03-01 Thread Hans Hagen
On 3/1/2019 12:01 PM, Mojca Miklavec wrote: On Fri, 1 Mar 2019 at 08:50, luigi scarso wrote: $> context luatex mkiv lua stats > used platform: linux-64, type: unix, binary subtree: texmf-linux-64 mkiv lua stats > used engine: luatex version 1.1 with functionality level 7088, banner: this

Re: [NTG-context] Modes and conditional part of the source

2019-03-01 Thread Hans van der Meer
I used \doifmode and friends for selection of mode dependent code. dr. Hans van der Meer > On 1 Mar 2019, at 01:24, Hans Hagen wrote: > > On 2/28/2019 11:29 AM, Procházka Lukáš Ing. wrote: >> Hello, >> I'm struggling with using modes to make a part of the text conditional. >> Here is my

[NTG-context] em-dash ligature is converted to en-dash in the generic fontloader

2019-03-01 Thread Marcel Krüger
On 2/23/2019 1:50 PM, Ulrike Fischer wrote: > As reported on the dev-luatex list --- is converted to an en-dash > (instead of em-dash) if there are no spaces around the ---. > > We could now reproduce the problem also with the generic fontloader: > it appears only with mode=node. I'm using the

Re: [NTG-context] em-dash ligature is converted to en-dash in the generic fontloader

2019-03-01 Thread Hans Hagen
On 3/1/2019 1:15 PM, Ulrike Fischer wrote: TeXLive is frozen and pretest has begun, so I don't see a danger to apply patches now. binaries get frozen at 22/3 and context isn't checked in yet (comes after first binary generation) anyway, i'll look at it (maybe this weekend) Hans

Re: [NTG-context] em-dash ligature is converted to en-dash in the generic fontloader

2019-03-01 Thread Hans Hagen
On 3/1/2019 12:29 PM, Marcel Krüger wrote: On Fri, 01 Mar 2019 11:17:56 +0100 Hans Hagen wrote > On 2/28/2019 12:38 PM, Marcel Krger wrote: > > On 2/23/2019 1:50 PM, Ulrike Fischer wrote: > >> As reported on the dev-luatex list --- is converted to an en-dash > >> (instead

Re: [NTG-context] em-dash ligature is converted to en-dash in the generic fontloader

2019-03-01 Thread Ulrike Fischer
Am Fri, 1 Mar 2019 11:17:56 +0100 schrieb Hans Hagen: > it looks ok in context You need to set automatichyphenmode=0 to see the problem in context: the handling of the --- ligature is clearly broken in some cases: \starttext \automatichyphenmode=0 A---B A --- B \stoptext > Hm, I don't see

Re: [NTG-context] Search path for typescripts

2019-03-01 Thread Rik Kabel
On 2/28/2019 22:42, Aditya Mahajan wrote: On Thu, 28 Feb 2019, Rik Kabel wrote: List, What is the proper place to put a custom typescript file to make it accessible to multiple projects? For testing I placed copies in" 1)  the local directory 2)  /texmf/fonts 3)  /tex/texmf-local/fonts/