From: jfbu <jfbu@free.fr>
To: ntg-context@ntg.nl
Subject: alternate to font feature file for glyph substitution ?
Date: Thu, 28 Apr 2016 16:08:45 +0200 [thread overview]
Message-ID: <CEDA41B6-8FAB-4106-8511-78AE534C9451@free.fr> (raw)
Hi,
how should I go at the Plain TeX level about implementing
the following glyph substitution which I formerly expressed
in a font feature file:
languagesystem DFLT dflt;
languagesystem latn dflt;
feature oneb {
sub one by one.ss01;
} oneb;
The font is Vollkorn, a Plain LuaTeX file which worked in TL2015 would be
\input luaotfload.sty
\font\x="Vollkorn:script=latn;language=DFLT;+tlig;featurefile=vollkornlua.fff;+oneb;"
\x 123
\bye
% Local Variables:
% TeX-engine: luatex
% End:
The glyph for digit 1 is modified and picked in stylistic set 1. I don't want
to globally switch to that stylistic set, I am only interested into digit 1.
My use case is more with LuaLaTeX+fontspec, but if I am explained
a Plain LuaTeX approach I can at least forward to Will Robertson
who maintains fontspec and cross my fingers that it trickles down
back to me at some point via update of fontspec, or luatex, or luaotfload,
...
Please CC to me as although I asked for (temporary) list inscription
I might not yet be registered.
I am aware of https://mailman.ntg.nl/pipermail/ntg-context/2016/083952.html
but can't work it out from there.
Jean-François
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2016-04-28 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 14:08 jfbu [this message]
2016-05-05 8:55 ` luigi scarso
2016-05-05 9:19 ` jfbu
2016-05-10 14:25 ` Hans Hagen
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=CEDA41B6-8FAB-4106-8511-78AE534C9451@free.fr \
--to=jfbu@free.fr \
--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).