A segment is a defined unit of source text, usually a sentence, heading, list item, or UI string, that a CAT tool isolates for translation. In localization files and translation memory systems, segmentation rules determine how text is divided, stored, and matched, which directly affects leverage, consistency, context visibility, and the ability to reuse previous translations across projects and language pairs.
Angel Translation editorial reference · Confirm the rendering against your source and approved project terminology.
Check source meaning → confirm the preferred term → record approved variants and references.
Segments are the default view in CAT tool editing panes, translation memory matches, QA checks, and word-count reports. Project managers inspect segmentation in file-preparation steps to adjust rules for source documents such as legal contracts, UI strings, or subtitles so that text units are not too long or too short.
Changing segmentation mid-project can alter context, split sentences in ways that mislead translators, and reduce translation memory matches, creating inconsistent translations across entire files. Translators may also translate isolated short segments too literally when surrounding source context is not shown, especially for pronouns, lists, UI strings, headings, or product names.
Creative and consumer content needs accurate meaning as well as tone and context. Subtitles, interfaces and voice scripts also require checks for timing, character limits and pronunciation.
Provide approved terms and previous translations with the source files. Agree how variants, ambiguous wording and revisions will be reviewed. Terminology maintenance and any termbase handback are confirmed in the project scope. See the 8-step AI + expert workflow.
Employee-training video transcription and dubbing.
Read the published project →Brand documentation.
Read the published project →Published scope shows related industry experience; it does not confirm that this specific term was used or reviewed in the project.
Include the source and target languages, file types, intended use, deadline and any approved termbase. Agree handling before sending sensitive files. Acknowledged in 4 hours, quoted in 24.
Prepare an inquiry email →Content Globalization solutions →File handling →A glossary entry is not an official standard or evidence of regulatory acceptance. Confirm current requirements for your project separately.