Hi Milamber,

Thanks, and sorry for the extra-trouble...
I did the push with: tx push -s -t
.. after linking the source, resource was 48xmessagesproperties.

I'm not sure if I did something wrong.. didn't check that branch before, but 
it's showing only 5% of strings in "translated state", while the other branches 
are ~60%...
Shouldn't Transifex catchup on the already translated strings?

I also updated the PR, btw.

-NT

Kind regards,

Nuno Tavares
Senior DevOps Infra Specialist
LeaseWeb Technologies B.V.

T: +31 20 316 0235
M:
E: n.tava...@tech.leaseweb.com
W: http://www.leaseweb.com

Luttenbergweg 8, 1101 EC Amsterdam, Netherlands


________________________________________
From: Milamber [milam...@apache.org]
Sent: Wednesday, February 10, 2016 8:14 AM
To: dev@cloudstack.apache.org
Subject: Re: Spannish translation mangled

Nuno, you are now Mainteners in the Web UI project. You can upload the
resources files to fix this charset issue.

On 10/02/2016 06:58, Nuno Tavares wrote:
> Hi Milamber,
>
> Not sure where I find my ID... but I'm this guys over here:
> https://www.transifex.com/user/profile/ntavares/
> :)
>
> -NT
>
> Kind regards,
>
> Nuno Tavares
> Senior DevOps Infra Specialist
> LeaseWeb Technologies B.V.
>
> T: +31 20 316 0235
> M:
> E: n.tava...@tech.leaseweb.com
> W: http://www.leaseweb.com
>
> Luttenbergweg 8, 1101 EC Amsterdam, Netherlands
>
>
> ________________________________________
> From: Milamber [milam...@apache.org]
> Sent: Wednesday, February 10, 2016 12:13 AM
> To: dev@cloudstack.apache.org
> Subject: Re: Spannish translation mangled
>
> Hum/Oups! Provide me your transifex account id to allow me to add to the
> maintainers team.
>
>
> On 09/02/2016 22:56, Nuno Tavares wrote:
>> Hi Milamber, thanks for the pointers... but apparently:
>>
>> $ tx push -s -t
>> Pushing translations for resource CloudStack_UI.48xmessagesproperties:
>> Exception: Only maintainers are allowed to update the source file.
>>
>> -NT
>>
>>
>> Kind regards,
>>
>> Nuno Tavares
>> Senior DevOps Infra Specialist
>> LeaseWeb Technologies B.V.
>>
>> T: +31 20 316 0235
>> M:
>> E: n.tava...@tech.leaseweb.com
>> W: http://www.leaseweb.com
>>
>> Luttenbergweg 8, 1101 EC Amsterdam, Netherlands
>>
>>
>> ________________________________________
>> From: Milamber [milam...@apache.org]
>> Sent: Tuesday, February 9, 2016 1:49 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: Spannish translation mangled
>>
>> Thanks
>>
>> Your can update the localization files on transifex using the little
>> utility on tools/transifex folder in source tree
>>
>> Requirement: Transifex client installed
>>
>> (go to the 4.8 branch)
>>
>> cd ./tools/transifex/
>> ./sync-transifex-ui.sh upload-l10n-languages
>> CloudStack_UI.48xmessagesproperties
>>
>> (all languages will be update from repo to transifex, you can reduce to
>> ES only if you editing the sync-transifex-ui.sh and change the LIST_LANG
>> value)
>>
>>
>>
>> On 09/02/2016 11:23, Nuno Tavares wrote:
>>> Hi all,
>>>
>>> I checked this issue yesterday with Daan, the problem is double UNICODE 
>>> encoding, and it's the source in Transifex that is broken. There are ~250 
>>> broken characters, so fixing one by one in Transifex is a bit of a waste of 
>>> time. I could fix this with a script, but I'm still wondering how the file 
>>> received patches and remain in this state (as in: is there any other 
>>> scenario where this double encoding shows up correct?)
>>>
>>> I've created a PR based on the tag 4.8.0 (#1407)
>>>
>>> -NT
>>>
>>> Kind regards,
>>>
>>> Nuno Tavares
>>> Senior DevOps Infra Specialist
>>> LeaseWeb Technologies B.V.
>>>
>>> T: +31 20 316 0235
>>> M:
>>> E: n.tava...@tech.leaseweb.com
>>> W: http://www.leaseweb.com
>>>
>>> Luttenbergweg 8, 1101 EC Amsterdam, Netherlands
>>>
>>>
>>> ________________________________________
>>> From: Daan Hoogland [daan.hoogl...@gmail.com]
>>> Sent: Monday, February 8, 2016 4:00 PM
>>> To: dev
>>> Subject: Spannish translation mangled
>>>
>>> @Milamber and other internationalisation specialists. I cannot get access
>>> to the spannish strings on transifex. It seems these get mangled into the
>>> source base. for instnce ```label.traffic.type=Tipo de Tráfico``` or
>>> ```label.total.of.vm=Total de máquinas virtuales```. Can someone give me
>>> access? or some spannish translator correct the strings? or some
>>> internationalization specialist give a transpose algorithm to deal with the
>>> issue?
>>>
>>> Thanks,
>>> --
>>> Daan

Reply via email to