This post is part of the sub-series on Translating a ClassicPress plugin with Poedit which is part of the Translating a ClassicPress plugin with Poedit series.
Poedit calls itself the fastest and most convenient way to translate apps and sites with gettext and is available for Windows, Mac and Linux and has two versions available; standard and pro.
Both versions have the same core features with Pro adding collaboration and functionality specific to Wordpress (which would also work with ,a href=’https://www.classicpress.net’>ClassicPress).
Poedit was built to handle translation using gettext, which is used by many PHP projects such as ClassicPress, WordPress and Drupal), Python projects (Django) and many applications running on Linux.
The Poedit features page explains how the translation of strings from code works as this:
- The developer writes their code using gettext APIs.
- The developer extracts all translatable texts in their code and creates a master PO file that translators can work with.
- The translator works through the PO file provided and hands back their translations, one file per language.
- Whenever the source code changes and there are translation differences the developer re-runs the extraction and updates the master PO file accordingly.
- The translator only has to update their translation file to match the master file 100%.
Poedit aims to help with stages 2 through 5 and save both translators and developers time at each stage.
In this series, I will be using the standard Windows version of Poedit.
Translating a ClassicPress plugin
| Translating a ClassicPress plugin with Poedit |
|---|
| What is Poedit? |
| Download Poedit |
| Install Poedit |
| Create New Translation Template |
| Create Translations |
