well , while dealing with chinese characters – there are MANY problems that can cause this , but many times , it is as simple as the encoding of the php files. (simple as a figure of speech – you will soon understand why ) A PHP file is a TXt file . and even … Read more
In your wp-config.php set the encoding constants correctly: define( ‘DB_CHARSET’, ‘utf8’ ); define( ‘DB_COLLATE’, ‘utf8_general_ci’ ); And add an accept-charset attribute to your form: <form name=”frm” method=”post” action=”<?php bloginfo(‘url’); ?>/message/” accept-charset=”utf8″ >
Take a look at get_blog_permalink
The before_widget and after_widget notices can go away with ease if you send those as params to the function you are using to call the Transposh widget Update: recent version (0.9.0) fixed those notices
No matter what languages your site are in, when using WPML you should never install a localised WordPress version, instead you should just install the default one (i.e. US English). Also make sure that you didn’t change the LANG definition in your wp-config.php file, so that should read: define (‘WPLANG’, ”); Then you need to … Read more
Use WordPress i18n functions. Normally good plugins are translation-ready, and you should create your translation files for that plugins (if not already present). Explain how to is too much for this answer, start looking at Codex page linked above, search Google and also have a look here. If a plugin is not translation-ready use another … Read more
2 notes regarding your own answer: try to not access on super global variables directly, but using filter_input your code throw a notice if $_GET[‘lang’] is not set So your code can be improved: function toscho_change_language() { return ‘bn_BD’; } if ( filter_input( INPUT_GET, ‘lang’, FILTER_SANITIZE_STRING ) === ‘bn’ ) { add_filter( ‘locale’, ‘toscho_change_language’ ); … Read more
I have used Polyang in the past which works nicely for manual translations. Here is a guide that covers it.
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