I’m not 100% sure this is the only issue that was preventing POEdit from correctly parsing my code (I’m not sure it actually cares about the WordPress side of things), but fixing these (stupid) errors and re-running POEdit from the .pot file below seems to have generated the correct translation strings: define( ‘MY_TEXTDOMAIN’, ‘MY_TEXTDOMAIN’ ); … Read more
Do i have make the content() also translation ready in theme? Short answer – No. 1). Content held in the database is generally not translated via static files. That includes post content and other user-defined data like taxonomies. As a theme developer, you only need prepare static text for translation. This should include any visible … Read more
After a heavy investigation, I understood what is happening. The solution to debug this was partially here but there were some php errors that´s why I got a blank page. So, after to test : Which language is called thanks with get_locale() Display WP_LANG_DIR to know where are language files are stored I tried to … Read more
I maintain WordPress Bengali project and yesterday I pushed the 3.9 translation update from bn.wordpress.org. You are right, there are no 3.9.x branch there so it’s pretty much not clear to me as well. Here’s how it works: we should always translate from the Dev version. When a new release comes, there is a SVN … Read more
So to make plugin translatable via translate.wordpress.org you need to add text domain into main plugin’s file: /* * Plugin Name: My Plugin * Author: Plugin Author * Text Domain: my-plugin */ So to make theme translatable via translate.wordpress.org you need to add text domain into main theme’s file: /* * Theme Name: My Theme … Read more
I do not know direct answer on your question but this maybe helps you. You can use plugin Loco translate or you can do it manually like this. _e( ‘Search’, ‘name_tag_of_translation’ ); Then go in wp-content/languages and there define what is you translation, in your case we talk about plugin, so you go: wp-content/languages/plugins and … 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
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
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