ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Simon Pepping <spepping@scaprea.hobby.nl>
Subject: Re: DocBookInContext & multi-languages (newbie) / utf
Date: Mon, 2 Dec 2002 21:16:53 +0100	[thread overview]
Message-ID: <20021202201653.GA1924@scaprea> (raw)
In-Reply-To: <20021202174029.GA24554@mail.inet.hr>

Hmm, I just wrote my email before fetching the emails that had been
exchanged over the weekend. Not a good idea.

On Mon, Dec 02, 2002 at 06:40:30PM +0100, Gour wrote:
> Hans Hagen (pragma@wxs.nl) wrote:
> 
> > >a) c4 81 -> amacron
> > >b) 0101  -> amacron
> > 
> > so, c4 is the trigger, and 81 the character; this means that the function 
> > attached to c4 has to map the 81 onto \amacron
> 
> I'm not sure whether c4 is the trigger for the 81 character.
> 
> c4 81 is two-byte representation in memory (that's what you'll see in some
> hexadecimal editor) of Unicode amacron character with the code U+0101, or
> simply said: utf-8 code for amacron :-)
>   
> > can you make me a file with a list like:
> > 
> > amacron : 01/01 : c4/c8 : <utfcode>
> > ^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^
> > normal ascii              real utf
> 
> So, the line for amacron should look like:
> 
> amacron	:	01/01	c4/c8
> 
> since c4/c8 is utfcode for amacron.
> 
> Is this OK?

I do not think the mapping files should touch utf-8. The input
mechanism should map utf-8 to unicode, and then the mapping should map
unicode to a macro. In that way the same mapping can be used by other
encodings, provided they have an input mapping to unicode.

Simon

-- 
Simon Pepping
email: spepping@scaprea.hobby.nl

  reply	other threads:[~2002-12-02 20:16 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-29  7:20 DocBookInContext & multi-languages (newbie) Gour
2002-11-29 19:18 ` Simon Pepping
2002-11-30 20:15   ` Gour
2002-11-30 20:55     ` Bruce D'Arcus
2002-12-01  6:40       ` Gour
2002-12-02 19:46     ` Simon Pepping
2002-12-02 20:30       ` Tobias Burnus
2002-12-02 21:54       ` Hans Hagen
     [not found]       ` <Pine.LNX.4.44.0212022106550.2205-100000@tom.physik.fu-berl in.de>
2002-12-02 21:59         ` Hans Hagen
2002-12-03 12:48           ` Tobias Burnus
2002-12-03 13:59             ` Willi Egger
     [not found]           ` <Pine.LNX.4.44.0212031306170.23965-100000@warp9.physik.fu-b erlin.de>
2002-12-03 13:45             ` Hans Hagen
2002-12-02 12:28   ` DocBookInContext & multi-languages (newbie) / utf Hans Hagen
2002-12-02 13:59     ` Gour
2002-12-02 14:43       ` Hans Hagen
2002-12-02 16:36         ` Taco Hoekwater
2002-12-02 17:40         ` Gour
2002-12-02 20:16           ` Simon Pepping [this message]
2002-12-02 21:57             ` Hans Hagen
2002-12-03 20:03               ` Simon Pepping
2002-12-03 23:31                 ` Hans Hagen
2002-12-04 14:10                   ` Gour
2002-12-04 16:31                     ` Hans Hagen
2002-12-04 20:08                       ` Gour
2002-12-05  0:10                         ` multi-languages [UTF-8 Roman and UTF-8 Nagari test files] Richard Mahoney
2002-12-05 11:58                         ` DocBookInContext & multi-languages (newbie) / utf Hans Hagen
2002-12-05 12:22                           ` Taco Hoekwater
2002-12-05 13:25                             ` Hans Hagen
2002-12-05 14:03                           ` Tobias Burnus
2002-12-05 19:09                           ` Create Type 1 fonts with Indological diacritics and UTF-8 TTF Richard Mahoney
2002-12-06 14:10                             ` Hans Hagen
2002-12-06 15:22                               ` Docu set Michael Hallgren
2002-12-07 14:12                                 ` Patrick Gundlach
2002-12-07 17:37                                   ` Michael Hallgren
2002-12-06 15:36                               ` Re: Create Type 1 fonts with Indological diacritics and UTF-8 TTF Gour
2002-12-06 16:47                                 ` Hans Hagen
2002-12-03 19:14           ` DocBookInContext ... [CSX+, UTF-8 Roman, and Nagari Codings] Richard Mahoney
2002-12-04 14:16             ` Gour

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=20021202201653.GA1924@scaprea \
    --to=spepping@scaprea.hobby.nl \
    --cc=ntg-context@ntg.nl \
    /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).