ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl, cs@miktex.org
Subject: Re: Updating Miktex and Context beta
Date: Wed, 22 Aug 2001 11:33:08 +0200	[thread overview]
Message-ID: <5.1.0.14.1.20010822113101.023a3a10@server-1> (raw)
In-Reply-To: <3.0.5.32.20010821211448.0085f860@mail.northcoast.com>

At 09:14 PM 8/21/2001 -0700, David Arnold wrote:
>Hans et al,
>
>Well, I completely unloaded Miktex 2.0 and installed Miktex 2.1 (Large),
>which installs an older version of Context (ver 2001.2.27). The following
>compiled nicely, producing the Lucida font in the pdf output (checked in
>Acrobat).
>
>\setupbodyfont[lbr]
>
>\starttext
>
>Hello, world!
>
>\stoptext
>
>Next, I unzipped the latest beta and rebuilt cont-en.efmt and placed it in
>place of the existing cont-en.efmt. The file above no longer compiles,
>giving this error when attempting to compile:
>
>(F:\Miktex\tex\context\base\type-spe.tex)
>(F:\Miktex\tex\context\base\type-exa.tex))makemf --verbose LucidaBright
>cannot find LucidaBright source file.
>hbf2gf -q -g LucidaBright 300
>MAKETFM: don't know how to make LucidaBright

right, but did you add the line

\setupencoding[default=texnansi]

in your cont-sys.tex file?

The LucidaBright name needs to be mapped onto a real file name, which can 
be any encoding.

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
-------------------------------------------------------------------------


      reply	other threads:[~2001-08-22  9:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22  4:14 David Arnold
2001-08-22  9:33 ` 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=5.1.0.14.1.20010822113101.023a3a10@server-1 \
    --to=pragma@wxs.nl \
    --cc=cs@miktex.org \
    --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).