From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/293
Path: main.gmane.org!not-for-mail
From: Taco Hoekwater <taco.hoekwater@wkap.nl>
Newsgroups: gmane.comp.tex.context
Subject: Re: Latest ConTeXt: No umlauts :-(
Date: Tue, 02 Feb 1999 13:24:15 +0000 (/etc/localtime)
Sender: owner-ntg-context@let.uu.nl
Message-ID: <14006.64639.337138.577801@localhost>
References: <36B44A8D.F6CC095E@gmx.de> <36B4EBD6.4545709@wxs.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 1035391156 22798 80.91.224.250 (23 Oct 2002 16:39:16 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Wed, 23 Oct 2002 16:39:16 +0000 (UTC)
Cc: ntg-context@ntg.nl
Original-To: fg@fgbbs.iaf.nl (Frans Goddijn)
Xref: main.gmane.org gmane.comp.tex.context:293
X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:293

>>>>> "Frans" == Frans Goddijn <fg@fgbbs.iaf.nl> writes:

    Frans> I had a little puzzling problem myself compiling a large
    Frans> doc with the newer ConTeXt/PDFtex. All seemed fine but the
    Frans> dutch word 'slotscene' with an accent grave on the first e
    Frans> showed, in the PDF file, a capital S with an inverted
    Frans> circonflexe ^ on top of it...

This depends on the enco-* file you have loaded into context. 

For Frans (dos/os2 terminal), this should be enco-ibm.tex which maps
the character that is present at location 138 of the ibm terminal font
into the equivalent of \`{e}. Result: it looks like /egrave on screen
and compiles as /egrave in context.

For windows/unix users, the character that is displayed as /egrave is
in location 0xE8 (decimal 232). The enco-win.tex file does the
conversion in this case. This one maps 232 into \`{e}, while 138
becomes \v{S}. 

So, Frans is loading the wrong file, probably because of changes to
context in the recent months. Try starting your document with

		\useencoding[ibm]

Greetings, Taco