Re: [Ltru] UTF-8

"Reshat Sabiq (Reşat)" <> Mon, 09 July 2007 00:13 UTC

Return-path: <>
Received: from [] ( by with esmtp (Exim 4.43) id 1I7gsV-000063-FS; Sun, 08 Jul 2007 20:13:23 -0400
Received: from ltru by with local (Exim 4.43) id 1I7gsB-0008Pd-Jx for; Sun, 08 Jul 2007 20:13:03 -0400
Received: from [] ( by with esmtp (Exim 4.43) id 1I7gsB-0008PU-38 for; Sun, 08 Jul 2007 20:13:03 -0400
Received: from ([]) by with esmtp (Exim 4.43) id 1I7gs6-0005TR-Bj for; Sun, 08 Jul 2007 20:13:02 -0400
Received: from [] ( []) by (8.13.6/8.13.6) with ESMTP id l690BGoY013422; Sun, 8 Jul 2007 19:11:21 -0500 (CDT)
Message-ID: <>
Date: Sun, 08 Jul 2007 19:10:45 -0500
From: "\"Reshat Sabiq (Reşat)\"" <>
User-Agent: Thunderbird (Windows/20070604)
MIME-Version: 1.0
To: John Cowan <>
Subject: Re: [Ltru] UTF-8
References: <> <> <> <> <> <>
In-Reply-To: <>
X-Enigmail-Version: 0.95.1
OpenPGP: id=262839AF; url=
Content-Type: text/plain; charset="UTF-8"
X-Virus-Scanned: Symantec AntiVirus Scan Engine
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by id l690BGoY013422
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc:, GerardM <>
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

Hash: SHA1

Reshat Sabiq (Reşat) yazmış:
> As far as passivity, if this takes effect w/ the next release of the
> registry spec, and people know about it in advance, then it's natural
> for it to not be passive. For temporary passivity, the old registry
> could continue to exist w/o updates at the existing URL, and the new
> registry to be updated could be exposed thru a new URL.
> That happened in java betweem 1.3 and 1.4, and 1.4 and 5: it's
> inevitable at early stages, and maybe even beyond. Deep down, do we not
> all know that it will be UTF-8 and XML at some point? I think we do, so
> passivity question will come up anyway, it's just a matter of managing
> it well.
I can't afford to stay abreast of the discussion, but i'd like to
elaborate on my idea for passivity, w/ a SOAP standards example: The
namespaces for the SOAP schemas change from version to version. For

If you wanted to have
passive, then UTF-based registry would just need to use a different
namespace (when using XML), and/or URL, such as:

If you want to give people 3 years to get ready for it, then this could
be planned as such for year 2010, and then it'd be some xxxx standard
above instead of 4646bis.

Or if, you'd like to have only 1 namespace for UTF-8-based registry,
then it could be something like (and then it wouldn't change from
4646bis to xxxx to yyyy, etc.):

My 2 cents,

P.S. Let's also schedule (log a bug, if possible)
app to handle UTF-8. ;)

- --
My public GPG key (ID 0x262839AF) is at:
Version: GnuPG v1.4.2.1 (Cygwin)


Ltru mailing list