Translations

  • Updated

Language editions are saved onto separate language sections. The translations tool is used to translate the web site onto another language.

loggedin1000.png

The language edition is chosen from the language menu in the upper right-hand corner, which displays the language currently used. The content can be translated when at least one language edition has been created into the CMS.


Page translations

pages_translations_15_8.png

Begin translating by choosing the page and pressing the Translations button. Here you choose the language you want and click Translate to ... button.

translatetoto.png

Type the translated page title into the pop up window and choose visibility. It is recommended to choose Hidden before the page is completely ready. Both the title and visibility can be changed later. It is recommended that the translation is Press Translate. LianaCMS then directs you to the translated language version's Sections tab.

The Translate button in the upper right-hand corner shows the language that is in use. The page has been copied for the language that it is to be translated in. The content and sections have been copied as well, so that they can be used as the basis for translation. The other sections can be translated by selecting Modify sections, choosing a section and translating its content.


Category translations

You can start translating a category by clicking the name of a category on the Categories page and choosing Category settings. This category's language version is written at the section of the chosen language.

The additional properties of the product's language edition are visible on the Category Properties tab. The content of the property can be defined so that it will be copied from another language. In this way, for example, the same image can be found on every version.


Contact translations

A contact is automatically displayed in all the language versions. Properties are translated by choosing a language from Property language.

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.