An inline tag is a piece of formatting or placeholder markup embedded within a translatable segment, such as a variable, link marker, emphasis tag, or line-break code. In localization and translation tools, inline tags protect non-translatable content and preserve its position so that translators can move tags appropriately without breaking the underlying structure, output format, or final rendered text in the localized product.
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.
Translators encounter inline tags in CAT-tool editors, translation management systems, and source files from formats such as XLIFF, HTML, XML, or JSON. They must keep tags intact and place them correctly when word order changes between languages, while automated QA checks often compare tag count, order, and whitespace to detect broken markup.
The most common error is deleting an inline tag or placing it in the wrong position, especially when a term order changes. A missing or misplaced tag can cause formatting to bleed across sentences, variables to display incorrectly, or the final file to fail parsing, which breaks build or publication.
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.