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

Reshat Sabiq (Reşat) wrote:
>
> However, i have some reservations about putting crh and tt into 1
> team. On the one hand it's possible, but would require calling the
> project accordingly: perhaps tt-crh, which in plain language would
> have to be spelled out like Tatar (Idil-Ural and Crimean), or Tatar
>  (Crimean, Idil-Ural). Here the naming might raise questions like,
> why is crh after tt? To avoid that, perhaps it could be listed as
> crh-tt in project name, "crh, tt" in ISO code column, and Tatar
> (Idil-Ural, Crimean) in plain language (mixed order). Since there
> are 2 distinct ISO codes for the 2 main literary versions of Tatar,
> i think for the time being it's expedient to adhere to them. I tend
> to think Crimean Tatars would actually want their ISO code
> distinct, given all the confusion going on about tt. I'm not sure
> how Crimean Tatars would feel about tt and crh being on the same
> project. So in short we could try making the project crh-tt, IMHO.
> If there are strong suggestions about separating them later on, i
> guess we would discuss separating crh and tt projects.
>
> Thanks.
All the projects i'm seeing so far have only 1 ISO code in them. So
crh-tt would be a first it appears. Despite the fact that the alphabet
i'm planning on using will provide orthography that will be very
similar to Crimean Tatar, i'm 50-50 on whether crh and tt should be
separate projects. There are advantages and disadvantages. If you guys
lean towards one crh-tt project, then i guess we can start off w/ that.

Thanks again.
- --
My public GPG key is at:
http://keyserver.veridis.com:11371/export?id=476802195259949354
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE+B+6Bp3xEgSYgSoRAnV0AKCAdjM8kbfZk/VgpqPeINmqZtkFMwCgiZus
OJ2znVxB2uNNGX/p19hKRh8=
=A9uI
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to