Should such messages be localized at all or are they out of scope for localization? Yes, they should be localized … but don’t depend on the text returned by the API. Does something like __( $message ); even make sense? Not really. First of all, you’re not providing a text domain for the string to … Read more
Interesting questions, I’ll try my best, but I hope others can also give input. re 1. Usually I use the theme’s text domain also for strings that are likely to be present in the main WordPress translation file re 2. correct re 3. I think it is a good idea, but I don’t know if … Read more
I would opt for readability and use a rather verbose solution: if ( 1 == $hours and 1 == $mins ) { _e( ‘One hour and one minute’, ‘your_text_domain’ ); } elseif ( 1 == $hours ) { printf( __( ‘One hour and %d minutes’, ‘your_text_domain’ ), $mins ); } elseif ( 1 == $mins … Read more
You could hook into the action switch_blog. You get the new blog ID as the first argument here. But loading the complete translation files here is expensive, you also have to restore the old files after that. WordPress does not use native gettext functions, but some custom code that is much slower. See #17268. The … 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
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