ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sietse Brouwer <sbbrouwer@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Hyphenation documentation
Date: Sun, 21 Apr 2013 19:27:55 +0200	[thread overview]
Message-ID: <CAF=dkzxakN3s5EfPSnyOvh4-f9gUcfGju-nyum_O1D_V-nnXng@mail.gmail.com> (raw)
In-Reply-To: <5173C2EB.3050106@wxs.nl>

Hi Wolfgang, hi Hans,

Thanks, I've updated the documentation accordingly.

> You have to use type 5 to create a rule for this,
> do you have a example where this is needed besides
> the one mentioned in the duden [1] example for a
> closing bracket.

No, this was just a gut reaction. I can see the sense of the other
way, too, and I couldn't hope to compete with the Duden for authority.
;-)

> \unexpanded\def\unhyphenated
>   {\groupedcommand{\lefthyphenmin\maxdimen}\donothing}

\unhyphenated also documented. The name is inconsistent with
\setupalign[nothyphenated];
perhaps \nothyphenated is a better name? (You could also add it as a
synonym, but it is cleaner to have only one name, I think.)

Cheers,
Sietse

On 21 April 2013 12:43, Hans Hagen <pragma@wxs.nl> wrote:
> On 4/21/2013 10:26 AM, Wolfgang Schuster wrote:
>
>> No, you have to use \hbox too but I think a command with a speaking
>>
>> name would be better.
>
>
> \unexpanded\def\unhyphenated
>   {\groupedcommand{\lefthyphenmin\maxdimen}\donothing}
>
> I'll add that.
>
> Hans
>
>
> -----------------------------------------------------------------
>                                           Hans Hagen | PRAGMA ADE
>               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
>                                              | www.pragma-pod.nl
> -----------------------------------------------------------------
>
> ___________________________________________________________________________________
> 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
___________________________________________________________________________________


  reply	other threads:[~2013-04-21 17:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-20 20:05 Sietse Brouwer
2013-04-21  8:26 ` Wolfgang Schuster
2013-04-21 10:43   ` Hans Hagen
2013-04-21 17:27     ` Sietse Brouwer [this message]
2013-04-21 20:24       ` Hans Hagen
2013-04-27 13:55 ` Marco Patzer
2013-04-27 14:35   ` Wolfgang Schuster

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='CAF=dkzxakN3s5EfPSnyOvh4-f9gUcfGju-nyum_O1D_V-nnXng@mail.gmail.com' \
    --to=sbbrouwer@gmail.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).