ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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: Mon, 10 Dec 2007 13:20:43 +0100	[thread overview]
Message-ID: <115224fb0712100420i3f4a197dt96ba8aae8b3129e7@mail.gmail.com> (raw)
In-Reply-To: <475D2C80.3050901@wxs.nl>

2007/12/10, Hans Hagen <pragma@wxs.nl>:
> Wolfgang Schuster wrote:
> > On Fri, 07 Dec 2007 20:09:33 +0100
> > Hans Hagen <pragma@wxs.nl> wrote:
> >
> >> Wolfgang Schuster wrote:
> >>> 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
> >> btw, these are attributes and therefore can be used grouped
> >>
> >> 123 {\setfontfeature{enableoldstyle} 456} 789
> >
> > Is it also possible to inherit the values from the previuos change,
> > e.g. I have enabled smallcaps and I want to enable oldstyle numerals
> > with another command, I tried this but the old setting is forgotten and
> > only the new setting work, how can I do this.
> >
> > \usetypescript[palatino]
> > \setupbodyfont[palatino]
> >
> > \definefontfeature[caps][smcp=yes,lnum=yes]
> > \definefontfeature[onum][onum=yes]
> >
> > \def\sc{\setfontfeature{caps}}
> > \def\os{\setfontfeature{onum}}
> >
> > \starttext
> >
> > Text 123 \sc Text 123 \os Text 123
>
> i assume ...
>
>         Text 123 {\sc Text 123 \os Text} 123
>
> ... is meant

no, why should I write this, this make absolutely no sense because
why should I enable odlstyle numerals and close the group before I
get them. Grouping make sense in real documents but this was only
a example and I don't nedd it here.

What I want is, write the first "Text 123" write the normal font settings,
enable for second "Text 123" small caps but use linings figures or whatever
else is the default value, this make sense in tables where I want to use
smallcaps e.g. in a title row but the numbers should remain in the local
style e.g. table numerals. My third "Text 123" pair should now be written
in smallcaps because I set it with \sc and use now oldstyle numerals.

> > \stoptext
>
> accumulated features is something on the agenda, but we need a proper
> definition interface for that; sometimes one wants to accumulate,
> sometines not; sometime one even wants to kill features

I can wait for this but it should be integrated in a not so distand future.

> > PS: Will the smallcaps key also work in a feature release of the latin
> > modern fonts, thid didn't work at the moment and I was forced to use
> > the Pagella fonts.
>
> maybe there will be a lmroman10 once that has the features merged
>
> Hans

No longer oldstyle numerals from the math fonts for latin modern,
this sound very good.

Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2007-12-10 12:20 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 [this message]
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=115224fb0712100420i3f4a197dt96ba8aae8b3129e7@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).