Re: [Gimp-developer] I18N in Python plugin

2013-06-04 Thread Ragnar Brynjúlfsson
I've added i18n/gettext support to my plug-in over the weekend. I don't know if it's completely correct, but it does work. :) You can get it from here http://ragnarb.com/toolbox/gimp-book/ and have a look at the code. The translation code is at the beginning of booy.py, and each string to be tran

Re: [Gimp-developer] I18N in Python plugin

2013-06-01 Thread Ragnar Brynjúlfsson
I found this readme, that might help. http://developer.gimp.org/README.i18n This is of interest for plug-in development " Third-party plug-ins (plug-ins that are not distributed with GIMP) can't have their messages in the gimp-std-plugins textdomain. We have therefore provided a mechanism th

Re: [Gimp-developer] I18N in Python plugin

2013-05-30 Thread Ragnar Brynjúlfsson
I was just going to ask the same question. I've started implementing this in my Gimp Book plug-in, following this http://wiki.maemo.org/Internationalize_a_Python_application guide, but haven't got it working yet, and have no idea what I'm doing wrong. What would be the correct way to go about tran

[Gimp-developer] I18N in Python plugin

2013-05-07 Thread Ofnuts
What is the right/best/officially blessed way to handle I18N in Python plugins? Or asked differently, what can I do in my code so that someone can make the plugin usable in other languages without having to update the code? ___ gimp-developer-list ma