The issue is, there is no value for local_package in the URL. At first I thought this might be a bug. Similar issues have been reported before (see here and here. I then stumbled on comment in trac ticket 8729 where user nbachiyski explains how localization should work: There are two ways to localize WordPress: … 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.
This is not a problem if every string gets its own template for translation. If you use the string You can include a %s in a childtheme. more than one time for different nouns it is not translatable. An example, taken from a recent article: New %s is in German (yes, we have gendered nouns … Read more
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
To find the answer to this question, you just need to look at how WordPress retrieves the translations. Ultimately it is the load_textdomain() function that does this. When we take a look at its source we find that it creates a MO object and loads the translations from a .mo file into it. Then it … Read more
Never rely on core strings for translation, they may change or get a context parameter any time. Once that happens your users get a partially translated interface, and your translators have no way to fix that. Also keep in mind the same string is not necessary translated everywhere with the same word. Even without a … Read more
__ (double underscore) is the base translate function. It translates a string and returns it as a string. _e does the same as __, but echo’s the result immediately. _x is the contextual translate function. It has a second option to provide context to people doing the translation. _ex is the same as _x, but … Read more
It’s used for translate text. The second argument is a kind of namespace (called domain here) to retrieve the translation (for example from a dedicated file or something else). So Anyword here, should be the guy behind the template, or the company or what ever that can be a domain/namespace. edit: The doc from wordpress … Read more