Re: [NTG-context] bug in \definefontfamily?

2017-03-20 Thread Hans Hagen
On 3/19/2017 10:08 PM, Pablo Rodriguez wrote: On 03/19/2017 09:58 PM, Wolfgang Schuster wrote: Pablo Rodriguez 19. März 2017 schrieb: But [features={none, quality}] disables everything and I canot enable protrusion plus expansion only. At least, it doesn’t work with \definefontfamily. I

Re: [NTG-context] bug in \definefontfamily?

2017-03-20 Thread Hans Hagen
On 3/19/2017 1:38 PM, Pablo Rodriguez wrote: On 03/19/2017 12:19 PM, josephcan...@gmail.com wrote: Hi Pablo, When I typeset your MWE below with latest beta version (on win 10) you use too, I see 2 lines of 1110 with different appearance. Hi Joseph, sorry, the second sample was different.

Re: [NTG-context] bug in \definefontfamily?

2017-03-19 Thread Wolfgang Schuster
Pablo Rodriguez 19. März 2017 um 22:08via Postbox Yes, this might work, but I’m afraid I need to disable other default features such as ligatures (not only liga, but TeX ligatures). I had

Re: [NTG-context] bug in \definefontfamily?

2017-03-19 Thread Pablo Rodriguez
On 03/19/2017 09:58 PM, Wolfgang Schuster wrote: >> Pablo Rodriguez 19. März 2017 schrieb: >> But [features={none, quality}] disables everything and I canot enable >> protrusion plus expansion only. >> >> At least, it doesn’t work with \definefontfamily. I haven’t tested this >> with

Re: [NTG-context] bug in \definefontfamily?

2017-03-19 Thread Wolfgang Schuster
Pablo Rodriguez 19. März 2017 um 21:40via Postbox But [features={none, quality}] disables everything and I canot enable protrusion plus expansion only. At least, it doesn’t work with

Re: [NTG-context] bug in \definefontfamily?

2017-03-19 Thread Wolfgang Schuster
Pablo Rodriguez 19. März 2017 um 21:40via Postbox But [features={none, quality}] disables everything and I canot enable protrusion plus expansion only. At least, it doesn’t work with

Re: [NTG-context] bug in \definefontfamily?

2017-03-19 Thread Pablo Rodriguez
On 03/19/2017 09:32 PM, Wolfgang Schuster wrote: >> Pablo Rodriguez 19. März 2017 um 21:07via Postbox >> [...] >> BTW, does it happen the same to mono fonts? In the past, I wanted to >> check whether quality values for protrusion and expansion would make >> sense in the document I was typesetting,

Re: [NTG-context] bug in \definefontfamily?

2017-03-19 Thread Wolfgang Schuster
Pablo Rodriguez 19. März 2017 um 21:07via Postbox Many thanks for your explanation, Wolfgang. I didn’t consider that Neo Euler might be a default font. And I didn’t know that the values would

Re: [NTG-context] bug in \definefontfamily?

2017-03-19 Thread Pablo Rodriguez
On 03/19/2017 08:38 PM, Wolfgang Schuster wrote: >> Pablo Rodriguez 19. März 2017 schrieb: >> [...] >> Is this a bug or what am I missing? > > When you use a math font (which Neo Euler is) the argument of the > features key is ignored and \definefontfamily uses internal default > values

Re: [NTG-context] bug in \definefontfamily?

2017-03-19 Thread Wolfgang Schuster
Pablo Rodriguez 19. März 2017 um 13:38via Postbox Hi Joseph, sorry, the second sample was different. The first line was TeX Gyre Pagella and the second line was Neo Euler. The default

[NTG-context] bug in \definefontfamily? (was: Re: OT salt feature not working?)

2017-03-19 Thread Pablo Rodriguez
On 03/19/2017 12:19 PM, josephcan...@gmail.com wrote: > Hi Pablo, > > When I typeset your MWE below with latest beta version (on win 10) you > use too, I see 2 lines of 1110 with different appearance. Hi Joseph, sorry, the second sample was different. The first line was TeX Gyre Pagella and the