-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Charles Schulz wrote: > Hello Eike, hello Reshat, >> What do governmental departments use in digital processing? I >> guess it's Cyrillic? If so, and you want a wide-spread use of >> OOo, you probably should support Cyrillic first. >> > > Good point. But let's just leave the decision to Reshat. After all, > if Cyrillic-written Tatar is used inside the Russian Federation, > Latin Tatar is also used in Ukraine (Crimea), so both versions are > valid. Anyway, I just wanted to clarify some points: You do not > need to open several Native-Lang projects. You can have multiple > encodings and locales for one language. So the project you could > open would be "TT" (if I'm not mistaken)... How about that? > > Charles. If a single project can support locales like: 1. language-region (where region could be RU, TR, UA, etc.) 2. language-region-modifiers (in the future) then looks like just calling the project tt for Idil-Ural (Qazan) Tatar would work. Although organizationally, there are eventually likely to be folks interested in using one alphabet, but not the other. Different mailing lists may be needed for that reason, although that can be handled externally, and i'm actually seeing different mailing lists supported on OOo as well.
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. - -- 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+AxVBp3xEgSYgSoRAnOeAJ0RARtQteGVui6SNvsYUDNTIHyx2QCgj7F6 UaWglii5kaj+qMiSJAXrKP4= =+lEm -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
