I did manage to solve this later on by using WPML, but over time found that WPML is quite bloaty and slow, support not very good, and if you need only 1 language (but original strings for theme are in English and the language you need is not) or perhaps 2, you do not need … Read more
Is it worth having two plugin textdomains – one for admin area strings and another one for “frontend”? In theory yes Does it break any guidelines (the plugin is public)? glotpress which drives the wordpress.org translation section is unlikely to ave any of it. For it you have to use only one text domain which … Read more
(Revised answer) The simple answer is because WordPress could not find the MO file, despite the file itself exists (in the plugin’s languages directory). And here’s why: The MO file needs to be named following this format: {text-domain}-{locale}.mo, and {text-domain}-{locale}.po for the PO file. See Loading Text Domain for further information. So you’re trying to … Read more
WordPress is community translated. For a good number of languages, the translation is relatively complete and follows high quality standards. The codex page on WordPress in your language reports: WordPress in Urdu – اردو is ongoing, but slow. Need more contributors. So in essence: No, WP is not entirely translated to Urdu yet. You could … Read more
It’s interesting idea and I think that such approach will work for you. What I would recommend you is that it will be better to use constructions like this: // $singular = 1 – for ‘me’, 2 – for ‘us’ $like_on = _n(‘Like me on %s’, ‘Like us on %s’, $singular, ‘my-plugin’); In this case … Read more
I think your function nesting is slightly muddled; call ucfirst after translating, like so: esc_html( ucfirst( translate_user_role( $user->roles[0] ) ) ); My bad, completely skipped a beat there. You should instead be using: translate_user_role( $GLOBALS[‘wp_roles’]->role_names[ $user->roles[0] ] ); It’s unreliable to assume that all role display names are simply ucfirst( $role key ). If that … Read more
Since WP 4.6 load_theme_textdomain() (and consequently load_child_theme_textdomain()) will give priority to .mo files downloaded from WP’s online translation platform (translate.wordpress.org). Due to some new code (here, on line 769) these functions will completely ignore your local .mo files if the textdomain is found in the general languages/ directory. You can, however, use the more basic … Read more
Add the following to your existing functions.php file: function ra_change_translate_text( $translated_text ) { if ( $translated_text == ‘January’ ) { $translated_text=”Jan11″; } return $translated_text; } add_filter( ‘gettext’, ‘ra_change_translate_text’, 20 ); If you want to change multiple strings, use this function instead: function ra_change_translate_text_multiple( $translated ) { $text = array( ‘January’ => ‘Jan11’, ‘February’ => ‘Feb22’, … Read more
Just modifying the .po file doesn’t do anything. The .po is the template. To be displayed, the .po must be compiled into an .mo file and it is the compiled .mo that makes the translations. If you’re just editing the .po in a text editor, you’re not changing anything. You’ll need a compiler. A good … Read more
$plugin_path = dirname( plugin_basename( __FILE__ ) ) . ‘/languages/’;