--- sourceDocument: Xanadu ServiceNow AI Platform Administration sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration Release : - xanadu ft:locale : - en-US ft:publication_title : - Xanadu ServiceNow AI Platform Administration ft:clusterId : - platadm bundleId : - platadm workflow : - Platform --- # Translating custom content # Translating custom content {#ariaid-title1} * Release version: Xanadu * * Updated August 1, 2024 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Translate content you create or modify to a supported language or add an unsupported language. Note: Using the Localization Framework application is recommend for translating to an unsupported language or translating large amounts of custom UI string content in a supported language. For more information, see [Localization Framework](https://servicenow-prod.fluidtopics.net/hWWbjrWLsHsFZGw_lOf5Hw "The ServiceNow Localization Framework application standardizes and enhances the translation process of artifacts across the platform through configurable workflows. Such artifacts include ServiceNow Service Catalog items, Virtual Agent topics, Natural Language Understanding models, and Document Templates of ServiceNow HR Service Delivery."). ServiceNow provides translations of the base system UI strings in supported languages through the internationalization (I18N) language plugins. For applications you create and modifications you make to the ServiceNow AI Platform® content, you must provide your own translations. You can also provide any translations to unsupported languages that ServiceNow does not provide translations for. The ServiceNow AI Platform does not provide any automatic translation capability. The translation method depends on the material that you are translating. Repeat the translation process whenever you edit or update content.{#translating-applications__table_xfh_rgr_f3b__entry__3} | What needs translation | Approach to take | Resources | |-|-|-| | Field labels in a table for a customer-created application | 1. Create English versions for all fields in the table. 2. Locate the records for the table in the application. 3. Open the Field Labels translation table. 4. Export the records, translate the appropriate fields, set the language field, and reimport through an import set. {#translating-applications__ol_s4m_fb1_2zb} | * [Export and edit translation records](https://servicenow-prod.fluidtopics.net/nw7FBFzmTHaJdlLlkrKW0w#t_TranslateTheInterface "Export translation records to translate to additional languages in your preferred translation environment and import the new or edited translation records through import sets.") * Alternatively, follow the procedure for translating individual labels in [Translate a field label](https://servicenow-prod.fluidtopics.net/LbwBOrPr_HniVtOFRWPAdg "Field labels are the names that appear on forms and lists to describe the type of information the field contains."). {#translating-applications__ul_png_nb1_2zb} | | HTML in a UI page in a customer-created application | 1. Create the English version. When creating the HTML in the UI Page form, wrap any translatable text in `gs.getMessage` calls. 2. Create a Message \[sys_ui_message\] record for each English message with a corresponding key/value pair. 3. Create additional Message records for each message for each other language. {#translating-applications__ol_epy_d5r_f3b} | [Translate a client script message](https://servicenow-prod.fluidtopics.net/ObgFIETPwBMtVZOsoagM0Q "Translate the messages used by client scripts.") | | Service Catalog items | 1. Navigate to AllSystem PropertiesSystem Localization and set Display translation prefix on translatable strings to Yes. 2. Create the item in English. 3. Change the preferred language to a different language. 4. Translate all the translatable items, now identified by translation prefix. 5. Save the record. {#translating-applications__ol_lcd_kbs_f3b} | * To activate translation prefixes, see [Debug translations](https://servicenow-prod.fluidtopics.net/4f7q~SHBu6sJE5zt7ax2yQ "Show which UI strings are translatable and their translation table to debug translations."). * For translatable text fields, which are common in Service Catalog items, see [Translating text fields](https://servicenow-prod.fluidtopics.net/zTLSvgK1GMisrbvrJChKnw#c_UseTranslatedText "Translate long pieces of text into the language of the user."). {#translating-applications__ul_gvr_pb1_2zb} | | Service Portal widget | 1. Create the English version. Externalize any translatable text by surrounding the text with` ${}` wrappers. 2. Create a Message \[sys_ui_message\] record for each English translatable text with a corresponding key/value pair. 3. Create additional Message records for each piece of translatable text for each other language. {#translating-applications__ol_psv_w5r_f3b} | * [Translate a client script message](https://servicenow-prod.fluidtopics.net/ObgFIETPwBMtVZOsoagM0Q "Translate the messages used by client scripts.") * [Internationalize a widget](https://www.servicenow.com/docs/access?context=c_WidgetLocalization&version=xanadu&pubname=xanadu-platform-user-interface&ft:locale=en-US) in Service Portal documentation * For unofficial advice, see [Building multi-lingual service portals](https://www.dylanlindgren.com/2018/11/07/building-multilingual-service-portals/) {#translating-applications__ul_umc_cpb_j3b} | | Edit a translation provided in a plugin | 1. Export the records from the translation table. 2. Edit them outside the translation table and reimport them. {#translating-applications__ol_j4c_hc1_2zb} Do not edit the records directly, because your changes could be overwritten when you upgrade or zBoot your instance. | [Export and edit translation records](https://servicenow-prod.fluidtopics.net/nw7FBFzmTHaJdlLlkrKW0w#t_TranslateTheInterface "Export translation records to translate to additional languages in your preferred translation environment and import the new or edited translation records through import sets.") | | Translate an instance to an unsupported language | 1. Create a Choice \[sys_choice\] record for that language. 2. Add other translation records through the Export and import set approach. {#translating-applications__ol_d34_nc1_2zb} | [Translating to an unsupported language](https://servicenow-prod.fluidtopics.net/8pd1J9fmPPy9Yf9eLa8p4A "Translate the interface of an instance to a language for which ServiceNow does not provide an internationalization (I18N) plugin.") | | Support Chat texts | Support Chat is mostly translated through the I18N language plugins. If you customize any Support Chat texts, follow the procedure for Service Portal widgets. | [Internationalize a widget](https://www.servicenow.com/docs/access?context=c_WidgetLocalization&version=xanadu&pubname=xanadu-platform-user-interface&ft:locale=en-US) in Service Portal documentation | | Notifications and surveys | System Localization does not cover platform notifications or surveys. The usual approach is to create a separate version of each survey or notification in each language and use business rules to send the right language version to the right end user. | --- | [Table 1. Translation methods and use cases] {#translating-applications__table_xfh_rgr_f3b} * **[Export and edit translation records](https://servicenow-prod.fluidtopics.net/nw7FBFzmTHaJdlLlkrKW0w#t_TranslateTheInterface)** Export translation records to translate to additional languages in your preferred translation environment and import the new or edited translation records through import sets. *[\>]: and then