From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: Superios with Cardo font
Date: Tue, 28 Jan 2020 18:29:27 +0100 [thread overview]
Message-ID: <abf3eac9-a14e-b3e1-c267-66068dc643ef@gmx.es> (raw)
In-Reply-To: <154d973d-e17a-cdc5-da8a-9f2a7cf1c504@mailbox.org>
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
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2020-01-28 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 16:00 Denis Maier
2020-01-28 17:29 ` Pablo Rodriguez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=abf3eac9-a14e-b3e1-c267-66068dc643ef@gmx.es \
--to=oinos@gmx.es \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).