From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: texfont: installed font only works with pdftex
Date: Tue, 08 Aug 2006 10:56:12 +0200 [thread overview]
Message-ID: <44D851AC.90603@elvenkind.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0608081020510.21304@rabat.Mathematik.Uni-Marburg.DE>
Andreas Schneider wrote:
> On Tue, 8 Aug 2006, Hans Hagen wrote:
>
>>if the problem is in a font not having glyphs, you can consider making a
>>special encoding vector + enco-* file; not that complex since one can
>>start with an existing one
>
>
> The problem is that it does work with pdftex (tex -> pdf via
> texexec --pdf), but it does NOT work with tex -> dvi -> ps via
> texexec, dvips (some glyphs, such as ligatures and umlauts, don't
> work in the latter case). It should be possible to get it working,
> as fontinst is able to do it, so I don't know why I should need an
> extra encoding.
Somehow you yourself (and not texfont!) have created a font map
file called bgj.map for dvips, and that file is wrong.
Taco
next prev parent reply other threads:[~2006-08-08 8:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 8:07 texfont produces faked ligatures with ec encoding Andreas Schneider
2006-08-06 9:52 ` Taco Hoekwater
2006-08-06 15:00 ` Andreas Schneider
2006-08-06 16:53 ` Thomas A. Schmitz
[not found] ` <Pine.LNX.4.64.0608062211300.31615@rabat.Mathematik.Uni-Marburg.DE>
2006-08-06 21:00 ` Thomas A. Schmitz
2006-08-07 7:59 ` Andreas Schneider
2006-08-07 8:29 ` Andreas Schneider
2006-08-07 8:42 ` Taco Hoekwater
2006-08-07 12:34 ` texfont: installed font only works with pdftex Andreas Schneider
2006-08-07 13:25 ` texfont produces faked ligatures with ec encoding Hans Hagen
2006-08-08 7:14 ` texfont: font only works with pdftex Andreas Schneider
2006-08-08 8:05 ` Hans Hagen
2006-08-08 8:33 ` texfont: installed " Andreas Schneider
2006-08-08 8:56 ` Taco Hoekwater [this message]
2006-08-08 19:27 ` Andreas Schneider
2006-08-08 21:26 ` Taco Hoekwater
2006-08-08 21:46 ` Hans Hagen
2006-08-08 21:57 ` Taco Hoekwater
2006-08-09 5:29 ` Thomas A. Schmitz
2006-08-09 10:21 ` Hans Hagen
2006-08-09 11:33 ` Taco Hoekwater
2006-08-09 13:58 ` Taco Hoekwater
2006-08-09 14:14 ` Hans Hagen
2006-08-09 14:29 ` Thomas A. Schmitz
2006-08-09 14:52 ` Hans Hagen
2006-08-09 15:44 ` Thomas A. Schmitz
2006-08-08 21:50 ` Hans Hagen
2006-08-11 9:34 ` Andreas Schneider
2006-08-11 9:59 ` Taco Hoekwater
2006-08-11 10:33 ` Andreas Schneider
2006-08-06 21:42 ` texfont produces faked ligatures with ec encoding Hans Hagen
2006-08-06 23:22 ` Mojca Miklavec
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=44D851AC.90603@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).