First, read this Codex page about translating WordPress. You have to create a language file to put into your language directory, do this by following the next steps: I assume you want to use poedit since you talk about a .po file download poedit File > new catalog In the first tab, fill in the … Read more
The easiest way for me is to change language settings for main blog multiple times (as mach as many languages I need) and WordPress will load these languages automatically. And after that I go to Update page and update language packages (loads languages for themes, plugins, etc.)
tl;dr Usually you should be safe by offering your Plugins in English first. If you create a good userbase, you could do your own resarch as to find out which languages are most important to your clients. Another thing to consider would be, if you want to support latin-signs only or if you want to … Read more
The security risk here is not about the plain text but about translation. You should note that esc_html_e is not only a function for escaping HTML but also for localization (l10n). I.e. other people can translate this String but you don’t know what the translation would be. It is possible that somebody translates the String … Read more
To do it properly, you need to generate a valid .mo file and load the text domain in your theme functions.php: function wpse222346_localize_theme() { load_theme_textdomain( ‘your_theme_domain’, get_template_directory() . ‘/languages’ ); } add_action( ‘after_setup_theme’, ‘wpse222346_localize_theme’ ); You can check the WordPress Codex for more info on the load_theme_textdomain function: https://codex.wordpress.org/Function_Reference/load_theme_textdomain Then you would call the translatable … Read more
The second part is not required, it just loads a PHP file with language specific functions. Examples In some countries/regions/religions it is not allowed to use capital letters in a word for anything else than the name of some god. In these cases you probably want to remove the WordPress to WordPress filter. Some languages … Read more
The value of a constant or variable can be evaluated by a PHP parser only. The tool that is used to extract the translatable strings is written in PHP, but is just a string parser. It doesn’t run your code, because that would be too slow and error prone. Here is an example for how … Read more
The list is available in $GLOBALS[‘l10n’][ $text_domain ]. To get the looong list of translatable WordPress strings just use: print ‘<pre>’ . htmlspecialchars( print_r( $GLOBALS[‘l10n’][‘default’], TRUE ) ) . ‘</pre>’; Do not use these strings in your theme or plugin. They are internal, de facto private. They can change any time, even in minor updates. … Read more
Here is a patch for 3.5 to use this with plugins. Use wp-content/languages/plugins/textdomain-pt_BR.po Apply this via SSH with: patch -p1 < no_plugin_overwrite.patch Hopefully its gonna be released in 3.6. Ticket #18200 (new task (blessed)) Implement language packs for core, plugins, and themes.
I couldn’t find an answer so I ended up providing the solution. It wasn’t simple given that I am not an expert with wordpress nor with php but WordPress documentation is great so here is the solution: // Set the post language when loading up the page based on the store meta function ppl_set_post_language() { … Read more