The Style Guide Every Translator Learns to Read Twice

  

Introduction

A Tamil translator sends back a 3,000-word onboarding guide. The meaning is right. The Tamil reads well. The reviewer still returns it with 40 comments.

The cause is small. The translation style guide instructions asked for the formal “you,” நீங்கள். The translator used the informal one. The same guide fixed one Tamil term for “workshop.” The translator chose another valid word.

This is an illustrative scenario, not a real client case. The Tamil was correct. The file still failed because it ignored the instructions.

If you lead a content or localization team, this reaches your numbers. Each returned file adds review hours. It pushes back the launch. It also teaches your team to doubt the vendor.

The style guide is the first file I open on a job. It is also the last one I check before delivery. This post covers what a style guide controls, how it affects quality scores, and a habit for following client style guides: read twice.

What a Style Guide Controls

More Than Tone

A style guide is a rulebook for how a text should read in the target language. Smartling describes it as covering tone, formality, grammar preferences, terminology, and what never to translate.

The list runs longer. Milestone Localization adds numbers, currencies, names, salutations, gender, links, and formatting. These are the client instructions in translation that no one should have to guess.

Large companies write these languages by language. Microsoft keeps a library of localization style guides that includes Tamil. Its guides cover language conventions, style in technical writing, and market-specific data formats.

Where Tamil Needs Its Own Rules

Tamil shows why one global guide is not enough. Three common decisions need a written answer.

• Register. The formal “you,” நீங்கள், and the informal நீ change the whole tone of a text.

• Terms: “Workshop” can be பயிலரங்கு, which suits a training session, or பட்டறை, which often suggests a craft or repair shop. A guide that picks one ends the debate.

• Numbers. Indian digit grouping writes ten lakh as 10,00,000, not 1,000,000. The guide must say which one the client wants.

Milestone advises a separate style guide for each target language. Smartling says one general guide can serve most languages, with language-specific guides only where needed. Both views agree on one point. Tamil decisions must be written down somewhere.

Why LSP Style Guide Compliance Shows Up in Quality Scores

Style Is a Scored Error

Quality frameworks treat style as its own error category. In Smartling’s MQM guide, a style error is text that is grammatically acceptable but deviates from the organization’s style guides. This is where translation quality standards meet daily work.

Severity matters too. In the default scheme, a major error carries a weight of 5 and a minor error a weight of 1. The major definition includes deviating from the style guide, TM, glossary, or instructions.

In this scheme, a correct sentence that ignores the guide costs five times what a typo costs.

A Miss Is Not Always the Translator’s Fault

The same page offers a useful note for leaders. A rise in style errors may point to gaps in your style guide. A rise in terminology errors may mean your glossary needs updating.

So LSP style guide compliance works in both directions. Linguists follow the guide. Clients and LSPs keep it clear, current, and complete. That is how a team reaches consistency in localization across files and linguists.

The Read-Twice Habit

Reading a guide once is easy. Following it through 20 pages of text is harder. This is my routine.

1. First read, before any work. Read the whole guide. Mark every rule that differs from your habits.

1. One-page cheat sheet. Keep the top ten rules: register, numbers, dates, do-not-translate terms, punctuation, and capitalization.

2. Load the assets. Attach the glossary and TM in your CAT tool. Turn on the term checks.

3. Translate with the cheat sheet open. Keep it where you can see it.

4. Second read, before delivery. Check the file against the cheat sheet, rule by rule.

5. One batch of questions. Do not guess. Do not send ten separate emails.

Case Study: Feedback on Three Manuals

I translated three sustainability manuals for an LSP client under NDA, so the client stays unnamed. The set ran to 152 pages across three batches.

The client’s review flagged 15 corrections. They fell into three groups: terminology precision, missing qualifying words, and untranslated terms. One item pointed to a possible error in the source text, which needed checking before any change.

Each group maps to the routine above. Terminology precision is a glossary job. Untranslated terms belong on the do-not-translate list. Missing qualifying words show up in the second read. The source error needs a query.

When Two Guides Disagree or the Guide Is Silent

Ask, Do Not Guess

Sometimes the client guide and the LSP guide say different things. Sometimes neither covers your case. Do not pick a side. Send a query.

Milestone describes the usual flow. The LSP drafts the guide. The client reviews it. Two or three rounds of changes follow. A gap in the guide is normal and fixable.

Write the Answer Down

Keep every answer in writing. Add it to your cheat sheet with the date. Tone counts in a query too. A blunt note can sound like a complaint. A vague note hides the question. I wrote about this trap in why politeness hides the real message.

Do-not-translate terms need a written answer most of all. I covered that choice in which English words should never be translated.

A Five-Minute Style Guide Audit for Leaders

You do not need to be a linguist to check your own guide. Ask five questions.

1. Does a guide exist for each language you publish in?

1. Does each rule come with an example?

2. Is the do-not-translate list current?

3. Does one person own and answer queries?

4. When was the guide last updated?

Questions Leaders Ask About Style Guides

What is a translation style guide?

It is a written set of rules for tone, formality, terms, numbers, and formatting in a target language. It keeps different linguists aligned across files.

Who writes it, the client or the LSP?

Either can. Milestone describes the LSP drafting it and the client reviewing it, with a few rounds of changes.

What if two guides conflict?

Send one clear query to the project manager. Keep the answer in writing.

Does every language need its own guide?

Milestone calls separate guides on best practice. Smartling says one general guide can work for most languages, with extra guides where needed. Tamil needs its own rules for registers, terms, and numbers.

Your Next Step

Pull the last file that came back with comments. Sort every comment into two piles. One pile holds language errors. The other holds instruction misses.

If the second pile is bigger, fix the guide or the reading habit before you fix the linguist. Then brief your team on the cheat-sheet routine above.

Which rule in your current style guide do your linguists break most often, and do you know why?

About the Author

P. Maria Sundara Raj is a Translator, Proofreader and Content Writer with 3+ years in content and 8+ years in translation. He works between English and Tamil, and writes WriteNest Musings on language, communication and the small choices that shape how people understand each other. Find his translation and localization work at WriteNest9.com, connect on LinkedIn, or write to raj26.musings@gmail.com.