Transifex "cs" vs. "cs_CZ"

[Adam Pribyl]

Sorry if this was asked already, there is so many emails about transifex 
now, I am not able to read all of them.

We have similar problem to that described in 
http://getsatisfaction.com/indifex/topics/_translate_now_cannot_be_activated

While I created Czech team on Transifex as "cs", there are projects that 
have language as "cs_CZ". Do we have to create two teams? As cs is more or 
less equal to cs_CZ, I'd love to have the same team for both... is it 
possible?

Adam Pribyl

[Dimitris Glezos]

On Tue, Mar 1, 2011 at 10:00 AM, Adam Pribyl  wrote:
> We have similar problem to that described in
> http://getsatisfaction.com/indifex/topics/_translate_now_cannot_be_activated
>
> While I created Czech team on Transifex as "cs", there are projects that
> have language as "cs_CZ". Do we have to create two teams? As cs is more or
> less equal to cs_CZ, I'd love to have the same team for both... is it
> possible?

We should use one language team; it will make things much easier (ie
not have to administrate two memberships etc). I guess the correct one
is cs.. this is the standard Czech locale, right?

-d

[Piotr Drąg]

2011/3/1 Dimitris Glezos :
> We should use one language team; it will make things much easier (ie
> not have to administrate two memberships etc). I guess the correct one
> is cs.. this is the standard Czech locale, right?

Yes. The problem is that Publican uses XML language codes (cs_CZ,
uk_UA etc.), and software uses only cs, uk etc locales. The right
solution would be linking cs_CZ and cs-CZ translations with cs team.
Do you want us to file a ticket on this?

I already have uk and uk-UA translations for TQSG.

[Dimitris Glezos]

On Tue, Mar 1, 2011 at 2:35 PM, Piotr Drąg  wrote:
> 2011/3/1 Dimitris Glezos :
> > We should use one language team; it will make things much easier (ie
> > not have to administrate two memberships etc). I guess the correct one
> > is cs.. this is the standard Czech locale, right?
>
> Yes. The problem is that Publican uses XML language codes (cs_CZ,
> uk_UA etc.), and software uses only cs, uk etc locales. The right
> solution would be linking cs_CZ and cs-CZ translations with cs team.

I think Publican (or the Fedora toolchain around it) should be adapted
to support cs.
> Do you want us to file a ticket on this?

We could have a ticket filed. Fwiw, support for multiple languages per
team is quite a big change in the codebase.

-d
> I already have uk and uk-UA translations for TQSG.

[Miloš Komarčević]

On Tue, Mar 1, 2011 at 12:40 PM, Dimitris Glezos  wrote:
> We could have a ticket filed. Fwiw, support for multiple languages per
> team is quite a big change in the codebase.

You mean multiple locales?

I.e., we can no longer have "sr" and "sr-Latn"/"sr@latin" under the same team?

If so, this is a big loss of feature compared to Tx < 1.0 instance on fp.o :(

Regards,
Miloš

[Dimitris Glezos]

On Tue, Mar 1, 2011 at 2:57 PM, Miloš Komarčević  wrote:
> On Tue, Mar 1, 2011 at 12:40 PM, Dimitris Glezos  wrote:
> > We could have a ticket filed. Fwiw, support for multiple languages per
> > team is quite a big change in the codebase.
>
> You mean multiple locales?
>
> I.e., we can no longer have "sr" and "sr-Latn"/"sr@latin" under the same team?
>
> If so, this is a big loss of feature compared to Tx < 1.0 instance on fp.o :(

Previously we didn't even have teams.. everyone could submit to every
language. :)

We can just create separate teams for now, if truly needed (like in
the case of sr/sr@latn), until we have a solution.

-d

[Miloš Komarčević]

On Tue, Mar 1, 2011 at 1:10 PM, Dimitris Glezos  wrote:
> Previously we didn't even have teams.. everyone could submit to every
> language. :)

Ah, I get it, so that grouping was purely cosmetic for translate.fp.o
website presentation purposes only.
> We can just create separate teams for now, if truly needed (like in
> the case of sr/sr@latn), until we have a solution.

Would be nice to take stuff like this onto account during design,
there are more languages that use more than one script and/or other
variant, thus resulting in multiple locales typically handled by one
team.

Regards,
Miloš

[Adam Pribyl]

On Tue, 1 Mar 2011, Dimitris Glezos wrote:
> On Tue, Mar 1, 2011 at 2:35 PM, Piotr Drąg  wrote:
> > 2011/3/1 Dimitris Glezos :
> > > We should use one language team; it will make things much easier (ie
> > > not have to administrate two memberships etc). I guess the correct one
> > > is cs.. this is the standard Czech locale, right?
> >
> > Yes. The problem is that Publican uses XML language codes (cs_CZ,
> > uk_UA etc.), and software uses only cs, uk etc locales. The right
> > solution would be linking cs_CZ and cs-CZ translations with cs team.
>
> I think Publican (or the Fedora toolchain around it) should be adapted
> to support cs.
> > Do you want us to file a ticket on this?
>
> We could have a ticket filed. Fwiw, support for multiple languages per
> team is quite a big change in the codebase.

And would it be very hard to constantly mirror the team members to another 
"language"? If it is inevitable, I may start another team for cs_CZ and 
ask people to join them both, but surely this is not very comfortable.
> -- 
> Dimitris Glezos

Adam Pribyl

[Yuri Chornoivan]

Від кого: "Piotr DrД…g"  
 Кому: "Fedora Translation Project List"  
 Дата: 1 березня 2011, 14:35:29 
 Тема: Re: Transifex "cs" vs. "cs_CZ"
> 2011/3/1 Dimitris Glezos :
> > We should use one language team; it will make things much easier (ie
> > not have to administrate two memberships etc). I guess the correct one
> > is cs.. this is the standard Czech locale, right?
>
> Yes. The problem is that Publican uses XML language codes (cs_CZ,
> uk_UA etc.), and software uses only cs, uk etc locales. The right
> solution would be linking cs_CZ and cs-CZ translations with cs team.
> Do you want us to file a ticket on this?

That would be good, but how someone will know for what branch (uk, uk_UA, etc.) to commit new doc translations? I think, the only solution is "one team -- one locale" without linking.
> I already have uk and uk-UA translations for TQSG.

I cannot commit in uk_UA locale, and noone answer my question neither in this mailing list, nor in IRC. Should I stop committing into "uk" until the solution will be found?

Thanks in advance for your answers.

Best regards,
Yuri