ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marco <netuse@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: Hyphenation of composed words
Date: Mon, 10 May 2010 17:54:10 +0200	[thread overview]
Message-ID: <20100510175410.1b37c664@vorbis> (raw)
In-Reply-To: <000b01caf019$483f7f50$8614a8c0@boschung.local>

> It seems that the en-dash *can* be used in English in some cases:
> 'high-priority--high-pressure tasks' from
> http://en.wikipedia.org/wiki/Hyphen
I see. But this is a --more or less-- contructed case where using an
en-dash instead of a hyphen makes sense. I agree with this example, the
en-dash clearifies things.

But for general purpose the hyphen is used and not the en-dash. And I
think the typesetting system should be set up to fit the general
purpose. (Hans has a different opinion, I know.)

BTW: If the appearance of the hyphen is unsatisfying it is better to
choose a different font (or hyphen from a different font) or maybe to
»correct« the font instead of altering settings of the typesetting
system.

> Concerning the hyphen sign, '\setuphyphenmark[sign=normal]' works as
> expected on my system (= normal hyphen sign).
> But it was (is?) not usable because, in case of a line break, the
> hyphen sometimes was placed at the beginning of a new line.
You're right. I mixed things up. My fault. It always produced the right
sign. And the bug is fixed (Thanks Hans!). So you can use

\setuphyphenmark[sign=normal]

again in your cont-sys.tex ;-)

> With '\def\compoundhyphen{-}' the compound hyphen breaks correctly.
Not needed any more.

Marco


___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2010-05-10 15:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16 14:46 Marco
2010-04-16 21:33 ` Hans Hagen
2010-04-16 22:16   ` Marco
2010-05-09 19:34   ` Marco
2010-05-10  3:25     ` Wolfgang Schuster
2010-05-10  5:27       ` Marco
2010-05-10  8:12         ` Hans Hagen
2010-05-10 15:26           ` Marco
2010-05-10  8:17         ` Thomas Floeren
2010-05-10 15:54           ` Marco [this message]
2010-04-19  5:57 ` Thomas Floeren
2010-04-19 18:37   ` Marco

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=20100510175410.1b37c664@vorbis \
    --to=netuse@lavabit.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).