Is it enough to just create a child-theme – let’s say technically without adding anything else but the bare minimum style.css – to have the translation of the parent-theme being used automatically for the child-theme as well? Basically, the answer is NO, … but… there’s an option: Add a mu-plugin. This (MU-)Plugin does several things: … Read more
quick-and-dirty hint to solve this problem: find the function list_translation_updates() in wp-admin/update-core.php $updates = wp_get_translation_updates(); if ( ! $updates ) <- locate the if … } else { <- add this print_r ( $updates ); } add the else-case and save the file reload the dashboard page and you will get the desired information.
You can use the tool POEdit to translate your theme from scratch or update/add new strings into the .po/.mo files. Here is the tool usage tutorial: Translating_With_Poedit There is a plugin that can do the job for you: codestyling-localization STEPS: 1. Load a text domain for the theme. add_action(‘after_setup_theme’, ‘my_theme_setup’); function my_theme_setup(){ load_theme_textdomain(‘mytheme’, get_template_directory() . … Read more
Step 1 Open your file in PoEdit. Step 2 Go to “Catalogue” » “Settings“ Step 3 Fill in “Language” and “Country” 1). Step 4 Fill “Pluralform” (last field). // For 2 plural forms nplurals=2; plural=n != 1; // For 3 plural forms (for e.g. russian), use: nplurals=3; plural=(n%10==1 && n%100!=11) ? 0 : ((n%10>=2 && … Read more
When adding _x to the keywords, try it this way: _x:1,2c This tells the parser to watch out for _x and to take the first argument as msgid and the second argument as a comment, which will then be recognized as context by poEdit and inserted as msgctxt. Oddly enough, my poEdit then shows me … Read more
Install the plugin WP Native Dashboard. Then you can set one language for the front-end in your wp-config.php and each user can choose another one for the back-end. See Change language of comments template for details and a screenshot.
Download your languages files from the SVN repo… I would strongly advise against this. The repo, as storage of language files, is being discontinued, in favor of Translate WordPress. Right now, you have no guarantees that the repo has a current version of the file. The current method of getting language files is either to … Read more
Since esc_html_e will escape HTML link (hence will show the HTML anchor as plain text), you’ll need to segment the text and escape the non-HTML part with esc_html_e or esc_html__, and print the HTML LINK part without HTML escaping. Method-1 (just for your understanding): You may do it in parts, like this: esc_html_e( ‘Dear Guest, … Read more
TL;DR: If you use strings that are in the parent theme, exaclty how they are used in parent theme, you don’t need to have a text domain for your child theme. But if you use strings that aren’t used in parent theme, to make them translatable, you’ll need another text domain with related translation (.mo) … Read more
I just found the answer and instead of putting this in the Title: <!–:en–>My English Title<!–:–><!–:fr–>My French Title<!–:–> We need to put this code: [:en]My English Title[:fr]My French Title and qTranslate does the rest 🙂