From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: showfont with xetex (syntax changed?)
Date: Thu, 6 Dec 2007 16:50:21 +0100 [thread overview]
Message-ID: <8C390B2E-12F2-4F31-ADBA-9A5591B88C2C@st.estfiles.de> (raw)
In-Reply-To: <115224fb0712060637i7fa3b7ffsf8ddfee203cc0d38@mail.gmail.com>
Am 06.12.2007 um 15:37 schrieb Wolfgang Schuster:
> 2007/12/6, Steffen Wolfrum <context@st.estfiles.de>:
>>
>> Am 06.12.2007 um 14:48 schrieb Hans Hagen:
>>
>>> something numbers=oldstyle could be supported but i see no real
>>> reason
>>> for it since then we end up in endless lists of possibilities
>>> (given all
>>> kind of combinations)
>>
>> I have not yet played with Lua, thus I can't follow your and Mojca's
>> discussion at that point.
>> But to have a handy way to switch on/off oldstyle figures would be
>> very useful!
>>
>> "numbers=oldstyle" shouldn't be considered as a theoretical
>> possibility, it is needed quite often.
>>
>> Steffen
>
> The following should work, can't test it at the moment
>
> \definefontfeature[enableoldstyle][onum=yes]
> \definefontfeature[disableoldstyle][onum=no]
>
> \starttext
>
> 123 \setfontfeature{enableoldstyle} 456 \setfontfeature
> {disableoldstyle} 789
>
> \stoptext
you mean typeset with Lua, right? with XeTeX it yields
! Undefined control sequence.
l.20 \setfontfeature!
Steffen
___________________________________________________________________________________
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 15:50 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 [this message]
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
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=8C390B2E-12F2-4F31-ADBA-9A5591B88C2C@st.estfiles.de \
--to=context@st.estfiles.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).