ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: "ntg-context" <ntg-context@ntg.nl>
Subject: Re: Umlaute ...
Date: Mon, 10 Sep 2001 23:34:09 +0200	[thread overview]
Message-ID: <5.1.0.14.1.20010910232505.022d97e8@server-1> (raw)
In-Reply-To: <001501c13944$0ee91440$0100a8c0@xs4all.nl>

At 05:22 PM 9/9/2001 +0200, Willi Egger wrote:
>Hi all,
>
>Since I am using CONTEXT Icoded all files with accented characters in the
>following way:
>
>    \'e or \"a ....
>
>Since the indtroduction of the new font mechaninsm however I get errors in
>the pdf-files, ending up with empty pages.
>
>If I write text where the accented characters are placed like this:
>
>    ï, ä, ë
>
>then I have no problems.
>
>The mentioned problem occurs with texnansi and ec encoded fonts like
>Palatino.
>
>Is there anybody who already had this and can give me a tip how to solve it?

This is strange since \"e becomes \eumlaut and this is mapped onto a glyph 
number; are you sure that pdftex does not report a missing map file?

for fonts you need:

(1) tfm/vf files
(2) type1 (pfb) files
(3) a map file
(4) to let context know what input/output encoding you use

when using fonts that match your key codes it may go well without noticing 
that in fact the system is set up wrong [this is i thing one reason for 
frequent errors in files

So, try to determine what happens with 1-4; especially (3) is organized 
rather messy in tex distributions due to incompatibilities in map files 
between dvips and pdftex and dvipdfm [currently texfont handles pdftex and 
i will handle the others later]

It can be very illustrative to say \showfont[Serif] so that you get an idea 
what font is used in what encoding. One reason to change context's defaults 
to more verbose low level font names is to catch problems like this.

[in a couple of days you may test the next beta, which is now fully 'new 
name' aware and [when set up ok] handles all map files itself. in that case 
you can generate all metrics you need for a specific encoding with one command]

[there are some remaining problems that i want to discuss with thanh first]

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


      reply	other threads:[~2001-09-10 21:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-09 15:22 Umlaute Willi Egger
2001-09-10 21:34 ` Hans Hagen [this message]

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=5.1.0.14.1.20010910232505.022d97e8@server-1 \
    --to=pragma@wxs.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).