From erik@sran8.sra.co.jp Wed Jan 22 01:12:05 1992
Received: from mcsun.EU.net by dkuug.dk via EUnet with SMTP (5.64+/8+bit/IDA-1.2.8)
	id AA14405; Wed, 22 Jan 92 01:12:05 +0100
Received: from srawgw.sra.co.jp by mcsun.EU.net with SMTP;
	id AA16707 (5.65a/CWI-2.134); Wed, 22 Jan 1992 01:12:08 +0100
Received: from sranha.sra.co.jp by srawgw.sra.co.jp (5.64WH/1.4)
	id AA08485; Wed, 22 Jan 92 09:11:48 +0859
Received: from sran8.sra.co.jp by sranha.sra.co.jp (5.64dw/6.4J.6-BJW)
	id AA15263; Wed, 22 Jan 92 09:11:26 +0900
Received: from localhost by sran8.sra.co.jp (4.0/6.4J.6-SJX)
	id AA19882; Wed, 22 Jan 92 09:11:18 JST
Return-Path: <erik@sran8.sra.co.jp>
Message-Id: <9201220011.AA19882@sran8.sra.co.jp>
Reply-To: erik@sra.co.jp
From: erik@sra.co.jp (Erik M. van der Poel)
To: i18n@dkuug.dk
Subject: Re: support for symbolic names
Date: Wed, 22 Jan 92 09:11:12 +0900
Sender: erik@sran8.sra.co.jp
X-Charset: ASCII
X-Char-Esc: 29

> My assumption has been that this discussion is about portability of
> the localized programs....
> 
> If we are talking about internationalized program, neither
> '<540404>' nor LOWER_O_SLASH should appear in it.  Only characters
> that can appear in the internationalized program are from
> the basic character set.  If you have LOWER_O_SLASH in your
> program, the program is not global. It is limited to the execution
> environment where such a character is available.

Imagine a super-internationalized email composer. I want to write mail
to Keld Jo/rn Simonsen, and I want to type the o-slash "properly". I
bring up the character menu, and select o-slash. Voila`, o-slash at
your service.

Of course, we will need better email standards (these are being worked
on as we speak), making use of such ISO standards as 10646 (if it ever
materializes) or even 2022 (already fully established in some
countries). The "availability of a character in an execution
environment" reduces to either the availability of such a font or the
availability of memory to load such a font.


Cheers,
Erik