Thanks a lot!
On Sat, Apr 12, 2025 at 3:38 AM Hans Hagen via ntg-context <
ntg-context@ntg.nl> wrote:
> On 4/12/2025 2:35 AM, Mohammad Hossein Bateni wrote:
> > Hello,
> >
> > \addff (and \doaddfeature) no longer seem to work. What's the
> > alterna
On 4/12/2025 2:35 AM, Mohammad Hossein Bateni wrote:
Hello,
\addff (and \doaddfeature) no longer seem to work. What's the
alternative to add/remove features on the fly?
nothing changed there
move the luacode before the \starttext or any place before the main font
is defined be
Hello,
\addff (and \doaddfeature) no longer seem to work. What's the alternative
to add/remove features on the fly?
MNWE:
===
\starttext
\startluacode
fonts.handlers.otf.addfeature{
name = "fanum",
type = "substitution",
data = {
[0
gt;> Line 2: {\setff{oldstylenumber}VAVAVAVAVAVA 12345}\par
>> Line 3: {\addff{oldstylenumber}VAVAVAVAVAVA 12345}\par
>> \testnoto
>> Line 4: {VAVAVAVAVAVA 12345}\par
>> Line 5: {\setff{oldstylenumber}VAVAVAVAVAVA 12345}\par
>> Line 6: {\addff{oldstylenumber}VAVAVAVAVAVA
setff{oldstylenumber}VAVAVAVAVAVA 12345}\par
Line 3: {\addff{oldstylenumber}VAVAVAVAVAVA 12345}\par
\testnoto
Line 4: {VAVAVAVAVAVA 12345}\par
Line 5: {\setff{oldstylenumber}VAVAVAVAVAVA 12345}\par
Line 6: {\addff{oldstylenumber}VAVAVAVAVAVA 12345}\par
\stoptext
Line 4 and 6 should be significantly shorter t
Hi all,
I can't get Kerning working with Noto Serif.
My minimal file is:
\definefontfeature[oldstylenumber][onum=yes]
\definefont[testnoto][file:NotoSerif-Regular*default at 12pt]
\starttext
Line 1: {VAVAVAVAVAVA 12345}\par
Line 2: {\setff{oldstylenumber}VAVAVAVAVAVA 12345}\par
Line 3: {\
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
Serif or SerifCaps.
Now I can load a goodies file myfontlfg and do something like this:
local smallcaps = {
smcp = yes,
}
But that does not change the behavior of \sc.
Yes, there is an easy workaround:
\definefontfeature[smallcaps][smcp=yes]
\define\sc{\addff{smallcaps}}
This works for all
\sc{\addff{smallcaps}}
This works for all styles that have the smcp feature, but I don't like
having to redefine a system command.
So the questions are:
1) Is there a recommended\better way to get \sc to work across all
styles?
\setupbodyfont[pagella]
\starttext
\tf Upright, \it I
applies to Serif or SerifCaps.
Now I can load a goodies file myfontlfg and do something like this:
local smallcaps = {
smcp = yes,
}
But that does not change the behavior of \sc.
Yes, there is an easy workaround:
\definefontfeature[smallcaps][smcp=yes]
\define\sc{\addff{smallcaps}}
This works
Dear gang,
Consider the following example:
==
\setupdirections[bidi=global,method=one]
\startTEXpage[offset=1em,width=14in]
\definedfont[almfixed*arabic]
\switchtobodyfont[almfixed*arabic]
\switchtobodyfont[almfixed]
% \addff{arabic}
\startbuffer[]
\startlines
الثَّعْلَبُ
ature[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,
]
\definefontfeature[smallcaps][ % use with \addff
smcp=yes, % smallcaps
%
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
uot;`" },
> ['’'] = { "'" }
> }
> }
Since `` and "' map to the same character, only "' works.
The table has only 5 entries, not 6! (This took me a while to realize. ;))
> best not use an existign feature because we ac
;texlig",
type = "ligature",
data = {
['“'] = { "`", "`" },
['”'] = { "'", "'" },
['„'] = { '"', "`" },
[''] = { '"', "'" },
['‘'] = { "`" },
['’'] = { "'" }
}
}
fonts.handlers.otf.addfeature {
name = "texs
"', "'" },
['‘'] = { "`" },
['’'] = { "'" }
}
}
fonts.handlers.otf.addfeature {
name = "texsub",
type = "substitute",
data = {
[''
On 10/20/2021 1:01 PM, Mikael Sundqvist via ntg-context wrote:
Hi,
looking at the output of
\setupbodyfont[libertinus]
%\setupmathematics[stylealternative={ssty}]
\starttext
%\addff{ssty}
$y'=f'$
\switchtobodyfont[newcomputermodern-book]
$y'=f'$
\stoptext
ssty doesn&#
Hi,
looking at the output of
\setupbodyfont[libertinus]
%\setupmathematics[stylealternative={ssty}]
\starttext
%\addff{ssty}
$y'=f'$
\switchtobodyfont[newcomputermodern-book]
$y'=f'$
\stoptext
I think that the primes in libertinus are too small. Indeed, looking
in the font
eteryg]
>
> %Set up right-to-left alignment:
>
> \setupalign[r2l]
>
> %Explicitly add dlig (in case it wasn't there already):
>
> \definefontfeature[plus-dlig][dlig=yes]
>
>
> \starttext
>
> \addff{plus-dlig}
>
> שֹׂבַע
>
> עָשׂוֹר
>
> קֹשֶ
lt]
\stoptypescript
\stoptypescriptcollection
%Set up the main font:
\setupbodyfont[keteryg]
%Set up right-to-left alignment:
\setupalign[r2l]
%Explicitly add dlig (in case it wasn't there already):
\definefontfeature[plus-dlig][dlig=yes]
\starttext
\addff{plus-dlig}
שֹׂבַע
עָשׂוֹר
קֹש
] [primes=yes]
% \definefontfeature[uppercasing][uppercasing=yes]
% \definefontfeature[lowercasing][lowercasing=yes]
% \definefontfeature[camelcasing][camelcasing=yes]
\setupbodyfont[dejavu]
\starttext
\startTEXpage[align={tolerant,stretch},offset=1ex]
{\addff{camelcasing} \samplefile{tufte
ote related stuff on board i'm
also not going to explore it ... when apostrophes get translated as you
do but with active characters it's no fun (ok, we still have a few in
context like ~ and |)
just for fun i made
{\addff{primes} 123'345''\par}
u
\setupheadertexts[chapter][{\addff{normnum}\pagenumber}][{\addff{normnum}\pagenumber}][]
\stopsetups
\startsetups noheader
\setupheadertexts[][][][]
\stopsetups
\startsetups bigchapter
\setupalign[flushleft,hz,hanging,verytolerant,nothyphenated]
\doifelse{\structureuservariable{image}}{}{% if
\getbuffer[ss01]}
{\type{enabled } \JHair \addff{ss01}\getbuffer[ss01]}
{\type{disabled} \JHair \subff{ss01}\getbuffer[ss01]}
{\type{default } \JHairI\getbuffer[ss01]}
{\type{enabled } \JHairI\addff{ss01}\getbuffer[ss01]}
{\type{disa
luacode
fonts.handlers.otf.addfeature {
name = "wtest",
type = "ligature",
data = {
['1'] = { "left_boundary", "a" },
}
}
\stopluacode
\definefontfeature[wtest][wtest=yes]
\definefontfeature[ltest][ltes
"wtest",
type = "ligature",
data = {
['1'] = { "left_boundary", "a" },
}
}
\stopluacode
\definefontfeature[wtest][wtest=yes]
\definefontfeature[ltest][ltest=yes]
\starttext
\definedfont[file:dejavu-serif.tt
086097, 1-7:~1087411, 0-7:~1087439, 2-8:~1099942,
>> 1-8:~1101249, 0-8:~1101277, 2-9:~1102409, 1-9:~1103718, 0-9:~1103746,
>> 4-6:~1138989, 4-7:~1180436, 4-8:~1194617, 4-9:~1196971, 5-3:~1729640,
>> 4-5:~1756438, 5-0:~1761922, 5-1:~1761941, 5-2:~1763565, 5-6:~2459757,
>> 5-7:~
:~1763565, 5-6:~2459757, 5-7:~2548510, 5-8:~2555440,
5-9:~2558871
}}
\stoptext
1. Use tabular numbers and hard-code all of the spaces you need:
\definefontfeature[default][default][tnum=yes]
or
\definefontfeature[ff:tnum][tnum=yes] ... \addff{ff:tnum} or
\feature[+][ff:tnum] where
small a and b
>> [0x02032] = { [0x00028] = -150 }, -- prime and left parenthesis
>> }
>> }
>> \stopluacode
>>
>> \definefontfeature[kerntest][kerntest=yes]
>>
>> \definefontfamily[lucidaopentype][rm][Lucida Bright OT]
>> \definefontfamily[lucidao
x00028] = -150 }, -- prime and left parenthesis
}
}
\stopluacode
\definefontfeature[kerntest][kerntest=yes]
\definefontfamily[lucidaopentype][rm][Lucida Bright OT]
\definefontfamily[lucidaopentype][mm][Lucida Bright Math OT]
\setupbodyfont[lucidaopentype,10pt]
\startTEXpage[offset=3pt]
abba
tical italic small a and b
>>> [0x02032] = { [0x00028] = -150 }, -- prime and left parenthesis
>>> }
>>> }
>>> \stopluacode
>>>
>>> \definefontfeature[kerntest][kerntest=yes]
>>>
>>> \definefontfamily[lucidaopentype][rm][Lucida Brig
}, -- a and b in text
>> [0x1d44e] = { [0x1d44f] = -150 }, -- mathematical italic small a and b
>> [0x02032] = { [0x00028] = -150 }, -- prime and left parenthesis
>> }
>> }
>> \stopluacode
>>
>> \definefontfeature[kerntest][kerntest=yes]
>>
>> \definefontfamily
> \definefontfeature[kerntest][kerntest=yes]
>
> \definefontfamily[lucidaopentype][rm][Lucida Bright OT]
> \definefontfamily[lucidaopentype][mm][Lucida Bright Math OT]
>
> \setupbodyfont[lucidaopentype,10pt]
>
>
> \startTEXpage[offset=3pt]
> abba $abba f'(x)$
&
rntest][kerntest=yes]
\definefontfamily[lucidaopentype][rm][Lucida Bright OT]
\definefontfamily[lucidaopentype][mm][Lucida Bright Math OT]
\setupbodyfont[lucidaopentype,10pt]
\startTEXpage[offset=3pt]
abba $abba f'(x)$
\addff{kerntest}
abba $abba f'(x)$
I prefer $f'\mkern-
usetypescriptfile[libertine]
\setupbodyfont[libertine,12pt]
\definefontfeature[frac][frac=yes]
\starttext
{\addff{frac} 1/2 3/4 5/6 7/8 9/10 11/12 31415/27182 1000/100}
\stoptext
if you see
fonts > otf chain > feature 'frac', type
'gsub_contextchain', chain lookup &
?
\addff{leftbounds}
Wer War?
Wer\subff{leftbounds} War?
\stopTEXpage
\stoptext
I’m afraid that the OT feature lfbd is applied in all the line.
Otherwise, the second and the third lines would have the same spacing
between words.
Could anyone confirm this or am I missing
Dear list,
I have the following sample:
\showframe
\definefontfeature[leftbounds][lfbd=yes]
\definefontfamily[mainface][rm][Linux Libertine O]
\setupbodyfont[mainface, 150pt]
\starttext
\startTEXpage[offset=1ex]
Wer War?
\addff{leftbounds}
Wer War?
Wer
breakpoints[compound] makes ConTeXt ignore the "frac" feature at
all.
Please try this:
\definefontfeature[frac][frac=yes]
\definefontfamily[default][rm][lato][features=frac]
\setupbodyfont[default,rm,11pt]
\setbreakpoints[compound]
\starttext
\addff{frac} 1/3, 1/100, 1/1000, {\setbreakp
eXt ignore the "frac" feature at
all.
Please try this:
\definefontfeature[frac][frac=yes]
\definefontfamily[default][rm][lato][features=frac]
\setupbodyfont[default,rm,11pt]
\setbreakpoints[compound]
\starttext
\addff{frac} 1/3, 1/100, 1/1000, {\setbreakpoints[reset]1633/100},
2345/12.
\sto
On Sat, 4 Feb 2017 09:10:33 -0700
Alan Braslau wrote:
> On Fri, 3 Feb 2017 17:26:35 -0500
> Rik Kabel wrote:
>
> > Is there a user-level control for the styling of urls in the new
> > bibliography system? I use
> >
> > \setupurl[style=\addff{f:
On Fri, 3 Feb 2017 17:26:35 -0500
Rik Kabel wrote:
> Is there a user-level control for the styling of urls in the new
> bibliography system? I use
>
> \setupurl[style=\addff{f:ns}\ss]
>
> (where f:ns is a fontfeature definition for lining/new style
> numerals) for the
ConTeXters,
Is there a user-level control for the styling of urls in the new
bibliography system? I use
\setupurl[style=\addff{f:ns}\ss]
(where f:ns is a fontfeature definition for lining/new style numerals)
for the rest of the document. The bibliography honors this formatting
for urls
ce=yes,offset=digitsnormal]
\definefontsynonym
[MathRoman][name:modern][features={math\mathsizesuffix,mathperiod},goodies=lm-math,fallbacks=mathdigits]
\starttext
$123.45.$
123.45.
\addff{mathperiod}
123.45.
\stopte
gt;> \stopluacode
>>
>> \definefontfeature[mathperiod][mpf=yes]
>>
>> \resetfontfallback [mathdigits]
>> %\definefontfallback[mathdigits][dejavusansmono][digitsexten
>> dedarabicindic][check=yes,force=yes,offset=digitsnormal]
>>
>>
[MathRoman][name:modern][features={math\mathsizesuffix,mathperiod},goodies=lm-math,fallbacks=mathdigits]
\starttext
$123.45.$
123.45.
\addff{mathperiod}
123.45.
\stoptext
Though this font feature works outside math, it does not seem to
have any effect within t
nonym
[MathRoman][name:modern][features={math\mathsizesuffix,mathperiod},goodies=lm-math,fallbacks=mathdigits]
\starttext
$123.45.$
123.45.
\addff{mathperiod}
123.45.
\stoptext
Though this font feature works outside math, it does not seem to have
any effect within the math font. Why is that? Can w
>> before = { digits },
>> lookups = { 1 },
>> }
>> }
>> }
>> }
>> \stopluacode
>>
>> \definefontfeature[mathperiod][mpf=yes]
>>
>> \resetfontfallback [mathdigits]
>
][digitsextendedarabicindic][check=yes,force=yes,offset=digitsnormal]
>
> \definefontsynonym
> [MathRoman][name:modern][features={math\mathsizesuffix,mathperiod},goodies=lm-math,fallbacks=mathdigits]
>
> \starttext
> $123.45.$
>
> 123.45.
>
> \addff{mathperiod}
>
esuffix,mathperiod},goodies=lm-math,fallbacks=mathdigits]
\starttext
$123.45.$
123.45.
\addff{mathperiod}
123.45.
\stoptext
Though this font feature works outside math, it does not seem to have any
effect within the math font. Why is that? Can we add font feature to the
math font? Are the charac
me = "stest",
type = "substitution",
data = {
a = "X",
b = "P",
}
}
\stopluacode
\definefontfeature[stest][stest=yes]
\starttext
\startTEXpage
\definedfont[file:DejaVuSerif.ttf*default]%
abracadabra\par
{\addff{stest}abracadabra\par}
\stopTEXpage
\s
ot;a" } },
current = { { "b", "c" } },
lookups = { 1 },
},
},
},
}
\stopluacode
\definefontfeature[stest][stest=yes]
\definefontfeature[atest][atest=yes]
\definefontfeature[mtest][mtest
["b"] = "B",
> ["c"] = "C",
> },
> },
> },
> -- steps= {
> -- {
> -- rules = {
> -- {
> -- before = { { &qu
},
-- },
-- },
-- },
data = {
rules = {
{
before = { { "a" } },
current = { { "b", "c" } },
lookups = { 1 },
},
]
\definefontfamily [mainface][mm][TeX Gyre Pagella Math]
\definefontfeature[f:sups][sups=yes]
\setupbodyfont[mainface]
\setupnote[footnote][textcommand=,textstyle=\addff{f:sups}]
\setupnotation[footnote][numbercommand=,headstyle=\addff{f:sups}]
\starttext
\input knuth\footnote{Knuth sample
]
\setupbodyfont[mainface]
\setupnote[footnote][textcommand=,textstyle=\addff{f:sups}]
\setupnotation[footnote][numbercommand=,headstyle=\addff{f:sups}]
\starttext
\input knuth\footnote{Knuth sample text}
\input ward\footnote{Ward sample text}
\stoptext
i'll add:
\definefontfe
[footnote][textcommand=,textstyle=\addff{f:sups}]
\setupnotation[footnote][numbercommand=,headstyle=\addff{f:sups}]
\starttext
\input knuth\footnote{Knuth sample text}
\input ward\footnote{Ward sample text}
\stoptext
\definefontfamily [mainface][mm][TeX Gyre Pagella Math]
\definefontfeature[f:sups][sups=yes]
\setupbodyfont[mainface]
\setupnote[footnote][textcommand=,textstyle=\addff{f:sups}]
\setupnotation[footnote][numbercommand=,headstyle=\addff{f:sups}]
\starttext
\input knuth\footnote{Knuth sample te
se \startsectionblockenvironment to set the setups at the begin of the
document.
> I tried to play with
>\defineconversionset
> and
>\setupsectionblock
>[appendix]
>[sectionconversionset=...]
> but I'm unable to understand how these commands work
On 5/23/2014 5:55 PM, Mojca Miklavec wrote:
Hi,
I always forget how to use bold or italic small caps (I keep mixing
addff/setff and smcp/+smcp/smallcaps etc.). In ideal world it could be
nice if simply
{\sc Normal and \bf Bold Small Caps} or
{\bf\sc Bold Small Caps}
would work out-of
Am 23.05.2014 um 17:55 schrieb Mojca Miklavec :
> Hi,
>
> I always forget how to use bold or italic small caps (I keep mixing
> addff/setff and smcp/+smcp/smallcaps etc.). In ideal world it could be
> nice if simply
>{\sc Normal and \bf Bold Small Caps} or
>{\
Hi,
I always forget how to use bold or italic small caps (I keep mixing
addff/setff and smcp/+smcp/smallcaps etc.). In ideal world it could be
nice if simply
{\sc Normal and \bf Bold Small Caps} or
{\bf\sc Bold Small Caps}
would work out-of-the-box.
The first hit on the wiki was
http
-8<---cut here---start->8---
> \definefontfamily[mainface][rm][Linux Libertine Initials O][features=tnum]
> \definefontfeature[default][default][tnum=yes]
> \setupbodyfont[mainface]
> \starttext
> \addff{tnum}
> \setff{tnum}
> \feature[+][tnum
ine]
\resetfeature \feature[reset] \feature[<]
\stoptyping
Each variant also accepts \type {{}} instead of \type {[]} so that they
can conveniently be used in square bracket arguments.
This mechanism replaces \addff cum suis, although for a while they will
stay around (mappe
, I'm assuming
this does not include the default ones defined, e.g., in the typescripts).
Question: Does/Will this mechanism completely replace \addff et al, or
will these mechanism ignore each other (e.g., \resetfeature does not pop
those defined by \addff).
A good exercise in understanding
for \subfs as well.
Hmm, it seems that \subfs functionality is built in through the same
mechanism. Will study this some more...
yes, but there in successive calls the last one counts
\addff{x} \addff{y} \addff{z} -> z is used on top of the current font's set
\feature{x} \f
speak.
\resetfeature pops all features added to the stack (again, I'm assuming
this does not include the default ones defined, e.g., in the typescripts).
This reverts back to the features that are set when the font is defined.
Question: Does/Will this mechanism completely replace \addff et a
tures added to the stack (again, I'm assuming
this does not include the default ones defined, e.g., in the typescripts).
Question: Does/Will this mechanism completely replace \addff et al, or
will these mechanism ignore each other (e.g., \resetfeature does not pop
those defined by \addf
ent for \subfs as well.
>>
>>
>> Hmm, it seems that \subfs functionality is built in through the same
>> mechanism. Will study this some more...
>
>
> yes, but there in successive calls the last one counts
>
> \addff{x} \addff{y} \addff{z} -> z is used on to
mechanism. Will study this some more...
yes, but there in successive calls the last one counts
\addff{x} \addff{y} \addff{z} -> z is used on top of the current font's
set
\feature{x} \feature{y} \feature{y} -> all are used on top
we might end up with replacing \addff etc by one mechanism
wants to enable in small text snippets. For this we have
\addff etc but these don't accumulate.
We used to have \addfs{} and \subfs{}, meaning "add
feature to the stack" and "subtract feature from the stack". But those
have been broken for a very long time.
afaik the
name).
\stack might be better, for the following reason:
Many fonts have language dependent features. There are also features
that one only wants to enable in small text snippets. For this we have
\addff etc but these don't accumulate.
We used to have \addfs{} and \subfs{}, me
Hi,
There is a new experimental feature and (at least for now) it's also
called \feature (maybe not the best name).
Many fonts have language dependent features. There are also features
that one only wants to enable in small text snippets. For this we have
\addff etc but these
text to show the smallcaps. I
tried an example out of this mailing list:
\definefontfeature[smallcapitals] [smcp=yes]
\definefontfeature[oldstylenumber][onum=yes]
%\setupbodyfont[pagella]
\setupbodyfont [charissil]
\starttext
{VA abc \setff{smallcapitals} VA abc}
{VA abc \addff{smallcapitals} VA
Am 28.11.2012 um 11:18 schrieb Sietse Brouwer :
> \setff{X} enables font feature X in the current scope --- do I
> understand this correctly?
> --Sietse
It enables a predefined set of features which need to define with
\definefontfeature.
There is also a difference between \setff a
On 17-10-2012 16:08, Philipp Gesang wrote:
Hi all,
this works in TL but not minimals:
·
\definefontfeature[textfigures] [onum=yes]
\definefontfeature[texligatures] [tlig=yes]
\starttext
\addff{textfigures} 1234567890
\addff
Hi all,
this works in TL but not minimals:
·
\definefontfeature[textfigures] [onum=yes]
\definefontfeature[texligatures] [tlig=yes]
\starttext
\addff{textfigures} 1234567890
\addff{texligatures} foo---bar
\stoptext
size=10pt, tnum=yes]
> \starttext
> \addff{tnum}
> \setff{tnum}
> 565656565656X\par
> X
> \stoptext
> --8<---cut here---end--->8---
\usemodule[simplefonts]
\definefontfeature[default][default][tnum=yes]
\setmainfont[Linux
Hi,
How can I enable tabular numerals please?
Test file, that does not work:
--8<---cut here---start->8---
\usemodule[simplefonts]
\setmainfont[LinLibertineIO][size=10pt, tnum=yes]
\starttext
\addff{tnum}
\setff{tnum}
565656565656X\par
X
\st
be also
called in the two shorter commands \addff and \setff. In the
\definehighlight command I enabled the predefined “none” list where
ligatures and kerning is disabled to prevent that -- results in –.
Wolfgang
ino][default][features=myfeatures]
Sometimes it is necessary to add additional features or to switch a different
feature list *in* the document. To do this context provides the commands
\addfontfeature and \setfontfeature which can be also called in the two shorter
commands \addff and \s
feature[smcp][smcp=yes]
\definedescription
[description]
[width=broad,
headstyle={\bf\addff{smcp}}]
\setupbodyfont[pagella]
\starttext
\input ward
\startdescription{Ward}
\input ward
\stopdescription
\stoptext
Wolfgang
_
Hi ConTeXt users,
Currently I'm experiencing problems with inline math mode in combination
with the addff{oldstyle} command!
The attached test file doens't compile with the latest version 2012.2.18
(MkIV), which seems to be caused by the introduction of the $\bullet$!
With olde
On 8-12-2011 13:50, Verhaag, G.C.H.M. wrote:
Thanks for the tips! I changed [default] into [latn], which brought back
the oldstyle numerals!
By the way, I think I used a version from last August before upgrading.
the addff like features didn't support auto .. the next beta should wo
typescript[schola]
\setupbodyfont[schola,10pt]
\definefontfeature [oldstyle] [default] [onum=yes]
\addff{oldstyle}
Hi,
you can play with my example. It seems "script=auto" (default) is not that robust. Setting it to
"latn" or "dflt" should help.
\definefontf
pt[schola]
> \setupbodyfont[schola,10pt]
>
> \definefontfeature [oldstyle] [default] [onum=yes]
> \addff{oldstyle}
Hi,
you can play with my example. It seems "script=auto" (default) is not that
robust. Setting it to "latn" or "dflt" should help.
\
in my preamble:
>
> \usetypescript[schola]
> \setupbodyfont[schola,10pt]
>
> \definefontfeature [oldstyle] [default] [onum=yes]
> \addff{oldstyle}
>
> Perhaps something changed that I missed! Thanks in advance!
Do you get an error message or are the settings just not applied? An
outp
Hi ConTeXt user's,
A few days ago I installed the latest ConTeXt version but now my
oldstyle settings don't seem to work any more!
I use the following settings in my preamble:
\usetypescript[schola]
\setupbodyfont[schola,10pt]
\definefontfeature [oldstyle] [default] [onum=y
Hi Pavneet,
I do not know which font/kind of font you intend to use. So provided the font
is a otf-type the following works:
\setupbodyfont[times,rm,12pt]
\definefontfeature[oldstyle][sript=latin,onum=yes]
\starttext
\addff{oldstyle}
1234567890 A Pause---between yes and no.
1234567890 A Pause
fine a second font called 'sb' for semibold
\starttext
Test normal\\
{\sb Test semibold}\\
{\sb \it Test semibold}\\
{\bf Test bold}\\
Opentype font feature demonstration:\\
{\addff{onum} 1234} 1234\\
{\addff{frac} 1/17}
\stoptext
%%% END
> Hello, I am coming to ConTeXt from LaTeX a
own example was misleading (or so it seems to have been).
Wolfgang has found the cause of the problem.
Disabling mall caps when having enabled them for the default didn't work
either with TeX Gyre Pagella, because of using \addff instead of \addfs.
>> Imagine a whole book in one
L[aurl][http://www.pragma-ade.com/download-1.htm]
%%% It comes with a proper setup for everything.
\setupurl[style={\tf\addff{url}}]
%%% If you must use the “href” macro, disable the font feature locally.
\define[1]\href{%
\begingroup
\addff{url}%
\goto{\hyphenatedurl{#1}}[url(#1)]%
\en
][onum=no]
%%% Best use context’s default url commands:
\useURL[aurl][http://www.pragma-ade.com/download-1.htm]
%%% It comes with a proper setup for everything.
\setupurl[style={\tf\addff{url}}]
%%% If you must use the “href” macro, disable the font feature locally.
\define[1]\href{%
\begingroup
;
> Wrong key, style is for the symbol/number of the item. A real setup key
for
> the content isn't available and the best i can do (without extra markup
> around each entry) is the following.
>
> \definefontfeature[smcp][smcp=yes]
>
> \setupitemize[1][command=\bf\add
ork for you?
Wrong key, style is for the symbol/number of the item. A real setup
key for the content isn’t available and the best i can do (without
extra markup around each entry) is the following.
\definefontfeature[smcp][smcp=yes]
\setupitemize[1][command=\bf\addff{smcp}]
\setupitemize[2][com
y first-rate typesetting job :)
>
> Adapt the following to your case:
>
> \setupbodyfont[pagella]
>
> \definefontfeature[allcaps][smcp=yes,c2sc=yes]
>
> \starttext
>
> \TreatFirstLine {\addff{allcaps}} {} {} {}
> The Earth, as a habitat for animal life, is in o
e can be smaller.
> Employing this technique makes the difference between a pretty good and a
> really first-rate typesetting job :)
Adapt the following to your case:
\setupbodyfont[pagella]
\definefontfeature[allcaps][smcp=yes,c2sc=yes]
\starttext
\TreatFirstLine {\addff{allcaps}
On 04/13/2011 08:27 AM, Taco Hoekwater wrote:
On 13 apr. 2011, at 00:07, Pontus Lurcock <mailto:p...@talvi.net>> wrote:
On Mon 11 Apr 2011, Khaled Hosny wrote:
...
(\addff is meant for temporally applying font features not the other way
around, but I think it should work this wa
On 13 apr. 2011, at 00:07, Pontus Lurcock wrote:
> On Mon 11 Apr 2011, Khaled Hosny wrote:
>
> ...
>> (\addff is meant for temporally applying font features not the other way
>> around, but I think it should work this way too, so may be something
>> is broken)
fontfeature [oldstyle] [default] [onum=yes]
> > \addff{oldstyle}
>
> A more correct way is:
>
> \definefontfeature[default][default][onum=yes] % redefines default feature set
>
> \usetypescript[schola]
> \setupbodyfont[schola,8pt]
...
> (\addff is meant for temp
]
\definefontfeature [oldstyle] [default] [onum=yes]
\addff{oldstyle}
but this doesn't seem to work anymore in my recently installed minimal ConTeXt
installation (ConTeXt ver: 2011.03.30 11:21 MkIV fmt: 2011.3.30 int:
english/english).
I use this installation with Debian 6.0 (Squeeze).
Any
1 - 100 of 159 matches
Mail list logo
