ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: hyphenation mess
Date: Wed, 02 Feb 2005 13:41:08 +0100	[thread overview]
Message-ID: <4200CA64.8050204@wxs.nl> (raw)

Hi,

When generating new minimal trees, i found out that the us patterns are now 
again in hyphen.tex and the uk patterns also got a new name. It is a that the 
naming of pattern files is a mess, and that some pattern files are not in the 
right spot, and things are not improving. The fact that this is solved with the 
fuzzy aliasses mechanism in web2c does not help, since this is implementation 
dependent and makes the texmf tree not sharable.

I'll try to catch the new names in the next version, and in the meantime start 
wondering if it makes sense to add consistently names and structured hyphenation 
files to the context distribution.

[similar things are happening with fonts and related enc files; the next release 
of context [alpha first] will be pure latin modern based and my guess is that it 
will take a while till lm support migrates into distributions, so i will put a 
zip with the font files needed alongside the context zip]

Hans

-----------------------------------------------------------------
                                           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
-----------------------------------------------------------------

             reply	other threads:[~2005-02-02 12:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02 12:41 Hans Hagen [this message]
2005-02-02 13:03 ` Taco Hoekwater
2005-02-02 13:30 ` Willi Egger

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=4200CA64.8050204@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).