Your code use load_theme_textdomain. If you are in child theme and need to load translated strings, use function load_child_theme_textdomain. Please take a look this answer too Override parent theme translation on child theme.
You should use placeholders: $time = sprintf( ‘<i class=”fa fa-clock-o” aria-hidden=”true”></i> %s: <time datetime=”%s”>%s</time>’, esc_html__(‘Posted on’, ‘textdomain’), get_the_time(‘Y-m-d’), get_the_time(‘j F Y’) );
You have to make these strings translatable by using __() function: comments_number( __(‘Comments (0)’), __(‘Comments (1)’), __(‘Comments (%)’) ); If you want to use the custom textdomain, e.g. ‘test’: comments_number( __(‘Comments (0)’, ‘test’), __(‘Comments (1)’, ‘test’), __(‘Comments (%)’, ‘test’) ); For more information see: __() Theme internationalization Very good article by Samuel Wood a.k.a. Otto: … Read more
I have written a function that will convert the qtranslate-x string into array of language and based on that you can use a particular language. /** * This function breaks q-translate string into array per language. * * @param – {string}$content – the q-translate string Eg : [:en]Title in English[:fr]Title in French * @return {array/bool} … Read more
Wrap the elements of $search and $replace arrays into __() function to get the translated strings: function search_replace_search() { $search_term = esc_attr( apply_filters( ‘the_search_query’, get_search_query( false ) ) ); // Get search term $search = array( __(‘word1’), __(‘word2’) ); $replace = array( __(‘something 1’), __(‘something 2’) ); $replacePairs = array_combine($search, $replace); echo strtr($search_term, $replacePairs); } … Read more
to use the file wp-content/languages/plugins/albdesign-wc-donations-uu_UU.mo in the plugin, it has to be declared like that : load_plugin_textdomain(“albdesign-wc-donations”); // search in wp-content/languages/plugins/ // search in the plugin files if not found in wp-content/languages/plugins/ load_plugin_textdomain(“albdesign-wc-donations”, FALSE, plugin_dir_path(__FILE__) . “languages/”); is it’s not the case, you can create another plugin to correct that loading of the translations files
You can try like adding content in this format in Widget title/text content. [:en]My English Title[:fr]My French Title and on echoing this.. q-translate will make them work .
It turns out the text domain has to match the plugin slug on wordpress.org. After changing the plugin text domain to multi-google-analytics the notice went away.
There are three usual possibilities: Translation files somewhere in theme’s directory. Translation files in site’s directory, defined by WP_LANG_DIR constant (typically wp-content/languages). Theme’s original strings are in different language, so that is its default state and it needs to be translated to English.
Added to the functions.php the next: $pather = get_stylesheet_directory().’/languages’; load_child_theme_textdomain( ‘Savia-child’, $pather ); And then called it as: __( ‘text to translate’, ‘Savia-child’); In the child theme I have created a dir: /languages and put there po and mo files with the names: [locale].po/.mp like: ru_RU.po and ru_RU.mo. That is.