[ckan-dev] Translation issue

[alexey medvetsky]

Hi David, Friedrich and team,

I think it's a good idea to split the web front end and the rest of the 
system. If I get this right, it will divide the user interface from the 
other code used mostly by developers.
So if you can somehow extract the end-user web interface and put it in a 
separate "package" available for translation - this would do fine.

Regards,
Alexey.



> Alexey,
>
> Sorry to hear about the updates to the strings after your super
> efforts in finishing the Russian translation. We do try hard to avoid
> changing strings too often, but we had a big refactor in the logic
> layer, for which there are a lot of error messages and the like that
> probably caused you issues. There is an argument that API messages and
> errors should not be translated, leaving the translation just to the
> web front end. This may cut down the work at keeping up to date by a
> big chunk - do let me know what you think about this.
>
> Friedrich, it's probably a good moment to hand over the transifex
> admin over to me, so I'll try and catch you for a chat about these
> processes.
>
> David
>
> On 25 August 2011 10:57, alexey medvetsky<a.medvetsky at gmail.com>  wrote:
>> Hi David,
>>
>> Thanks, yes, it is. I have already finished the translation (actually twice)
>> meaning to test it online, but the updates keep coming and that makes me
>> confused.
>> Hope there is a way to coordinate these two update/translate processes. Or
>> simply deploy the translation, as it is now, on to the ckan testing
>> interface. Otherwise it seems like the translators will never catch up with
>> the programmers. :)
>>
>>
>> Best,
>> Alexey.
>>
>>> Hi Alexey,
>>>
>>> I just saw your message on the community meetup pad:
>>>
>>> Hi guys, cannot join the discussion tonight, but hope you'll find a
>>> minute to talk abt CKAN interface translations at Transifex, esp. the
>>> circular problem of updating the core and translating it which seems
>>> to become endless.
>>> Best,
>>> Alexey, the Russian translation team.
>>>
>>> I'm just wondering what this circular problem is? Is it simply that
>>> edits to CKAN affect the strings too frequently, making it difficult
>>> for translators to keep up? Or is there a technical problem?
>>>
>>> David
>>