From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: font problems with new beta
Date: Tue, 21 Aug 2001 10:19:19 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20010821100808.0341d300@server-1> (raw)
In-Reply-To: <3.0.5.32.20010820204114.00862830@mail.northcoast.com>
At 08:41 PM 8/20/2001 -0700, David Arnold wrote:
>All,
>
>I haven't been following closely the new font developments, so I am a bit
>behind (A miktex user). This file:
>
>%output=pdf
>\starttext
> \setupbodyfont[lbr,10pt]
>Hello, mama!
>\stoptext
>
>Which compiled fine with my old Context (I've just installed the latest
>beta), gives this error:
>
>(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
I used to predefine some font names, but now do so at runtime, depending on
usage an dencoding [keep in mind that there is more than english, so some
users may want to default to ec, il2, pl0, cyr, or whatever encoding]. You
set up the encoding in cont-sys.tex (it may be worth to take a look in
cont-sys.rme)
\setupencoding[default=texnansi]
This setup determines what typescript will be chosen, and for texnansi, i
didn't yet set up the ec one (which is default). So, there is a typescript
that maps lucida on the natural names, but this may eventually even change
into prefixed names, but i lost the original lucida files [that is, they
must be somewhere on an old floppy] and only have texnansi encoded ones.
if you take a look at the type-* files, you can get an idea on how things
are selected; these methods permit simple definition files [typescripts]
with many encodings without ending up in thousands of tex files for fonts
btw, the idea is that either you load the associated map files manually
[probbaly happens now] or let context/pdftex do so. i already discussed the
sometimes fuzzy map file handling with thanh and when he's back in vietnam
he will look into these issues.
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
-------------------------------------------------------------------------
prev parent reply other threads:[~2001-08-21 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 3:41 David Arnold
2001-08-21 8:19 ` 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.20010821100808.0341d300@server-1 \
--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).