From what I understand, the process was to upload the files to Crowdin, and then download the translations generated by Crowdin and commit them back to the repo.
Now the plugin READMEs are pulled in to the website build, and get translated along with it. So, those individual language-specific files in plugin repos shouldn't be necessary anymore. We'll probably revisit this process and clean up once we get to automating the Crowdin steps. Kindly, Dmitry -----Original Message----- From: julio cesar sanchez [mailto:jcesarmob...@gmail.com] Sent: Friday, April 22, 2016 4:12 PM To: dev@cordova.apache.org Subject: Re: Plugin documentation translations As far as I know, the translations are created in crowdin ( https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fcrowdin.com%2fproject%2fcordova&data=01%7c01%7cdblotsky%40microsoft.com%7cf57f3f3186c74e697faa08d36b0387f1%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=vD2jpn%2f5F2ccF%2fL1u963dAd22HJoRz75KSnYe7NhhSU%3d) It creates the index.md, I have no idea about the README.md. According to the mails on the list, Victor Sosa was the one taking care of it but he didn't have enough time and Andrey Kurdumov took over, so maybe he can shed some light. 2016-04-23 0:30 GMT+02:00 Jesse <purplecabb...@gmail.com>: > First off, I apologize for not being up to date in how we handle > translation of plugin docs. > Second, I want to thank whoever has been. > > So, looking thru the docs folder of the device-orientation plugin, I > see some very similar files ... each language folder appears to > contain an index.md and a README.md which are 'almost' identical. The > important part here is the 'almost'. > All of which finally brings me to my questions. > > How are these files created and updated? Why are they different? Where > are they shown? > > Thanks in advance! > Cheers, > Jesse > > > @purplecabbage > risingj.com >
