From: S Barmeier <severinbarmeier@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: hyphenation of hyphenated words
Date: Tue, 13 Mar 2012 09:58:57 +0530 [thread overview]
Message-ID: <4F5ECD09.1090002@googlemail.com> (raw)
In-Reply-To: <4F5DB3AC.4060403@wxs.nl>
non-standard still breaks as
non-stan-
dard
the stan- protruding from the text-block, whilst the rest of the line is
compressed as much as possible... Maybe context thinks, if it breaks at
the hyphen you can't tell that there was meant to be a hyphen, so to be
clear it uses two...?
I can't make much sense of it.
Severin
On 03/12/2012 01:58 PM, Hans Hagen wrote:
> On 11-3-2012 15:51, S Barmeier wrote:
>> On 03/11/2012 07:30 PM, Hans Hagen wrote:
>>> On 10-3-2012 21:52, S Barmeier wrote:
>>>> non-standard breaks as
>>>>
>>>> non-stan-
>>>> dard
>>>>
>>>> Is there a way to tell context to break the word at the hyphen that
>>>> already exists?
>>>
>>> \hyphenation{bla-bla-bla}
>>>
>>> Hans
>> Before \starttext after \starttext, \hyphenation{non-standard} is
>> resisting... (see attached) Setting \hyphenation{non-standard}, I'm
>> surprised it breaks like \hyphenation{non-stan\-dard}...
>
> You need to make sure that a language is set and patterns are loaded.
>
> \mainlanguage[en]
> \hyphenation{bla-bla}
>
>> Thank you,
>> Severin
>>
>> P.S.: Is there a way to break words without adding a hyphen, e.g.
>> beginner/intermediate/advanced breaking into
>>
>> beginner/
>> intermediate/advanced?
>
>
___________________________________________________________________________________
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:[~2012-03-13 4:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2708.1331386188.4232.ntg-context@ntg.nl>
2012-03-10 20:32 ` ruby for vertical layout S Barmeier
2012-03-11 8:51 ` Wolfgang Schuster
2012-03-11 8:57 ` S Barmeier
2012-03-11 9:05 ` Wolfgang Schuster
2012-03-11 9:18 ` S Barmeier
2012-03-11 9:28 ` Wolfgang Schuster
2012-03-11 9:35 ` S Barmeier
2012-03-10 20:52 ` hyphenation of hyphenated words S Barmeier
2012-03-10 20:56 ` Marco Pessotto
2012-03-11 14:00 ` Hans Hagen
[not found] ` <4F5CBC0E.4040107@googlemail.com>
[not found] ` <4F5DB3AC.4060403@wxs.nl>
2012-03-13 4:28 ` S Barmeier [this message]
2012-03-11 7:14 ` ntg-context Digest, Vol 93, Issue 36 S Barmeier
2012-03-11 11:54 ` More CJK fall-back fonts (S Barmeier) dalyoung
2012-03-13 5:01 ` More CJK fall-back fonts S Barmeier
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=4F5ECD09.1090002@googlemail.com \
--to=severinbarmeier@googlemail.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).