When you use _e your echoing the translated string. But you already have an echo so just use __(. This is the correct code for your example echo ‘<h1>’ . __(‘September’, ‘simultan’) . ‘ ‘ . $day . ‘</h1>’; If you want to add variables in your translations you should use sprintf like this: $date … Read more
Yes, Recent Tweets Widget is one of the many plugins which their translations are managed through translate.wordpress.org, and this means that upon installing the plugin (*remember, installing and activating are different), WordPress (on your site) will automatically download the plugin’s language pack (.po and .mo files) from translate.wordpress.org, and then store the translation files in … Read more
Based on a previous Q&A, How to get current get_post_types name?, you could use get_post_type_object() to get the whole post type object, which will have the translated name in it. $post_type_object = get_post_type_object(get_post_type()); if ( $post_type_object ) { echo esc_html( $post_type_object->labels->singular_name ); }
The use of each depends on your choice. If, for example, the text is in front of a field, I think it is better to use the symbol: In general, you should see if it really needs it or not. You do not have to use it or not. In the text you sent, the … Read more
Based on your comment: The html generated by the widget? That one just shows the Strings in the _e function for eg: _e(“Category”) displays “Category” I suspect that you’ve not configured your translation strings properly. You need to include the textdomain in every translation string function call, or else the strings will never get translated. … Read more
Have you added the Function load_theme_textdomain to the theme? so if you have them themes .mo files in theme/mytheme/languages Loads the theme’s translated strings: add_action(‘after_setup_theme’, ‘my_theme_setup’); function my_theme_setup(){ load_theme_textdomain(‘my_theme’, get_template_directory() . ‘/languages’); } Put this in your functions.php
It is only a design for one site and won’t be a theme anyone can use and hence I don’t want to bother with internationalization. If the theme will only ever be used by you, internationalization isn’t a huge deal. Unless, of course, you will want to use a different language version of your theme … Read more
The translation strings not only get parsed during rendering (output on screen/in browser), but also by the GNU gettext parser. This one is not a PHP parser, so it can’t fetch variables. This is the only part of a Theme or a Plugin, where you need to repeat yourself and add the plain string to … Read more
A .mo file is the machine readable Version of a .po file, which in turn holds the translation of a .pot file. Hence, the latter is what you want to have in the first place. And if it is your theme you want to localize, you certainly do not need a random plugin’s simplified Chinese … Read more
What would be the easiest, cheapest approach for this? Simple, create one form per language. In functions.php or, preferably, as a custom plugin: add_shortcode( ‘my-lingo-form’, ‘shortcode_wpse_98360’); function shortcode_wpse_98360() { $lingo = your_language_detection_method(); switch( $lingo ) { case ‘en’: echo do_shortcode(‘[form-en]’); break; default: echo do_shortcode(‘[form-other-languages]’); break; } } In your post or page: [my-lingo-form].