Re: [Ltru] UTF-8

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Reshat Sabiq (Reşat) yazmış:
> Most importantly, if UTF-8 is going to be easier for 95% of mainstream
> users, couldn't we tell 5% of peculiar users to deal w/ it? The registry
> for the internet should probably be based on up-to-date technologies,
> rather than trying to accommodate obsolete ones as well, which i think
> are used to rarely to be cared about anyway.
I just read the updates thru http, and i agree w/ Randy and Addison's
idea of converting escapes
to UTF-8 after the email phase. The submitter can always verify the
correctness thereof thru http,
and object if there are any mistakes. If this is done by a little
program, that is written w/ some unit tests, and tested, then errors
should be minimal.
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.

- --
My public GPG key (ID 0x262839AF) is at: http://keyserver.veridis.com:11371
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)

iD8DBQFGfAhjO75ytyYoOa8RAr46AKCS1xewkVIBkDeF2hWnAbr/4IJ5OACglfGh
nd9m3loc749N0Pyy0aOWNh4=
=t4Pf
-----END PGP SIGNATURE-----


_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru