Re: [NTG-context] definefont

2019-01-23 Thread Alan Braslau
On Wed, 23 Jan 2019 18:03:51 +0100 Wolfgang Schuster wrote: > > Are not the default set of OpenType features activated by default? > > (as the name might suggest...). Perhaps *no* features are selected, by > > default... > > (a misnomer, therefore). > > default is just one of many predefined

Re: [NTG-context] definefont

2019-01-23 Thread Wolfgang Schuster
Alan Braslau schrieb am 23.01.19 um 17:49: On Wed, 23 Jan 2019 17:32:41 +0100 Henning Hraban Ramm wrote: What are the roles of "*default" and "sa 3" as these appear to be unnecessary? *default activates the default set of OpenType features. Are not the default set of OpenType features

Re: [NTG-context] definefont (was: definefontfamily use)

2019-01-23 Thread Alan Braslau
On Wed, 23 Jan 2019 17:32:41 +0100 Henning Hraban Ramm wrote: > > What are the roles of "*default" and "sa 3" as these appear to be > > unnecessary? > > *default activates the default set of OpenType features. Are not the default set of OpenType features activated by default? (as the name

Re: [NTG-context] definefont

2019-01-23 Thread Wolfgang Schuster
Henning Hraban Ramm schrieb am 23.01.19 um 17:32: And how can I \definefont so that \em or \emph works the same as in bodyfont? You can’t. Or, the other way round, how must I \definehighlight[emph][style=italic] so that it works in all sizes? - \setupbodyfont[rm,12pt]

Re: [NTG-context] definefont (was: definefontfamily use)

2019-01-23 Thread Henning Hraban Ramm
And how can I \definefont so that \em or \emph works the same as in bodyfont? Or, the other way round, how must I \definehighlight[emph][style=italic] so that it works in all sizes? - \setupbodyfont[rm,12pt] \definefont[TitleFont][SansBold*default sa 3]

Re: [NTG-context] \definefont problem with latest beta (mkiv)

2008-11-14 Thread Peter Rolf
Hans Hagen schrieb: Peter Rolf wrote: Peter Rolf schrieb: Taco Hoekwater schrieb: Peter Rolf wrote: I followed that one. But my problem is more the *wrong strut height*, e.g. using a \totalstrut value of 12pt with a 8pt font. The strut height is simply not adapted to the actual font size

Re: [NTG-context] \definefont problem with latest beta (mkiv)

2008-11-13 Thread Wolfgang Schuster
Am 13.11.2008 um 16:22 schrieb Peter Rolf: Peter Rolf schrieb: Taco Hoekwater schrieb: Peter Rolf wrote: I followed that one. But my problem is more the *wrong strut height*, e.g. using a \totalstrut value of 12pt with a 8pt font. The strut height is simply not adapted to the actual

Re: [NTG-context] \definefont problem with latest beta (mkiv)

2008-11-13 Thread Peter Rolf
Peter Rolf schrieb: Taco Hoekwater schrieb: Peter Rolf wrote: I followed that one. But my problem is more the *wrong strut height*, e.g. using a \totalstrut value of 12pt with a 8pt font. The strut height is simply not adapted to the actual font size anymore (even if I use \setstrut). I can

Re: [NTG-context] \definefont problem with latest beta (mkiv)

2008-11-13 Thread Peter Rolf
Wolfgang Schuster schrieb: Am 13.11.2008 um 16:22 schrieb Peter Rolf: Peter Rolf schrieb: Taco Hoekwater schrieb: Peter Rolf wrote: I followed that one. But my problem is more the *wrong strut height*, e.g. using a \totalstrut value of 12pt with a 8pt font. The strut height is

Re: [NTG-context] \definefont problem with latest beta (mkiv)

2008-11-12 Thread Hans Hagen
Peter Rolf wrote: Taco Hoekwater schrieb: Peter Rolf wrote: I followed that one. But my problem is more the *wrong strut height*, e.g. using a \totalstrut value of 12pt with a 8pt font. The strut height is simply not adapted to the actual font size anymore (even if I use \setstrut). I can

Re: [NTG-context] \definefont problem with latest beta (mkiv)

2008-11-12 Thread Taco Hoekwater
Peter Rolf wrote: I followed that one. But my problem is more the *wrong strut height*, e.g. using a \totalstrut value of 12pt with a 8pt font. The strut height is simply not adapted to the actual font size anymore (even if I use \setstrut). I can understand why you think this is a

Re: [NTG-context] \definefont problem with latest beta (mkiv)

2008-11-12 Thread Peter Rolf
Taco Hoekwater schrieb: Peter Rolf wrote: I followed that one. But my problem is more the *wrong strut height*, e.g. using a \totalstrut value of 12pt with a 8pt font. The strut height is simply not adapted to the actual font size anymore (even if I use \setstrut). I can understand why

Re: [NTG-context] \definefont problem with latest beta (mkiv)

2008-11-12 Thread Peter Rolf
Hans Hagen schrieb: Peter Rolf wrote: Taco Hoekwater schrieb: Peter Rolf wrote: I followed that one. But my problem is more the *wrong strut height*, e.g. using a \totalstrut value of 12pt with a 8pt font. The strut height is simply not adapted to the actual font size anymore (even if I use

Re: [NTG-context] \definefont problem with latest beta (mkiv)

2008-11-11 Thread Wolfgang Schuster
Am 11.11.2008 um 17:40 schrieb Peter Rolf: You should write new typescripts/files for MkIV because you could use Truetype fonts without map and tfm files. Yes, this works and is also faster. But now I have a different positioning (text baseline is too low, plus bigger interline spacing),

Re: [NTG-context] \definefont problem with latest beta (mkiv)

2008-11-11 Thread Peter Rolf
Wolfgang Schuster schrieb: Am 11.11.2008 um 17:40 schrieb Peter Rolf: You should write new typescripts/files for MkIV because you could use Truetype fonts without map and tfm files. Yes, this works and is also faster. But now I have a different positioning (text baseline is too low, plus

Re: [NTG-context] \definefont problem with latest beta (mkiv)

2008-11-11 Thread Peter Rolf
Wolfgang Schuster schrieb: On Tue, Nov 11, 2008 at 2:37 PM, Peter Rolf [EMAIL PROTECTED] wrote: Hi. First of all: mkii format generation still fails here because of [context.mkii] \loadmkiifile{core-swd} I added the mkii suffix here to make it run. Back to the subject. When

Re: [NTG-context] \definefont problem with latest beta (mkiv)

2008-11-11 Thread Peter Rolf
Wolfgang Schuster schrieb: On Tue, Nov 11, 2008 at 2:37 PM, Peter Rolf [EMAIL PROTECTED] wrote: Hi. First of all: mkii format generation still fails here because of [context.mkii] \loadmkiifile{core-swd} I added the mkii suffix here to make it run. Back to the subject. When

[NTG-context] \definefont problem with latest beta (mkiv)

2008-11-11 Thread Peter Rolf
Hi. First of all: mkii format generation still fails here because of [context.mkii] \loadmkiifile{core-swd} I added the mkii suffix here to make it run. Back to the subject. When using mkiv there is a problem in finding the map files of my fonts. Instead of the expanded value of

Re: [NTG-context] \definefont problem with latest beta (mkiv)

2008-11-11 Thread Wolfgang Schuster
On Tue, Nov 11, 2008 at 2:37 PM, Peter Rolf [EMAIL PROTECTED] wrote: Hi. First of all: mkii format generation still fails here because of [context.mkii] \loadmkiifile{core-swd} I added the mkii suffix here to make it run. Back to the subject. When using mkiv there is a problem in