Yes, rename your pt_AR.mo to ar.mo and pt_FR to fr_FR.mo. In step one install but not activate yet the plugin Admin in English. Edit the plugin’s php script. Find line with en_US string and replace this string with fr_FR. Save and activate the plugin. Now your Dashboard will be in French. In step two remove … Read more
The easiest approach would be to have custom fields on the edit page: one text field for every language you want to use (and perhaps different title fields?) For this you could use a plugin like ACF. This would provide an easy interface for non-tech editors. Supposing you are building your own theme you can … Read more
I figured it out almost immediately after asking the question, after months of frustration. The issue was I was using the load_textdomain function (which was the way I learned it) instead of the apparently newer/favored load_plugin_textdomain. The working code looks like this function rsvpmaker_load_plugin_textdomain() { load_plugin_textdomain( ‘rsvpmaker’, FALSE, basename( dirname( __FILE__ ) ) . ‘/translations/’ … Read more
1) Presuming you’re running WordPress 4.x. The WPLANG constant does nothing. WordPress 3 and below defined the default language in wp-config.php but since WordPress 4 setting your site language is done via the General Settings page in your admin area. Go to Settings > General and scroll to the bottom where is says “Site Language” … Read more
Anyway, I found my answer. I used qTranslate to translate menu wordings as well as widget titles. Free & useful.
What I have seen in translation plugins (qTranslate, WPML, Multilingual Press) are two approaches. One is qTranslate’s (and the defunct xLanguage): use one field (one for title, other for content, etc) to hold all translations. And then, in the front end, decode its output according to the actual language. <!–en–>English<–:–><!–es–>Español<–:–> In the back end, the … Read more
You shouldn’t be using a constant (in your case CORE_THEME_NAME) for the textdomain. This is because the call to __ is parsing your code, not running it. Simply said: it’s not looking up the value of the constant. So, it won’t translate. Quoting the famous Otto: Inside all translation functions, no PHP variables are allowed … Read more
From the source code of load_plugin_textdomain it becomes appararent that the function will first look for $domain . ‘-‘ . $locale . ‘.mo’ (so, that’s myplugin-fr_FR.mo) in WP_LANG_DIR . ‘/plugins/’ . $mofile. Only when the file is not there, it will start looking at the specified path and if it is not there in the … Read more
(this kind of issues is part of why my standard recommendation is to not have front end with two languages) The core reason to the problem is that your ajax returns text. AJAX should be treated like API which provide machine level values which the front end translate to human text. When your code is … Read more
What I normally do when using this combination of plugins is to create one form per language. Easy and effective. You could also try qTranslate quicktags: [:en]English text[:ru]Фамилия. But much probably this will lead to some issues down the road.