From: Thomas Fehige <thomas@fehige.de>
To: ntg-context@ntg.nl
Subject: Test Suite Fonts "extensions-001"
Date: Fri, 29 Apr 2016 10:38:07 +0200 [thread overview]
Message-ID: <57231D6F.8040207@fehige.de> (raw)
In-Reply-To: <1cad4caa-38f3-a38a-9b09-1492dd6b2129@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 806 bytes --]
Below is a minimal not-working example extracted from
"extensions-001.tex" in the fonts section of the test suite. From what I
understand of the code, the second line should read "XPrXcXdXPrX"
instead of "abracadabra". But it doesn't, it is still "abracadabra".
Compiling the original extensions-001 gives me seven lines of
"abracadabra". What am I doing wrong? I'm running ConTeXt version
2015.05.18 12:26 MKIV current fmt: 2016.4.28 from the debian/ubuntu
texlive packets.
\startluacode
fonts.handlers.otf.addfeature {
name = "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
[-- Attachment #1.2: Type: text/html, Size: 4399 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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 prev parent reply other threads:[~2016-04-29 8:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 7:10 uppercase, small caps, numerals and German capital sharp s Thomas Fehige
2016-04-19 12:05 ` Wolfgang Schuster
2016-04-19 12:46 ` Thomas Fehige
2016-04-20 14:03 ` Thomas Fehige
2016-04-20 14:25 ` Wolfgang Schuster
2016-04-20 21:25 ` Thomas Fehige
2016-04-20 21:27 ` Thomas Fehige
2016-04-22 11:35 ` glyph substitution Thomas Fehige
2016-04-22 20:28 ` Hans Hagen
2016-04-25 9:53 ` Thomas Fehige
2016-04-25 12:48 ` Thomas Fehige
2016-04-25 15:49 ` Thomas Fehige
2016-04-25 18:12 ` Thomas Fehige
2016-04-25 20:44 ` Wolfgang Schuster
2016-04-26 8:42 ` Thomas Fehige
2016-04-27 14:27 ` Thomas Fehige
2016-04-27 15:10 ` Hans Hagen
2016-04-29 7:44 ` Thomas Fehige
2016-04-29 7:56 ` Hans Hagen
2016-04-29 8:38 ` Thomas Fehige [this message]
2016-04-29 9:05 ` Test Suite Fonts "extensions-001" Wolfgang Schuster
2016-05-03 9:22 ` Setting up TeXworks Thomas Fehige
2016-05-06 8:04 ` Mojca Miklavec
2016-05-06 11:39 ` L.S.-Soc&Gam
2016-05-16 15:46 ` Thomas Fehige
2016-05-16 15:55 ` Jean-Pierre Delange
2016-05-17 11:16 ` Thomas Fehige
2016-05-17 12:39 ` Thomas Fehige
2016-05-17 12:59 ` Hans Hagen
2016-05-19 14:09 ` Thomas Fehige
2016-05-17 13:22 ` Jean-Pierre Delange
2016-05-19 15:16 ` Thomas Fehige
2016-05-19 16:15 ` Jean-Pierre Delange
2016-05-07 10:49 ` Thomas Fehige
2016-05-09 11:02 ` Thomas Fehige
2016-05-15 19:29 ` Thomas Fehige
2016-05-16 14:34 ` ConTeXt and Scite Thomas Fehige
2016-05-03 9:51 ` Setting up TeXworks Thomas Fehige
2016-05-03 10:21 ` Mojca Miklavec
2016-05-03 13:01 ` Thomas Fehige
2016-04-25 20:47 ` glyph substitution Wolfgang Schuster
2016-04-26 7:42 ` Thomas Fehige
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=57231D6F.8040207@fehige.de \
--to=thomas@fehige.de \
--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).