From: Michael Saunders <odradek5@gmail.com>
To: ntg-context@ntg.nl
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: LuaTeX error ... object in use
Date: Sun, 30 May 2010 16:24:14 -0500 [thread overview]
Message-ID: <AANLkTinI1bAj8nZ3CZ6qXyvjEEefwmMMU6cB0T73NlPB@mail.gmail.com> (raw)
In-Reply-To: <4C02D30A.2090105@wxs.nl>
> you can try
>
> mtxrun --script font --list --info garamondpremrpr
...
> to see what happens with features
Thanks. This seems to confirm that the features are there:
MTXrun | dnom cyrl dflt
MTXrun | grek dflt
MTXrun | latn aze crt deu dflt fra ita mol rom srb trk
MTXrun | numr cyrl dflt
MTXrun | grek dflt
MTXrun | latn aze crt deu dflt fra ita mol rom srb trk
MTXrun | ordn cyrl dflt
MTXrun | grek dflt
MTXrun | latn aze crt deu dflt fra ita mol rom srb trk
MTXrun | sinf cyrl dflt
MTXrun | grek dflt
MTXrun | latn aze crt deu dflt fra ita mol rom srb trk
MTXrun | sups cyrl dflt
MTXrun | grek dflt
MTXrun | latn aze crt deu dflt fra ita mol rom srb trk
but still,
\definefontfeature[body][default][script=latn,onum=yes,pnum=yes,calt=yes,protrusion=quality,expansion=quality]
\definefontfeature[in][body][sinf=yes]%inferior
\definefontfeature[su][body][sups=yes,ordn=yes]%superior
\definefontfeature[nu][body][numr=yes]%numerator
\definefontfeature[de][body][dnom=yes]%denominator
in {\addff{in}123}
su {\addff{su}123}
nu {\addff{nu}123}
de {\addff{de}123}
produces only proportional oldstyle figures.
___________________________________________________________________________________
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:[~2010-05-30 21:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 2:35 Michael Saunders
2010-05-29 5:39 ` Taco Hoekwater
2010-05-29 7:53 ` Michael Saunders
2010-05-29 12:56 ` Taco Hoekwater
2010-05-29 15:58 ` Michael Saunders
2010-05-30 9:54 ` Taco Hoekwater
2010-05-30 11:24 ` Michael Saunders
2010-05-30 11:35 ` Hans Hagen
2010-05-30 16:52 ` Michael Saunders
2010-05-30 19:08 ` Michael Saunders
2010-05-30 19:29 ` taco
2010-05-30 20:36 ` Michael Saunders
2010-05-30 21:05 ` Hans Hagen
2010-05-30 21:24 ` Michael Saunders [this message]
2010-05-30 21:33 ` Hans Hagen
2010-05-30 22:08 ` Michael Saunders
2010-05-31 6:44 ` Hans Hagen
2010-05-31 11:32 ` Hans Hagen
2010-05-30 18:29 ` taco
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=AANLkTinI1bAj8nZ3CZ6qXyvjEEefwmMMU6cB0T73NlPB@mail.gmail.com \
--to=odradek5@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).