If these theme strings are prepared for translation and the theme is not in english by default (they’re outputed with __() or _e() functions) and you include your theme textdomain correctly, then you probably haven’t translated these strings to english. WPML had/has some tool to do this, but it isn’t very user-friendly (at least I … Read more
The correct string is ‘← Back to %s’. The site name is inserted after the translation. See the function login_footer() for details.
I’d use printf to put the markup into place after the translation. You can force the order with the right modifiers, but translators are probably smart enough to not really need that. printf( __(‘The image %sMUST%s be less than %s500 KB%s in size.’, CUSTOM_TEXT_DOMAIN), ‘<em>’, ‘</em>’, ‘<strong>’, ‘</strong>’ ) ; I consider Otto’s post to … Read more
Turns out that wordpress uses context strings for this piece of text: _x(‘Add New’, ‘post’) and _x(‘Add New’, ‘page’) This is because the string ‘Add New’ is different depending on the following noun in some languages. i.e in Danish: ‘Add New Post’ => ‘Tilføj Nyt Indløg’ ‘Add New Page’ => ‘Tilføj Ny Side’. Notice the … Read more
You are exploding the text with explode( ‘ ‘, $ctxttext ). Therefore you are translating word by word, not strings. That is why it’s working with single word string, and not with multiple words. When you call First Name you are translating First and Name. Cheers
You are making wrong assumption here. define(‘WPLANG’, ”); doesn’t mean “original locale of the string” or anything like that, it is taken literally as “no locale specified”. And when it’s nothing WP proceeds to assume default locale, which is en_US. This is why as soon as you add English translations of string they are displayed … Read more
global $langOK; add_action( ‘plugins_loaded’, ‘myplugin_load_textdomain’ ); function myplugin_load_textdomain() { global $langOK; $langOK = load_plugin_textdomain( ‘my-plugin’, false, dirname( plugin_basename( __FILE__ ) ) . ‘/languages’ ); } Later you can check the value of $langOK ( TRUE = success, FALSE = failure ).
In lack of translation file the default strings from source code are being used. So if plugin is coded in US english then it just has that version in source and doesn’t need the translation for it. The native way to generate translation files in WP is makepot script, shipped with development version of WordPress … Read more
It’s sometimes easier to work with sprintf(): ‘Default’ => sprintf( ‘<img src=”https://wordpress.stackexchange.com/questions/213508/%s/admin/images/default.png” width=”120″ height=”80″ alt=”%s” />’, get_template_directory(), esc_attr__( ‘Default’, ‘my_theme’ ) ); where we use the esc_attr__() to return a translated value that’s safe to be used in an attribute, but I’m not sure what your THEMEROOT contains, so I just replaced it with get_template_directory().
Recheck your filter code closely. You are modifying $name but returning $status_name which is undefined. If you had debugging enabled, you should have seen the debug message telling you that $status_name is an undefined variable Simply change return $status_name; to return $name;