ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Cc: "Eckhart Guthöhrlein"
	<eckhart_guthoehrlein@public.uni-hamburg.de>,
	"ConTeXt mailing list" <ntg-context@ntg.nl>
Subject: Re: two questions
Date: Tue, 10 Jul 2001 09:17:24 +0000	[thread overview]
Message-ID: <3B4AC824.6040602@elvenkind.com> (raw)
In-Reply-To: <3.0.6.32.20010709104800.0133e8b0@server-1>

Hans Hagen wrote:

> At 09:58 AM 7/9/01 +0200, Taco Hoekwater wrote:
> 
>>Eckhart Guthöhrlein wrote:
>>
>>>At 09:11 06.07.2001 +0000, you wrote:
>>>\def\nolig{\nobreak\discretionary{-}{}{\kern.03em}\nobreak\hskip\z@skip} %
>>>(after changing the catcode of @)
>>>
>>>Is there any problem with that definition? If not, I would suggest
>>>including a similar command in ConTeXt, since ligatures in words like
>>>"Auflage" or "hinauffliegen" have to be corrected.
>>>
>>Not really a problem, but it also allows hyphenation at this point, and
>>ensures that hyphenation for the partial (left&right) words is also
>>possible.
>>This isn't always desired, I think. So there should be two commands I
>>guess. One to just block ligatures, and another that does what babel
>>does.
>>
>  
> taco, do you remember what the proposed [etex] lig prevention primitive
> was? \nolig or \noligs or so [lots my notes] and what is the most robust
> definition? \kern\zeropoint? 

IIRC, both were proposed. \noligs to disable all ligs in the current 
font, and \nolig for individual use. \kern\zeropoint is probably the 
cleanest definition for \nolig (\noligs is nearly undoable in macros),
and then you probably need an |x| command for the hyphenatable thing
(as in babel).

Greetings,

Taci


  reply	other threads:[~2001-07-10  9:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-05 12:03 Eckhart Guthöhrlein
2001-07-05 21:10 ` Hans Hagen
2001-07-06  9:11   ` Taco Hoekwater
2001-07-06  7:57     ` maartenwisse
2001-07-07 14:47     ` Eckhart Guthöhrlein
2001-07-08 22:57       ` Hans Hagen
2001-07-09  7:58       ` Taco Hoekwater
2001-07-09  8:48         ` Hans Hagen
2001-07-10  9:17           ` Taco Hoekwater [this message]
2002-07-08  7:27 Two questions scarsoluigi
2002-07-12 16:41 ` Hans Hagen
2003-02-06 17:13 two questions Tasos Drosopoulos
2003-02-06 17:31 ` Idris S Hamid
2003-02-06 17:35 ` Hans Hagen
2003-02-06 19:56 ` Willi Egger
2003-02-07  7:26   ` Gour
2003-02-07  9:32     ` Hans Hagen
2003-02-08 20:08     ` Willi Egger
2007-11-06  7:07 Dalyoung Jeong

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=3B4AC824.6040602@elvenkind.com \
    --to=taco@elvenkind.com \
    --cc=eckhart_guthoehrlein@public.uni-hamburg.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).