From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/3561 Path: main.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: fonts in embedded tex in embedded metapost in context Date: Mon, 11 Dec 2000 01:15:53 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <3.0.6.32.20001211011553.018ccaf0@pop.wxs.nl> References: <3.0.6.32.20001208201424.015bd960@pop.wxs.nl> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1035394291 18132 80.91.224.250 (23 Oct 2002 17:31:31 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:31:31 +0000 (UTC) Cc: ntg-context@ntg.nl, roegel@lorraine.loria.fr (Denis B. Roegel) Original-To: "Denis B. Roegel" In-Reply-To: <200012082134.WAA29308@bar.loria.fr> Xref: main.gmane.org gmane.comp.tex.context:3561 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:3561 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 -------------------------------------------------------------------------