ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas Floeren" <thomas.floeren@boschung.com>
To: "'Taco Hoekwater'" <taco@elvenkind.com>,
	"'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: Hyphenation list and umlauts
Date: Wed, 8 Jul 2009 12:15:36 +0200	[thread overview]
Message-ID: <002f01c9ffb5$09c86020$8614a8c0@boschung.local> (raw)
In-Reply-To: <4A422B42.3030500@elvenkind.com>

Taco Hoekwater <mailto:taco@elvenkind.com> scribbled on Wednesday, June 24, 2009 3:34 PM:

> Thomas Floeren wrote:
>> Hi,
>> 
>> I stumbled upon a problem with my hyphenation list:
>> 
>> In MKIV, all the words in the list that contain umlauts are
>> completely ignored. MKII is fine. 
> 
> Luatex 0.40.5 is broken in this regard, sorry.
> 
> (The problem is that the exception handling uses \lccodes
> for the *byte* range 128-255, which is quite wrong). This is
> serious enough that there will be a 0.40.6 later in the week.
> 
> Best wishes,
> Taco



Well, in my other mail I said that it worked perfectly now with 0.40.6, but this isn’t entirely true:

It works perfectly on Mac, Linux and Win Vista. But for any obscure reason I can not get it to work on Win XP (to which I’m bound at work, unfortunately).

Linux and WinVista are running as virtual machines on Mac Intel systems, WinXP is running nonvirtually on PC. 

In order to minimize installation differences I have even copied the entire context folder from Vista to the XP machine (including binaries, minimals, texmf-local), trashed the caches, remade the formats ... but still no UTF hyphenation exceptions on the XP-PC.

Do you - or anybody - have an idea of what the reason for this could be?
Some stupid small thing that I have overlooked?


Any help is appreciated
Thanks

Thomas

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2009-07-08 10:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 13:28 Thomas Floeren
2009-06-24 13:33 ` Taco Hoekwater
2009-06-27 20:53   ` Thomas Floeren
2009-07-08 10:15   ` Thomas Floeren [this message]
2009-07-08 10:25     ` Taco Hoekwater
2009-07-08 11:06     ` Peter Rolf
2009-07-08 18:22       ` tomfloeren
2009-07-08 18:37       ` thomas.floeren
2009-07-09  4:55         ` Lutz Haseloff
2009-07-09  6:10           ` Thomas Floeren
2009-07-09  6:29             ` Lutz Haseloff
2009-07-09  6:39               ` Taco Hoekwater
2009-07-09  7:43                 ` Thomas Floeren
2009-07-09  8:48                 ` Lutz Haseloff
2009-07-09 10:56                   ` Peter Rolf
2009-07-10  5:32                 ` Thomas Floeren
2009-07-10  6:33                   ` Taco Hoekwater
2009-07-10  9:21                   ` Mojca Miklavec
2009-07-10 16:51                     ` tomfloeren
2009-07-16  6:55                     ` Thomas Floeren

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='002f01c9ffb5$09c86020$8614a8c0@boschung.local' \
    --to=thomas.floeren@boschung.com \
    --cc=ntg-context@ntg.nl \
    --cc=taco@elvenkind.com \
    /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).