It uses the Collection Name as the Group name, and the Shared Table Data asset GUID as the Group Id. The Localization system treats each String Table Collection as a Group. The XLIFF standard uses Groups as a way to organize units into structured hierarchies. The Translation Unit also contains a name and ID which maps to the Key name and Id, so that when the Localization system re-imports updated translations, it can correctly map them to their table entries. It contains the source text and the translated text (if it exists). ![]() The file contains a reference to the original asset path and its GUID, so that Unity can import any changes to the file back into the same String Table.Ī Translation Unit represents an entry taken from a String Table. TermĪ file is the container for localization material extracted from an entire String Table. It can also contain Notes.Ī Group contains at least one Translation Unit or Group. It can also contain Notes.Ī Translation Unit contains one Source Language Table entry and, optionally, one Target Language Table entry. Each file contains at least one Translation Unit or Group. See the table below the diagram for details on each node.Īn XLIFF document contains one or more XLIFF files. The simplified XLIFF standard has the following structure. The API provides a simplified version of the XLIFF standard that works across both versions.You can also access version-specific features in script. The Localization package supports both XLIFF version 1.2 and 2.0. ![]() 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. It is supported by many different Computer Aided Translation (CAT) tools, which allows for a smoother translation pipeline when working with translators. XML Localisation Interchange File Format (XLIFF) is a standardized way to store localization data.
0 Comments
Leave a Reply. |