Quote:
Originally Posted by DiapDealer
That would be great! Since it's set up now, I'll wait a bit to see if any others want to contribute a translation before releasing a new version. The .pot file is available from the github repository (link in first post of this thread), that can be used to create the editable .po files.
If you can't contribute via Github, just let me know what I need to provide for you and I'll get it to you.
|
I've already downloaded the pot file, and I've created es.po and es.mo (it's a work in progress at this moment). I'll try to make a push at some moment in the next week, but I'm not sure when. If I have some problem I'll tell you.
Quote:
Originally Posted by DiapDealer
I just need to come up with a scripted workflow to update the existing .po files whenever I change things for a new release (when the changes require the translators to revisit them). Shouldn't be too difficult. That way people can submit pull requests on Github, or email me updated files and I'll script something that compiles them all to .mo files when I make a new release of the plugin.
|
I'm not sure if the first step is really necessary. I think you only need to change the Trad.pot and, later, everybody can update the po file from that, and translate the new strings (it's like I usually do, and the plugins I check usually follow this pattern).