ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl, roegel@lorraine.loria.fr (Denis B. Roegel)
Subject: Re: another question on regimes and encoding
Date: Thu, 28 Dec 2000 18:12:07 +0100	[thread overview]
Message-ID: <3.0.6.32.20001228181207.013d0c10@pop.wxs.nl> (raw)
In-Reply-To: <200012280311.EAA09265@bar.loria.fr>

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: 

<active char 234> 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
-------------------------------------------------------------------------


  reply	other threads:[~2000-12-28 17:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-08 16:37 fonts in embedded tex in embedded metapost in context 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
2000-12-28  3:11           ` another question on regimes and encoding Denis B. Roegel
2000-12-28 17:12             ` Hans Hagen [this message]
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.20001228181207.013d0c10@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).