From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: showfont with xetex (syntax changed?)
Date: Thu, 6 Dec 2007 18:45:42 +0100 [thread overview]
Message-ID: <115224fb0712060945p4e4b73cdxe0994fe0606b6156@mail.gmail.com> (raw)
In-Reply-To: <6faad9f00712060835l4604d133n6d902e72d1e0ee26@mail.gmail.com>
2007/12/6, Mojca Miklavec <mojca.miklavec.lists@gmail.com>:
> On Dec 6, 2007 5:09 PM, Steffen Wolfrum wrote:
> >
> > Am 06.12.2007 um 12:32 schrieb Mojca Miklavec:
> >
> > > The general approach would be something like:
> > > \definefontfeature[mine][smcp=yes]
> > > \definefontsynonym[a][name:Warnock Pro][features=mine]
> > > \showfont[a]
> > > (grep the sources for definefontfeature)
> >
> >
> > hmm ... the only hit is in /base/font-ini.mkii (and font-ini.tex)
> >
> > \def\mkdefinefontfeature#1% #2
> > {\setvalue{\??fa#1}} % {#2}
>
> \definefontfeature
> [default]
> [liga=yes,kern=yes,tlig=yes,trep=yes] % texligatures=yes,texquotes=yes
>
> \definefontfeature
> [smallcaps]
> [liga=yes,kern=yes,tlig=yes,trep=yes,smcp=yes] %
> texligatures=yes,texquotes=yes
I would prefer something like
\definefontfeature
[smallcaps]
[default] % inherit settings from default
[smcp=yes] % add smcp to the feature list
I can define my own fontfeature without looking into the source.
Wolfgang
> \definefontfeature
> [oldstyle]
> [liga=yes,kern=yes,tlig=yes,trep=yes,onum=yes] %
> texligatures=yes,texquotes=yes
>
> font-otf.lua:--
> \definefontfeature[calt][language=nld,script=latn,mode=node,calt=yes,clig=yes,rlig=yes]
> font-otf.lua:--
> \definefontfeature[dflt][language=nld,script=latn,mode=node,calt=no,
> clig=yes,rlig=yes]
> font-otf.lua:--
> \definefontfeature[fixd][language=nld,script=latn,mode=node,calt=no,
> clig=yes,rlig=yes,ignoredrules={44,45,47}]
> s-pre-64.tex:
> \definefontfeature[default][method=node,script=latn,language=dflt,liga=yes,onum=yes,kern=yes]
>
> (Might change!!!)
>
> Mojca
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2007-12-06 17:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 10:26 Steffen Wolfrum
2007-12-06 11:32 ` Mojca Miklavec
2007-12-06 13:48 ` Hans Hagen
2007-12-06 14:30 ` Steffen Wolfrum
2007-12-06 14:37 ` Wolfgang Schuster
2007-12-06 15:50 ` Steffen Wolfrum
2007-12-06 17:33 ` Wolfgang Schuster
2007-12-06 17:58 ` Hans Hagen
2007-12-07 19:09 ` Hans Hagen
2007-12-09 12:13 ` Wolfgang Schuster
2007-12-10 12:09 ` Hans Hagen
2007-12-10 12:20 ` Wolfgang Schuster
2007-12-07 19:08 ` Hans Hagen
2007-12-06 16:30 ` Mojca Miklavec
2007-12-07 9:29 ` Hans Hagen
2007-12-07 9:33 ` Hans Hagen
2007-12-06 14:23 ` Wolfgang Schuster
2007-12-07 19:07 ` Hans Hagen
2007-12-06 15:43 ` Steffen Wolfrum
2007-12-06 16:09 ` Steffen Wolfrum
2007-12-06 16:35 ` Mojca Miklavec
2007-12-06 16:59 ` Steffen Wolfrum
2007-12-06 17:36 ` Wolfgang Schuster
2007-12-06 17:45 ` Wolfgang Schuster [this message]
2007-12-06 17:55 ` Hans Hagen
2007-12-06 20:14 ` Steffen Wolfrum
2007-12-06 20:32 ` 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=115224fb0712060945p4e4b73cdxe0994fe0606b6156@mail.gmail.com \
--to=schuster.wolfgang@googlemail.com \
--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).