You’ve got two options: In wp-config.php, set $text_direction = “rtl”; If you’ve defined your own .po or .mo translation file for Pashto (is there really not one already?) there should be a string to translate value: ltr context: text direction Set the translation to be “rtl”. If that’s the user’s loaded locale then that will … Read more
Whew – Ok I figured it out. First off thanks Pippin and Peter. The problem is that it apparently confuses some wp plugins if a specific collate hasn’t been declared in wp-config: /** Database Charset to use in creating database tables. */ define(‘DB_CHARSET’, ‘utf8’); /** The Database Collate type. Don’t change this if in doubt. … Read more
Not the first line but the last line could be it. Please check if you have a space after the last ?> sign of your header.php file. Its better suggested that you just remove the last ?> sign as well. So there wont be any headers already sent error generated. And this sort of error … Read more
Well use translation plugin (multilingual Plugins)to create page in english and gujrati. There are a few basic types of multilingual Plugins: 1 Manage multilingual posts in one post per language (e.g. WPML – paid, xili-language, Polylang or Bogo). Translations are then linked together, indicating that one page is the translation of another. 2 Store all … Read more
The localized version is the English version translated. It contains the original and translated strings. You should look for missing translations or badly translated strings. Use a desktop tool like PoEdit or a plugin like Codestyling Localization to manage your WordPress, Themes and Plugins translations (the localized .po and .mo files).
You are making wrong assumption here. define(‘WPLANG’, ”); doesn’t mean “original locale of the string” or anything like that, it is taken literally as “no locale specified”. And when it’s nothing WP proceeds to assume default locale, which is en_US. This is why as soon as you add English translations of string they are displayed … Read more
I dealt with this writing a custom template tag. You may want to adjust the structure and classes in order to fit the needs of your styling: function mysite_languages() { if ( function_exists( ‘icl_get_languages’ ) ) : $languages = icl_get_languages( ‘skip_missing=N&orderby=KEY&order=DIR&link_empty_to=str’ ); if ( ! empty( $languages ) ) : echo “\n<ul class=\”languages\”>\n”; foreach ( … Read more
I can separate my answer to two sections Recommended: A bit about the translation plugins Nothing wrong if you use Polylang, WPML or QTranslate or other, those plugins are widely used and are for that purpose, also actively maintained. Also, those plguins support Arabic language very well. Switching posts Plugins like Polylang, WPML and other … Read more
You can use a filter to modify the value before it is set function __language_attributes($lang){ // ignore the supplied argument $langs = array( ‘en-US’, ‘KO’, ‘JA’ ); // change to whatever you want $my_language = $langs[0]; // return the new attribute return ‘lang=”‘.$my_language.'”‘; } add_filter(‘language_attributes’, ‘__language_attributes’); Then just make sure your theme header has the … Read more
You already have it in the code: __( ‘Your message will only be visible after manual moderation’, ‘your_text_domain’ ) __ is a translation function and part of the static string translation system in WordPress core. Polylang might allow you to translate dynamic content, but __() and its friends are for static strings. These use the … Read more