From: Jens-Uwe Morawski <morawski@gmx.net>
Subject: Re: Fonts: ConTeXt+MikTeX
Date: Wed, 31 Jul 2002 10:42:51 +0200 [thread overview]
Message-ID: <20020731104251.6f62bd15.morawski@gmx.net> (raw)
In-Reply-To: <p05100302b96cab8b9778@[172.16.22.38]>
On Tue, 30 Jul 2002 22:48:28 +0200
Axel Rose <rose@sj.com> wrote:
> Thank you Hraban for making things clearer.
>
> though here:
>
> > > \setupencoding[default=ec]
> >
> >this tells ConTeXt to use ec (alias 8a?) encoded fonts as default;
not 8a. 8a is Adobe standard encoding, the encoding of the AFMs.
8r is a (strange) raw encoding, used by fontinst to build on top
of them virtual fonts. ec (aka T1) is 8t encoding.
> >you can try texnansi, 8r or some east european encs, if some special
> >chars (accented) doesn't show up.
>
> I'd like to get more information about which encoding to use when.
> Anybody?
TeX uses TFMs in order to access a font. The encoding of these TFMs
you have to know, since it depends on your font installation. IMO
there are only 2 useful encodings: ec (aka T1 aka 8t) and texnansi.
texnansi (aka LY1) is employed by texfont.pl. Thus i would call it the
ConTeXt default/prefered encoding. But ec and texnansi are not that
different. I see no advantage to prefer one of them.
I personally prefer ec, but that is not an encoding but more a
time issue. When i install fonts i often have to install it for
ConTeXt and LaTeX as well. With fontinst i get very easily
the LaTeX set-up. Then the only thing to do for ConTeXt is writing
a typescript.
jm2c
Jens
next prev parent reply other threads:[~2002-07-31 8:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 15:35 ConTeXt font messages Marc
2002-07-29 17:49 ` Bill McClain
2002-07-30 10:23 ` Fonts: ConTeXt+MikTeX mari.voipio
2002-07-30 19:11 ` Henning Hraban Ramm
2002-07-30 20:48 ` Axel Rose
2002-07-31 8:42 ` Jens-Uwe Morawski [this message]
[not found] ` <Pine.OSF.4.30.0207301304090.16709-100000@sirppi.helsinki.f i>
2002-07-30 21:22 ` Hans Hagen
2002-07-30 21:26 ` ConTeXt font messages Hans Hagen
2002-07-30 8:55 ` Eckhart Guthöhrlein
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=20020731104251.6f62bd15.morawski@gmx.net \
--to=morawski@gmx.net \
/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).