ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jack M. Lyon" <jack.lyon@comcast.net>
Subject: Hyphenation exception list
Date: Mon, 14 Feb 2005 14:07:41 -0700	[thread overview]
Message-ID: <000e01c512d9$3c174b90$cd050a0a@jlyond800> (raw)
In-Reply-To: <000a01c512d2$45e38d20$cd050a0a@jlyond800>

Dear ConTeXt experts:

I'm trying to create an external list of hyphenation exceptions.

I believe this command is what I need:

\hyphenation{ex-ample}

But I would like to make a whole list of these:

\hyphenation{ex-ample}
\hyphenation{disc-iple}
\hyphenation{woman}

And so on.

Then, I'd like to keep these in a separate file that I can call from any
ConTeXt document, something like this:

\input{hyphenlist}

When I try this, however (for a file named hyphenlist.text), I get this
error message:

! I can't find file `{hyph}'.
l.88 \input{hyph}
                 
Please type another input file name: Terminating on signal SIGBREAK(21)
>Exit code: -1073741510

Is there a way to implement such a hyphenation list?

Thanks so much for your help.

Best wishes,
Jack M. Lyon
___________________________________________________

The EDITORIUM
Microsoft Word Add-Ins for Publishing Professionals
http://www.editorium.com
___________________________________________________

  reply	other threads:[~2005-02-14 21:07 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-12 10:25 server down ? Steffen Wolfrum
2005-02-12 16:21 ` Taco Hoekwater
2005-02-12 16:35   ` Widows, flush bottom, and word breaks Jack M. Lyon
2005-02-12 18:46     ` Peter Münster
2005-02-12 19:33     ` Adam Lindsay
2005-02-12 21:08       ` Peter Münster
2005-02-12 23:25         ` Adam Lindsay
2005-02-13  0:43           ` Jack M. Lyon
2005-02-13 18:11             ` Adam Lindsay
2005-02-13  8:43           ` Peter Münster
2005-02-13 14:58             ` Jack M. Lyon
2005-02-14  8:11               ` Hans Hagen
2005-02-14  8:45             ` Hans Hagen
2005-02-14 16:24               ` Peter Münster
2005-02-14 17:50                 ` Hans Hagen
2005-02-14 19:15               ` Adam Lindsay
2005-02-14 20:17                 ` Jack M. Lyon
2005-02-14 21:07                   ` Jack M. Lyon [this message]
2005-02-14 21:40                     ` Hyphenation exception list Jack M. Lyon
2005-02-15 10:32                       ` Hans Hagen
2005-02-14 22:10                     ` Vit Zyka
2005-02-14 22:53                       ` Taco Hoekwater
2005-02-14 23:26                         ` Jack M. Lyon
2005-02-15 10:35                           ` Hans Hagen
2005-02-15 10:34                         ` Hans Hagen
2005-02-15 10:31                     ` Hans Hagen
2005-02-14 22:06                   ` Widows, flush bottom, and word breaks Jack M. Lyon
2005-02-15  7:57                   ` Hans Hagen
2005-02-15  7:56                 ` Hans Hagen
2005-02-13 12:51 ` server down ? h h extern
     [not found] <000801c51386$13a3e260$cd050a0a@jlyond800>
2005-02-15 17:53 ` Hyphenation exception list Hans Hagen
2005-02-15 18:43   ` Taco Hoekwater
2005-02-15 18:53     ` 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='000e01c512d9$3c174b90$cd050a0a@jlyond800' \
    --to=jack.lyon@comcast.net \
    --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).