MO (Machine Object) file – A binary representation of the PO file.Every string listed in the POT will be in the PO file together with it’s correct translation. PO (Portable Object) file – translation files that holds all translations for a specific language per file.
POT (Portable Object Template) file – the template file containing every string used within the plugin that is translatable.But in order for translations to take place a few files are needed. WordPress uses the GNU gettext localization framework to do these translations. Prepare / Generate Your Translation Files What’s the difference between _(), _e(), _x(), and _ex()? is another great article which outlines the differences between the different localization functions within WordPress. In our plugin’s context, the domain will be the plugin’s slug or unique identifier. This is the domain that WordPress uses when performing the translation. Notice I am passing in a second parameter ‘my-plugin-domain’ to these functions. Or you could have used the _e() function to translate and echo: _e('I am translatable', 'my-plugin-domain') An example will explain best: //this string is not translatableĮcho _('I am translatable', 'my-plugin-domain') Rather wrap them with the WordPress functions _() or _e().
#Woocomerce plugin poedit code#
Whenever you use a string in your code files, don’t just echo or print them out. Now back to the code… Write Code With Localization In Mind His “sister-post” to this article is particularly inspiring this week and I recommend you check it out. His posts always give great insight into how he found my articles, along with any hurdles he had.
Tell your plugin to use your translation files.Īs you may know, Matt is following this tutorial and posting his results on his own blog. Prepare/generate your translation files. Write your code with localization in mind. Read up more about localization in WordPress. This is what you need to do in order to make your plugin translation ready: But it does provide a really easy way for your plugin users to provide their own translation files. But making your plugin ready for translation doesn’t mean you need to do the translations yourself. Why make your plugin translatable, you might ask? Well, to increase your plugin’s target audience by allowing any person, who speaks any language, the ability to understand and use it. !Important – Make sure that the language of your files is the same as in your WordPress admin panel – Settings – General Settings.WordPress provides us with all the tools (and functions) we need to make our plugins translatable or localizable. mo files according to your language, the file names should look like this: trx_utils-pt_BR.po and trx_utils-pt_BR.mo. – wp-content\plugins\trx_utils\languages if your theme includes ThemeREX utilities plugin. mo files according to your language, the file names should look like this: trx_addons-pt_BR.po and trx_addons-pt_BR.mo. wp-content\plugins\trx_addons\languages if you are using ThemeREX addons plugin Our themes are using ThemeREX addons or ThemeREX utilities plugin (depending on the theme), so some translation should be done in the language files of the plugin in this directory: Make sure these files are in the same directory as. According to the example above, the file would be called pt_BR.mo.ħ. po file is saved, Poedit automatically creates a new. Please note, if you use the wrong naming convention WordPress can not process your translation.Ħ. See Language Codes and Country Codes for the lists of codes. If you are not familiar with the codes for your native language and country, then visit the GNU website. In this case, the difference is in the first and second letter pairs for the UK, the code would be en_GB, whereas the en_US stands for the USA. However, there is a difference for languages like English or Portuguese, which are spoken in several countries natively. In most cases, the language and country are the same, like “de_DE” for Germany. The first lower-case letters define the language, whereas the second upper-case letter defines the country. pt for Portuguese) followed by the country code (for instance _BR for Brazil). po file using the naming convention based on the language code (e.g. Next, you’ll need to save changes to your.
0 kommentar(er)
