One error: the function is load_theme_textdomain(), not load_textdomain(). The former is used for Themes to define/load a textdomain; the latter is for core, I believe. (Plugins have an analogous function, load_plugin_textdomain().) Try using: load_theme_textdomain( get_theme_text_domain(), get_template_directory() . ‘/languages’ );
Just add the full string of the plugin name into the plugin’s text domain. WordPress looks this up automatically. Same with Description, PluginURI, Author and AuthorURI. See the internal function _get_plugin_data_markup_translate. The string extractor in Glotpress (and my own plugin Loco Translate) adds these header strings automatically to new POT files.
To set a specific language in a multi-site the language files must be available in the language directory, usually in wp-content/languages. So if you want to set the language to ja_JP a file ja_JP.mo must exist there. You can get the language files from the SVN repository.
Single translation for many locales
WordPress doesn’t quite have a practice of localizing something that isn’t core/plugin/theme. My educated guess would be that it will work just fine with same concepts, but you will have to write custom loading logic. Use lower level load_textdomain(), since higher level functions are meant for plugins/themes specifically. As long as you determine and load … Read more
Well, actually, you should view your site as requiring “multilingual” capabilities, even if the base language for both countries is identical, because the actual locale for each is nevertheless different. More specifically, you can create variant “translations” for your British (‘en_GB’) and Irish (‘en_IE’) localizations. A plugin such WPML (WordPress Multilingual) can help you implement … Read more
Best way would probably be to use the built in Internationalization function in WordPress. This will then translate according to the language pack being used. The “U” character to a date() call gives the unix timestamp, which is just what you need in this case, for passing to date_i18n(). For example: echo date_i18n(‘j F Y … Read more
$plugin_path = dirname( plugin_basename( __FILE__ ) ) . ‘/languages/’;
Singular name Plugin localization
if I have said string in comments.php in line 60, and move it to line 74, does it still get localized by the msgid? Yes it does. Localization does not depend on line numbers of strings.