After about 3 weeks of beta tests, Polylang 1.1 has just been released.
Old users will notice that the menus tab in Polylang settings has totally disappeared. All the multilingual menus management is now fully integrated in the WordPress interface under Appearance->Menus. Polylang multiplies the number of menu locations of your theme by the number of languages, to easily assign a menu to a theme location and a language at the same time. Moreover, the language switcher is now a menu item that you can use as any other menu item. It means that it can be placed anywhere you want, and can even be used in a submenu… The same options as before have been kept. All these seemlessly integrate in the new menu interface of WordPress 3.6 as well as in older versions.
Another change concerns the strings translations table. All translations are now assigned a group and users can filter the strings by group. Thus, it should be easier to find new strings to translate. It is also now possible to delete the strings registered in WPML compatibility mode.
Although less visible, numerous changes have been made to improve the compatibility with themes and other plugins. For example, some themes query a specific category for a specific usage (such as a slider). Polylang is now able to automatically query the translation of this specific category when it exists (It was sometime necessary to modify the theme to make it work with Polylang before this).
Again the compatibility with WordPress SEO has been improved (you must use pretty permalinks and add the language code to all urls to make both plugins work together in a correct way).
Thanks to all people who tested the development version and reported bugs before the final release. I will now go to modify the documentation to include the new features!