Segmentation is the splitting of source texts into smaller parts. This improves the retrieval of previously translated text from a translation memory. Segments are presented in the editor and can be filtered. If a project has workflow steps, changes in segments are presented in the translation changes pane.
Default segmentation rules correspond with specifics of each supported language and can be customized.
Jobs imported with bad segmentation such as poorly formatted document files or the application of inappropriate segmentation customization can affect TM match values.
Example:
Good segmentation:
-
Translation memories with multilingual target languages are supported and can be used bidirectionally.
Match value of 100%.
Poor segmentation
-
Translation memories with multilingual target languages are supported.
Match value of 100%.
-
and can be used bidirectionally.
Match value of 63%.
Segments can not be joined or split if a Linguist does not have editing rights on the source text or the segment is part of the plural form.
Segment splitting and joining is done only virtually, and therefore is not taken into account when splitting jobs. When splitting a job after a segment that had been split in the Editor, the whole original segment is considered, not its parts.
To join segments, follow these steps:
-
Select a segment.
-
Click join segments
or Ctrl/Cmd+J.
The selected segment and that below are joined. The joining point is indicated with the {j} tag. The {j} tag is a visual representation of the whitespace mark which exists and is applied between the two joined segments. Do not remove this tag even if previously joined segments are split again as it will corrupt the formatting.
To split segments, follow these steps:
-
Place the cursor at a point in the source segment that requires splitting.
-
Click split segments
or Ctrl/Cmd+E.
The segment is separated at the specified point.
Caution
Ensure leading and trailing spaces are added to the target side based on the source text.
When splitting segments in a job where the source is a space-less CJK language and the target is a language that uses spaces as a word delimiter, ensure leading or trailing spaces are added to the target to delimit words in the translation. This is normally automatically applied to segments formed by the default segmentation rules as no spaces are added in manually split segments or those formed by additional custom segmentation rules.
All segments (unless locked by a Project manager) in a job must be confirmed before a job can be set as Complete. Confirmation can be performed via keyboard shortcuts, menu or clicking on in the table.
To confirm a segment, follow these steps:
-
Open a job in an editor.
Segments are presented as unconfirmed
.
If confirmed in a previous workflow step, segments are presented with a gray checkmark
.
-
Click on a segment to review.
Matches are presented in the pane.
-
Review matches for accuracy and either accept or change.
-
Confirm the segment by clicking the
Segment is presented as confirmed
.
Editing a segment removes confirmation status from that segment.
-
If required, run a QA check.
Select segment numbers to highlight multiple segments:
-
Hold down Shift while selecting multiple segments as a group.
-
Hold down CTRL (Windows) or Cmd (macOS) while selecting multiple individual segments.
Confirmation behavior can be modified in CAT preferences.
Locked segments
Only Project managers and Administrators can lock and unlock segments (Ctrl+L or from the menu) and may restrict Linguists and Vendors from being able to edit them. Locked segments don't require confirmation before a linguist sets the job to Completed. Locked segments can be excluded from the QA.
If a segment is locked and available for editing, click F2 to access the content.
Saving segments to a translation memory ensures that translation work performed can be reused in future translation projects.
Segments can not be saved to a translation memory if:
-
Working offline in the CAT desktop editor.
-
When a job is pre-translated with the option selected.
If confirmed segments are locked during pre-translation and then unlocked in the editor, unlocked segments will be saved into the TM.
-
When importing an .XLIFF file as a new job with the option selected.
Linguists and Vendors can save segments to translation memories in projects set as writable by a Project Manager.
Segments are saved in two ways:
-
Automatically saved to the TM when confirmed during the translation process.
-
Upload of translated bilingual file via the desktop editor or the tools menu in the linguist portal.
Project managers can save segments to translation memories in three ways:
-
Upload via the tools menu on the Job page.
-
Import a standard .XLIFF file as a new job with the option selected in file import settings.
-
Directly import a bilingual .MXLIFF file into the TM.