During my time on working on the WordPress Plugin Boilerplate, I’ve had some really good discussions with Gary Jones about some of the practices and conventions used throughout the code.
Up until this point, I’ve traditionally included a plugin.po
file with each of my plugins to make it easy for translators; however, Gary’s been kind enough to point out the a .pot
file should actually be included.
From a discussion on GitHub:
If you read the Codex page you linked to, you’ll see that it explains that .pot is the correct extension to use for the original translation file, since it is the template from which .po and .mo files are generated.
I’m not above admitting when there’s something I’ve not been doing correctly – after all, most developers should constantly be improving right?
At least I hope that’s the case.
Luckily, there are tools that make generating this catalog trivially easy so I thought I’d provide the steps necessarily to internationalize WordPress plugins specifically how I did so for the latest release of the Boilerplate.