If you go to http://bit.ly/QdBvJ9 (link obscured so this isnt the first thing to show up when the new site is searched for) and click on japanese in the top left corner, it shows the japanese page with this showing up: <!--[if gt IE 8]><!--> <html class="no-js" lang="ja" dir="ltr"> <!--<![endif]--> but the actual content remains in English, other non-latin languages like हिन्दी work fine but Japanese doesnt. I have no idea why this is happening. If you need anymore info i'll be happy to provide it. P.S. QTranslate is also enabled on this site, disabling it had no effect. Using WP 3.4.2 and the latest Transposh.
EDIT: DEBUG SHOWS THIS:
Notice: Undefined variable: cache_wptouch in /home/content/34/8802234/html/sarvatma/wp-content/plugins/wp-super-cache/plugins/wptouch.php on line 109
Warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at /home/content/34/8802234/html/sarvatma/wp-content/plugins/wp-super-cache/plugins/wptouch.php:109) in /home/content/34/8802234/html/sarvatma/wp-content/plugins/transposh-translation-filter-for-wordpress/transposh.php on line 513
Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/content/34/8802234/html/sarvatma/wp-content/plugins/wp-super-cache/plugins/wptouch.php:109) in /home/content/34/8802234/html/sarvatma/wp-content/plugins/transposh-translation-filter-for-wordpress/transposh.php on line 513
Notice: Undefined variable: google_font_link in /home/content/34/8802234/html/sarvatma/wp-content/themes/sarva/header.php on line 42
Notice: Undefined variable: before_widget in /home/content/34/8802234/html/sarvatma/wp-content/plugins/transposh-translation-filter-for-wordpress/wp/transposh_widget.php on line 266
Notice: Undefined variable: after_widget in /home/content/34/8802234/html/sarvatma/wp-content/plugins/transposh-translation-filter-for-wordpress/wp/transposh_widget.php on line 342
$var['foo']when there is no key'foo'. They are probably not the cause of your problem. I guess there is an encoding problem somewhere, maybe an overly optimistic regex … but I have to pass on this. Let’s see what other members say. – toscho♦ Sep 10 '12 at 1:16