A string is a discrete piece of text in a user interface or software resource, such as a button label, menu item, or error message, that is treated as a translatable unit. In localization, strings are extracted from source code or content files and stored as separate entries for translation in CAT tools, where translators must preserve any embedded placeholders and inline tags.
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.
Strings appear in software localization resource files, mobile app projects, and website translation workflows. Translators work on strings inside CAT tools or translation management systems, often with context previews or screenshots; localization engineers review placeholder syntax, concatenation issues, and string length after translation because broken strings can cause runtime errors or layout defects.
A common error is translating a string without seeing where it appears, which can produce the wrong word for buttons, titles, or status messages. Another is breaking placeholders or inline tags; this can corrupt the UI, trigger build failures, or make variables display incorrectly to end users, requiring immediate fixes before release.
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.