From: Taco Hoekwater <taco.hoekwater@wkap.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Latest ConTeXt: No umlauts :-(
Date: Tue, 02 Feb 1999 13:24:15 +0000 (/etc/localtime) [thread overview]
Message-ID: <14006.64639.337138.577801@localhost> (raw)
In-Reply-To: <36B4EBD6.4545709@wxs.nl>
>>>>> "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
next prev parent reply other threads:[~1999-02-02 13:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <36B44A8D.F6CC095E@gmx.de>
1999-01-31 23:48 ` Hans Hagen
1999-02-02 11:54 ` Frans Goddijn
1999-02-02 14:08 ` Hans Hagen
1999-02-03 12:01 ` Frans Goddijn
1999-02-03 13:25 ` Hans Hagen
1999-02-02 13:24 ` Taco Hoekwater [this message]
1999-02-02 14:11 ` Hans Hagen
1999-02-02 17:07 ` Frans Goddijn
1999-02-03 9:22 ` Taco Hoekwater
1999-02-03 13:47 ` Taco Hoekwater
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=14006.64639.337138.577801@localhost \
--to=taco.hoekwater@wkap.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).