Managing App Localizations
Manage the displayed text in your app for multiple languages
Last updated
Manage the displayed text in your app for multiple languages
Last updated
The ARwayKit Sample App utilizes the to configure the localization settings.
You will need to modify the localization strings to remove any mention of ARway if you want to customize your own app with unique branding.
Follow this by Unity to select which locale your application will use by default.
The Unity localization package offers three ways to modify and export: CSV, Google Sheets, and XLIFF.
You can use the CSV (Comma Separated Values) format to import and export . This makes it easier to work with translators who use CSV for translation; you can export String Table Collections from Unity to CSV files, send them to the translator for modification, and then re-import the modified files back into Unity.
Navigate to "Window -> Asset Management -> Localization Tables"
In Localization Tables window, click on the "Edit Table Collection" tab to open the table collection with the name "StringTable_Localization"
Click the three vertical dots at the top right of the window and select "Export -> CSV…".
Then select a location to store the CSV and then save.
After you have exported the CSV, you can make changes to the different string stored in each cell.
Navigate to "Window -> Asset Management -> Localization Tables"
In Localization Tables window, click on the "Edit Table Collection" tab to open the table collection with the name "StringTable_Localization"
Click the three vertical dots at the top right of the window and select "Import -> CSV…".
Select CSV file to be imported.
Note: When importing, make sure that the structure / headers of the CSV file that was exported remains the same.
Once imported, check the data in the Table Collection to ensure that the imported data is correct.
XML Localisation Interchange File Format (XLIFF) is a standardized way to store localization data. It is supported by many different Computer Aided Translation (CAT) tools, which allows for a smoother translation pipeline when working with translators.
You can export String Table Collections from Unity to one or more XLIFF files, modify them with external CAT tools, and finally re-import them back into Unity with the updated translations.
To use the localized assets in the player, you must build the Addressables player content.
After updating source codes, take these conditions into account to determine if building Addressable is necessary:
If this is the initial build after checking out the source code.
If Addressable hasn't been built successfully in previous attempts.
If there have been modifications to String Tables.
To do this, in the Addressables window:
Navigate to "Window -> Asset Management -> Addressable -> Groups".
In the Addressables Groups window, click on "Build -> New Build -> Default Build Script".
The Unity Localization package allows you to synchronize data with the content of a String Table Collection. By default, this feature can synchronize a String Table’s keys, values, and comment metadata. You can also add support for additional data through scripts.
More information can be found on the page.
More information can be found on the page.
