From: Marco <netuse@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: Hyphenation of composed words
Date: Mon, 10 May 2010 17:26:36 +0200 [thread overview]
Message-ID: <20100510172636.4c15fe5c@vorbis> (raw)
In-Reply-To: <4BE7BFE8.7050706@wxs.nl>
> > 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.
>
> because we needed it to be this way: we use it for separating
> compound words and then we want to have the hyphen between the
> compounds to be different from the ones within
That's not how it is done in everyday typography, seems to be more a
border case.
> .. also, the reason for kerned hyphens instead of an endash is simple:
> the endash is too thin (at least in lm)
That's true. The en-dash is condiderably thinner.
> this works ok here (and i'm prety sure that it's also ok a few betas
> ago)
>
> \starttext
>
> test||test
>
> \setuphyphenmark[sign=normal]
>
> test||test
>
> test|-|test
>
> \stoptext
Sure, my fault. This works. There _was_ a bug with the hyphen appearing
on the start of the next line. This is fixed. Thank you. I thought you
would also fix the »wrong« hyphenation sign, so I didn't check, just
assumed that both issues aren't fixed. So
\setuphyphenmark[sign=normal]
works now as expected (even if it's not the default). Thanks for this
fix.
> and the defaults are unlikely to change, but you can set it in your
> local cont-sys.tex file
Ah, I see. I was not aware of a user configuration file (wiki helps how
to set it up I just looked). So I can put my »personal« default hyphen
there.
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 15:26 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 [this message]
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=20100510172636.4c15fe5c@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).