-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Thomas" == Thomas A Schmitz <[EMAIL PROTECTED]> 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-----
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
