Re: [NTG-context] Hyphenation documentation

2013-04-27 Thread Marco Patzer
On 2013–04–20 Sietse Brouwer wrote: 1. how do I protect a single instance of a word against hyphenation? Does ConTeXt, like LaTeX, use \hbox{myfragileword}, or something different? You can enclose it in vertical bars: |thiswordwillnotbehyphenated| However, I'd prefer the new \unhyphenated

Re: [NTG-context] Hyphenation documentation

2013-04-27 Thread Wolfgang Schuster
Am 27.04.2013 um 15:55 schrieb Marco Patzer home...@lavabit.com: On 2013–04–20 Sietse Brouwer wrote: 1. how do I protect a single instance of a word against hyphenation? Does ConTeXt, like LaTeX, use \hbox{myfragileword}, or something different? You can enclose it in vertical bars:

Re: [NTG-context] Hyphenation documentation

2013-04-21 Thread Wolfgang Schuster
Am 20.04.2013 um 22:05 schrieb Sietse Brouwer sbbrou...@gmail.com: Hello all, I've just pulled together some questions of mine and their answers, and written them up into a hyphenation QA. http://wiki.contextgarden.net/Hyphenation http://wiki.contextgarden.net/Command/definebreakpoint

Re: [NTG-context] Hyphenation documentation

2013-04-21 Thread Hans Hagen
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

Re: [NTG-context] Hyphenation documentation

2013-04-21 Thread Sietse Brouwer
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

Re: [NTG-context] Hyphenation documentation

2013-04-21 Thread Hans Hagen
On 4/21/2013 7:27 PM, Sietse Brouwer wrote: 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,