From: Berend de Boer <berend@pobox.com>
Subject: Re: Enable hyphenation or how to check it is enabled
Date: Wed, 16 Aug 2006 14:01:28 +1200 [thread overview]
Message-ID: <87y7tp4ex3.fsf@dellius.nederware.nl> (raw)
In-Reply-To: <CD506752-6F02-45C3-BED2-1A6053460DD9@uni-bonn.de> (Thomas A. Schmitz's message of "Tue, 15 Aug 2006 22:25:32 +0200")
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Thomas" == Thomas A Schmitz <thomas.schmitz@uni-bonn.de> writes:
Thomas> Easiest test would be to try some long and weird words
Thomas> with \hyphenatedword{transformational}
Thomas> in your source. If you get proper hyphens there, the
Thomas> problem must lie elsewhere.
I tried this:
\starttext
\hyphenatedword{transformational} \hyphenatedword{transformational}
\hyphenatedword{transformational} \hyphenatedword{transformational}
\hyphenatedword{transformational} \hyphenatedword{transformational}
\hyphenatedword{transformational} \hyphenatedword{transformational}
\stoptext
Overfull message, but no hyphens.
- --
All the best,
Berend de Boer
(PGP public key: http://www.pobox.com/~berend/berend-public-key.txt)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQFE4nx4IyuuaiRyjTYRAhfjAKDpVtVu5WYGc4RyUOyMxXhriTEbvACeJTXV
rMsVFrwylEU9s9ztVmQ+Lmc=
=9KLZ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-08-16 2:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 19:59 Berend de Boer
2006-08-15 20:25 ` Thomas A. Schmitz
2006-08-16 2:01 ` Berend de Boer [this message]
2006-08-16 6:22 ` Thomas A. Schmitz
2006-08-17 5:31 ` Berend de Boer
2006-08-16 8:36 ` Hans Hagen
2006-08-17 6:10 ` Berend de Boer
2006-08-17 7:42 ` Hans Hagen
2006-08-17 9:02 ` Berend de Boer
2006-08-17 11:29 ` Taco Hoekwater
2006-08-18 22:52 ` Berend de Boer
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=87y7tp4ex3.fsf@dellius.nederware.nl \
--to=berend@pobox.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).