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 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 Italic
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
الثَّعْلَبُ
][
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
% c2sc=yes, % caps
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,
]
\definefontfeature[smallcaps][ % us
}
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 accumulate ... features
> come in order (you can force order if needed as you probably saw in
> one of the
ype = "ligature",
data = {
['“'] = { "`", "`" },
['”'] = { "'", "'" },
['„'] = { '"', "`" },
[''] = { '"', "'" },
['‘'] = { "`" },
['’'] = { "'" }
}
}
fonts.handlers.otf.addfeature {
name = "texsub",
type = "substitute",
data = {
[''] = '“',
}
}
\stopluacode
ot;'" }
}
}
fonts.handlers.otf.addfeature {
name = "texsub",
type = "substitute",
data = {
[''] = '“',
}
}
\stopluacode
% with lmodern or palatino it breaks
\setupbodyfont[schola]
\definefontfeature[ltest][texlig=y
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't kick in as we're
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, they look like
gt;
> %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}
>
> שֹׂבַע
>
> עָשׂוֹר
>
> קֹשֶׁט
>
>
typescript
\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
elated 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}
use primes ... in a next upload
\setupheadertexts[chapter][{\addff{normnum}\pagenumber}][{\addff{normnum}\pagenumber}][]
\stopsetups
\startsetups noheader
\setupheadertexts[][][][]
\stopsetups
\startsetups bigchapter
\setupalign[flushleft,hz,hanging,verytolerant,nothyphenated]
\doifelse{\structureuservariable{image
[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{disabled} \JHa
rs.otf.addfeature {
name = "wtest",
type = "ligature",
data = {
['1'] = { "left_boundary", "a" },
}
}
\stopluacode
\definefontfeature[wtest][wtest=yes]
\definefontfeature[ltest][ltest=yes]
\starttext
\definedfon
type = "ligature",
data = {
['1'] = { "left_boundary", "a" },
}
}
\stopluacode
\definefontfeature[wtest][wtest=yes]
\definefontfeature[ltest][ltest=yes]
\starttext
\definedfont[file:dejavu-serif.ttf*default]%
{\addff{ltest} ab
23,
>> 3-9:~1057765, 2-7:~1086097, 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-
:~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
mathematical italic small a and b
>> [0x02032] = { [0x00028] = -150 }, -- prime and left parenthesis
>> }
>> }
>> \stopluacode
>>
>> \definefontfeature[kerntest][kerntest=yes]
>>
>> \definefontfamily[lucidaopentype][rm][Lucida Bright OT]
>>
{ [0x00028] = -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
-150 }, -- 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
ntest][kerntest=yes]
>>
>> \definefontfamily[lucidaopentype][rm][Lucida Bright OT]
>> \definefontfamily[lucidaopentype][mm][Lucida Bright Math OT]
>>
>> \setupbodyfont[lucidaopentype,10pt]
>>
>>
>> \startTEXpage[offset=3pt]
>> abba $abba
t; \stopluacode
>
> \definefontfeature[kerntest][kerntest=yes]
>
> \definefontfamily[lucidaopentype][rm][Lucida Bright OT]
> \definefontfamily[lucidaopentype][mm][Lucida Bright Math OT]
>
> \setupbodyfont[lucidaopentype,10pt]
>
>
> \startTEXpage[offset=
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-3mu(x)$
\sto
1000/100
\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 l
?
\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
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 present in bibtex note entries, but persist
On Fri, 3 Feb 2017 17:26:35 -0500
Rik Kabel <cont...@rik.users.panix.com> 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 lin
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
arabicindic][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}
}
>> }
>> }
>> \stopluacode
>>
>> \definefontfeature[mathperiod][mpf=yes]
>>
>> \resetfontfallback [mathdigits]
>> %\definefontfallback[mathdigits][dejavusansmono][digitsexten
>> dedarabicindic][check=yes,force=yes,off
nefontsynonym
[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 ef
[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?
002E } },
>> after = { digits },
>> before = { digits },
>> lookups = { 1 },
>> }
>> }
>> }
>> }
>> \stopluacode
>>
>> \definefontfeature[mathperiod][mpf=yes]
>>
>> \resetfontfallback [mathdigi
ck[mathdigits][dejavusansmono][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.
>
> \
ix,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 charact
;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
\stoptext
_
nt = { { "b", "c" } },
lookups = { 1 },
},
},
},
}
\stopluacode
\definefontfeature[stest][stest=yes]
\definefontfeature[atest][atest=yes]
\definefontfeature[mtest][mtest=yes]
\definefontfeature[ltest][ltest=yes]
\definefontfeature[ktest]
uot;c"] = "C",
> },
> },
> },
> -- steps= {
> -- {
> -- rules = {
> -- {
> -- before = { { "a" } },
> -- current = { {
rules = {
{
before = { { "a" } },
current = { { "b", "c" } },
lookups = { 1 },
},
},
},
}
\stopluacode
\definefontfeature[stest][stes
[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
]
\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:
\definefontfeature
]
\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
]
\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 text}
\input ward\footnote{Ward sample text
]
[sectionconversionset=...]
but I'm unable to understand how these commands work exactly.
Take a look at the example below how this can be achieved.
begin example
\def\sc{\addff{smallcaps}}
\def\os{\addff{oldstyle}}
\setuplabeltext
[appendix=Appendix~]
\setuphead
[title
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
Am 23.05.2014 um 17:55 schrieb Mojca Miklavec mojca.miklavec.li...@gmail.com:
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
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
-8---
\definefontfamily[mainface][rm][Linux Libertine Initials O][features=tnum]
\definefontfeature[default][default][tnum=yes]
\setupbodyfont[mainface]
\starttext
\addff{tnum}
\setff{tnum}
\feature[+][tnum]
\feature[+][tnum=yes]
565656565656X\par
X
\stoptext
--8
]
\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 (mapped onto add
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{feature} and \subfs{feature}, meaning add
feature to the stack and subtract feature from the stack. But those
have been broken for a very long time.
afaik they're
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} \feature{y} \feature{y} - all are used on top
we might end up with replacing \addff etc by one
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} \feature{y} \feature{y
. Is that right?
\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).
Question: Does/Will this mechanism completely replace \addff et al, or
will these mechanism ignore each other (e.g., \resetfeature does
completely replace \addff et al, or
will these mechanism ignore each other (e.g., \resetfeature does not pop
those defined by \addff).
I dont' know ... in fact, they share code deep down in the machinery but
indeed it might make sense to remove them (or at least depricate them).
Hans
it off I guess we need a replacement 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
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 \addff).
A good exercise
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 don't
not the best 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{feature} and \subfs
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 abc
\setff and \addff, with \setff you replace
the active
feature set (in most cases “default”) with a new set, you can see it in the
first line
because kerning etc. is disabled after \setff which I haven’t included in my
list.
In the second line I used \adff which add my new list to the active list
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
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
Am 10.06.2012 um 00:01 schrieb Peter Münster:
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
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
\stoptext
=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 \setff. In the \definehighlight
\addfontfeature and \setfontfeature which can 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
={\bf\addff{smcp}}]
\setupbodyfont[pagella]
\starttext
\input ward
\startdescription{Ward}
\input ward
\stopdescription
\stoptext
Wolfgang
___
If your question is of interest to others as well, please add an entry
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 older versions
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=yes]
\addff
:
\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
output file from a working ConTeXt version and one from
]
\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.
\definefontfeature [default] [default] [script=latin]
\definefontfeature [osf] [onum=yes
[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.
\definefontfeature [default] [default] [script=latin
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
' 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 and have a typescript question. I
[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
/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)]%
\endgroup%
}
\starttext
42
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 document. If you have more than 100 urls, it
would
/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][command=\tf\subfs{smcp}]
\setupitemize[3][command
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][command=\tf\subfs{smcp}]
\setupitemize[3][command=\it]
\setupitemize[4][command=\tf
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 old age and has a fatal illness.
Several, in fact. It would
{\addff{allcaps}} {} {} {}
The Earth, as a habitat for animal life, is in old age and has a fatal
illness. Several, in fact. It would be happening whether humans had ever
evolved or not. But our presence is like the effect of an old-age patient who
smokes many packs of cigarettes per day — and we
On 13 apr. 2011, at 00:07, Pontus Lurcock 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 way too, so may be something
is broken)
\addff{oldstyle} works
On 04/13/2011 08:27 AM, Taco Hoekwater wrote:
On 13 apr. 2011, at 00:07, Pontus Lurcock p...@talvi.net
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
]
\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 idea
On Mon 11 Apr 2011, Khaled Hosny wrote:
In my earlier MkIV minimal ConTeXt installation (dec.2010) I used
the following in my preamble to activate oldstyle numbering:
\usetypescript[schola]
\setupbodyfont[schola,8pt]
\definefontfeature [oldstyle] [default] [onum=yes]
\addff
Hi,
In my earlier MkIV minimal ConTeXt installation (dec.2010) I used the
following in my preamble to activate oldstyle numbering:
\usetypescript[schola]
\setupbodyfont[schola,8pt]
\definefontfeature [oldstyle] [default] [onum=yes]
\addff{oldstyle}
but this doesn't seem to work anymore
]
\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 idea what's wrong?
The following two methods
] [onum=yes]
\addff{oldstyle}
A more correct way is:
\definefontfeature[default][default][onum=yes] % redefines default feature set
\usetypescript[schola]
\setupbodyfont[schola,8pt]
\starttext
12345678
\stoptext
(\addff is meant for temporally applying font features not the other way
around
for that in
tex,
we have to define it using the font feature.
If , like Bernhard wrote, \addff is broken, that would affect also
features like 'sups', 'dlig' and so on.
-Ursprüngliche Nachricht-
Von: Bernhard Rosensteiner
[mailto:brosenstei...@gmail.com]
Gesendet
[c2sc][default][c2sc=yes]
\setmainfont[Minion Pro][expansion=quality, protrusion=quality,
script=latin]
\starttext
{\addff{c2sc} THIS TEXT SHOULD BE CONVERTED TO SMALL CAPS.} % does not
result in small caps, what's wrong???
Compare: {\sc small caps} % does give small caps (therefore, not part of my
for that in tex,
we have to define it using the font feature.
If , like Bernhard wrote, \addff is broken, that would affect also features
like 'sups', 'dlig' and so on.
-Ursprüngliche Nachricht-
Von: Bernhard Rosensteiner [mailto:brosenstei...@gmail.com]
Gesendet: Sonntag, 3. April
, and
since (to my knowledge) there is no style like \sc for that in tex,
we have to define it using the font feature.
If , like Bernhard wrote, \addff is broken, that would affect also features
like 'sups', 'dlig' and so on.
-Ursprüngliche Nachricht-
Von: Bernhard Rosensteiner
(or at least using) the other font feature (c2sc) does not
work, and since (to my knowledge) there is no style like \sc for that in tex,
we have to define it using the font feature.
If , like Bernhard wrote, \addff is broken, that would affect also
features like 'sups', 'dlig' and so
1 - 100 of 149 matches
Mail list logo
