[wp-hackers] Looking for best practices in how to deal with translations as a plugin developer

[José Fontainhas]

I'd say so, that's the way it's implemented for WordPress.org, see:

http://translate.wordpress.org/projects/wp

-Z

On 10 January 2011 14:30, Alex Hempton-Smith <hempsworth at gmail.com> wrote:
> I've just installed GlotPress on my plugin site for BuddyPress Like, and
> it's really easy to get used to, and allows all the translations to happen
> centrally. However, I would like some advice with projects...
>
> Should I have a subproject for Trunk, and then a subproject for each
> subsequent version that is released?
>
> -- Alex
>
>
> On Sat, Jan 8, 2011 at 1:13 PM, Bjorn Wijers <burobjorn at gmail.com> wrote:
>
>> Hi,
>>
>> I've created a few plugins and I've made translations for them. Now I need
>> to update some plugins and I wonder what the best practices are for dealing
>> with multiple versions and translations. E.g. do you always need to generate
>> a new pot file from scratch? Or are there better ways of dealing with this?
>> I'm looking for any hints, tips and methods from fellow plugin developers
>> dealing with this.
>>
>> Thanks in advance!
>>
>> --
>>
>> met vriendelijke groet,
>> Bjorn Wijers
>>
>> * b u r o b j o r n .nl *
>> digitaal vakmanschap | digital craftsmanship
>>
>> Werkdagen:
>> Van maandag t/m donderdag vanaf 10:00
>> Vrijdag is voor experimenteren en eigen projecten.
>>
>> Concordiastraat 68-126
>> 3551 EM Utrecht
>> The Netherlands
>>
>> tel: +31 6 49 74 78 70
>> http://www.burobjorn.nl
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>