ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Tom" <Tom@tuxedo-press.com>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: Iwona-Light error
Date: Wed, 9 Feb 2011 17:53:41 -0500	[thread overview]
Message-ID: <030901cbc8ac$335eebe0$9a1cc3a0$@com> (raw)
In-Reply-To: <AANLkTi=5FGKz6gbOL-TAuYAAjSvL8nY+wCrx1oERdSMq@mail.gmail.com>

That works. Now I get:
Cannot find Helvetica-Caps.mf 
for Postscript font.

\usetypescriptfile[type-one]
\usetypescript[postscript][ec]
\setupbodyfont[postscript,12pt]

\starttext
\switchtobodyfont[ss]
\showbodyfont
\showbodyfontenvironment
\input knuth
\stoptext

Tom Benjey
717-258-9733 voice
717-243-0074 fax
blog: www.TomBenjey.com




-----Original Message-----
From: ntg-context-bounces@ntg.nl [mailto:ntg-context-bounces@ntg.nl] On
Behalf Of Mojca Miklavec
Sent: Wednesday, February 09, 2011 2:51 PM
To: mailing list for ConTeXt users
Subject: Re: [NTG-context] Iwona-Light error

On Wed, Feb 9, 2011 at 20:37, Tom <Tom@tuxedo-press.com> wrote:
> I get the following error message when trying to use the iwona-light font
in
> MKII:
> Cannot find Iwona-CapsLight.mf.

In type-one.mkii it should have been:

    \starttypescript [sans] [iwona-light] [name]
        \setups[font:fallback:sans]
...
        \definefontsynonym [SansCaps]           [Iwona-CapsLight-Regular]
        \definefontsynonym [SansItalicCaps]     [Iwona-CapsLight-Italic]

Instead of just Iwona-CapsLight and Iwona-CapsLightItalic.

Thanks for noticing.

Mojca
____________________________________________________________________________
_______
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
____________________________________________________________________________
_______

___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2011-02-09 22:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 19:37 Tom
2011-02-09 19:51 ` Mojca Miklavec
2011-02-09 22:01   ` Hans Hagen
2011-02-09 22:53   ` Tom [this message]
2011-02-10  6:41     ` Mojca Miklavec
2011-02-10 14:37       ` Tom
2011-02-10 15:06         ` Hans Hagen
2011-02-10 17:26         ` Mojca Miklavec
2011-02-11 15:34           ` Tom
2011-02-11 16:07             ` Mojca Miklavec
2011-02-11 16:08               ` Mojca Miklavec
2011-02-11 16:11                 ` Tom
2011-02-11 16:12               ` Tom

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='030901cbc8ac$335eebe0$9a1cc3a0$@com' \
    --to=tom@tuxedo-press.com \
    --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).