ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Patrick Gundlach <pg@levana.de>
Cc: B.Jackowski@gust.org.pl
Subject: Re: \type doen't type -- with latin-modern fonts.
Date: Sun, 14 Sep 2003 00:10:01 +0200	[thread overview]
Message-ID: <m2fzj0mjba.fsf@levana.de> (raw)
In-Reply-To: <5.2.0.9.1.20030913205803.08664320@localhost> (Hans Hagen's message of "Sat, 13 Sep 2003 21:17:12 +0200")

Hans Hagen <pragma@wxs.nl> writes:


Hi,

> since this effect does not show op with cmtt, it looks like the lmtt
> fonts indeed have a ligature, which makes them somehow incompatible;

right. See for example cork-lmtt10.tfm

(LIGTABLE
   (LABEL O 41)        1
   (LIG O 140 O 275)
   (STOP)
   (LABEL O 77)        2
   (LIG O 140 O 276)
   (STOP) 
   (LABEL O 55)        3
   (LIG O 55 O 25)     4
   (LIG O 177 O 177)   5
   (STOP)
   )

the first and second one is the standard TeX ?` and !` (perhaps I've
got the accent wrong), that are also in cmtt. The third (3-4) is
hyphen-hyphen->endash and the last one (3-5)
hyphen-strangechar->strangechar (what is it? some 
other kind of hyphen?).


> the best solution would be a \noligs primitives (also handy for xml)

:-) I think a lot of TeXhackers would like to see something like this.

> an alternative is to have two tfm files, one for tt text with ligature
> building and one for verbatim, say:
>
> cmtt10.tfm
> cmtv10.tfm
>
> (cmvtt is already taken)

and some more of the font mess....

> let's see what Jacko says ...

that would be good to hear.


Patrick

  reply	other threads:[~2003-09-13 22:10 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 [this message]
2003-09-14  7:26     ` Daniel Flipo
2003-09-14  9:38       ` Patrick Gundlach

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=m2fzj0mjba.fsf@levana.de \
    --to=pg@levana.de \
    --cc=B.Jackowski@gust.org.pl \
    --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).