ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: assembling typescript
Date: Mon, 20 Mar 2006 10:34:01 +0100	[thread overview]
Message-ID: <441E7709.5020400@wxs.nl> (raw)
In-Reply-To: <441D7A07.2050904@ecology.uni-kiel.de>

Karsten Heymann wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> after Patrick Gundlach convinced me at DANTE 2006 to switch the small
> scientific magazine project I'm currently working on for a client from
> LaTeX co ConTeXt, I'm now preparing a sample document for my client to
> convince him, and for that I need your help :)
>
> I've spent the last two weeks getting in touch wich context and I must
> say I'm really impressed, nice work!
>
> First challenge is that the document fonts are URW GaramondNo8 for the
> text and Bitstream Futura (really: Bitstream Geometric 211) for the
> headings. I managed quite easyly to install them with texfont and the
> instructions from the contextgarden wiki[1] and compile the sample
> document with either font family. But now I'm trying to (1) understand
> the typescript files and (2) build an own typescript putting those fonts
> together. This is what I have so far:
>
> \usetypescriptfile[type-ugm]
> \usetypescriptfile[type-bfu]
>
> \starttypescript [ifa][texnansi]
> \definetypeface [ifa] [rm] [serif] [garamond] [default]
> ~                [encoding=texnansi]
> \definetypeface [ifa] [ss] [sans] [futura] [default]
> ~                [encoding=texnansi]
> \definetypeface [ifa] [tt] [mono] [modern] [default]
> ~                [encoding=texnansi]
> \stoptypescript
>
> \usetypescript[ifa][texnansi]
> %\ifa
> \starttext
>
> \ss
> \input knuth
>
> \rm
> \input knuth
> \stoptext
>
> (type-ugm.tex and type-bfu.tex are attached). What happens is: When I
> compile the file a is it is set in computer modern. To enable my fonts I
> have to comment out \starttypescript, \stoptypescript and \usetypescript
> and enable \ifa. How do I activate my fonts via a typescript.
you can use \setuptypescript[...], but best is to just use: 

\setupbodyfont[ifa] 

since the typescript mechanism is a layer on top of the more low level traditional-texie font mechanism 

so, you can have several typefaces alongside and switch between them; this is one of the reasons that typefaces exist: they enable you to construct combinations and use many of them in a document (mixed font families, math styles, etc) 


Hans 

Hans 


-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

      parent reply	other threads:[~2006-03-20  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-19 15:34 Karsten Heymann
2006-03-19 19:03 ` Peter Rolf
2006-03-20  9:34 ` Hans Hagen [this message]

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=441E7709.5020400@wxs.nl \
    --to=pragma@wxs.nl \
    --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).