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
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
Seems like the right thing to do there is to call esc_html instead of esc_html__. I have a feeling you don’t need any escaping there at all.
The default language of WordPress is always English (en-US). Regardless of what your site language is set to. This is what the entire WordPress community expects for the language of source strings, and how many translation projects for WordPress will be set up too. So yes, it is bad practice to choose use different source … Read more
Start a new theme from scratch to see if you have the same result. I test with theses files and the translation works style.css /* Theme Name: My Theme */ functions.php <?php add_action( ‘after_setup_theme’, ‘my_theme_load_theme_textdomain’ ); function my_theme_load_theme_textdomain() { load_theme_textdomain( ‘my-theme’, get_template_directory() . ‘/languages’ ); } languages/es_ES.po (file languages/es_ES.mo created with poedit) msgid “Featured” msgstr … Read more
Apply to become a translator If you want to provide your own translations, you have to post a request at https://make.wordpress.org/polyglots/ stating which languages you want to translate yourself, so this implies that you actually speak those languages fluently. This is what I have done and what I will describe in this answer. But if … Read more
None of them are correct. These APIs are not intended for dynamic data or content in the database. This would be the best practice answer: echo ‘<h2 class=”title”>’; esc_html_e( ‘static string’, ‘text-domain’ ); echo ‘</h2>’; If you want to translate posts and other database user entered content, use a translation plugin, not the localisation API. … Read more
You need to do “msgfmt” using the command line tool to convert the .po to a .mo, that is what WordPress (and all gettext compliant software) uses.
Localizing a string with html markup inside the string can be a very opinionated story as you can see from one of my questions when I started out. I would not say you are right, neither would I say that you are wrong, but I would say that your method is not prefered. If you … Read more
load_theme_textdomain() needs an absolute path to the directory, so you should set your THEME_URL like so define(“THEME_URL”, get_template_directory()); define(“TRANSLATION_URL”, THEME_URL . “/languages”); It wasn’t working for you because get_bloginfo(“template_url”) is an URL and not an absolute path on your server.