Poedit plugin install#
Poedit plugin update#
Poedit plugin manual#
Poedit plugin pro#

Top ↑ Try to keep the same level of formality (or informality)Įach message has a different level of formality or informality. Even with more structural items in messages, you have creative license to adapt and change if you feel it will be more logical for, or better adapted to, your target audience.

It’s the difference between creating an equal message and an equivalent message: don’t replicate, replace. Translated messages don’t need to be structured the same way as the English ones: take the ideas that are presented and come up with a message that expresses the same thing in a natural way for the target language. Top ↑ Don’t translate literally, translate organicallyīeing bi- or multi-lingual, you undoubtedly know that the languages you speak have different structures, rhythms, tones, and inflections. There is grunt-po2mo that will convert all of the files. There is a setting in the preferences where you can enable or disable it. Msgfmt is also integrated in Poedit allowing you to use it to generate the MO file. cd C:/path/to/language/folder/my-plugin/languages & C:/cygwin/bin/bash -c /cygdrive/c/path/to/script/directory/potomo.sh You can run this command in the command line. Save the translated file as my-plugin- $file done Here is an example Grunt.js and package.json that you can place in the root of your plugin. Steps on setting up grunt are beyond the scope of this documentation, but just be aware that it is possible. There are even some grunt tasks that you can use to create the POTs.

Poedit plugin update#

Once you have placed the blank POT in the languages folder you can click “Update” in Poedit to update the POT file with your strings.

Poedit plugin pro#

If you don’t have the pro version you can easily get the Blank POT and use that as the base of your POT file. If a MO was generated then you can delete that file as it is not needed. After generating the PO file you can rename the file to POT. A pro version of it also features one-click scanning for WordPress plugins.

Poedit plugin manual#

The free Poedit default version supports manual scanning of all source code with Gettext functions. This is an open source tool for all major OSs. You can also use Poedit locally when translating.

Poedit plugin install#

Install WP-CLI and use the wp i18n make-pot command according to the documentation. There are a couple of ways to generate a POT file for your plugin: Note: It is a good idea to offer the POT file along with your plugin, so that translators won’t have to ask you specifically about it. The POT and PO files can easily be interchangeably renamed to change file types without issues. The POT file is the one you need to hand to translators, so that they can do their work. A text domain is a handle of each module, which has a different MO file. The conversion is done using the msgfmt command line tool. In general, an application may use more than one large logical translatable module and a different MO file accordingly. PO files), and are a “compiled” version of the PO file. These are machine-readable, binary files that the gettext functions actually use (they don’t care about. There is one PO file per language.įrom every translated PO file a MO file is built. The result is a PO file with the same format as a POT, but with translations and some specific headers. This file contains the original strings (in English) in your plugin.Įvery translator will take the POT file and translate the msgstr sections into their own language. Top ↑ POT (Portable Object Template) files Localization is often abbreviated as l10n (because there are 10 letters between the l and the n.) Localization describes the subsequent process of translating an internationalized plugin.

Read other software’s localizations in your language.

Don’t use slang or audience-specific terms.

Try to keep the same level of formality (or informality).

Don’t translate literally, translate organically.