You can filter ‘gettext’. Sample code, not tested: add_filter( ‘gettext’, ‘wpse_65085_change_error_messages’, 10, 3 ); function wpse_65085_change_error_messages( $translated, $text, domain ) { if ( ‘default’ !== $domain ) { return $translated; } switch( $text ) { case ‘Hint: The password should be at least seven characters long. To make it stronger, use upper and lower case … Read more
You can make changes to the translation, yes, but it’s not as simple as editing the text inside the fi.po file (or any PO file, for that matter). That’s because WordPress actually uses another file, with an .MO extension, to render the translations. That extension is not meant to be read by humans, so you … Read more
Localize WordPress or write and load special localization for your language specialy for thickbox. Thickbox dialogs support localization provided by WP Update – Let’s Check 1. You have uncomented string <code>define(‘WPLANG’, ‘pl_PL’);</code> in your wp-config.php 2. You have localization files in wp-content/languages/
There are a couple of things you can do: Paid solution. you pay for the updates and support. WPML, is very nice and compatible with a lot of plugins. It has a language switcher in a widget and has a shortcode which you can use to place the language switch. Free solution. Q translate gives … Read more
I guess you could use either HTML5 or IP based geolocation, set a current_language cookie and you are good to go. Or even better if you just simply ask the user about it. WordPress translation is not equal to multi-language by any means.
I don’t remember doing it in practice, but from quick look at documentation there is a load_child_theme_textdomain() function for precisely that. Once you use it with your copy of translation (note that timing and such, as per documentation) your changes should override parent theme’s version.
The current WP versions expose interface for this and store locale in WPLANG option. Depending on your tools you could set it up during your spin up process (for example with WP CLI). Older version used WPLANG constant in wp-config.php. I think it should still work on a fresh install (if you don’t have option … Read more
You can filter mu_dropdown_languages and re-add American English here. Sample code, not tested: add_filter( ‘mu_dropdown_languages’, function( $output, $lang_files, $current ) { array_unshift( $output, ‘<option value=””‘ . selected( $current, ‘en_US’, false ) . ‘>’ . __( ‘American English’ ) . “</option>” ); return $output; }, 10, 3 ); Filter sanitize_option_WPLANG or pre_update_option_WPLANG to jump into the … Read more
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.
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.