-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Charles Schulz wrote:
> Hello Reshat,
>> 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.
> We usually respect the ISO codes, and you were right in your
> observations. Here is what I suggest, but that needs to be
> validated by the NLC leads: we could open a native-lang project
> with two names, tt and crh. We did this with the Brazilian project
> at the time, "br" and "br-pt". Then later one the project can
> split. What do you think?
I'm not sure what you mean by "a native-lang project with two names".
Did you mean what i mentioned as an option previously, like crh-tt,
spelled out as Tatar (Idíl-Ural (Qazan), Crimean)? If the project gets
an OOo site at some point, what would it be? Smt. like
crh-tt.openoffice.org?
So i guess the options are:
1. crh-tt project, spelled out something like as Tatar (Idíl-Ural
(Qazan), Crimean)
2. separate projects:
2.1. crh
2.2. tt
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+LOJBp3xEgSYgSoRAoEGAJ9/TAbgKqc7pkL7kthAwu7K7Y3/twCfXRVp
vJAZmNzFjHfp0L3dUQCEyn0=
=R7ve
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
