ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: hyphenation not working
Date: Fri, 18 Mar 2005 10:26:28 +0100	[thread overview]
Message-ID: <423A9EC4.2020001@elvenkind.com> (raw)
In-Reply-To: <20050318060534.GA7676@localhost.localdomain>


See also this threade:

http://archive.contextgarden.net/message/20041228.225433.b0bd0faf.html

This is becoming a FAQ, unfortunately.

Greetings, Taco

Paul Tremblay wrote:
> Has anyone else had problems with hyphenation? I have a brand new
> version of ConTeXt, and cannot get one of its main features, hyphenation,
> to work. 
> 
> I looked at the documentation, specifically the file called hypenation
> patterns. According to this, I should be able to invoke a took called
> ctxtools, or at least a tool called texmfstart ctxtools. Neither tool
> exists with my distribution.
> 
> I do have a file called hyphen.tex. On Hans' suggestion, I copied this
> to ushyph1.tex and ushyph2.tex. That didn't help. I also  changed my cont-usr.tex file, changing all lines that had ushyp* to hyphen. This also didn't work.
> 
> I am at a loss, and I consider hyphenation pretty important. How do I
> proceed from here?
> 
> Thanks
> 
> Paul
> 

  parent reply	other threads:[~2005-03-18  9:26 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18  6:05 Paul Tremblay
2005-03-18  9:05 ` Hans Hagen
2005-03-18 21:08   ` Paul Tremblay
2005-03-18 21:55     ` Patrick Gundlach
2005-03-19  1:02       ` Paul Tremblay
2005-03-19 10:11         ` yet another mirror (was: hyphenation not working) Patrick Gundlach
2005-03-19 12:41           ` VnPenguin
2005-03-19 12:46             ` yet another mirror Taco Hoekwater
2005-03-19  1:01   ` hyphenation not working Paul Tremblay
2005-03-19  8:03     ` Taco Hoekwater
2005-03-19 15:16       ` Paul Tremblay
2005-03-19 15:26       ` Paul Tremblay
2005-03-19 15:37         ` Taco Hoekwater
2005-03-19 15:58           ` Paul Tremblay
2005-03-19 16:05             ` Adam Lindsay
2005-03-19 16:20               ` Paul Tremblay
2005-03-19 16:42                 ` Adam Lindsay
2005-03-19 17:05                   ` Paul Tremblay
2005-03-19 16:27             ` Taco Hoekwater
2005-03-19 17:02               ` Paul Tremblay
2005-03-19 17:56                 ` Patrick Gundlach
2005-03-19 21:39                   ` Paul Tremblay
2005-03-19 22:00                     ` Patrick Gundlach
2005-03-19 22:41                       ` Paul Tremblay
2005-03-19 22:47                         ` Patrick Gundlach
2005-03-19 11:17     ` how to place figures next to each other Peter
2005-03-20 22:35       ` Matthias Weber
2005-03-21 22:26         ` Peter
2005-03-20 12:18   ` hyphenation not working Christopher Creutzig
2005-03-18  9:26 ` Taco Hoekwater [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-16  5:16 Paul Tremblay
2005-03-16  9:03 ` Hans Hagen
2005-03-16 20:56   ` Paul Tremblay
2005-03-17  9:06     ` Hans Hagen
2005-03-17 22:52       ` Paul Tremblay
2005-03-18  8:56         ` Hans Hagen

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=423A9EC4.2020001@elvenkind.com \
    --to=taco@elvenkind.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).