Localization is the process of adapting content, products, or services for a specific language and regional market, often abbreviated as L10n. It goes beyond text translation to include locale-specific formats such as dates, times, currencies, and units, as well as cultural references, imagery, regulatory requirements, and user experience expectations that make a product feel native to the given target market.
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.
Localization appears in software, website, game, and documentation projects where a product is prepared for new regional markets. Teams use localization kits, style guides, term bases, and CAT tools to manage files; later they run localization testing and in-country review to confirm that UI layout, date and currency formats, and cultural references work correctly in the target locale.
A common mistake is reducing localization to text translation and ignoring locale-specific formats, imagery, or non-linguistic requirements. This can produce a product that is understandable but feels foreign or even non-compliant in the target market, leading to poor adoption, regulatory risk, or costly rework after launch; a simple date format like 03/04 may be misinterpreted across locales.
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.