More-Lang

More-Lang provides two filters:

• 'morelang_front_cssurl', filters the css url styling the language switcher. Parameters: '$front_css_url', the built-in css url.
• 'morelang_flag_url', filters the flag icon urls. Parameters: '$img_src', the original url; '$locale', the current requested locale; '$position', where to be placed, it can be "menu" or "panel". After the release 1.8.5, you can also check "Do not use the default styles for the language switchers", then 'morelang_front_cssurl' filter is not needed.

• The "Enable compatibility with Plugins & Themes in some special cases" option provides solutions for some compatibility issues.
• If the plugin uses short codes, it's usually very simple: create short code for every language, then paste the short codes to the corresponding contents.
• The premium add-on More-Lang Pro provides support for WooCommerce, translations of options, and URI-map, etc.
• If the plugin uses widgets, try this way: find out the filters used for the texts, add your filter handlers in your theme to return localized texts.

More-Lang provides in-place editors as far as possible. If it does not provide in certain cases(i.e., the Name of any Custom Field, or the Name of any non-taxonomy Product attribute), you can translate in the "Translations" page, and in most cases(the only exception is the the_meta() function), you need to make code change to get the localized text, there are 2 approaches:

• Use the translating filter:   apply_filters('morelang_translate_text', $default_text)   .
• Use the translating function:   _ml_t($default_text, $any='')   . This approach is more concise. Its shortcoming is that it is a function, if you deactivate the More-Lang plugin, your site may fail. To avoid the fail, you can add a fallback function in your theme's functions.php file, e.g.:

The $any parameter is optional, _ml_t() doesn't use it at all. You can simply ignore it, or set it to the $domain of the Wordpress __($text, $domain) function, then if one day you would like to uninstall the More-Lang plugin, you can simply replace "_ml_t" with "__" to use the default approach of Wordpress.

• Implement the filter morelang_texts_to_translate (parameter: $arr), then More-Lang will fill the translation table with the texts returned by the filter, e.g.:

There's very good reason for not providing in-place editors for the Names of Custom Fields(and similar scenarios): the in-place editors can appear in many Posts, which can lead to inconsistent translation.

• No additional work is required for reordering the non-default languages.
• If you change the default language to another language after entering any content for either of the two languages, the link from the content to the language will be broken, you need to re-enter the content.
• No additional work is required adding new languages.
• No additional work is required for modifying all the fields except the Locale.
• If you modify a Locale after entering any content for the language, the link from the content to the language will be broken, you need to re-enter the content.

• The setting data is saved in the "wp_options" table, with "morelang_nml_option" as the option_name.
• The localized post title, post content, post excerpt, custom fields and menu items are saved in "wp_postmeta" table.
• All the other localized options are saved in the "wp_options" table.