Toolset plugins and WordPress Multilingual plugin (WPML) all come from the same team, so multilingual functionality comes standard. Using WPML, you will be able to translate everything that you build in Toolset. In this tutorial, we will explain what you can translate, where it appears, and how to translate it.
To build fully multilingual sites with Types, Views, Layouts, CRED and Access, you will need WPML core plugin and WPML String Translation and WPML Translation Management add-ons, which come with the Multilingual CMS package.
You should configure WPML’s Theme and plugins localization to translate with WPML. In this mode, the .mo files are still loaded, but you can also translate using WPML’s String Translation.
|How to prepare the site to run multilingual||You will need to install and configure the required plugins. Then, you need to choose which post types should be multilingual. Finally, set slugs per language for the post types.|
|Translating the content editing interface||This is needed when you want to run the WordPress admin in different languages, typically for users who each speaks a different language. You will translate the texts that editors see in the admin when writing or editing content.|
|Translating the content||You will translate the actual posts with their fields and taxonomy terms. The translated content will appear both in the WordPress admin and on the front-end.|
|Translating Layouts||You will translate the texts that appear in the site’s layouts, so that the layouts display correctly in different languages.|
|Translating Content Templates, WordPress Archives, Views, and CRED forms||You will prepare all the front-end displays that Toolset generates to show in the correct language.|