From: "Maarten Wisse" <pmw4197@hotmail.com>
Subject: Font problems when using dvips
Date: Tue, 14 Nov 2000 08:30:57 GMT [thread overview]
Message-ID: <F236DKPGzGqiuLeHTgz000010f6@hotmail.com> (raw)
Hi ConTeXt experts,
It was a long time ago that I used ConTeXt, but now I'm back to ConTeXt for
making a birth announcement. No don't congratulate me, because one should do
this actually before the baby is there :-)
Ok, I use a Bitstream font Kabel/Cable and I've made the necessary font
files using fontinst with \latinfamily command. Then I do the following in
my ConTeXt files:
\definefontsynonym [Kabel-Light] [bkbr8t] [encoding=ec]
\definefontsynonym [Sans] [Kabel-Light]
For dvips and pdftex, I do the following in bkb.map:
bkbr8r Geometric-LightC "TeXBase1Encoding ReEncodeFont" <8r.enc <bkbm8a.pfb
This I do for all the different variants of the font, of course. It works
perfectly when making pdf files with PDFeTeX 13d. All accented characters
and an en-dash which are on the card appear correctly. However, when trying
to compile to dvi and then to dvips, accents and en-dash disappear. I
already tried two alternatives:
1. Change bkbr8t in the \definefontsynonym command to bkbr8r and change
encoding to [encoding=texnansi].
2. change bkbr8r in the bkb.map file to bkbr8t and leaving the ConTeXt files
unmodified. In this case, I do an upd.map rerun of course, to get the
modifications into psfonts.map and pdftex.map
Neither of these works. Does anyone know what is wrong?
My platform: RedHat 7.0 with teTeX 1.0.7
Thanks in advance,
Maarten Wisse
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
next reply other threads:[~2000-11-14 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-14 8:30 Maarten Wisse [this message]
2000-11-14 11:47 ` Hans Hagen
2000-11-14 12:35 ` S2P development
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=F236DKPGzGqiuLeHTgz000010f6@hotmail.com \
--to=pmw4197@hotmail.com \
/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).