[wp-hackers] Handling Plugin translations

Peter Westwood peter.westwood at ftwr.co.uk
Sun Jan 10 11:26:21 UTC 2010

On 9 Jan 2010, at 10:46, Dion Hulse (dd32) wrote:

> On Sat, 09 Jan 2010 21:21:50 +1100, TobiasBg <wp-hackers at tobias.baethge.com 
> > wrote:
>> <snip>
>> With the latest plugin release, I have now started to set  
>> translations that were not updated in a while to "inactive".
>> This means that I don't include them into the final release, but in  
>> beta or dev versions (so that already translated strings are not  
>> lost forever, I just does not make sense to include them in the  
>> final, as the translation is not very useful, if it only covers  
>> half of the plugin).
>> As mentioned above, I had to set 6 of the 15 translations to  
>> inactive. That just happens. In two cases the translators email  
>> addresses are no longer existing, and in the rest they just don't  
>> respond.
> Thats pretty much the approach i was thinking of taking for this  
> release. I'm going to get a RC/beta out tonight for the plugin, and  
> send a email around for translations, Cheers :)
>>> I was considering installing GlotPress and maybe getting people to  
>>> update them there directly, Has anyone else taken this route?
>> I would really love to do that, but unfortunately GlotPress is not  
>> (yet) ready for that. I would love to test and play around with it,  
>> but unfortunately have severe problems, especially because of this  
>> issue: http://trac.glotpress.org/ticket/26
> I might have to get involved in GlotPress then and get it up and  
> running for myself, see what i cant fix along the way :)

Patch to fix this is on the ticket now as I got curious again and  
tracked down the issue.

Hopefully this will make it into GlotPress trunk soon.

Peter Westwood
http://blog.ftwr.co.uk | http://westi.wordpress.com
C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5

More information about the wp-hackers mailing list