From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Install mess (Type3 Fonts)
Date: Tue, 21 Mar 2006 09:53:11 +0100 [thread overview]
Message-ID: <441FBEF7.9050506@elvenkind.com> (raw)
In-Reply-To: <ops6qny4rl9niby6@localhost>
Hi Nico,
nico wrote:
> I know, I shouldn't have updated the context distrib, but I did... Of
> course, I add problems with missing fonts, and installed the lm fonts from
> CTAN. Now texexec can compile again.
>
> But the fonts used are now horrible, producing fuzzy letters. Can anyone
> give me some hints to fix this buggy install?
I can try:
> [1.1{/usr/local/share/texmf-dist/fonts/map/dvips/context/original-empty.map}{/u
> sr/local/share/texmf-dist/fonts/map/dvips/context/original-base.map}{/usr/local
> /share/texmf-dist/fonts/map/dvips/context/ec-public-lm.map}{/usr/local/share/te
> xmf-dist/fonts/map/dvips/context/ec-base.map}{/usr/local/share/texmf-dist/fonts
> /map/dvips/context/8r-base.map}{/usr/local/share/texmf-dist/fonts/map/dvips/con
> text/t5-base.map}{/usr/local/share/texmf-dist/fonts/map/pdftex/context/original
> -ams-base.map}{/usr/local/share/texmf-dist/fonts/map/dvips/context/original-ams
> -euler.map}{/usr/local/share/texmf-dist/fonts/map/dvips/context/original-public
> -lm.map}]
It looks like pdftex cannot find the actual font files, and the above
section of loaded map files hints why. It looks like you installed
the new context in texmf-dist instead of in texmf-local, and probably
that is why it is still finding map files from the old installation.
The ones in fonts/map/dvips/context are most likely from the original
tetex install, and the new ones are in fonts/map/pdftex/context.
Cheers, Taco
next prev parent reply other threads:[~2006-03-21 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 1:05 nico
2006-03-21 6:48 ` Thomas A. Schmitz
2006-03-21 8:53 ` Taco Hoekwater [this message]
2006-03-21 18:22 ` nico
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=441FBEF7.9050506@elvenkind.com \
--to=taco@elvenkind.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).