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/


A typescript file is simply a tex file, so the usual rules for storing 
tex file applies. You should try a sub-directory of:


$TEXMFHOME/tex/context/

or

$TEXMFLOCAL/tex/context/

Aditya 


Thank you,  Aditya.

I had the file at the wrong place in the local tree (with my fonts). 
Moving it to  ./tex/context indeed solves the problem.


--
Rik

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


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

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


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 those lines here 

I see 

 local tail = getprev(stop) 

in line 844 of font-ots.lua in a just updated context minimals. 

If I change this to 

 local tail = stop

as suggested by Marcel and rebuild the formats, the ligature behaves
again. 

> (and definitely not in the tex live code freeze window)

TeXLive is frozen and pretest has begun, so I don't see a danger to
apply patches now. 


-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


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 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 files from 2019-02-14,
  > >> but the problem appeared first in the files from 2018-11-18):
  > >>
  > >> \font\test={file:texgyreheros-regular.otf:+tlig;mode=node;}\test
  > >>
  > >> dashes-these % gives dash
  > >>
  > >> dashes--these % gives en-dash
  > >>
  > >> dashes---these % gives en-dash WRONG
  > >>
  > >> dashes --- these % gives em-dash
  > >>
  > >> em-dashes---these % gives em-dash
  > >>
  > >> \bye
  > >>
  > >> context is not affected, there the code works fine.
  > >
  > > This issue can be fixed in the fontloader with the attached patch.
  > Hm, I don't see those lines here and it looks ok in context so ... no

For reproduction in context, the code

 \starttext
 ff\discretionary{l}{}{l}
 \stoptext

currently produces a single `fl` ligature instead of `ffl`.

Interesting that you didn't see those lines, maybe we have different versions?
The patched line is line 844 in the file `font-ots.lua` of ConTeXt beta, 
updated today.

your patch referred to other numbers

i'll look into it (also why it is as it is)

thanks for the example

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


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 is luatex, version 1.10.0 (tex live 2019)
mkiv lua stats  > control sequences: 53180 of 65536 + 10
mkiv lua stats  > lua properties: engine: lua 5.3, used memory: 441 MB (ctx: 
437 MB), hash chars: min(64,40), symbol mask: utf (τεχ)
mkiv lua stats  > runtime: 21.608 seconds, 294 processed pages, 294 shipped 
pages, 13.606 pages/second
system  | total runtime: 47.547 seconds


OK, strange. It works for me in TeX Live as well after I installed the
missing dejavu fonts. I didn't imagine that it would break with such a
strange error when a font is missing though.


( forget the time, it's a zero-optimized binary (fast to compile))


It takes even longer for me with the binary from the distribution.

On the mac, is that one run?

With luatex 1.10 (mingw 64 version), when i delete the tuc file so with 
multiple runs to get the cross ref and lists right, I get:


mkiv lua stats  > runtime: 13.676 seconds, 294 processed pages, 294 
shipped pages, 21.498 pages/second

system  | total runtime: 67.472 seconds

After that, single runs take around 13 seconds:

mkiv lua stats  > runtime: 13.227 seconds, 294 processed pages, 294 
shipped pages, 22.227 pages/second


so, so, on my laptop (which for sure is slower than yours) a 21 pps rate 
is normal


Hans


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


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  we use the minimals  as checkpoint;
on that platform 47.547 seconds for standard luatex means that something is
(profoundly) wrong.



-- 
luigi
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


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 2019)
> mkiv lua stats  > control sequences: 53180 of 65536 + 10
> mkiv lua stats  > lua properties: engine: lua 5.3, used memory: 441 MB (ctx: 
> 437 MB), hash chars: min(64,40), symbol mask: utf (τεχ)
> mkiv lua stats  > runtime: 21.608 seconds, 294 processed pages, 294 shipped 
> pages, 13.606 pages/second
> system  | total runtime: 47.547 seconds

OK, strange. It works for me in TeX Live as well after I installed the
missing dejavu fonts. I didn't imagine that it would break with such a
strange error when a font is missing though.

> ( forget the time, it's a zero-optimized binary (fast to compile))

It takes even longer for me with the binary from the distribution.

> In general: at every new release I have complains about "how deadly slow is 
> texlive  installation".
> On the other side , some  could wonder why *DejaVu* are not installed by 
> default regardless of  engine/scheme.

You could wonder that for all the zillions of fonts that ship with TeX Live.
Only CM is compulsory, the rest is up to user's taste.

Mojca
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


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 only with mode=node. I'm using the files from 2019-02-14,
but the problem appeared first in the files from 2018-11-18):

\font\test={file:texgyreheros-regular.otf:+tlig;mode=node;}\test

dashes-these % gives dash

dashes--these % gives en-dash

dashes---these % gives en-dash WRONG

dashes --- these % gives em-dash

em-dashes---these % gives em-dash

\bye

context is not affected, there the code works fine.


This issue can be fixed in the fontloader with the attached patch.
Hm, I don't see those lines here and it looks ok in context so ... no 
patches applied (and definitely not in the tex live code freeze window)


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


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 publish the patterns for Mojca and me to add to the
repository.

Arthur
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


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 code:
>> 
>> \def\b#1{\startmode[#1]}
>> \def\e{\stopmode}
>> % \enablemode[100] % For optional usage
>> \starttext
>>   A
>>   \b{100} % Should be start of some conditional text from here ...
>> B
>>   \e % ... to here
>> \stoptext
>> 
>> Compilation fails with:
>> "
>> tex error   > tex error on line 0 in file : ! Emergency stop
>> <*> cont-yes.mkiv
>> 
>> *** (job aborted, no legal \end found)
>> "
>> How to make the sample work?
> modes are like buffers ... don't wrap them in macros
> 
> (using names like \b \e is a bad idea anyway)
> 
> Hans
> 
> 
> -
>  Hans Hagen | PRAGMA ADE
>  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[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 files from 2019-02-14,
> but the problem appeared first in the files from 2018-11-18):
> 
> \font\test={file:texgyreheros-regular.otf:+tlig;mode=node;}\test
> 
> dashes-these % gives dash
> 
> dashes--these % gives en-dash
> 
> dashes---these % gives en-dash WRONG
> 
> dashes --- these % gives em-dash
> 
> em-dashes---these % gives em-dash
> 
> \bye
> 
> context is not affected, there the code works fine.

This issue can be fixed in the fontloader with the attached patch.

Best regards,
Marcel Krüger

0001-Fix-ligature-followed-by-disc.diff
Description: Binary data
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___