ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: "Patrick Gundlach" <pg@levana.de>
Subject: Re: Re: changing tt only
Date: Thu, 30 Jan 2003 00:40:32 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20030130003523.0426f210@remote-1> (raw)
In-Reply-To: <20030129190011.5880@news.comp.lancs.ac.uk>

At 07:00 PM 1/29/2003 +0000, Adam Lindsay wrote:

> >how do I use this? I have tried for the last .... hours. The
>
>Sorry I wasn't clear. I assumed too much. I spent an entire weekend
>working through this stuff at the start.

not bad, since fonts is the most complicatd part of tex (due to the fact 
that math is involved and so)

I haven't been clever enough to figure out how to include the typescript
>in the same file that I'm ConTeXting. My guess is that this is because of
>a (reasonable) assumption of wanting to reuse typescripts.

indeed, also, having all of them in mem takes space

> >Is there any description /documentation of the typescript mechanism?
> >Besides mfont.pdf? mfont is not clear enough. There are only some
> >examples but no real explanation how this mechanism works. At least I
> >cannot see it.

consider typescripts to be:

\starttypescript [key a] [key b] [key c]

\stoptypescript

and all key's being optional

selecting them is a matter of best match, say [key a] or [key a][key b] or 
...  so

\usetypescript [key a] [key b]

filters all instances that match those first two keys (actually sets of keys)

the definetypeface macro (just take a look in type-ini) filters a couple of 
combinations

inside typescripts can be all kind of things but in practice it's mainly 
mapping files

Hans


-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------

  parent reply	other threads:[~2003-01-29 23:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29 17:15 Patrick Gundlach
2003-01-29 17:25 ` Adam Lindsay
2003-01-29 18:11   ` Patrick Gundlach
2003-01-29 19:00     ` Adam Lindsay
2003-01-29 19:39       ` Patrick Gundlach
2003-01-29 23:43         ` Hans Hagen
2003-01-30 23:03           ` Patrick Gundlach
2003-01-29 21:12       ` Hraban
2003-01-29 23:40       ` Hans Hagen [this message]
2003-01-30 23:18         ` Patrick Gundlach
2003-01-31 12:34           ` Hans Hagen
2003-01-31 15:01             ` My Way (was: Re: Re: changing tt only) Adam Lindsay
2003-01-31 15:26               ` Hans Hagen
2003-01-31 15:27             ` changing tt only Patrick Gundlach
2003-01-29 20:58     ` Hraban
2003-01-29 23:32   ` Hans Hagen
2003-01-30 10:34     ` Patrick Gundlach
2003-01-31 23:04       ` 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=5.1.0.14.1.20030130003523.0426f210@remote-1 \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=pg@levana.de \
    /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).