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: Hyphenation documentation
Date: Sat, 20 Apr 2013 22:05:21 +0200	[thread overview]
Message-ID: <CAF=dkzydSPw55jhrMN7Ntg6CLWQAyEMtToGPp96nbwLdzLxEZQ@mail.gmail.com> (raw)

Hello all,

I've just pulled together some questions of mine and their answers,
and written them up into a hyphenation Q&A.
http://wiki.contextgarden.net/Hyphenation
http://wiki.contextgarden.net/Command/definebreakpoint

Unfortunately, there are still some holes in the documentation I
wrote. Questions I still have, and which I now pose to the list:

1. how do I protect a single instance of a word against hyphenation?
Does ConTeXt, like LaTeX, use \hbox{myfragileword}, or something
different?

2. In the command \definebreakpoint, what do these keys do? I can't
get them to do anything (MWE below)
** left
** middle
** right

3. Is there perhaps a bug in breakpoints of type 2 and 3. (MWE below.)
The key 'type' seems to control where hyphens appear. If 1 is a
hyphenation character of type 1, etc, this is the observed behaviour
(`/` is the linebreak):
...1...1  / ...
...2...   / 2-...   % I would expect: ...2... / -2...
...3...-3 / ...     % I would expect: ...3...3- / ...
...4...4  / 4...
......    / ...     % breakpoint of type 5 just disappears

If this behaviour is not a bug: is there a way to set a breakpoint X
that produces ...X...X- / ...?

Cheers,
Sietse

% 2013-04-20
\definebreakpoints[aapje]
\definebreakpoint [aapje] [1] [nleft=3,nright=3,type=1]
\definebreakpoint [aapje] [2] [nleft=3,nright=3,type=2]
\definebreakpoint [aapje] [3] [nleft=3,nright=3,type=3]
\definebreakpoint [aapje] [4] [nleft=3,nright=3,type=4]
\definebreakpoint [aapje] [5] [nleft=3,nright=3,type=5]
\definebreakpoint [aapje] [6] [nleft=3,nright=3,left=X,middle=Y,right=Z]
\setbreakpoints[aapje]

\setuppapersize[A7]
\showframe

\starttext

\setupwhitespace[big]
aapje1aapje1aapje1aapje1aapje1aapje1aapje \par
aapje2aapje2aapje2aapje2aapje2aapje2aapje \par
aapje3aapje3aapje3aapje3aapje3aapje3aapje \par
aapje4aapje4aapje4aapje4aapje4aapje4aapje \par
aapje5aapje5aapje5aapje5aapje5aapje5aapje \par
aapje6aapje6aapje6aapje6aapje6aapje6aapje \par
\stoptext
___________________________________________________________________________________
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-20 20:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-20 20:05 Sietse Brouwer [this message]
2013-04-21  8:26 ` Wolfgang Schuster
2013-04-21 10:43   ` Hans Hagen
2013-04-21 17:27     ` Sietse Brouwer
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=dkzydSPw55jhrMN7Ntg6CLWQAyEMtToGPp96nbwLdzLxEZQ@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).