From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl, roegel@lorraine.loria.fr (Denis B. Roegel)
Subject: Re: fonts in embedded tex in embedded metapost in context
Date: Tue, 12 Dec 2000 18:26:37 +0100 [thread overview]
Message-ID: <3.0.6.32.20001212182637.0156da50@pop.wxs.nl> (raw)
In-Reply-To: <200012112030.VAA22482@bar.loria.fr>
At 09:30 PM 12/11/00 +0100, Denis B. Roegel wrote:
>Presumably, the regime is similar to a mapping function
No, an encoding maps input or commands to a font char, a mapping takes care
of upper/lowercase handling, and a regime is a input char translation thing.
>(I checked the enco* files).
>What I would like to know is what regime I am supposed to use
>in the following cases:
>
> - input in il1 and cmr10 font
a regime, like [latin1] which will go into enco-lat but is not yet defined
> - input in il1 and ecrm1000 font
an encoding, this time [ec]
> - normal 7 bit input (such as \'e) and cmr10 font
nothing, works by default
> - normal 7 bit input (such as \'e) and ecrm1000 font
in this case, we need font-ecr i suppose, something like font-csr and
font-plr, this time with an il1 spec, or in tex world terms
encoding=ec
>Also, \enableencoding [il1] is not clear to me. What does it do?
>Does it merely make a bunch of characters active?
no, there is no il1, it's [ec]
You may make me a [latin1] regime fo you want.
imagine the steps for cmr:
composed(e,") -> regime[latin1] -> \"e -> composed tex char
\"e -> composed tex char
and for ecmr
composed(e,") -> encoding as triggered by font -> composed(e,")
\"e -> idem -> composed(e,")
[there is btw an aer font file that may suit your needs]
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE
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
-------------------------------------------------------------------------
next prev parent reply other threads:[~2000-12-12 17:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 16:37 Denis B. Roegel
2000-12-08 19:14 ` Hans Hagen
2000-12-08 21:34 ` Denis B. Roegel
2000-12-11 0:15 ` Hans Hagen
2000-12-11 20:30 ` Denis B. Roegel
2000-12-12 17:26 ` Hans Hagen [this message]
2000-12-28 3:11 ` another question on regimes and encoding Denis B. Roegel
2000-12-28 17:12 ` Hans Hagen
2000-12-28 23:24 ` Denis B. Roegel
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=3.0.6.32.20001212182637.0156da50@pop.wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=roegel@lorraine.loria.fr \
/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).