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: Mon, 11 Dec 2000 01:15:53 +0100 [thread overview]
Message-ID: <3.0.6.32.20001211011553.018ccaf0@pop.wxs.nl> (raw)
In-Reply-To: <200012082134.WAA29308@bar.loria.fr>
At 10:34 PM 12/8/00 +0100, Denis B. Roegel wrote:
>\starttext
>\startMPenvironment
>\ss
>\enableencoding [il1]
>\stopMPenvironment
>\startuseMPgraphic{test}
>label(btex élève etex,origin);
>\stopuseMPgraphic
>\useMPgraphic{test}
>\stoptext
>
>and it doesn't display ``é'' and ``è''.
>
>When I look at the mpx file, I see
>
>begingroup save _p,_r,_s,_n; picture _p; _p=nullpicture;
>string _n[];
>vardef _s(expr _t,_f,_m,_x,_y)=
> addto _p also _t infont _f scaled _m shifted (_x,_y); enddef;
>_n0="cmss12";
>_s("lve",_n0,1.00000,0.0000,0.0000);
>setbounds _p to (0,0.0000)--(13.3110,0.0000)--
> (13.3110,8.3022)--(0,8.3022)--cycle;
>_p endgroup
>mpxbreak
>
>so presumably, the problem is cmss12.
>
>Can you explain how ``é'' is handled? In LaTeX,
>é becomes \'e (with the input encoding latin1) and
>this is translated into some position in the font,
>or some combination of characters. With cmss12, LaTeX
>would map \'e to some \accent combination.
>
>What is the context position on this matter?
\'e is mapped onto a glyph when present, or composed, like in cmr when not
the same goes for é but here it can either be a direct mapping on a glyph
or an active character expanding into \'e and thereby mapped onto a glyph
or composed char
so anything can be the case:
\command char => accented glyph
\command char => accent + glyph
char => accented glyph [with same code]
active char => accented glyph
active char => accent + glyph
the
\command char mapping is called an encoding
direct mapping is just direct mapping
active char mapping is called a regime
[there is also unicode mapping with intermediate remapping as well as pdf
remapping at the output level]
So, when you need for cmr, since there are no direct glyphs, is either \'e
or a regime that makes the il1 chars into active chars and maps them.
You may try:
\enableregime[win]
\enableregime[ibm]
or whatever matches il1, else we need to make one. [see enco-win for an
example]
A regime is enabled in the document and an encoding is either enables in
the document or assiciated with a font file name.
Ah, and there are also special character sequences [grep for
languagespecifics] which map for instance "e onto \"e onto
glyph/accent+char. This is for instance used in germany.
So, the machinery [and in many cases the fuel too] is there.
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-11 0:15 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 [this message]
2000-12-11 20:30 ` Denis B. Roegel
2000-12-12 17:26 ` Hans Hagen
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.20001211011553.018ccaf0@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).