From: Marco <netuse@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: Hyphenation of composed words
Date: Mon, 10 May 2010 07:27:07 +0200 [thread overview]
Message-ID: <20100510072707.19eb2897@vorbis> (raw)
In-Reply-To: <4BE77CB8.7010800@googlemail.com>
> 1. || does *not* produce a en-dash but to kerned hyphens
You're right, I looked it up in the sources. It just looked like an
en-dash for me. But this is wrong. For hyphenation a hyphen is used. The
font designer has created a dedicated glyph for this purpose. And two
hyphens (or an en-dash) is too large. I've never seen the advice in a
typography book to kern two hyphens. I don't know why this is
implemented like this.
> 2. The correct method to get a *normal* hyphen is
>
> \setuphyphenmark[sign=normal]
>
Yes, this is the correct method. It should be enabled by default. If
somebody wants a larger hyphen (for some mysterious reasen), he/she can set it
up with
\setuphyphenmark[sign=wide]
> If the output is not correct it's a bug.
Yes, it is a bug. Hans already confirmed and said, he'll fix it, but it is not
yet done, that's why I wanted to remember him. You can try and run the example
from my first post. With Thomas' workaround the output is OK, but it is only a
workaround. I (and probably many other users) would like to have correct
behaviour by default.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-05-10 5:27 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 [this message]
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
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=20100510072707.19eb2897@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).