ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Siep <siepo@cybercomm.nl>
Subject: Re: lucida
Date: Fri, 13 Dec 2002 12:58:39 +0100	[thread overview]
Message-ID: <20021213125839.47c678f4.siepo@cybercomm.nl> (raw)
In-Reply-To: <15863.31435.114326.267227@localhost.localdomain>

On Wed, 11 Dec 2002 09:50:03 -0800
"Larry Stamm" <larry@larrystamm.com> wrote:

> siep  <siep@elvenkind.com> writes:
> 
>      > Now I got the file showfont.pdf. I copied the example, but I
>      > still got a texnansi-lbr missing font. \setupbodyfont didn't work
>      > either.
> 
>      > A LaTeX file with \usepackage{lucidabr} and either with or
>      > without \usepackage{texnansi} works perfectly.
> 
>      > What assumptions are being made about the way the fonts are
>      > installed? I have been testing on what is basically a stock tetex
>      > with lb... pfb's added and with a context from August, and on a
>      > stock miktex also with with lb... pfb's added.
> 
> After I installed the 10-23-2002 version, I couldn't get any of the
> postcript fonts to work.  So I ended copying all the .afm and .pfb
> postscript files into a temporary directory, and running texfont on the
> whole bunch.  Now they work fine.
> 
> I don't have the lucida .pfb or .pfa files installed on my system, so
> these fonts won't work until I get the .pfb files (is this right?).
> Maybe you should check for the existence of the lucida .pfb files on
> your system as a starting point.  If you find them, read mtexfont.pdf
> and follow the instructions for installing a new font on the lucida font
> files.  You should be in business then.
> 
> I'm just learning myself, and this may be all wrong.  Please enlighten
> me if so; I find the ConTeXt font system to be difficult to understand,
> although it is beginning to make some sense.

Thanks for your input.

Hans, can you confirm that there is no simple way to use an existing
Lucida installation and that this is really necessary? And what about
other PostScript fonts?

-- 
Siep Kroonenberg
siepo@cybercomm.nl

  reply	other threads:[~2002-12-13 11:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 14:46 lucida Siep
2002-12-10 15:21 ` lucida Matthew Huggett
2002-12-10 15:46   ` lucida Siep
2002-12-10 16:03     ` lucida Daniel Graham
2002-12-11  1:08       ` lucida Matthew Huggett
2002-12-11  9:04         ` lucida Siep
2002-12-11 17:50           ` lucida Larry Stamm
2002-12-13 11:58             ` Siep [this message]
2002-12-13 17:48               ` lucida Hans Hagen
2002-12-11  1:07     ` lucida Matthew Huggett
2010-11-08 12:33 Lucida Herbert Voss
2010-11-08 13:42 ` Lucida Mojca Miklavec
2010-11-08 15:58   ` Lucida Herbert Voss
2010-11-08 20:49     ` Lucida Hans Hagen
2010-11-08 21:12   ` Lucida Herbert Voss
2010-11-09  7:45     ` Lucida Mojca Miklavec
2010-11-09  9:10       ` Lucida Herbert Voss
2010-11-09  9:47         ` Lucida Hans Hagen
2010-11-09 12:31         ` Lucida Herbert Voss
2010-11-09 13:08         ` Lucida Mojca Miklavec
2010-11-09 13:28           ` Lucida Herbert Voss
2010-11-09 14:12           ` Lucida Herbert Voss
2010-11-09 15:45             ` Lucida Mojca Miklavec
2010-11-09 16:42               ` Lucida Hans Hagen
2010-11-09  9:24       ` Lucida Hans van der Meer

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=20021213125839.47c678f4.siepo@cybercomm.nl \
    --to=siepo@cybercomm.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).