ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Patrick Gundlach <pg@levana.de>
Subject: Re: ligatures?
Date: Mon, 12 May 2003 23:41:46 +0200	[thread overview]
Message-ID: <87he7z6dwl.fsf@gundla.ch> (raw)
In-Reply-To: <20030512155450.12369@news.comp.lancs.ac.uk> ("Adam Lindsay"'s message of "Mon, 12 May 2003 16:54:49 +0100")

"Adam Lindsay" <atl@comp.lancs.ac.uk> writes:

Hello Adam,

I am not a TeX expert, but I try to give an answer. Please anybody
out there correct me. 

> So, am I right in concluding that ligatures are *only* handled by the
> output routine? 

The ligatures defined by the font are handled by the paragraph
breaking routine. Deep down inside the lion. The "output routine"
(OTR) is something different.

> There's no way of using ConTeXt to map my normal text input ('i'
> followed by 'j') to the already-defined \ijligature?

In order to parse the text so that ij is mapped to \ijligature, you
probably have to make the "i" active and check if the next char is
"j" and if yes, replace it with \ijligature. Don't think about it.


Patrick

      parent reply	other threads:[~2003-05-12 21:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 14:28 ligatures? Adam Lindsay
2003-05-12 14:57 ` ligatures? Bruce D'Arcus
2003-05-12 15:01   ` ligatures? Bill McClain
2003-05-12 15:25     ` ligatures? Bruce D'Arcus
2003-05-12 15:43       ` Dumb newbie question about UTF-8 support Edmund Lian
2003-05-12 15:03 ` ligatures? Patrick Gundlach
2003-05-12 15:46   ` ligatures? Bruce D'Arcus
2003-05-12 21:27     ` ligatures? Patrick Gundlach
2003-05-12 22:04       ` ligatures? Bruce D'Arcus
2003-05-12 15:54   ` Adam Lindsay
2003-05-12 20:54     ` Bruce D'Arcus
2003-05-12 21:41     ` 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=87he7z6dwl.fsf@gundla.ch \
    --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).