From: Patrick Gundlach <pg@levana.de>
Subject: Re: \type doen't type -- with latin-modern fonts.
Date: Sun, 14 Sep 2003 11:38:21 +0200 [thread overview]
Message-ID: <m2brtnn20i.fsf@levana.de> (raw)
In-Reply-To: <200309140726.h8E7QAYE030812@reserv1.univ-lille1.fr> (Daniel Flipo's message of "Sun, 14 Sep 2003 09:26:07 +0200")
Daniel Flipo <Daniel.Flipo@univ-lille1.fr> writes:
> Note that the bug also occurs with ae-fonts, so they should be fixed
> too... although ae-fonts will probably disappear when lm-fonts spread.
this is due to fontinst. The lm fonts, as far as I know, were created
by "hand" (metatype1). We could pick up the discussion for ligatures
in monospaced fonts by fontinst if needed.
But I have to admit that I can imagine a situation where one wants
this ligature: when you typeset text in a regular font and switch to
tt afterwards.
Patrick
--
Silent is the goldfish in its bowl
prev parent reply other threads:[~2003-09-14 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 16:49 Daniel Flipo
2003-09-13 17:44 ` Patrick Gundlach
2003-09-13 19:17 ` Hans Hagen
2003-09-13 22:10 ` Patrick Gundlach
2003-09-14 7:26 ` Daniel Flipo
2003-09-14 9:38 ` Patrick Gundlach [this message]
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=m2brtnn20i.fsf@levana.de \
--to=pg@levana.de \
--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).