From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem creating a typescript for Adobe Avenir
Date: Thu, 26 Mar 2009 08:40:07 +0100 [thread overview]
Message-ID: <B651524E-79EE-4D02-A52C-EDB8FC9B6C05@uni-bonn.de> (raw)
In-Reply-To: <d8df50ed0903251221l5f6c0deld248a7865a89ddf1@mail.gmail.com>
Hi Markus,
you're on the right track; just two or three small corrections, and
you should be in business:
On Mar 25, 2009, at 8:21 PM, Markus Hubig wrote:
>
> My map file looks like this (texnansi-adobe-avenir.map):
>
> texnansi-AVENI17 Avenir-Heavy 4 < AVENI17.ttf texnansi.enc
> texnansi-AVENI18 Avenir-HeavyOblique 4 < AVENI18.ttf texnansi.enc
> texnansi-AVENI23 Avenir-Oblique 4 < AVENI23.ttf texnansi.enc
> texnansi-AVENI24 Avenir-Roman 4 < AVENI24.ttf texnansi.enc
>
I'm not sure if you can have a space after the <
> \starttypescript [map] [avenir] [textansi]
> \loadmapfile [texnansi-adobe-avenir.map]
> \stoptypescript
>
> \starttypescript [sans] [avenir] [texnansi]
> \definefontsynonym [Avenir-Heavy] [texnansi-AVENI17]
> [encoding=texnansi]
> \definefontsynonym [Avenir-HeavyOblique] [texnansi-AVENI18]
> [encoding=texnansi]
> \definefontsynonym [Avenir-Oblique] [texnansi-AVENI23]
> [encoding=texnansi]
> \definefontsynonym [Avenir-Roman] [texnansi-AVENI24]
> [encoding=texnansi]
> \stoptypescript
>
> \starttypescript [sans] [avenir] [name]
> \definefontsynonym [Sans] [Avenir-Roman]
> \definefontsynonym [SansItalic] [Avenir-Oblique]
> \definefontsynonym [SansBold] [Avenir-Heavy]
> \definefontsynonym [SansBoldItalic] [Avenir-HeavyOblique]
> \stoptypescript
>
> \starttypescript [Avenir]
> \definetypeface [Avenir] [rm] [sans] [avenir] [default]
> \stoptypescript
>
Two things here: you're defining a sans font, so change [rm] into
[ss]. And for mkii (old-fashioned pdftex), I think you'll need to add
the encoding to the typescript:
\starttypescript [Avenir] [texnansi]
\definetypeface [Avenir] [ss] [sans] [avenir] [default]
[encoding=texnansi]
\stoptypescript
> When I try to use my typescript in my environment file like this:
>
> \usetypescriptfile[type-adobe-avenir]
> \usetypescript[Avenir]
> \setupbodyfont[Avenir,10pt]
Yes, you have defined a sans font, but you're not setting sans as your
bodyfont. ConTeXt defaults to serif (i.e. rm), and since your
typescript doesn't define a rm font, it defaults to latin modern. So
simply write:
\setupbodyfont[Avenir,ss,10pt]
HTH
Thomas
___________________________________________________________________________________
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:[~2009-03-26 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 19:21 Markus Hubig
2009-03-26 7:40 ` Thomas A. Schmitz [this message]
2009-03-26 11:56 ` Markus Hubig
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=B651524E-79EE-4D02-A52C-EDB8FC9B6C05@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.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).