From: "Idris Samawi Hamid" <ishamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: old-style numerals and .
Date: Wed, 27 Feb 2008 18:37:58 -0700 [thread overview]
Message-ID: <op.t67n5kcdnx1yh1@your-b27fb1c401> (raw)
In-Reply-To: <m2pruhapop.fsf@calaveras.Stanford.EDU>
On Wed, 27 Feb 2008 17:29:42 -0700, Jesse Alama <alama@stanford.edu> wrote:
>> Something like the following
>>
>> \usetypescript[modern-base][texnansi] % a simplified latin-modern
>> typescript
>> \usetypescript [map] [latin-modern-os] [texnansi]
>> \setupbodyfont[reset]
>> \setupbodyfont[modern,11pt]
>>
>> used to work in mkii (pdftex + context) but I don't know if it still
>> does
>> -- mkii support for oldstyle has not been a stable feature (due to the
>> changes from cm to lm): I had to recalibrate every couple of years or
>> so.
>> So try and see.
>
> It looks like this is more complicated than I thought. What would I do
> if I wanted old-style numerals just for a table of contents? Currently,
> my table of contents is set up like so:
>
> \setupcombinedlist[content][alternative=c,numberstyle={\os},pagestyle={\os}]
>
> This produces the triangles for periods, and I think I understand why
> that is so. What value should go in for the numberstyle key to enable
> old-style numerals just for the table of contents?
In that case you'll have to switch fonts for the TOC. So you still need to
have a font setup that supports os, then switch to that font for the TOC.
For example, if you can define a latin modern typeface that uses the
oldstyle numerals, then \switchtotypeface[my-lm] in your TOC setup.
As I mentioned before I'm not sure what the present protocol is for
setting up an oldstyle LM typeface in mkii. Basically you want something
like
%% THIS IS ONLY AN ILLUSTRATION!!!
\starttypescript [LModern-OS]
\definebodyfontenvironment
[lmodern-os]
[default]
[interlinespace=2.8ex]
\definetypeface [lmodern-os] [rm] [serif] [lmodern-os] [latin-modern-os]
[texnansi]
\stoptypescript
%% THIS IS ONLY AN ILLUSTRATION!!!
but maybe someone on the list knows the exact protocol. Then you can do
\usetypescript[LModern-OS] in your preamble and
\switchtotypeface[lmodern-os] where you need it.
Once the final move to mkiv is made this will all be much easier...
Best wishes
Idris
--
Professor Idris Samawi Hamid, Editor-in-Chief
International Journal of Shi`i Studies
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
___________________________________________________________________________________
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:[~2008-02-28 1:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 3:03 Jesse Alama
2008-02-23 5:06 ` Idris Samawi Hamid
2008-02-28 0:29 ` Jesse Alama
2008-02-28 1:37 ` Idris Samawi Hamid [this message]
2008-02-24 20:15 ` 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=op.t67n5kcdnx1yh1@your-b27fb1c401 \
--to=ishamid@colostate.edu \
--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).