and monospace fonts.
\starttypescript [serif,sans,mono] [uprightonly]
\definefontsynonym [\typescriptprefix\typescriptone Italic]
[\typescriptprefix\typescriptone]
\definefontsynonym [\typescriptprefix\typescriptone Slanted]
[\typescriptprefix\typescriptone]
\definefontsynonym
Denis Maier via ntg-context schrieb am 24.08.2024 um 08:25:
You could define a specific typescript for that without a definition for
bold.
Below is an implementation of your suggestion which gets rid of all font
styles for serif, sans serif and monospace fonts.
\starttypescript [serif,sans
out success, I
> could only get it to load when saving them in the current working directory
> but that is annoying, help me by telling me the correct way to install it...
> I leave you my code so you can review it and give me advice to improve it
>
> \starttypescript [sa
at is annoying, help me by telling me the correct way to install it... I
leave you my code so you can review it and give me advice to improve it
\starttypescript [sans] [urbanist]
\definefontsynonym
[Urbanist][file:urbanist-regular.otf*default][features=default]
\definefontsynonym
[UrbanistI
rectory, and below is the minimal source code!
"""
\starttypescriptcollection[CustomFontSelection]
\starttypescript [serif] [CustomFontSelection] [name]
\setups[font:fallback:serif]
\definefontsynonym [Serif]
% [file:font/Lora-Regular.ttf]
[file:font/Lora
ce code!
"""
\starttypescriptcollection[CustomFontSelection]
\starttypescript [serif] [CustomFontSelection] [name]
\setups[font:fallback:serif]
\definefontsynonym [Serif]
% [file:font/Lora-Regular.ttf]
[file:font/Lora-Medium.ttf]
[features=def
nte". It seems to be something in
"miCorm" that produces the protruding
\starttypescript[miFuente]
\definetypeface [miFuente] [rm] [serif] [libertinus] [default]
\definetypeface [miFuente] [ss] [sans] [libertinussans] [default]
\definetypeface [miFuente] [tt] [mono] [libert
pansion=quality,
]
\definefontfeature[smallcaps][% use with \addff
smcp=yes, % smallcaps
% c2sc=yes, % caps to smallcaps
]
\starttypescript[serif][libertinus]
\definefontsynonym[LibertinusSerif-Regular]
[file:/fonts/LibertinusSerif-Regular.otf]
\definefontsynonym[Liberti
ng fo rinstance
\starttypescript [sans] [AlegreyaMedium]
and then use
\switchtobodyfont[AlegreyaMedium]\sl
or
\AlegreyaMedium\sl
which is also more efficient than adding more variants
Ok, thank you – that’s what I was usually doing. So I won’t change it.
H
On 3/8/2024 5:55 PM, Henning Hraban Ramm wrote:
Hi, if I need an additional pair of upright and italic font faces, e.g.
a Medium or Light version, would it make sense to define them like this:
I'd just define a new typeface / bodyfont, using fo rinstance
\starttypescript
}
\let\md\normalmd
\let\mi\normalmi
\let\ms\normalms
\definehighlight[medium ] [command=no,style=medium]
\definehighlight[mediumitalic ] [command=no,style=mediumitalic]
\definehighlight[mediumslanted] [command=no,style=mediumslanted]
Is that necessary? And is it enough?
\starttypescript
s overwriting with
> > >> "T="&decimal(currentime) which has been used previously in textext()
> > >> before the for k=1 endfor loop. This overwriting happens only for the
> > >> first textext() which occurs inside the for k=1 endfor loop. A
me)) scaled 2 shifted(0,2in) withcolor
> >> magenta ; » is commented out, the first textext() inside the for k=1
> >> endfor loop is not drawn neither. It must be an issue with textext(),
> >> because when I replace textext() by lmt_outline[], the text i
. This overwriting happens only for the
> > >> first textext() which occurs inside the for k=1 endfor loop. All other
> > >> textext() inside the for k=1 endfor loop are not drawn at all. If the
> > >> line « draw textext("T="&decimal(curren
n at all. If the line
> >> « draw textext("T="&decimal(currentime)) scaled 2 shifted(0,2in) withcolor
> >> magenta ; » is commented out, the first textext() inside the for k=1
> >> endfor loop is not drawn neither. It must be an issu
inside the for k=1
> >> endfor loop is not drawn neither. It must be an issue with textext(),
> >> because when I replace textext() by lmt_outline[], the text is drawn.
> >>
> >> Adjusted mwe:
> >>
> >> \enableregime[utf] % enable unicoded input
>
n.
>>
>> Adjusted mwe:
>>
>> \enableregime[utf] % enable unicoded input
>>
>> \definefontfamily [RomanFont] [rm] [calluna]
>>
>> \definefontfamily [KoreanFont] [rm] [applemyungjo]
>>
>> \definefontfamily [JapaneseFont] [rm] [hannotatesc]
>>
>> \de
neseFont] [rm] [hannotatesc]
>
> \definefontfeature
> [fea]
> [mode=node,language=dflt,script=arab,
> init=yes,
> medi=yes,
> fina=yes,
> isol=yes,
> calt=yes,
> rlig=yes,
> tlig=yes,
> trep=yes,
> curs=yes,
> kern=yes,
> mark=y
ly [JapaneseFont] [rm] [hannotatesc]
> \definefontfeature
> [fea]
> [mode=node,language=dflt,script=arab,
> init=yes,
> medi=yes,
> fina=yes,
> isol=yes,
> calt=yes,
> rlig=yes,
> tlig=yes,
> trep=yes,
> curs=yes,
> kern=yes,
> mark=yes
> ]
>
> \sta
r.
So to put it all together, this now works for me:
\definefontfamily [mainface] [rm] [TeX Gyre Pagella]
\definefontfamily [mainface] [ss] [TeX Gyre Heros]
\starttypescript [math] [default] [size]
\definebodyfont [8.5pt] [mm] [default]
\stoptypescript
\definetypeface [mainface] [mm]
[mainface, 8.5pt]
\starttext
\bold{\math{x_y}}
\stoptext
You get the same error with Latin Modern as soon as you use a non
predefined font size in combination with bold math.
begin example
% \starttypescript [math] [default] [size]
% \definebodyfont [8.5pt] [mm] [default
efontfeature
[fea]
[mode=node,language=dflt,script=arab,
init=yes,
medi=yes,
fina=yes,
isol=yes,
calt=yes,
rlig=yes,
tlig=yes,
trep=yes,
curs=yes,
kern=yes,
mark=yes
]
\starttypescript [serif] [notonaskharabic]
\definefontsynonym [notonaskharabic-Light] [name:notonaskharabic] [features=fea]
\d
gt;
> \definefontfamily [KoreanFont] [rm] [applemyungjo]
>
> \definefontfamily [JapaneseFont] [rm] [hannotatesc]
>
> \definefontfeature
> [fea]
> [mode=node,language=dflt,script=arab,
> init=yes,
> medi=yes,
> fina=yes,
> isol=yes,
> calt=yes,
&g
=yes,
fina=yes,
isol=yes,
calt=yes,
rlig=yes,
tlig=yes,
trep=yes,
curs=yes,
kern=yes,
mark=yes
]
\starttypescript [serif] [notonaskharabic]
\definefontsynonym [notonaskharabic-Light] [name:notonaskharabic] [features=fea]
\definefontsynonym [notonaskharabic-Bold] [name:notonaskharabic] [fe
,semibold,bold,black} {
\definetypescriptprefix [b:adobesource#1##1]
[-\typescriptprefix{b:as:##1}]
\definetypescriptprefix [bi:adobesource#1##1]
[-\typescriptprefix{b:as:##1}it]
}
}
\starttypescript
[adobesource,adobesourcedisplay,adobesourcelight,adobesourcedisplaylight]
%
-looking companion math font.
* A harmonious-looking companion math font that uses glyphs from Adobe
Serif 4 when available.
Thanks,
Vincent\starttypescriptcollection[adobesource]
\startluacode
require("adobesource")
\stopluacode
\starttypescript[serif,sans,mono]
[
a
ould visualize them but one never knows for sure if one
sees them)
nbsp are spaces and become glue that we can trace reliable in the node list
Many thanks. Ok, here is another MWE featuring a workaround using fallbacks:
==
\definefontfallback[nosymbols] [file:lmmono10-regular] [200C
for sure if one
sees them)
nbsp are spaces and become glue that we can trace reliable in the node list
Many thanks. Ok, here is another MWE featuring a workaround using fallbacks:
==
\definefontfallback[nosymbols] [file:lmmono10-regular] [200C,200D] [force=yes]
\starttypescript [s
]
% synonym mapping
\starttypescript [serif] [myfont] [name]
\loadfontgoodies[myfontlfg]
\definefontsynonym [Serif] [MyFontRegular][features=myfont-tf]
\definefontsynonym [SerifItalic] [MyFontItalic] [features=myfont-it]
\definefontsynonym [SerifBold] [MyFontBold
,cpsp=yes,smcp=yes, % smcp activie
trnsl=force]
% synonym mapping
\starttypescript [serif] [myfont] [name]
\loadfontgoodies[myfontlfg]
\definefontsynonym [Serif] [MyFontRegular]
[features=myfont-tf]
\definefontsynonym [SerifItalic] [MyFontItalic]
[features=myfont-it
]
% synonym mapping
\starttypescript [serif] [myfont] [name]
\loadfontgoodies[myfontlfg]
\definefontsynonym [Serif] [MyFontRegular][features=myfont-tf]
\definefontsynonym [SerifItalic] [MyFontItalic] [features=myfont-it]
\definefontsynonym [SerifBold] [MyFontBold
On 8/11/2023 6:19 PM, Vincent Hennebert wrote:
Say I want to use the Adobe Source font family in my document. They are
installed on my system, but the file names are different to what’s in the
typescript file provided with the ConTeXt distribution. If I do this:
\starttypescript [serif
Say I want to use the Adobe Source font family in my document. They are
installed on my system, but the file names are different to what’s in the
typescript file provided with the ConTeXt distribution. If I do this:
\starttypescript [serif] [source] [name]
\definefontsynonym [Serif
on \TeX\ shows a
> > > > > > > >
> > > > > > > > tSP:3.282
> > > > > > > > THK:-1.721
> > > > > > > > H__E
> > > > > > > > X
> > > > > > >
> > tSP:3.282
> > > > > > > THK:-1.721
> > > > > > > H__E
> > > > > > > X
> > > > > > > HK:-1.291
> > > > > > > SP:3.282
> > > > > >
> > > > > > n
te:
> > > > > On 7/5/2023 3:18 PM, Carlos wrote:
> > > > > > \showmakeup on \TeX\ shows a
> > > > > >
> > > > > > tSP:3.282
> > > > > > THK:-1.721
> > > > > > H__E
> > > >
t; > > tSP:3.282
> > > > THK:-1.721
> > > > H__E
> > > > X
> > > > HK:-1.291
> > > > SP:3.282
> > >
> > > no MWE includes so clueless
> >
> > \starttypescript[mylucidaserif]
> &g
SP:3.282
no MWE includes so clueless
\starttypescript[mylucidaserif]
\definefontsynonym[LucidaBrightRegular][file:LucidaBrightRegular]
\definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic]
\definefontsynonym[LucidaBrightDemiBold] [file:LucidaBrightDemiBold
t; > > tSP:3.282
> > > > THK:-1.721
> > > > H__E
> > > > X
> > > > HK:-1.291
> > > > SP:3.282
> > >
> > > no MWE includes so clueless
> >
> > \starttypescript[mylucidaserif]
> &g
On 7/5/2023 5:53 PM, Carlos wrote:
On Wed, Jul 05, 2023 at 04:43:56PM +0200, Hans Hagen wrote:
On 7/5/2023 3:18 PM, Carlos wrote:
\showmakeup on \TeX\ shows a
tSP:3.282
THK:-1.721
H__E
X
HK:-1.291
SP:3.282
no MWE includes so clueless
\starttypescript[mylucidaserif]
\definefontsynonym
> > > X
> > > HK:-1.291
> > > SP:3.282
> >
> > no MWE includes so clueless
>
> \starttypescript[mylucidaserif]
> \definefontsynonym[LucidaBrightRegular][file:LucidaBrightRegular]
> \definefontsynonym[LucidaBrightItalic]
On Wed, Jul 05, 2023 at 04:43:56PM +0200, Hans Hagen wrote:
> On 7/5/2023 3:18 PM, Carlos wrote:
> > \showmakeup on \TeX\ shows a
> >
> > tSP:3.282
> > THK:-1.721
> > H__E
> > X
> > HK:-1.291
> > SP:3.282
>
> no MWE includes so cluel
-0xF]
[check=no,force=no,rscale=0.85]
\starttypescript [contextstart]
\definetypeface [contextstart] [rm] [serif] [cambria]
[default][fallbacks=symbolaFB]
\definetypeface [contextstart] [ss] [sans] [segoe]
[default][fallbacks=arialFB]
\definetypeface [contextstart] [tt] [
xmf-dist/tex/context/base/mkiv/cont-yes.mkiv'
Minimal example:
\enableregime[utf]
\setuppapersize[A4]
\definefontfeature[default][default][fakecombining=yes,compose=yes]
\starttypescript [serif] [adobetextpro]
\definefontsynonym[AdobeTextPro-Regular]
[file:AdobeTextPro-Regular] [fea
issues on
two different systems one running a full TeXLive and the other on e
customized on-demand package installatino
but that part you said in the beginning:
> Normally context will fall bakc on latin modern but when you explicitly load
that's simply brilliant Hans
\starttype
c2sc=yes, % caps to smallcaps
]
\starttypescript[sans][roboto,robotosans]
\definefontsynonym[Roboto-Regular][name:robotoregular]
\definefontsynonym[Roboto-Black][name:robotoblack]
\definefontsynonym[Roboto-BlackItalic][name:robotoblackitalic]
\definefontsynonym[Roboto-Bold][name:robotobold]
style={\switchtobodyfont[roboto-flex,20pt]\ss}]
While the Garamond is embedded and text is styled, the chapter tible is
typeset with Garamond not Roboto.
Any hints or feed back will be very appriciated.
\usetypescriptfile[ebgaramond]
\starttypescript [sans] [robotoflex]
\setups[font:fallback
\setuppapersize[A4]
\starttypescript [serif] [myfont]
\setups[font:fallback:serif]
\definefontsynonym [Serif] [name:palatinoltstdlight] [features=default]
\definefontsynonym [SerifItalic] [name:palatinoltstdlightitalic]
7;re right that loading a map file is not needed, but If you're concerned
> > about afm files then bring these files over to the working directory, and
> > then mtxrun --generate the same
> >
> > So yes. Even though the file was something like (intended
ect?) but since the map file is no longer necessary then afm
should suffice
\starttypescript [serif] [lucida] [texnansi]
\definefontsynonym[LucidaBrightDemiBold][texnansi-lucidabrightdemibold][encoding=texnansi]
\definefontsynonym[LucidaBrightDemiItalic][texnansi-lucidabrightdemiit
ect?) but since the map file is no longer necessary then afm
should suffice
\starttypescript [serif] [lucida] [texnansi]
\definefontsynonym[LucidaBrightDemiBold][texnansi-lucidabrightdemibold][encoding=texnansi]
\definefontsynonym[LucidaBrightDemiItalic][texnansi-lucidabrightde
ypescripts for Lucida so that casual
and fax (and all the other various Lucida fonts, really) are easily accessible.
Something like:
\starttypescript[serif][lucbr]
\definefontsynonym[Serif][name:LucidaBright]
\definefontsynonym[SerifItalic][name:LucidaBright-Italic]
\definefontsynonym
lucidacasual normal normal normal normal lucidacasual
/home//.fonts/LucidaCasual.ttf
Then the following code should work :
\starttypescript [myserif]
\definefontsynonym[LucidaCasual-Regular] [file:LucidaCasual.ttf]
\stoptypescript
\starttypescript [myserif]
\setups
]
\starttypescript[mainface]
\definetypeface[mainface][rm][serif][pagella][default]
\definetypeface[mainface][ss][sans] [modern] [default][rscale=1.075]
\definetypeface[mainface][tt][mono] [modern] [default][rscale=1.075]
\definetypeface[mainface][mm][math] [pagella][default][fallbacks=cal
when I do \setupbodyfont[mainface,rm].
Cheers,
Jacob
\definefontfallback[cal-fallback][name:modern][uppercasescript,lowercasescript]
\starttypescript[mainface]
\definetypeface[mainface][rm][serif][palatino][default]
\definetypeface[mainface][ss][sans] [modern] [default][rscale=1.075]
\defi
specimen/Roboto
Here is my code:
[...]
\starttypescript [sans] [roboto]
\definebodyfont [default] [rm]
Replace [rm] with [ss]:
\definebodyfont [default] [ss]
[lf=SansLight sa 1,
li=SansLightItalic sa 1,
tf=Sans sa 1,
it=SansItalic sa 1,
md=S
context garden example typescript for Roboto:
\definefontfeature[robotofeatures][
mode=node,
ccmp=yes, % character composition
liga=yes, tlig=yes, % ligatures
pnum=yes,
cpsp=yes, % capital spacing
kern=yes,
language=dflt,
protrusion=quality,
expansion=quality,
]
\definefon
ht
\definefontalternative[li] % lightitalic
\definefontalternative[md] % medium
\definefontalternative[mi] % mediumitalic
\starttypescript [sans] [roboto]
\definefontsynonym [SansLight][file:Roboto-Light]
[features=default]
\definefontsynonym [SansLightItalic] [file:Roboto
'sequence')
\starttypescriptcollection[myfonts]
% Mono - iosevka (Iosevka SS09 — Terminal, Hinted)
% Source: https://github.com/be5invis/Iosevka/blob/v16.3.6/doc/PACKAGE-LIST.md
\starttypescript [mono] [iosevka] [name]
\setups[font:fallback:mono]
\definefontsynonym [Mono][fi
le to define 'lato-regular' as
'lato-12pt-ss-tf-0--0'
---
If I change the file: reference I get it working with both MKIV/LMTX:
\starttypescript [\s!sans] [lato] [\s!name]
\setups[\s!font:\s!fallback:\s!sans]
% \definefontsynonym [\s!Sans] [\
> % replace tilde in LM
> \definefontfallback[tildeFB]
>[file:seguisym.ttf]
>[0x0007E-0x0007E]
>[force=yes]
>
>
> \starttypescript [start]
>\definetypeface [start] [rm] [serif] [cambria]
> [default][fallbacks={seguiFB,emoneFB}]
>\definetypeface [start] [
0x0-0xF]
[check=yes,force=no]
\definefontfallback[emoneFB]
[name:EmojiOneColor]
[0x0-0xF]
[check=yes,force=no]
% replace tilde in LM
\definefontfallback[tildeFB]
[file:seguisym.ttf]
[0x0007E-0x0007E]
[force=yes]
\starttypescript [start]
\definetypeface [sta
allback[tildeFB]
[file:seguisym.ttf]
[0x0007E-0x0007E]
[force=yes]
\starttypescript [start]
\definetypeface [start] [rm] [serif] [cambria]
[default][fallbacks={seguiFB,emoneFB}]
\definetypeface [start] [ss] [sans] [modern]
[default][fallbacks={seguiFB,emoneFB}]
\definetypeface [st
pplied to both
type = "ligature",
data = {
[0x2013] = { "-", "-" }, -- en dash
[0x2014] = { "-", "-", "-" }, -- em dash
}
}
\stopluacode
\definefontfeature [venetian-301-demi-ligatures] [v1=yes,
es,v3=yes]
>> Note that the names v1, v2 and v3 are entirely arbitrary. Also, the
>> \starttypescript section sets the font features to be just those I've
>> defined - potentially losing whatever 'default' would provide. But since the
>> font doesn'
Am 20.07.22 um 21:40 schrieb Bruce Horrocks via ntg-context:
\definefontfeature [venetian-301-demi-ligatures] [v1=yes,v3=yes]
\definefontfeature [venetian-301-BT-ligatures] [v2=yes,v3=yes]
Note that the names v1, v2 and v3 are entirely arbitrary. Also, the
\starttypescript section sets the
data = {
[0x2013] = { "-", "-" }, -- en dash
[0x2014] = { "-", "-", "-" }, -- em dash
}
}
\stopluacode
\definefontfeature [venetian-301-demi-ligatures] [v1=yes,v3=yes]
\definefontfeature [venet
tium]
\definefontfallback
[alegreyagentium-fallback]
[name:gentium]
[greekandcoptic,greekextended]
\starttypescript [serif]
[alegreya-serif,alegreya-light-serif,alegreya-medium-serif] [name]
\setups[font:fallback:serif]
\definefontsynonym[Serif] [name:alegreyaregular]
[features=def
That works perfectly, thank you very much Wolfgang!
On Sat, Jun 11, 2022 at 12:23 PM Wolfgang Schuster via ntg-context <
ntg-context@ntg.nl> wrote:
> Stefan Nedeljkovic via ntg-context schrieb am 11.06.2022 um 10:05:
> > Dear list,
> >
> > I have the following fil
Stefan Nedeljkovic via ntg-context schrieb am 11.06.2022 um 10:05:
Dear list,
I have the following file:
\starttypescript [lidia]
\definetypeface[lidia][rm][serif][lidiaweb][cpsp=yes]
\stoptypescript
\setupbodyfont[lidia,36pt]
\starttext
\startTEXpage[align=normal,width=100cm,autowidth=force
Dear list,
I have the following file:
\starttypescript [lidia]
\definetypeface[lidia][rm][serif][lidiaweb][cpsp=yes]
\stoptypescript
\setupbodyfont[lidia,36pt]
\starttext
\startTEXpage[align=normal,width=100cm,autowidth=force,offset=0pt]
\startalignment[middle]
2{\hskip 0em}412{\hskip 0em}772
> Dear list,
> >
> > A quick question about a font that has a separate file for small caps. I
> > have the following:
> >
> >
> > \starttypescript [sans] [dtl-documenta-sans-t]
> > \definefontsynonym[Sans] [name:dtldocumentasanst][features=default]
> > \
Am 25.05.22 um 22:23 schrieb Stefan Nedeljkovic via ntg-context:
Dear list,
A quick question about a font that has a separate file for small caps. I
have the following:
\starttypescript [sans] [dtl-documenta-sans-t]
\definefontsynonym[Sans] [name:dtldocumentasanst][features=default
Dear list,
A quick question about a font that has a separate file for small caps. I
have the following:
\starttypescript [sans] [dtl-documenta-sans-t]
\definefontsynonym[Sans] [name:dtldocumentasanst][features=default]
\definefontsynonym[SansItalic]
[name:dtldocumentasanstitalic][features
> >
> >
> > Sincerely,
> >
> > Stefan
> >
> > \definefontalternative[md]
> >
> > \definefontalternative[mi]
> >
>
;> > >
>> > > Dear list,
>> > >
>> > >
>> > > I'm trying to set up Custodia in LMTX, but the
>> > custodiasemibolditalic
>> > > won't show up. It shows
he
> > custodiasemibolditalic
> > > won't show up. It shows up regularly when I run mtxrun --script
> > fonts
> > > --list --all --pattern=Custodia
> > >
> > > I'm attaching the output for reference. Any help would b
t; Stefan
>
> \definefontalternative[md]
>
> \definefontalternative[mi]
>
>
> \starttypescript [serif] [custodia]
>
> \definefontsynonym[Serif] [name:custodianormal][features=default]
>
> \definefontsynonym[SerifItalic]
> [name:cust
gt; >
> > I'm attaching the output for reference. Any help would be appreciated.
> >
> >
> > Sincerely,
> >
> > Stefan
> >
> > \definefontalternative[md]
> >
> > \definefontalternative[mi]
> >
> >
> > \starttype
cerely,
Stefan
\definefontalternative[md]
\definefontalternative[mi]
\starttypescript [serif] [custodia]
\definefontsynonym[Serif] [name:custodianormal][features=default]
\definefontsynonym[SerifItalic]
[name:custodianormalitalic][features=default]
\definefontsynonym[SerifMedium] [name:custodiasem
cerely,
Stefan
\definefontalternative[md]
\definefontalternative[mi]
\starttypescript [serif] [custodia]
\definefontsynonym[Serif] [name:custodianormal][features=default]
\definefontsynonym[SerifItalic]
[name:custodianormalitalic][features=default]
\definefontsynonym[SerifMedium] [name:custodiasemibold][f
Робу и рачун примио \emdash КУПАЦ
\eTD
\eTR
\eTABLE
\stop
%\showlayout
\stoptext\starttypescript [mono] [ibmplex-thin]
\definefontsynonym[Mono] [name:ibmplexmonothin]
\definefontsynonym[MonoItalic] [name:ibmplexmonothinitalic]
\definefontsynonym[MonoBold] [name:ibmplexmonotext]
\definefontsy
27;m on ConTeXt
version 2022.05.02 16:19.
Here is a MWE using Almendra
(https://fonts.google.com/specimen/Almendra<https://fonts.google.com/specimen/Almendra?preview.text=Th%20Almost%20before%20we%20knew%20it,%20we%20had%20left%20the%20ground.%20&preview.text_type=custom>
view.text_type=custom>)
from Google Fonts.
```
\starttypescriptcollection[myfont]
\starttypescript[myfont]
\definefontsynonym[Serif][Almendra-Regular][features=default]
\stoptypescript
\starttypescript[myfont]
\definetypeface[\typescriptone][rm][serif][
16:21 schrieb Joel via ntg-context:
> I have a font that already comes with a smallcaps variant.
>
> How do I define it?
>
> I've tried the following, which I think should work from the
> documentation I've seen, but doesn't:
>
>
> \starttypescript[s
Am 24.04.22 um 16:21 schrieb Joel via ntg-context:
I have a font that already comes with a smallcaps variant.
How do I define it?
I've tried the following, which I think should work from the
documentation I've seen, but doesn't:
\starttypescript[serif]
I have a font that already comes with a smallcaps variant.
How do I define it?
I've tried the following, which I think should work from the documentation I've
seen, but doesn't:
\starttypescript[serif] [garamond]
\definefontsynonym[Serif]
ed by just using the default
ConTeXt font and the error still appears, also in
live.contextgarden.net. I tried searching the mailing list, as this
seems like something that must have come up, but couldn't find any
question about this.
Why won't it render both?
See Adams answer.
\st
must have
> come up, but couldn't find any question about this.
>
> Why won't it render both?
>
>
> \starttypescript[serif] [garamond]
> \definefontsynonym[Serif] [file:~/.fonts/12/EBGaramond-Regular.otf]
> \definefontsynonym[SerifBold] [file:~/.fonts/
ill appears, also in live.contextgarden.net. I tried searching the mailing
list, as this seems like something that must have come up, but couldn't find
any question about this.
Why won't it render both?
\starttypescript[serif] [garamond]\definefontsynonym[Serif]
[file:~/.f
]
\starttypescriptcollection [amiri]
\starttypescript [serif] [amiri]
\definefontsynonym [Serif] [file:Amiri-Regular.ttf]
[features=arabic]
\stoptypescript
\starttypescript [amiri]
\definetypeface [amiri] [rm] [serif] [amiri] [default]
[fallbacks=latin-fallback]
\stoptypescript
% \definefontsynonym[junicodeitalic] [\s!file:junicodetwobetavf-italic.ttf]
%
% \starttypescript [\s!serif] [junicode]
% \definefontsynonym [Junicode-Regular]
[junicoderegular][\s!features=default]
% \definefontsynonym [Junicode-Italic] [junicodeitalic]
[\s!features=default]
fault][script=latn]
% Libertine with a Junicode fallback, lib-fb-jun
\definefontfallback[junicodefallback][name:Junicode][privateusearea][check=yes,force=no]
\starttypescript [serif] [lib-fb-jun]
\definefontsynonym [Libertine-Roman] [file:linlibertiner]
\definefontsynonym [Libertine-Slant
>
> % Libertine with a Junicode fallback, lib-fb-jun
>
>
> \definefontfallback[junicodefallback][name:Junicode][privateusearea][check=yes,force=no]
>
> \starttypescript [serif] [lib-fb-jun]
>\definefontsynonym [Libertine-Roman] [file:linlibertiner]
>\definefontsynonym [Li
gt; spot anything.
>
> Does anyone have a suggestion as to another place to look? Or something
> I'm overlooking?
>
> Minimal example (attached too, if it comes through):
>
> ```
> \definefontfeature[default][default][script=latn]
>
>
> % Libertine with a Junicode fall
allback, lib-fb-jun
\definefontfallback[junicodefallback][name:Junicode][privateusearea][check=yes,force=no]
\starttypescript [serif] [lib-fb-jun]
\definefontsynonym [Libertine-Roman] [file:linlibertiner]
\definefontsynonym [Libertine-Slanted] [file:linlibertineri] % works fine
\stoptypescript
\st
PRAGMA ADE \& \CONTEXT\ Development Team}]
%C
%C This module is part of the \CONTEXT\ macro||package and is
%C therefore copyrighted by \PRAGMA. See mreadme.pdf for
%C details.
\starttypescriptcollection [kurier]
\starttypescript [\s!sans] [kurier-light,kurier,kurier-medium]
\def
nt
>
> My ConTeXt (LMTX) version is: 2021.08.30 19:56
>
> I am using the following typescript for Murty:
>
> \starttypescript [serif] [murty]
> \definefontsynonym
> [Serif]
> [name:murtysanskritregular]
> [features=devanagari-two]
> \
rendering (since I have no issues in XeLaTeX (using Harfbuzz)):
https://tex.stackexchange.com/questions/612634/devanagari-forms-in-context-using-shobhika-font
My ConTeXt (LMTX) version is: 2021.08.30 19:56
I am using the following typescript for Murty:
\starttypescript [serif] [murty
lig, as in the following example, things
> change, but they still aren't right:
>
> ```
>
> \starttypescriptcollection[keteryg]
>
> \starttypescript[serif][keteryg]
>
> \definefontsynonym[Serif][file:../fonts/KeterYG/KeterYG-Medium.ttf][features=hebrew]
> % al
1 - 100 of 1192 matches
Mail list logo
