From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: two superscript versions with Garamond Libre
Date: Mon, 18 May 2020 17:18:25 +0200 [thread overview]
Message-ID: <558ed947-66c4-6711-355f-ffa257ba7aec@gmx.es> (raw)
Dear list,
I’m accesing superscript glyphs for Garamond Libre with the OT feature
and the character with the following sample:
\definefontfeature[sups][script=latn, sups=yes]
\definefontfamily[twoface][rm][GaramondLibre]
\definefontfamily[mainface][rm][EB Garamond 12]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1ex]
{\feature[+][sups]1}¹{\feature[+][sups]2}²{\feature[+][sups]3}³%
{\feature[+][sups]8}⁸{\feature[+][sups]9}⁹{\feature[+][sups]0}⁰\\
\setupbodyfont[twoface]
{\feature[+][sups]1}¹{\feature[+][sups]2}²{\feature[+][sups]3}³%
{\feature[+][sups]8}⁸{\feature[+][sups]9}⁹{\feature[+][sups]0}⁰\\
\stopTEXpage
\stoptext
Typeface is available at
https://github.com/dbenjaminmiller/garamond-libre/releases/latest.
Sorry, but I’m a bit thick now. Does anyone know why characters and OT
sups provide differently sized glyphs?
I think there might be a bug in the typeface, but I need to know first
what to report.
Many thanks for your help,
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
___________________________________________________________________________________
next reply other threads:[~2020-05-18 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 15:18 Pablo Rodriguez [this message]
2020-05-18 16:13 ` Hans Hagen
2020-05-18 18:06 ` Pablo Rodriguez
2020-05-18 20:23 ` Henning Hraban Ramm
2020-05-19 6:08 ` Jan U. Hasecke
2020-05-19 6:24 ` Henning Hraban Ramm
2020-05-19 14:29 ` Pablo Rodriguez
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=558ed947-66c4-6711-355f-ffa257ba7aec@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).