From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: utf (8)
Date: Thu, 5 Dec 2002 14:39:58 +0100 [thread overview]
Message-ID: <20021205143958.23ed0e23.taco@elvenkind.com> (raw)
In-Reply-To: <5.1.0.14.1.20021205141709.0255e4f0@server-1>
> (4) we have Taco to extend tex to 32 bits -)
Yeah :)
Actually, my tex.pl toy version does something like this.
It uses [$commandcode,$charcode] as native perl integers, so you can have
31-bit chars and (2^31-325) control sequence names (in case you are wondering:
the first 325 are internal command codes)
--
groeten,
Taco
prev parent reply other threads:[~2002-12-05 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 11:02 Hans Hagen
2002-12-05 12:27 ` Taco Hoekwater
2002-12-05 12:44 ` Taco Hoekwater
2002-12-05 13:21 ` Hans Hagen
2002-12-05 13:39 ` Taco Hoekwater [this message]
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=20021205143958.23ed0e23.taco@elvenkind.com \
--to=taco@elvenkind.com \
--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).