From: Hans Hagen <pragma@wxs.nl>
Subject: Re: error with \hyphenation after update
Date: Sun, 30 Apr 2006 15:25:52 +0200 [thread overview]
Message-ID: <4454BAE0.7020209@wxs.nl> (raw)
In-Reply-To: <Pine.LNX.4.58.0604292149310.12637@gaston.pm>
� wrote:
> Hello,
> this used to work about 3 weeks ago. With version 2006.04.27, I get an
> error:
>
> \enableregime[il1]
> \hyphenation{Di-sul-fid-br�cken}
> \starttext
> Error: \type{Improper \hyphenation will be flushed.}
> \stoptext
>
> Could you help please?
>
is regi- iso-8859-1.tex loaded?
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2006-04-30 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-30 7:15 Peter Münster
2006-04-30 13:14 ` Hans Hagen
2006-04-30 13:25 ` Hans Hagen [this message]
2006-04-30 14:27 ` Hans Hagen
2006-04-30 17:33 ` Peter Münster
2006-04-30 19:17 ` Volker RW Schaa
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=4454BAE0.7020209@wxs.nl \
--to=pragma@wxs.nl \
--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).