Reply to: RE>>Response 01/25/94 8:28 AM
Mark Davis who said that the intention of MIME was to identify DIS 1 as the
charset
I am afraid that I view the whole direction of this discussion as pointless;
there are many different approaches that one could take to the development of
any standard; there will always be people who are discontented with the
results, whatever they are. I have no desire to endlessly debate what could
have been.
However, I do need to respond when I see my name used. You have misunderstood
me; I have no longings whatsoever for DIS 1. There were a host of working
drafts, national contributions, individual contributions, draft proposals, and
draft international standards in the process of producing IS 10646. They are
now just history; it is the IS that has been approved and is being
implemented.
Mark Davis
P.S.
As I already know that I can't display Japanese text with UNICODE without
some profiling information, you don't have to do so.
BTW, Unicode includes the full repertoire, code for code, of JIS 208 and 212,
as well as codes for compatibility with shift-JIS. It is not very productive
to continue without your having read and understood the Unicode standard (V1,
V2 and TR#4).
--------------------------------------
Date: 01/24/94 8:33 PM
To: Mark Davis
From: Masataka Ohta
From: Masataka Ohta
<mohta(_at_)necom830(_dot_)cc(_dot_)titech(_dot_)ac(_dot_)jp>
Date: Mon, 24 Jan 94 15:42:20 JST
Have we agreed that ISO 10646 needs some profiling to be a MIME charset?
No, it does not need profiling to be used by MIME. If it does, then
ASCII does too.
I'm afraid that you don't understand the fact that *no* character
set specifies the precise details of the graphical expression of the
text.
Anyway, you should read RFC 1555.
10646 here means DIS 10646-1.0 which is much better than the current IS.
Excuse me, but what purpose does it serve to keep recalling DIS 1?
Ask Mark Davis who said that the intention of MIME was to identify
DIS 1 as the charset.
It is dead and buried.
So bury Mark's longing with it.
> (Unicode provides an detailed algorithm for determining presentation
> order of 10646 characters within a line or paragraph--even in the
> absence of presentation format codes.
I have never seen any detailed algorithm in Uncode books.
Where is it described?
Well, it may not be your idea of "detailed", but Appendix A in volume I,
along with corrections in Appendix D of volume II and erratta in TR #4
define an algorithm, which, if you possess only an average amount of
cleverness, will allow you to implement the Unicode BIDI algorithm in
real code without any problems. Of course, it would help if you knew
something about Arabic or Hebrew too; so perhaps it will be a bit more
difficult for you.
Do you want to convince me that some necessary profiling information
for 10646 is provided by Unicode?
As I already know that I can't display Japanese text with UNICODE without
some profiling information, you don't have to do so.
Masataka Ohta
------------------ RFC822 Header Follows ------------------
Received: by qm.taligent.com with SMTP;24 Jan 1994 20:33:03 -0800
Received: from UNICODE.ORG by taligent.com with SMTP (5.67/23-Oct-1991-eef)
id AA26934; Mon, 24 Jan 94 20:29:49 -0800
for
Received: from necom830.cc.titech.ac.jp by Unicode.ORG (NX5.67c/NX3.0M)
id AA24750; Mon, 24 Jan 94 20:01:30 -0800
Received: by necom830.cc.titech.ac.jp (5.65+/necom-mx-rg); Tue, 25 Jan 94
13:09:53 +0859
From: Masataka Ohta
<mohta(_at_)necom830(_dot_)cc(_dot_)titech(_dot_)ac(_dot_)jp>
Return-Path: <mohta(_at_)necom830(_dot_)cc(_dot_)titech(_dot_)ac(_dot_)jp>
Message-Id:
<9401250410(_dot_)AA15763(_at_)necom830(_dot_)cc(_dot_)titech(_dot_)ac(_dot_)jp>
Subject: Re: Response
To: glenn(_at_)metis(_dot_)com (Glenn Adams)
Date: Tue, 25 Jan 94 13:09:52 JST
Cc: ietf-822(_at_)dimacs(_dot_)rutgers(_dot_)edu,
unicored(_at_)Unicode(_dot_)ORG
In-Reply-To: <9401241637(_dot_)AA06999(_at_)trubetzkoy(_dot_)metis(_dot_)com>;
from "Glenn Adams" at
Jan 24, 94 11:37 am
X-Mailer: ELM [version 2.3 PL11]