From: Oliver Heins <olli@sopos.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: hyphenation problem using |-| in composed words -- bug?
Date: Wed, 25 Nov 2009 15:06:29 +0100 [thread overview]
Message-ID: <87d436vguy.fsf@sopos.org> (raw)
Hi,
when using |-| in a word as a non exclusive dash, this produces wrong
hyphenation.
For example, the word »longer-word-to-be-hyphenated« should be
hyphenated e.g. like this:
longer-
word-
to-
be-
hy-
phen-
ated
but actually it is hyphenated like this:
longer
-word
-to
-be
-hy-
phen-
ated
Using || instead of |-| works like expected, so using it in combination
with \setuphyphenmark[sign=normal] could be considered a workaround.
Sadly, that produces the same bad result. :-(
Here's a minimal example:
%\setuphyphenmark[sign=normal]
\starttext
\hsize 1em
longer|-|word|-|to|-|be|-|hyphenated
longer||word||to||be||hyphenated
\stoptext
TIA,
olli
--
Oliver Heins heins@sopos.org http://oliverheins.net/
http://blog.overheins.net/ F27A BA8C 1CFB B905 65A8
http://scriptorium-adp.de/ 2544 0F07 B675 9A00 D827
1024D/9A00D827 2004-09-24 -- gpg --recv-keys 0x9A00D827
Please avoid sending me Word or PowerPoint attachments:
http://www.gnu.org/philosophy/no-word-attachments.html
___________________________________________________________________________________
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 reply other threads:[~2009-11-25 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 14:06 Oliver Heins [this message]
2009-11-25 17:32 ` Oliver Heins
2009-11-26 7:58 ` Taco Hoekwater
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=87d436vguy.fsf@sopos.org \
--to=olli@sopos.org \
--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).