"Reshat Sabiq (Reşat)"
tatar.iqtelif.i18n at gmail.com
Thu May 3 06:29:27 CEST 2007
-----BEGIN PGP SIGNED MESSAGE-----
Michael Everson yazmış:
> At 23:32 -0500 2007-05-01, Reshat Sabiq (Res¸at) wrote:
>> Denotes alphabet used in Turkic republics/regions
>> of the former USSR in late 1920s, and throughout 1930s, which aspired to
>> represent equivalent phonemes in a unified fashion. Also known as: New
>> Turkic Alphabet, Birlәşdirilmiş Jeni Türk
>> Әlifbasь, Jaŋalif.
> I am not really very happy about tinkering so soon after registration.
> But if we do change it I would like to get rid of the illegible &xxxx;
> notation. If the registry entries are to be in HTML, they should be so
> normatively, with charset tagging so that they display properly. If they
> are not tagged, then ASCII fallback should be used so the strings are
> legible. As it is I can only guess, or drag out the Unicode book and
> look them up. That's not legibility.
I see that in multiple tags. Why is the file not encoded in UTF-8? I
think that's all that would need to be done at a minimum. I even tried
it out on fx, ie, windows, and linux.
Speaking of corrections, there needs to be another one, ü->y (let
that that be number 4 instead of Suppress-Script), to make my correction
suggestion as follows:
Denotes alphabet used in Turkic republics/regions
of the former USSR in late 1920s, and throughout 1930s, which aspired to
represent equivalent phonemes in a unified fashion. Also known as: New
Turkic Alphabet, Birlәşdirilmiş Jeni Tyrk
Please let me know whether i should use escape sequences or UTF-8, and i
will be submitting the form for above within a week or so.
P.S. I guess it helps to get my earlier remarks' point across: the
alphabet doesn't really look completely latin w/ all the mixed
My public GPG key (ID 0x262839AF) is at: http://keyserver.veridis.com:11371
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v18.104.22.168 (Cygwin)
-----END PGP SIGNATURE-----
More information about the Ietf-languages