From: "Thomas Floeren" <thomas.floeren@boschung.com>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: Hyphenation of composed words
Date: Mon, 19 Apr 2010 07:57:21 +0200 [thread overview]
Message-ID: <005101cadf85$2d9a1ec0$8614a8c0@boschung.local> (raw)
In-Reply-To: <20100416164615.7381cc63@vorbis>
Marco <> wrote on Friday, April 16, 2010 4:46 PM:
> Hi,
>
> I've yet another hyphenation problem. I cannot get proper hyphenation
> in
> composed words. Take this MWE:
>
> \setuplayout [width=1.5cm]
> \starttext
>
> composed-word\par % not hyphenated, as expected
> composed||word\par % wrong: hyphenated, but an en-dash is used,
> % not a hyphen, so [sign=wide] seems to be the default
> composed|-|word\blank % wrong: hyphenated, but the hyphen is at the
> start of % the next line
>
> \setuphyphenmark [sign=normal] % For hyphenation a hyphen is used,
> % not an endash
> composed-word\par % not hyphenated, as expected
> composed||word\par % wrong: hyphen is at the start of the next line
> composed|-|word % wrong: hyphen is at the start of the next line
> \blank[2*line]
>
> \setbreakpoints [compound] % my workaround
> composed-word\par % correct hyphenation behaviour with hyphen
>
> \stoptext
>
> I hope with the comments the problem is clear. At first the default
> value for »sign« is wrong. It has to be »normal«. But with »normal« I
> cannot get the
> hyphen at the end of the line, instead it always appeares at the
> beginning of
> the next line.
>
At the moment I use \def\compoundhyphen{-} instead of \setuphyphenmark.
It seems to work (mkii).
Thomas
> The workaround works but has the disadvantage that everything is
> hyphenated, everywhere. I prevent this at the moment by using bars:
>> not-a-composed-word|
>
> Thanks in advance
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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-04-19 5:57 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
2010-04-19 5:57 ` Thomas Floeren [this message]
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='005101cadf85$2d9a1ec0$8614a8c0@boschung.local' \
--to=thomas.floeren@boschung.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).