Memsource Editor



Segmentation is the process that splits original 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.


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%.

Joining and Splitting Segments

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:

  1. Select a segment.

  2. Click Join.

    The selected segment and that below are joined. The joining point is indicated with the J tag.


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:

  1. Place the cursor at a point in the source segment that requires splitting.

  2. Click Split.

    The segment is separated at the specified point.


Make sure to add leading and trailing spaces to the target side based on the source. When splitting segments in a job where source is a space-less CJK language and the target is a language that uses spaces as a word delimiter, make sure to add leading or trailing spaces to the target to delimit words in the translation. (While this happens automatically in segments formed by the default segmentation rules, no spaces are added in manually split segments or those formed by additional custom segmentation rules. See also: Segmentation Rules Overview.)

Confirming Segments

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 Red_X.png in the table.

To confirm a segment, follow these steps:

  1. Open a job in an editor.

    Segments are presented as unconfirmed Red_X.png.

  2. Click on a segment to review.

    Matches are presented in the CAT pane.

  3. Review matches for accuracy and either accept or change.

  4. Confirm the segment.

    Segment is presented as confirmed green_check.png.

    Editing a segment unconfirms that segment.

  5. If required, run a QA check.

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 Edit menu) and may restrict Linguists and Vendors from being able to edit them. Locked segment don't require confirmation before a linguist sets the job to Completed. Locked segment 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

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 the Set segment status to confirmed for... 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 Set segment status to confirmed for... 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 Editor for Desktop 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 Save confirmed segments to TM on import option selected in file import settings.

  • Directly import a bilingual MXLIFF file into the TM.

Was this article helpful?

Sorry about that! In what way was it not helpful?

The article didn’t address my problem.
I couldn’t understand the article.
The feature doesn’t do what I need.
Other reason.

Note that feedback is provided anonymously so we aren't able to reply to questions.
If you'd like to ask a question, submit a request to our Support team.
Thank you for your feedback.