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/’;
I’ll speak for qTranslate, I’ve used it a few times and been pretty happy with it. What it sets out to do – letting you offer translations of post content in multiple languages and switch between them – it does pretty well. It gets a bit dicey when you try to extend it beyond alternate … Read more
That plugin loads its language the moment its main file is included: load_plugin_textdomain( ‘wordpress-seo’, false, dirname( plugin_basename( __FILE__ ) ) . ‘/languages’ ); So when your locale filter is used, the language is already there. :/ Move your small plugin into the mu-plugins directory. You can create it if it doesn’t exists in wp-content. That … Read more
Should be put to the translation function. <?php comment_form(array (‘title_reply’ => __(‘Leave a comment’, ‘mytextdomain’))); ?> Or use WordPress translation: <?php comment_form(array (‘title_reply’ => __(‘Leave a comment’))); ?>
I have my own implementation of twig in WordPress as plugin and my translations are working. You can check my code. Keep in mind couple of things when when you will test the code: be sure that your WordPress have set locale which you want translate to be sure that you your mo file is … Read more