Multilingual support in the Content Library
Summarize
Summary of Multilingual Support in the Content Library
The Content Library offers multilingual support through two primary features:Translate contentfor initiating translation workflows andSwitch languagefor altering the interface language. This functionality enhances user accessibility and content reach across different languages.
Show less
Key Features
- Switch Language: Allows content creators to change the language of the Content Library interface, similar to system language settings.
- Translate Content: Enables the initiation of a translation workflow for various content types, except Calendar content. The process creates localization request items for each selected language and assigns tasks to users with the localizationfulfiller role.
- Localization Workflow: Content managers can monitor the status of localization requests, and upon completion, schedule the content for publishing using the same content schedule for both original and translated versions.
- Language Status Indicators: The Switch language window displays the status of available languages as Base language, Translated, or Not translated.
Key Outcomes
By leveraging these multilingual capabilities, ServiceNow customers can efficiently manage and publish content in multiple languages, improving accessibility for global audiences. It is essential to switch back to the original language before leaving the page to maintain the correct interface language. Additionally, customers using non-English languages may need to turn off Content versioning or enter initial content in English before utilizing the translation feature.
The Content Library includes two features for multilingual content creation: Translate content (content translation workflow) and Switch language (changes the interface language).
Switch language vs Translate content
- Switch language
- The Switch language option enables content creators to change the language of the Content Library interface (similar to changing the system language setting).
- Translate content
- The Translate content option sends the content for translation in the specified language.
Translating content in the Content Library
- The Content manager requests content translation from the Content Library or Block content interface and specifies the languages.
- The system creates a localization request item (prefix LRITM) for each language selected. Each localization request item has an associated localization task (prefix LFTASK), which is assigned to the user or group with the
localization_fulfiller role.
The Content manager can view the status of the localization request item from the list.
- The user with the localization_fulfiller role performs the translation. For more details, see Fulfill a localization task.
- When the localization request item has a
Closed completestate, the Content manager can schedule the content for publishing, see Create a publish plan for your content. The system uses the same content schedule for the original and translated content.
Changing the Content Library interface language
- Base language
- The default language based on system settings.
- Translated
- Indicates that translations are available for the content. This occurs when the content has been translated through the Localization Framework or manually translated in the New Content form fields.
Selecting this option will translate both the interface and the values entered in the New Content form to the chosen language.
- Not translated
- Translation for the field values is not available. In this case, only the interface language is translated, while the values entered in the form remain unchanged.
Content versioning and translation
When content versioning is enabled, the Switch Language button appears only for the first draft version and published content.
- Turn off Content versioning, then click the Switch Language button to enter the content in a non-English language.
- Enter the content in English, then use the Translate Content button to initiate the translation workflow.
For more information, see Content versioning.