Hi, I am trying to use the Cardo font with superior figures. But somehow these seems to work differently here than with other fonts: ==================== \definefontfeature[default][default][ onum=yes, pnum=yes, ] \definefontfeature[f:newstyle][onum=no,pnum=no] \definefontfamily[cardo][rm][Cardo] \definefontfamily[libertine][rm][Linux Libertine O] \starttext \setupbodyfont[cardo] 12345 {\feature[+][f:superiors]12345} 12345 {\feature[+][f:newstyle]\feature[+][f:superiors]12345} \setupbodyfont[libertine] 12345 {\feature[+][f:superiors]12345} 12345 {\feature[+][f:newstyle]\feature[+][f:superiors]12345} \stoptext ==================== Why is it that I have to manually disable onum and pnum with Cardo for sups to work? (Note: Cardo is a ttf font, Linux Libertine O is a otf) By the way, what is the correct way to define a new font feature for superios? (VerticalPosition=Superior; sups=yes; VerticalPosition=Superscript ...) Best, Denis
On 1/27/20 5:00 PM, Denis Maier wrote:
Hi,
I am trying to use the Cardo font with superior figures. But somehow these seems to work differently here than with other fonts: [...] Why is it that I have to manually disable onum and pnum with Cardo for sups to work?
Hi Denis, you can’t have them all. It might be related to the loopup order in the font itself. onum or pnum precedence might require onum/pnum sups.
(Note: Cardo is a ttf font, Linux Libertine O is a otf)
I think this makes no difference at all.
By the way, what is the correct way to define a new font feature for superios? (VerticalPosition=Superior; sups=yes; VerticalPosition=Superscript ...)
sups=yes is the only way to invoke a font feature (such as it is defined in the font itself [this is an OpenType tag]). VerticalPosition and your values might be valid in fontspec. But ConTeXt doesn’t go that way. Just in case it helps, Pablo -- http://www.ousia.tk
participants (2)
-
Denis Maier -
Pablo Rodriguez