cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lisa Seacat DeLuca <>
Subject Re: Crowdin and translation process
Date Tue, 20 Jan 2015 16:43:57 GMT


I'm a little confused by your request.  Are you saying that you make
changes to the translation outside of the Crowdin tool?  If that's the
case, yes, all of your changes are going to be lost every time.  You'll
need to make the changes within Crowdin.  When the script is ran to make
sure the latest documentation is pushed to the Crowdin tool it doesn't
override any translations that have already been done.  It just adds
updates to the documentation (new sentences, new code, etc) or changes that
were made.  So unless sections of the english version of the documentation
has been changes your Russian updates shouldn't be affected.  I see no
reason why you couldn't own the Russian part of the translation process.
Whenever Victor goes to pull down the translations if the Russian
translations aren't at 100% he can talk to you.  Does that sound
reasonable?  Did I understand your concern correctly?


From:	Andrey Kurdumov <>
To:, Victor Adrian Sosa Herrera
Date:	01/20/2015 01:22 AM
Subject:	Crowdin and translation process


I start working on the improving Cordova documentation for Russian
Earlier I put fix for the YAML license headers directly to Github for all

Right now after I put documentation translation checker tool, I see issues
which I would like to improve Russian translation.

I download latest translation from Crowdin and compare that field with docs
in the source control. What I found is that YAML fixes is not in CrowdIn.

1. This raises question how we could could work on translation with Victor
together effectively, not impacting each other?
When documentation files is uploaded to the Crowdin?
When translation is collected from Crowdin?
Are there any rules which could be used, so I could prepare to these

2. Current script just download everything and commit it in the
cordova-docs repository.
What I think is that it could be effective is that I take responsibility
for maintaining Russian translation and Victor would maintain other
translations, like it was before. And downloading script could be modified
to include language which should be downloaded, so this allow explicit
control which languages is created. I recently cleanup a lot of files from
probably Crowdin mistakes, and don't want that this would be introduced

  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message