For plugins using the directory referred to by load_plugin_textdomain, the language files should be named “domain-locale.mo”. So for your case, the filenames should be mysignup-bn_BD.mo.
I maintain WordPress Bengali project and yesterday I pushed the 3.9 translation update from bn.wordpress.org. You are right, there are no 3.9.x branch there so it’s pretty much not clear to me as well. Here’s how it works: we should always translate from the Dev version. When a new release comes, there is a SVN … Read more
Modify your installation such that your custom Farsi language files are associated with a non-standard WPLANG value. For example, instead of the standard ‘fa_IR’, maybe try something non-standard like ‘farsi_IR’ (or even ‘myCustomFarsi_IR’). This way, when new WordPress versions are released for the “official” Farsi version, you will no longer get updated.
So to make plugin translatable via translate.wordpress.org you need to add text domain into main plugin’s file: /* * Plugin Name: My Plugin * Author: Plugin Author * Text Domain: my-plugin */ So to make theme translatable via translate.wordpress.org you need to add text domain into main theme’s file: /* * Theme Name: My Theme … Read more
Check the following function in your plugin: load_plugin_textdomain (); and be sure that the directory to languages folder is correct. This fixed the issue for above question.
I do not know direct answer on your question but this maybe helps you. You can use plugin Loco translate or you can do it manually like this. _e( ‘Search’, ‘name_tag_of_translation’ ); Then go in wp-content/languages and there define what is you translation, in your case we talk about plugin, so you go: wp-content/languages/plugins and … Read more
I did manage to solve this later on by using WPML, but over time found that WPML is quite bloaty and slow, support not very good, and if you need only 1 language (but original strings for theme are in English and the language you need is not) or perhaps 2, you do not need … Read more
Is it worth having two plugin textdomains – one for admin area strings and another one for “frontend”? In theory yes Does it break any guidelines (the plugin is public)? glotpress which drives the wordpress.org translation section is unlikely to ave any of it. For it you have to use only one text domain which … Read more
(Revised answer) The simple answer is because WordPress could not find the MO file, despite the file itself exists (in the plugin’s languages directory). And here’s why: The MO file needs to be named following this format: {text-domain}-{locale}.mo, and {text-domain}-{locale}.po for the PO file. See Loading Text Domain for further information. So you’re trying to … Read more
WordPress is community translated. For a good number of languages, the translation is relatively complete and follows high quality standards. The codex page on WordPress in your language reports: WordPress in Urdu – اردو is ongoing, but slow. Need more contributors. So in essence: No, WP is not entirely translated to Urdu yet. You could … Read more