Re: New teams for Crimean Tatar (crh), Tatar based on IQTElif (tt iqtel) (was: New teams for Crimean Tatar (crh), Tatar in Turkey (tt_TR))



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

Reshat Sabiq (Reşat) wrote:
> Well, crh and tt are related languages (looking at ISO
> classification), or dialects, but they are not the same. They are
> mutually comprehensible, so in a sense they can be considered
> dialects, but extent of mutual comprehensibility also depends on
> what alphabet one uses, etc. In general, tt_TR would be using 2
> more characters in comparison to crh, spelling is fairly frequently
> slightly different (though again mutually comprehensible), some
> suffixes are different between the 2, and vocabulary is different
> in some cases.
>
> P.S. What you were probably told is that there is mutual
> comprehensibility, not that there is no difference. There'd even be
>  less difference using Arabic alphabet in comparison to Latin
> alphabet, but that's a historical alphabet at this time.
>
> Thanks, Reşat.
Everything said above is still valid, but i'd like to delay tt_TR
(which might still come up later), in favor of tt iqtel  I was
hesitating about @iqtel earlier, because it's not a registered
modifier. But it was explained to me on launchpad that the modifier
doesn't have to be registered. ije in sr ije isn't registered either.
iqtel stands for İQTElif (İdíl-Ural-Qırım Tatar Elifbası), which is
version of Latin alphabet. The reason i need to use a modifier like
that under tt is because there are about 6 versions of Latin alphabet
currently de-facto in use, and none of them has gained official
status. This alphabet is characterized by:
1. phonetic correctness
2. closeness of orthography to kindred languages (like Crimean Tatar,
where Latin alphabet is official)
3. conventionality (no weird characters)

Basically, there needs to be 2 new teams:
crh
and
tt iqtel (so that folks who share preference for IQTElif have a common
workspace)

Thanks.
- --
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+MQEBp3xEgSYgSoRAr6NAJ9SdO75QtyJNqdFb67sGemiGt6svACeJHcF
gUe6pSw47K2aIBi7ZUJ4A+Q=
=LgsM
-----END PGP SIGNATURE-----



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]