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.
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.
Translation memories with multilingual target languages are supported and can be used bidirectionally.
Match value of 100%.
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.
To join segments, follow these steps:
Select a segment.
The selected segment and that below are joined. The joining point is indicated with thetag.
Incorrectly joined segments may cause formatting problems with a document.
If lines separated by a soft enter (Shift+Enter) are joined, they will become one line.
To split segments, follow these steps:
Place the cursor at a point in the source segment that requires splitting.
The segment is separated at the specified point.
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 shortcut, 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 thepane.
Review matches for accuracy and either accept or change.
Confirm the segment.
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.
Confirmation behavior can be modified in CAT Preferences.
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 Memsource Editor for Desktop.
When a job is pre-translated with theoption 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 theoption 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 Editor for Desktop or the tools menu in the Linguist Portal.
Project Managers can save segments to Translation Memories in three ways: