Re: [NTG-context] set fallback in \definefont

Mohammad Hossein Bateni schrieb am 15.02.2021 um 22:31: Thanks for the quick response, Pablo.  I already use typescripts (\definetypeface, \definefontsynonym and \definefontfallback): https://github.com/bateni/dabeer/tree/master/texmf-local/tex/context/fonts/mkiv By arbitrary style, I meant so

Re: [NTG-context] set fallback in \definefont

>> > >> Is there a way to set the fallback for fonts when we define them not as > >> a typescript but using \definefont? > >> > >> \definefont[MyFont][Font.otf*MyFeatures] > >> > >> Is there a default fallback one can specify? > >> Is

Re: [NTG-context] set fallback in \definefont

Pagella]] https://wiki.contextgarden.net/Font_Switching says fontstyle is rm, ss, tt, mm, hw, cg, ... Because the the three dots at the end, I thought it would be possible to define new fontstyles. But I get an error if I do so. So I usually use \definefont to set up one-off fonts for specific use

Re: [NTG-context] set fallback in \definefont

Pablo Rodriguez schrieb am 15.02.2021 um 21:51: On 2/15/21 8:47 PM, Mohammad Hossein Bateni wrote: Hi, Is there a way to set the fallback for fonts when we define them not as a typescript but using \definefont? \definefont[MyFont][Font.otf*MyFeatures] Is there a default fallback one can

Re: [NTG-context] set fallback in \definefont

On 2/15/21 8:47 PM, Mohammad Hossein Bateni wrote: > Hi, > > Is there a way to set the fallback for fonts when we define them not as > a typescript but using \definefont? > > \definefont[MyFont][Font.otf*MyFeatures] > > Is there a default fallback one can specify?

[NTG-context] set fallback in \definefont

Hi, Is there a way to set the fallback for fonts when we define them not as a typescript but using \definefont? \definefont[MyFont][Font.otf*MyFeatures] Is there a default fallback one can specify? Is simplefonts module deprecated or discouraged now? When we define a font via typescript

Re: [NTG-context] How to define a font with an effect as a font with \definefont

> On 23 May 2020, at 20:06, Wolfgang Schuster > wrote: > > Pablo Rodriguez schrieb am 23.05.2020 um 20:02: >> On 5/23/20 11:52 AM, Gerben Wierda wrote: >>> [] >>> Actually, my setup is Optima with Helvetica used for Cyrillic: >>> >>> \definefallbackfamily >>> [archimate] >>> [ss] >>> [H

Re: [NTG-context] How to define a font with an effect as a font with \definefont

On 5/23/20 9:50 PM, Gerben Wierda wrote: > [...] >>> \definefontfeature >>>   [effect-widen] >>>   [effect={width=.2,delta=0.3}] >>> >>> \definefallbackfamily >>>   [archimate] >>>   [ss] >>>   [Helvetica] >>>   [preset=range:cyrillic, >>>    tf=style:light, >>>

Re: [NTG-context] How to define a font with an effect as a font with \definefont

On 5/23/2020 15:50, Gerben Wierda wrote: On 23 May 2020, at 20:06, Wolfgang Schuster > wrote: Pablo Rodriguez schrieb am 23.05.2020 um 20:02: On 5/23/20 11:52 AM, Gerben Wierda wrote: [] Actually, my setup is Optima with Helvetica used for Cyrilli

Re: [NTG-context] How to define a font with an effect as a font with \definefont

On 5/23/20 8:06 PM, Wolfgang Schuster wrote: > Pablo Rodriguez schrieb am 23.05.2020 um 20:02: >> On 5/23/20 11:52 AM, Gerben Wierda wrote: >>> [] >>> Actually, my setup is Optima with Helvetica used for Cyrillic: >>> >>> \definefallbackfamily >>>   [archimate] >>>   [ss] >>>   [Helvetica] >>>

Re: [NTG-context] How to define a font with an effect as a font with \definefont

Pablo Rodriguez schrieb am 23.05.2020 um 20:02: On 5/23/20 11:52 AM, Gerben Wierda wrote: [] Actually, my setup is Optima with Helvetica used for Cyrillic: \definefallbackfamily   [archimate]   [ss]   [Helvetica]   [preset=range:cyrillic,    tf=style:light,    it=style:lightoblique,    b

Re: [NTG-context] How to define a font with an effect as a font with \definefont

On 5/23/20 11:52 AM, Gerben Wierda wrote: > [] > Actually, my setup is Optima with Helvetica used for Cyrillic: > > \definefallbackfamily >   [archimate] >   [ss] >   [Helvetica] >   [preset=range:cyrillic, >    tf=style:light, >    it=style:lightoblique, >    bf=style:regular, >    bi=style:obliqu

[NTG-context] How to define a font with an effect as a font with \definefont

a \definefont so I can use that instead. Actually, my setup is Optima with Helvetica used for Cyrillic: \definefallbackfamily [archimate] [ss] [Helvetica] [preset=range:cyrillic, tf=style:light, it=style:lightoblique, bf=style:regular, bi=style:oblique, force=yes, rscale

Re: [NTG-context] definefont

is just one of many predefined feature sets: > > \definefontfeature >   [default] >   [always] >   [liga=yes, >    tlig=yes, >    trep=yes] Sure, and I guess that it is not activated by default by \definefont. In this case, "standard" might be a be

Re: [NTG-context] definefont

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 activa

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

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 mi

Re: [NTG-context] definefont

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] \definefont

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

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] \setuphead[chapter][style

Re: [NTG-context] Dimension in mkiv definefont

Am 02.07.2014 um 23:43 schrieb Uwe Koloska : > Dear list, > > the following runs fine in mkii (i.e. if compiled with 'texexec') but > gives an error with mkiv (compiled with 'context'): > > \showframe > > \newdimen\Ssize \Ssize=18pt > %\definef

[NTG-context] Dimension in mkiv definefont

Dear list, the following runs fine in mkii (i.e. if compiled with 'texexec') but gives an error with mkiv (compiled with 'context'): \showframe \newdimen\Ssize \Ssize=18pt %\definefont[MyFont][Serif at 18pt] \definefont[MyFont][Serif at \Ssize] \starttext \MyFont \input knu

Re: [NTG-context] "Missing number, treated as zero" error when using \definefont with \define'd dimension

ssing Number error, and I have a short example > that reproduces it: > > \define\largefontsize{13pt} > > % Works fine: \definefont[SerifL][Arial at 13pt] > % Leads to error: > \definefont[SerifL][Arial at \largefontsize] > > % "Missing number, treated as

[NTG-context] "Missing number, treated as zero" error when using \definefont with \define'd dimension

efine\largefontsize{13pt} % Works fine: \definefont[SerifL][Arial at 13pt] % Leads to error: \definefont[SerifL][Arial at \largefontsize] % "Missing number, treated as zero" error thrown on the following line: \starttext \SerifL{Hello} \stoptext Note that the SerifL font definition

Re: [NTG-context] default parameter in \definefont

Am 26.02.2013 um 16:04 schrieb john Culleton : > I hesitate to trouble you with a string of questions, > one by one. Right now the two critical files are: > \input formatting.tex > --- > > \usemodule [simplefonts] > \definefont

Re: [NTG-context] default parameter in \definefont

blem the ugly way. I moved the fonts to the > > directory where I was compiling the document. Added otf suffix to > > the \definefont file names. Now MKIV can find the fonts. > > > > A better solution is of course welcome. > > ___ Did you set OSFONTDIR? > ___ Does

Re: [NTG-context] default parameter in \definefont

ent. Added otf suffix to > the \definefont file names. Now MKIV can find the fonts. > > A better solution is of course welcome. ∙ Did you set OSFONTDIR? ∙ Does OSFONTDIR include /usr/share/fonts/OTF? ∙ Did you run mtxrun -script fonts -reload? ∙ Do these commands return the fonts? mtxru

Re: [NTG-context] default parameter in \definefont

hey exist in /usr/share/fonts/OTF. The run completes > but other fonts and sizes are used for the title page. > Solved my problem the ugly way. I moved the fonts to the directory where I was compiling the document. Added otf suffix to the \definefont file names. Now MKIV can find the fonts.

Re: [NTG-context] default parameter in \definefont

On Tue, 26 Feb 2013 08:18:25 +0100 Wolfgang Schuster wrote: > > Am 26.02.2013 um 00:00 schrieb john Culleton : > > > Some time back Wolfgang advised me to use statements like this: > > \definefont [titlefont][MyriadPro-Bold*default at 70bp] > > > > I cannot

Re: [NTG-context] default parameter in \definefont

Am 26.02.2013 um 00:00 schrieb john Culleton : > Some time back Wolfgang advised me to use statements like this: > \definefont [titlefont][MyriadPro-Bold*default at 70bp] > > I cannot find what the *default parameter does. Can someone educate me? When you use a font in MkIV you hav

[NTG-context] default parameter in \definefont

Some time back Wolfgang advised me to use statements like this: \definefont [titlefont][MyriadPro-Bold*default at 70bp] I cannot find what the *default parameter does. Can someone educate me? -- John Culleton Wexford Press Free list of books for self-publishers: http://wexfordpress.net

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

as a large x-height > so you can best use a different interline specification, like > > x\strut qgjyQWT\par > \setupinterlinespace[line=1.2\bodyfontsize] > x\strut qgjyQWT\par > > you might even want to change the height:depth ratio (keep in mind that > we cannot predi

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

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 anymor

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

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

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

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 >>> \set

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

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 n

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

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 anymor

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

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 >>> \setst

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

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 under

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

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 di

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

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 t

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

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 spa

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

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 t

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

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 t

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

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

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

ptfile[type-cow] \usetypescript[all][cow][default] \usetypescript[cow][default] \definefont [TestFont] [Cows at 40pt] \starttext {\TestFont Just a test.} \stoptext ___ If your question is of interest to others as well, please

Re: [NTG-context] How to use text Calligraphic font using \definefont

On Wed, 6 Dec 2006, John R. Culleton wrote: > On Tuesday 05 December 2006 17:27, Aditya Mahajan wrote: >> Hi, >> > >> \definefont[BigText] [Calligarphic sa 2] >> >> \BigText test >> >> which gives me the math calligraphic fonts. How do I get t

Re: [NTG-context] How to use text Calligraphic font using \definefont

do ut des ( it.wikipedia.org/wiki/Do_ut_des in the first sense «io do affinché tu dia») luigi ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] How to use text Calligraphic font using \definefont

On Tuesday 05 December 2006 17:27, Aditya Mahajan wrote: > Hi, > > \definefont[BigText] [Calligarphic sa 2] > > \BigText test > > which gives me the math calligraphic fonts. How do I get the text > calligraphic fonts, using \definefont? The virtue of the Context syst

[NTG-context] How to use text Calligraphic font using \definefont

] [encoding=texnansi] \definetypeface [boldface] [mm] [boldmath][euler] [euler] [encoding=texnansi,rscale=1.03] \setupbodyfont[mainface,11pt] I want to use the Calligraphic font font for headers etc, so I tried \definefont[BigText] [Calligarphic sa 2] \BigText test