{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":39710,"path":"platform-administration/system-localization/t_TranslateTheInterface.md","title":"Export and edit translation records","bundle":null,"doc_type":null,"release":"australia","body":"\n# Export and edit translation records\n\nExport translation records to translate to additional languages in your preferred translation environment and import the new or edited translation records through import sets.\n\n## Before you begin\n\n**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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/localization-framework/localization-framework-landing.md).\n\nRole required: admin\n\n## About this task\n\nIn the following cases, translate strings in the UI outside of the ServiceNow AI Platform and import them through import sets:\n\n-   You have a significant amount of customer-created UI components and you want to translate these components into other languages.\n-   You want to modify translations that ServiceNow provides in internationalization plugins.\n-   You want to translate an instance into a language that ServiceNow does not support with internationalization plugins. For more information, see [Translating to an unsupported language](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/system-localization/self-localize.md).\n\nAll translatable UI strings items are stored in translation table records. The only time you would translate UI directly in translation records is when you have a small amount of customer-created UI components and you know exactly where they are. For more information about translation tables, see [Translation tables](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/system-localization/r_TranslationTables.md) and [Translating individual UI strings](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/system-localization/c_TranslateIndFieldLabelsAndValues.md).\n\n## Procedure\n\n1.  If you are translating customer-created UI components, locate the translatable strings.\n\n    For more information, [Locating translatable UI strings](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/system-localization/c_TranslateNewCustomizations.md).\n\n2.  Export the relevant translation table records into a format \\(such as Excel\\) that can be easily manipulated.\n\n    For more information about exporting a list of records, see [Export data from a list](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/table-administration-and-data-management/export-list-data.md).\n\n3.  Within the exported document, translate the following fields in each row, depending on the translation table:\n\n    |Translation table|Fields to translate|\n    |-----------------|-------------------|\n    |Field Labels|Label, Plural, Hint|\n    |Translated Name/Field|Label \\(translate\\)|\n    |Message|Message|\n    |Choices|Label|\n    |Translated Text|Value|\n\n4.  Within each row, change the \"Language\" column to the [BCP 47](http://www.iana.org/assignments/language-subtag-registry/language-subtag-registry) code of the new language.\n\n    In Translated Text and Message records, type the full name of the language instead of the BCP 47 code.\n\n5.  Save your changes.\n\n\n## What to do next\n\nImport the translated document back into the instance as an import set.\n\n**Parent Topic:**[Translating custom content](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/system-localization/translating-applications.md)\n\n## Import a translation from an Excel spreadsheet\n\nThe System Import Sets application contains import tables and corresponding transform maps to assist with importing translations from an Excel spreadsheet.\n\n### Before you begin\n\nRole required: admin\n\n### Procedure\n\n1.  Navigate to **All** > **System Import Sets** > **Load Data**.\n\n2.  Select **Use Existing** and the **Table name** that matches the type of data being imported, as follows.\n\n    -   For choices, select the `[u_sys_choice]` table.\n    -   For field labels, select the `[u_sys_documentation]` table.\n    -   For translated names and fields, select the `[u_sys_translated]` table.\n    -   For messages, select the `[u_sys_ui_message]` table.\n    -   For translated text, select the `[u_sys_translated_text]` table.\n3.  Select **Upload an Excel file**, and then click **Browse** to select the source Excel spreadsheet.\n\n4.  If appropriate, specify the Work sheet and Header row number.\n\n5.  Select **Go**.\n\n    The translations are now available in the appropriate Import Set Table.\n\n6.  Navigate to **All** > **System Import Sets** > **Table Name** and review the imported information to verify that the import was successful.\n\n7.  To transform the imported data into the corresponding table, navigate to **All** > **System Import Sets** > **Run Transform**.\n\n8.  Select the appropriate transform map, as follows.\n\n    **Note:** Make sure you choose a transform map that has the **Run Business Rule** option selected. If the transform map does not have this option selected, any customized translations you have may be overwritten during the next upgrade.\n\n    -   For choices, select the **Sys Choice Translation Map**.\n    -   For field labels, select the **Sys Documentation Translation Map**.\n    -   For translated names and fields, select the **Sys Translated Translation Map**.\n    -   For messages, select the **Sys UI Message Translation Map**.\n    -   For translated text, select the **Sys Translated Text Translation Map**.\n9.  Select **Transform**.\n\n\n"}}