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 no idea if people are used to creating their own .po files and compiling them to .mo file themselves, or what? I can provide .po files for the target languages and compile the completed ones if necessary. Whatever works best.
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.
|
Good idea for the .po and .pot files, you're right they don't need to be in the final plugin, but I wasn't really sure how to filter them out...
For the creation of the .POT and .PO files I used Poedit. And apparently I didn't configure it properly so the update isn't working as intended... I did it again it should work this time, I will push it to github.
Actually you just have to click on
update in the toolbar or you can use
update from POT file when you are in the PO file. (to configure the source you need to go to catalogue -> properties -> sources paths and add the path to the .py files to translate, but I've done it)
And the MO files are automatically created by Poedit so I think the translators can produce it easily enough.
For future updates I can update the translations if you like (I will follow this thread but feel free to PM me here or on github). The easiest thing is probably to update the .po files so that translators just have to add the missing strings.