baku1926

"Reshat Sabiq (Reşat)" tatar.iqtelif.i18n at gmail.com
Thu May 17 06:20:24 CEST 2007


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

Frank Ellermann yazmış:
> Michael Everson wrote:
>> Is ASCII fallback forbidden?
> 
> It's up to the proponent / reviewer to decide what's
> best for the description / commment.  A proposal to
> restrict the Unicode points to Latn was fortunately
> rejected for RFC 4646.
Since current entries use escapes, i just submitted the modification
form w/ escapes.

The only change is in the comments. The escaped sequence stands for:

Also known as: New Turkic Alphabet; Birlәşdirilmiş Jeni Tyrk
Әlifbasь; Jaŋalif.

I opted for keeping semicolon, to make sure that it's clear that these
are 3 names, so i excluded my prior change number 3 suggestion, and
reflected the rest of the 4 changes i mentioned.

In the long term, i think this should be encoded in UTF-8, and comment
on top of the file could say:
File-Date:	2007-04-20
Encoding:	UTF-8

Sınce escapes are only a matter of encoding, and don't change content,
there could probably be a single decision, and a machine-based
re-encoding on all entries performed.

Sincerely,
Reşat.

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

iD8DBQFGS9gIO75ytyYoOa8RAjPFAJsHblPkNGSSP3PJtVHXiNhoARisjQCggXGd
pMUz1smffmRoCdSVUgYEOT4=
=+TzL
-----END PGP SIGNATURE-----


More information about the Ietf-languages mailing list