From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/1481 Path: main.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: Use-Encoding Date: Tue, 04 Jan 2000 09:39:18 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <3.0.6.32.20000104093918.01448100@pop.wxs.nl> References: <3870EEE9.C59CC03E@gmx.de> <3870EEE9.C59CC03E@gmx.de> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: main.gmane.org 1035392304 667 80.91.224.250 (23 Oct 2002 16:58:24 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 16:58:24 +0000 (UTC) Cc: ntg-context@ntg.nl Original-To: Taco Hoekwater In-Reply-To: <14449.47896.585243.805392@PC709.wkap.nl> Xref: main.gmane.org gmane.comp.tex.context:1481 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:1481 At 09:19 AM 1/4/2000 +0000, you wrote: >You need to use PostScript fonts (well, at least fonts in an 8-bit >encoding) for this to work. CMR doesn't have the needed characters Not in this case. In enco-win, only a regime is defined (mapping input encoding onto internal encoding, using active chars). I just tested it here and I get accented chars, (so, there's direct input encoding support, mapping char pos's onto font pos's and indirect regime support; sorry about the confusion, but this 4 dimensional input/font/language/dialect space is fuzzy anyhow; take a look at the chinese files, and you will see that even within an language there can be encoding dependencies). 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.nl -----------------------------------------------------------------