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

José Fontainhas jfontainhas at gmail.com
Mon Jan 10 08:28:27 UTC 2011


Every new version of the plugin needs a new .pot (as line numbers for
strings change between versions). The usual (but not mandatory)
practice is to create a lang folder for your plugin which contains the
.pot file, so that translators can create their languages' .po and .mo
files there, and send them to you, if you want to distribute them
along with the plugin.

Creating a .pot file is not a big hassle and takes a few seconds.


On 8 January 2011 13:13, 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

More information about the wp-hackers mailing list