ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
Subject: Re: fundamental problem with headings
Date: Fri, 11 Mar 2005 13:45:09 +0100	[thread overview]
Message-ID: <a06210202be5740a3d3aa@[62.134.77.169]> (raw)

Adam Lindsay <atl@comp.lancs.ac.uk> wrote:

>  Steffen Wolfrum said this at Fri, 11 Mar 2005 12:33:13 +0100:
>
>  >In fact, this is something I would like to have also for other
>  >purposes (for example to use a second set of oldstyle figures):
>  >defining my own *myserif* or *mysans* that could be used then in a
>  >typescriptfile the same way as sans, serif and mono are used there.
>  >
>  >But up to now I didn't manage it.
>  >
>  >Somebody did and would like to share his/her knowledge?
>
>  Okay, thanks for clarifying.
>
>  You might like to take a look at the typescripts in the OpenType.zip file
>  at <http://homepage.mac.com/atl/tex/>. I defined full myserif/mysans
>  families (I called them romancaps and capsans) to stand next to the serif
>  and sans families (same font, different features). There are also a
>  couple convenience macros in there to help switch between the two.
>
>  Is that the sort of thing you're looking for? There's nothing inherently
>  SmallCaps (or OpenType) about the fundamental typescripts--that's just
>  the first testing ground I found.


I had a look at your file but I think my point is different:

You still use only the predefined serif, sans etc.
\usetypescript[serif]...
\usetypescript[sans]...
\usetypescript[math]...

but I would like to use also
\usetypescript[myserif]...
and the corresponding \myrm (next to \tt and \ss).

I don't know Hans' texnical term for serif, sans, mono, math etc. is 
(as used above).

Steffen

             reply	other threads:[~2005-03-11 12:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 12:45 Steffen Wolfrum [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-11 11:33 Steffen Wolfrum
2005-03-11 11:46 ` Adam Lindsay
2005-03-10 22:11 Steffen Wolfrum
2005-03-10 23:17 ` Adam Lindsay
2005-01-24 14:27 Steffen Wolfrum
2005-01-24 10:46 Steffen Wolfrum
2005-01-24 11:09 ` Taco Hoekwater
2005-01-24 19:15   ` Willi Egger
2005-01-24 19:11 ` Willi Egger

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='a06210202be5740a3d3aa@[62.134.77.169]' \
    --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).