ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ville Voipio <ville.voipio@kpatents.com>
Subject: A font problem with the stand-alone Windows distribution
Date: Wed, 18 Jan 2006 21:40:26 +0200	[thread overview]
Message-ID: <43CE99AA.9060003@kpatents.com> (raw)
In-Reply-To: <op.s3k2ruvjnx1yh1@walayah1.wildblue.com>

A font problem -- again. I am so sorry.

I try to use the URW postscript fonts with the stand-alone 
mswincontext.zip distribution. Everything else seems to work fine, but 
when I say:

   \usetypescript[adobekb][\defaultencoding]
   \usetypescript[pos][\defaultencoding]
   \setupbodyfont[pos,11pt]

I get a bunch of complaints from Acroread, and it uses Helvetica 
everywhere. (The same happens with Postscript instead of pos.)

The reason is rather clear, the log has the following rows:

   Warning: pdfetex.exe (file ptmb8y): Font ptmb8y at 79 not found
   Warning: pdfetex.exe (file pcrr8y): Font pcrr8y at 55 not found
   Warning: pdfetex.exe (file pcrr8y): Font pcrr8y at 86 not found
   etc.

So, the system tries to find the Adobe fonts which I do not have. Their 
URW counterparts are included in the stand-alone distribution, but the 
system does not seem to look for the u***** fonts.

I do not claim to understand the complete font mess, but ConTeXt seems 
to get the right map files:

   fonts           : resetting map file list
   fonts           : using map file: original-base
   fonts           : using map file: ec-public-lm
   fonts           : using map file: ec-base
   fonts           : using map file: original-ams-base
   fonts           : using map file: original-public-lm
   fonts           : using map file: texnansi-base
   fonts           : using map file: texnansi-urw-times
   fonts           : using map file: original-youngryu-tx
   fonts           : using map file: texnansi-urw-helvetica
   fonts           : using map file: texnansi-urw-courier

What goes wrong? I am using the newest mswincontext.zip downloaded just 
a half an hour ago, the log says:

   ConTeXt  ver: 2006.01.09  fmt: 2006.1.9  int: english  mes: english

Thanks for all hints. And once again, sorry for spamming the list with 
YAFP (Yet Another Font Problem).

- Ville

  reply	other threads:[~2006-01-18 19:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 16:58 a little ConTeXt advocacy-) Idris Samawi Hamid
2006-01-18 19:40 ` Ville Voipio [this message]
2006-01-18 21:07   ` A font problem with the stand-alone Windows distribution Taco Hoekwater
2006-01-19  9:40     ` Ville Voipio
2006-01-19 10:17       ` Taco Hoekwater
2006-01-18 21:41 ` a little ConTeXt advocacy-) Henning Hraban Ramm
2006-01-18 23:04   ` Idris Samawi Hamid

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=43CE99AA.9060003@kpatents.com \
    --to=ville.voipio@kpatents.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).