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
On BuddyPress Multilingual you can read: This plugin requires WPML. It uses WPML’s language API and hooks to BuddyPress to make it multilingual. You need to have WPML installed for BuddyPress Multilingual to function correctly. Also, Buddypress Multilingual is for Buddypress sites. If you want to make your WordPress site multilingual, my advice is to … Read more
Refer to the documentation for more details: http://codex.wordpress.org/Installing_WordPress_in_Your_Language Skip the first two steps and the backend won’t be translated. 1) Download the Italian version of WordPress. 2) Upload the files located in /wp-content/languages/ to your live site. These files are for translating the Backend. 3) Define the language in wp-config.php as define (‘WPLANG’, ‘it_IT’);. Before … Read more
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
For people, as me, that comes to this thread, looking for a solution, pll_get_post() is your function. I think this is the easiest solution for this problem. $the_translated_page = get_page_by_title( ‘Custom page’ ); $the_translated_page = pll_get_post( $the_translated_page->ID ); $the_translated_page_URL = get_permalink( $the_translated_page ); I’m pretty sure that this function (pll_get_post) was recently included in the … Read more
Use both: a specialized plugin and multisite. There are plugins doing that (I’m the developer for one, Multilingual Press, but there are others). The main advantage is indeed interoperability: you can activate language and theme specific other plugins per sub-site, you don’t get any data hidden in custom post types or post meta fields, and … Read more
Yes, it is possible to convert the nav menu container can be switched, some the content is switched.. To start see this link in wiki http://wiki.xiligroup.org/index.php/Xili-language:_navigation_menu and example child themes (link in readme.txt displayed in plugin pages)
In most cases you are better with using two different installations or two different sites on a network installation. The only use case for the plugins is when you need almost all of your content to be translated or when you need good control over what was translated and what wasn’t.