From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/3691 Path: main.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: another question on regimes and encoding Date: Thu, 28 Dec 2000 18:12:07 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <3.0.6.32.20001228181207.013d0c10@pop.wxs.nl> References: <3.0.6.32.20001212182637.0156da50@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 1035394416 19336 80.91.224.250 (23 Oct 2002 17:33:36 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:33:36 +0000 (UTC) Cc: ntg-context@ntg.nl, roegel@lorraine.loria.fr (Denis B. Roegel) Original-To: "Denis B. Roegel" In-Reply-To: <200012280311.EAA09265@bar.loria.fr> Xref: main.gmane.org gmane.comp.tex.context:3691 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:3691 At 04:11 AM 12/28/00 +0100, Denis B. Roegel wrote: >That's a late reply to your message of December 12. > >`Hans Hagen' wrote >> >... >> 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,") > >One more question: if I wanted ``ë'' to be mapped on ``é'' in ecrm1000, >I would presumably > >\enableencoding[ec] since I am using ecrm1000 > >\enableregime[mystrangeregime] > > (where enco-mystrangeregime.tex would contain > > \defineactivecharacter ë {\'e} > ) > >Is that right? Right. Like enco-win, enco-ibm and enco-lat. But, if you can wait for a few more days, it's there for you. I'm currently redefining some encoding vectors so that we can more easilly remap to unicode which is needed for pdf resources [especially for our central european friends]. The endings will now look like: \startencoding [ec] \definecharacter eacute 234 \stopencoding and in this case \startencoding [ec][ec] will also produce the regime codes. It means that inside context \eacute will more around as fully expandable something. This is not that different from the current approach but more readable. All chars will be accessible that way, independ of their encoding. So, in your case: regimes onto <\somechar> encodes onto [\char234 uchar{1}{123} ...] etc, depending on the setting. I still have to sort out a few guillemot things and so. There will also be tracing features and one can generate tables that show if a char is a composed one [accent/pseudo accent] or a direct one. It will be a group effort to get the vectors complete since i don't know all chars [so i may have missed a few] and i want fall backs for all cases. 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 -------------------------------------------------------------------------