From michka@trigeminal.com  Tue Feb  5 14:27:54 2002
Received: by suse.blue-edge-tech.com id g155RsI16226; Tue, 5 Feb 2002 14:27:54 +0900
Delivered-To: yuditorg-gsinai@yudit.org
Received: from mail.yudit.org [206.245.164.55]
	by localhost with POP3 (fetchmail-5.9.6)
	for gsinai@localhost (single-drop); Tue, 05 Feb 2002 14:27:54 +0900 (JST)
Received: (qmail 12060 invoked from network); 5 Feb 2002 05:00:32 -0000
Received: from smarthost.microsoft.com (HELO smarthost.redmond.corp.microsoft.com) (131.107.3.106)
  by mailserv2.iuinc.com with SMTP; 5 Feb 2002 05:00:32 -0000
Received: from vmichka3 ([172.30.84.61]) by smarthost.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 4 Feb 2002 21:00:18 -0800
Message-ID: <004801c1ae02$095fb780$13a52640@redmond.corp.microsoft.com>
From: "Michael \(michka\) Kaplan" <michka@trigeminal.com>
To: "Gaspar Sinai" <gsinai@yudit.org>
Cc: "Unicode List" <unicode@unicode.org>
References: <Pine.LNX.4.44.0202051236420.13325-100000@suse.blue-edge-tech.com>
Subject: Re: Unicode and Security
Date: Mon, 4 Feb 2002 21:00:30 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 5
X-MSMail-Priority: Low
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime: 05 Feb 2002 05:00:19.0012 (UTC) FILETIME=[0204C840:01C1AE02]
Status: RO
X-Status: 
X-Keywords:                 

From: "Gaspar Sinai" <gsinai@yudit.org>

> If the standard wants me to confuse the user, I would
> rather dump the standard than comply.

Well, don't let the door hit you in the a** on the way out?

Te users will be less confused than you realize -- only people who walk in
with agendas see the flaws you claim.

> Talking about characters: I think  bi-di should not be in
> Unicode  Standard because it is not a character.
> It is an algorithm.

And it is documented as such.

Clearly what you want of Unicode does not match what it actually is -- when
my wife and I realized such about each other, she became my ex-wife. Since
that is your goal here, I guess your "divorce" from Unicode should not be a
surprise?

<snip out of order>

> Thank you for mentioning Yudit - I don't need
> advertisement, there are enough users.

Perhaps some will leave if you are honest about your "divorce" though -- you
might be surprised how many people follow the standard?

> I also start think this thread is a waste of time.
> This thread won't solve the our problem.

The only issue though is that we do not have a problem, here?

> I feel sorry for interrupting in the "Let's praise and
> celebrate Unicode" mood of this mailing list.

Sorry, thats not the mood of the list. But in order to have a healthy
respect for the people who give sound and reasonable arguments, we must show
a matching lack of respect for those who give specious arguments.

> I updated:
> http://www.yudit.org/security/
> I wanted to remove it after solving the problem, but
> it seems that this page will stay.

The problem is solved, though. The real problem at this point can be found
at
http://www.yudit.org/gaspar/ though.


MichKa

Michael Kaplan
Trigeminal Software, Inc.  -- http://www.trigeminal.com/
