A style guide is a project-specific reference document that defines the required tone, voice, grammar, punctuation, formatting, and terminology choices for translated or localized content. In localization workflows, it gives translators, editors, and reviewers a shared baseline so that all deliverables stay consistent, and it often includes rules for UI labels, error messages, brand names, and locale-specific conventions, and is usually created or approved by the client before translation begins.
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.
Style guides appear in localization kits, onboarding packages, and client reference folders for software, marketing, and multimedia projects. Linguists consult the guide before translating UI strings, help content, or subtitles, and reviewers use it to judge whether a text meets the expected register and terminology before sign-off. It also supports QA checks by defining what counts as a preferred or acceptable choice.
A common mistake is treating the style guide as optional or relying on generic language rules, which leads to inconsistent terminology and tone across files. Another error is not updating the guide when a product name or term changes, so translators keep using outdated language and reviewers have to reject otherwise accurate work.
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.