From: Berend de Boer <berend@pobox.com>
Subject: Using Adobe built-in fonts with latest context + texlive 204
Date: Tue, 13 Sep 2005 11:53:50 +1200 [thread overview]
Message-ID: <87u0gp3ks1.fsf@dellius.nederware.nl> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello All,
I just upgraded my entire TeX system. There are no traces of old files
anymore, everything is brandnew. I installed texlive 2004 (because I
had it on a DVD, thanks NTG!).
I got the latest ConText (Aug 31).
The first thing I had to do was to setup the proper encoding. For
example I had to specify this:
\setupencoding[\s!default=8r] % or "ec", if you prefer
\usetypescript[berry][\defaultencoding]
or ec encoding, works as well. It didn't work out of the box
unfortunately.
But this seems to get me the URW fonts, not the greatest fonts. It
seems the latest tex has something like updmap, whatever that
is. Using "updmap --edit" I changed the LW35 setting to ADOBEkb and now
I get the built-in fonts I believe. Is that correct?
But I still got complaints about this one:
Warning: pdfetex (file ptmbi8a.pfb): cannot open Type 1 font file for reading
Warning: pdfetex (file ptmri8a.pfb): cannot open Type 1 font file for reading
Warning: pdfetex (file ptmr8a.pfb): cannot open Type 1 font file for reading
Warning: pdfetex (file ptmb8a.pfb): cannot open Type 1 font file for reading
But document displays fine BTW.
I fixed that by changing another setting: setting pdftexDownloadBase14
to false.
But I'm a bit confused here. I thought Adobe had made those fonts
freely available, so shouldn't they be in my tex installation? Or is
this still an encoding issue, and should I use a different encoding in
order for pdfetex to find these four missing font files??
- --
Live long and prosper,
Berend de Boer
(PGP public key: http://www.pobox.com/~berend/berend-public-key.txt)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQFDJhUNIyuuaiRyjTYRAqHNAKDDNtQ8BqyXrpUAix0Dr1it7YBMTgCdGmHX
/IgEDy4JJta6dO/v/y7z/vo=
=5l6+
-----END PGP SIGNATURE-----
next reply other threads:[~2005-09-12 23:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 23:53 Berend de Boer [this message]
2005-09-13 8:22 ` Taco Hoekwater
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=87u0gp3ks1.fsf@dellius.nederware.nl \
--to=berend@pobox.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).