To find the answer to this question, you just need to look at how WordPress retrieves the translations. Ultimately it is the load_textdomain() function that does this. When we take a look at its source we find that it creates a MO object and loads the translations from a .mo file into it. Then it … Read more
Try qtranslate…I use it religiously. Has some issues like with dates and times, but I always find a solution.
In wp-includes/l10n.php you will find the function get_locale(). It offers a filter; you can set the language and ignore the constant: function get_locale() { global $locale; if ( isset( $locale ) ) return apply_filters( ‘locale’, $locale ); // WPLANG is defined in wp-config. if ( defined( ‘WPLANG’ ) ) $locale = WPLANG; // If multisite, … Read more
I think I found a solution, but before a little Premise load_theme_textdomain() and load_child_theme_textdomain() are basically equal, the only difference is the default path they use: they get the current language (using get_locale()) and add the relative .mo file to the path passed as argument; then they call load_textdomain() passing as argument both the textdomain … Read more
You can do the following: Get the the language pack (e.g. de_DE.mo) from wordpress.org. If the language pack isn’t available as a standalone download, you could also use the .mo file which is bundled in the WordPress ZIP-file for your language. Located under wp-content/languages. Move the .mo file to wp-content/languages/ of your default (english) WordPress … Read more
Indeed, wp_localize_script() is simple, it just adds quotes around the values and escapes the content, expecting all of them to be strings. However, there is the l10n_print_after key of the array, which will be printed without any interference at all. It can be used to execute arbitrary code after the strings are passed. You can … Read more
You could use gettext filter: add_filter( ‘gettext’, ‘cyb_filter_gettext’, 10, 3 ); function cyb_filter_gettext( $translated, $original, $domain ) { // Use the text string exactly as it is in the translation file if ( $translated == “Categorie: %s” ) { $translated = “Sectie: %s”; } return $translated; } If you need to filter a translation with … Read more
I wouldn’t try to localize your slugs. Instead, why not give your users the option to change them by adding another field to the permalink settings page? Hook into load-options-permalink.php and set up some things to catch the $_POST data to save your slug. Also add a settings field to the page. <?php add_action( ‘load-options-permalink.php’, … Read more
By far the best (easiest) way is to use the locale filter (inside get_locale()). First set up a quick function for retrieving a different language to use on the locale filter. /** * A function returns with returns the user’s selectd locale, if stored. */ function wpse35622_get_new_locale($locale=false){ $new_locale = get_user_meta(get_current_user_id(), ‘wpse_locale’, true); if($new_locale) return $new_locale; … Read more
1. Write with localization in mind Don’t use echo or print() to produce text output, instead use the WordPress functions __() and _e(): /** Not localization friendly */ echo “Welcome to my plugin”; // OR print(“Welcome to my plugin”); /** Localization friendly */ _e(‘Welcome to my plugin’, ‘my-plugin’); // OR $my_text = __(‘Welcome to my … Read more