ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Fonts not found
Date: Tue, 30 Jan 2001 18:42:27 +0100	[thread overview]
Message-ID: <3.0.6.32.20010130184227.013fd210@server-1> (raw)
In-Reply-To: <20010129233402.A764@ruhrau.de>

At 11:34 PM 1/29/01 +0100, Johannes H?sing wrote:
>On Sun, Jan 28, 2001 at 11:08:57PM +0100, Hans Hagen wrote:
>> At 10:11 AM 1/28/01 +0100, Johannes H?sing wrote:
>[...]
>> >Since then, I get disturbing messages running ConTeXt like
>> >"Warning: cont-en (file cmr8): Font cmr8 at 720 not found"
>> >and even more disturbing output (ugly pixelish fonts), even though the
>> >font files seem to be there: "locate cmr8.pfb" gets me
>> >/usr/share/texmf/fonts/type1/bluesky/cm/cmr8.pfb.
>> >
>> >Looking at the log I see that all paths mentioned use the TEXLOCAL
>> >tree. The only exception is /usr/share/texmf/pdftex/config/pdftex.cfg. 
>> >Oh yes, and cmr8.pfb is mapped to cmr8 in pdftex.map.
>>  
>> This is unrelated to context. 
>
>Most certainly, but maybe not to ConTeXt :-). I run pdflatex without 
>problems so the issue apparently is not within pdftex.
>
>> Are you sure that the pdf config file
>> includes a proper map file from the right path? 
>
>I don't know if pdftex.cfg expects the pdftex.map file to reside in the
>$TEXMFMAIN/dvips/config folder, so I created a soft link to the same
>directory as pdftex.cfg. Same effect. So, where would pdftex expect the
>map file to be? Oh yes, and I ran texhash.

You may then check the paths as specified in texmf.cnf where fonts are
sought. Maybe there is a difference there. 

you cal so otry one of the obscure path search debugging flags (pdfetex
--help)

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-01-30 17:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-28  9:11 Johannes H?sing
2001-01-28 22:08 ` Hans Hagen
2001-01-29 22:34   ` Johannes H?sing
2001-01-30 17:42     ` Hans Hagen [this message]
2010-06-27 16:49 fonts " Ciro
2010-06-27 23:21 ` Ciro
2017-03-09  9:33 The requested font has no files for the 'tf' alternative Marco Patzer
2017-03-14 20:39 ` Wolfgang Schuster
2017-03-14 22:44   ` Marco Patzer
2017-03-15  7:17     ` Henning Hraban Ramm
2017-03-15  7:27       ` Fonts not found Henning Hraban Ramm
2017-03-16 21:28         ` Henning Hraban Ramm

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=3.0.6.32.20010130184227.013fd210@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).