Easiest test would be to try some long and weird words with
\hyphenatedword{transformational}
in your source. If you get proper hyphens there, the problem must lie
elsewhere.
Best
Thomas
On Aug 15, 2006, at 9:59 PM, Berend de Boer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi All,
>
> I've a weird problem: it just looks like hyphenation is disabled for
> my English documents, at least I don't see hyphenation happening at
> all. Do I have to enable it explicitly?
>
> This is some US english text. I've specified:
>
> \language[us]
>
> at the top of my file.
>
> I'm using the latest ConTeXt, 2006-08-08.
>
>
> It looks like they get loaded when I generate the format:
>
> language : no patterns en for en (n=1,e=ec,m=ec) (lang-
> en.pat,ukhyph.tex
> )
> language : hyphenations en for en loaded (n=1,e=ec,m=ec)
> (/usr/TeX/texmf/tex/context/patterns/lang-us.hyp))
> language : patterns en for en loaded (n=1,e=*,m=*)
> language : hyphenations en for en loaded (n=1,e=*,m=*)
> language : no patterns uk for uk (n=2,e=ec,m=ec) (lang-
> uk.pat,ukhyph.tex
> )
> language : hyphenations uk for uk loaded (n=2,e=ec,m=ec)
>
>
> I've tried to specify
>
> \setupalign
> [hyphenated]
>
> but that does not seem to help.
>
> Any test I can run to see that hyphenation is actually enabled?
>
> - --
> 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/>
>
> iD8DBQFE4ieUIyuuaiRyjTYRAkFwAJ0QYn4VnHW2T1H0QxHVAcCHXWJE4QCcCz3e
> qVB8X/MCve7ZeKnQY4zjh24=
> =vrqm
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> ntg-context mailing list
> [email protected]
> http://www.ntg.nl/mailman/listinfo/ntg-context
_______________________________________________
ntg-context mailing list
[email protected]
http://www.ntg.nl/mailman/listinfo/ntg-context
