From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/1489 Path: main.gmane.org!not-for-mail From: Tobias Burnus Newsgroups: gmane.comp.tex.context Subject: Re: Use-Encoding Date: Tue, 04 Jan 2000 18:29:44 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <38722E08.2C44C7E1@gmx.de> References: <3870EEE9.C59CC03E@gmx.de> <3.0.6.32.20000104093918.01448100@pop.wxs.nl> <14449.52403.202079.307256@PC709.wkap.nl> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035392311 708 80.91.224.250 (23 Oct 2002 16:58:31 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 16:58:31 +0000 (UTC) Cc: ntg-context@ntg.nl Original-To: Taco Hoekwater Xref: main.gmane.org gmane.comp.tex.context:1489 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:1489 Hi Taco, > Hm. In that case: perhaps you are using a tcx file and/or something > else that changes the catcodes of the 8-bit chars back into 'letter'? > enco-win sets then to \active, just like ~. No, but: > If Hans doesnt have the problem (neither have I, btw), then probably > it makes sense to update your context distrib first, just in case. This was using the beta Hans mentioned. Using the new 2000 version, the problem went away (see my mail from yesterday, 20:42 CET). Tobias