From: Giuseppe Bilotta <gip.bilotta@iol.it>
Subject: Re[2]: Status update on e-Omega/Aleph
Date: Wed, 10 Sep 2003 15:09:26 +0200 [thread overview]
Message-ID: <11617628107.20030910150926@iol.it> (raw)
In-Reply-To: <5.2.0.9.1.20030909184703.0286c558@localhost>
Tuesday, September 9, 2003 Hans Hagen wrote:
> At 09:45 09/09/2003 -0600, you wrote:
>> > * If my work is entirely in English, is there any benfit of Aleph for
>> > me?
>>
>>Sure. Consider, for example, the problem of
>>transliteration. You may want to
>>define a series of character mappings using otps to avoid using a lot of
>>control sequences for accents and the like. Let's say u have an accent "\.d"
>>that u use often for transliterating some sound. With an otp u can define
>>the character sequence ".d" so that it always gives you \.d in the output.
>>You can group your otp's so that they only take effect when delimited in
>>some predefined way, e.g. "<.d>"
>>
>>Suppose you want a character to behave as a control sequence but don't want
>>to make that character active. You can define a character in an otp so that
>>whenever you type it you get a particular control sequence.
>>
>>I'm sure there are other creative examples as well.
> i suggest that later this year idris/gb/me try to cook up a manual for that
> kind of thingies
The two ideas presented by Idris surprised me because I had
never thought about (ab)using OCPs these ways :) I'll see what
I can think of :)
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2003-09-10 13:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 14:43 Giuseppe Bilotta
2003-09-08 15:07 ` Bill McClain
2003-09-08 16:08 ` Re[2]: " Giuseppe Bilotta
2003-09-08 17:59 ` Simon Pepping
2003-09-08 23:06 ` Re[2]: " Giuseppe Bilotta
2003-09-09 15:45 ` Idris S Hamid
2003-09-09 16:49 ` Hans Hagen
2003-09-10 13:09 ` Giuseppe Bilotta [this message]
2003-09-09 18:20 ` Bill McClain
2003-09-09 20:59 ` Idris S Hamid
2003-09-09 21:24 ` Idris S Hamid
2003-09-10 23:09 ` Hans Hagen
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=11617628107.20030910150926@iol.it \
--to=gip.bilotta@iol.it \
--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).