A translation unit (TU) is a source segment and the target segments for all languages grouped together and saved into a translation memory. It's not possible to save multiple target versions in the same language, there can be only one target segment per selected language.
When a segment/TU is saved, pre-defined attributes or metadata are automatically added to the source and/or target of the TU in the translation memory.
These attributes can be saved with the target segment or source segment as indicated:
-
Created (date/time) - target segment
-
Created by - target segment.
Only Phrase usernames are supported.
When a non-empty segment is first confirmed by a user other than the segment's original author, the Created by field will be populated with the original author's username, and the user confirming the segment will be added to the Last modified by field.
-
Last modified (date/time) - target segment
Only the latest version of the target segment is saved to TM. This attribute marks the time when the latest version was saved.
-
Last modified by - target segment.
Only Phrase Usernames are supported.
-
Project - target segment
-
Client - target segment.
This is the Client as set in the project when the translation was created.
-
Domain - target segment
This is the Domain as set in the project when the translation was created.
-
Subdomain - target segment
This is the Subdomain as set in the project when the translation was created.
-
File - target segments
Name of the file where the translation was created.
-
Context - source segment
This is the Previous segment, Next segment or Segment key, depending on the when the job was created.
Translation Memory attributes (Domain, Client, Business Unit, etc.) have no effect on translation unit metadata.
For importing and exporting the content of a translation memory using the .TMX format, the following metadata is supported:
-
Properties in the source TUV element:
<prop type="context_prev">Text of the previous segment </prop> <prop type="context_next">Text of the following segment </prop><prop type="x-context_seg_key">Context Key</prop>*
*For context based on a segment key
-
Properties in target TUV element:
<prop type="created_at">1322746823589</prop> <prop type="created_by">Some name</prop> <prop type="modified_at">1323854662890</prop> <prop type="modified_by">Some name</prop> <prop type="project">Project name</prop> <prop type="client">59131</prop> <prop type="domain">6678</prop><prop type="subdomain">5370</prop> <prop type="filename">File name</prop><prop type="aligned">false</prop><prop type="reviewed">false</prop>
For importing and exporting the content of a translation memory using the .XLSX format, the following metadata is supported:
-
ID - Phrase internal ID
-
{source language code} - for example 'en' or 'en_us'
-
prev - text of the previous segment
-
next - text of the following segment
-
seg_key - text of the context key
-
mdata - metadata of Phrase tags
-
{target language code} - en or en_us
-
created_by - Phrase Username
-
created_at - in format 2017.07.07 14:39:52,000
-
modified_by - Phrase Username
-
modified_at - in format 2017.07.07 14:39:52,000
-
client - Phrase ID (number)
-
project - Phrase ID (number)
-
domain - Phrase ID (number)
-
subdomain - Phrase ID (number)
-
note - text (external use only, not visible in Phrase)
-
reviewed - true/false (external use only, not visible in Phrase)
-
aligned - true/false (external use only, not visible in Phrase)
-
filename - the name of the original file (test.docx)
-
mdata - metadata of Phrase tags
The order of the columns reflects the attributes of the source segment and the attributes of the target segment.