All rules

Too much translationese

translationese-densityon by default (info)Japanese

Japanese that copies English syntax (を可能にする, 重要な役割を果たす, あなたは) too often

Example

Flagged
この機能は、あなたが設定を共有することを可能にします。キャッシュは速度において重要な役割を果たします。あなたは設定画面からいつでも変えることができます。
What chaff prints
1:1 「を可能にする」など、翻訳調の言い回しが 1000 字あたり 5 個あります(1 個まで) 1:28 「重要な役割を果たす」など、翻訳調の言い回しが 1000 字あたり 5 個あります(1 個まで) 1:52 「あなたは」など、翻訳調の言い回しが 1000 字あたり 5 個あります(1 個まで)
Fixed
この機能を使うと、設定を共有できます。速度にはキャッシュが大きく効きます。設定は設定画面からいつでも変えられます。
What chaff prints
no finding

The rule measures the whole document, so this example was tried with an ordinary passage (about 200 words) after it that gives chaff nothing to report.

How to fix

Say it the way Japanese would (を可能にする → ができる; drop あなたは).

Why it matters

Phrases that copy English syntax into Japanese (を可能にする for "enable", 重要な役割を果たす for "play an important role", されることができる, あなたは for "you") read fine once, but stacked they make the whole document read like a translation, and the reader translates it back to get the meaning. They are common in machine translation, drafts thought out in English, and generated text. None of them is wrong alone, so the rule counts them per length of the document. The phrases are in the lexicon translationese, each with a plainer Japanese way to say it.

What it does not flag

None of these is wrong alone, so documents shorter than 500 characters are not measured. Phrasings common in human technical writing (を提供する, に焦点を当てる, することができる) are not counted. A document whose only such phrases address the reader (あなたの, あなたは) has chosen to speak to its reader and is not reported; beside other phrases they count. The literature preset turns it off, since a novel calls its characters 彼女.

Turning it off or relaxing it

Silence this one spot (in the document)
<!-- stet: translationese-density — reason -->
Relax it for the team (the reason is kept as a comment in chaff.yaml)
npx chaffjs relax translationese-density --why "reason"
Turn it off for the team (chaff.yaml)
rules: translationese-density: off
Technical details
Layer
L2
Status
stable
Severity
info
Languages
ja
Suited to
business, technical, blog, legal, docs, academic, literature, speech

Levels

Set a level for this rule under rules in chaff.yaml. With nothing set, it runs at the level its genre gives it (see By genre below).

strictup to 0 translated phrasings per 1000 characters
normalup to 1 translated phrasings per 1000 characters
relaxedup to 2 translated phrasings per 1000 characters

By genre

Runs by default in
technical/spec, technical/readme, blog/tech, blog/essay, blog/owned-media, business/proposal, business/report, business/email, business/press-release, business/meeting-notes, legal/contract, legal/statute, legal/judgment, legal/patent, docs/manual, docs/faq, docs/glossary, academic/paper, speech/address, speech/transcript
Turned off by the genre in
literature/fiction, literature/essay, literature/poetry, literature/play

Genres

Message

"{matched}" and other translated phrasings: {density} per 1000 characters (limit {limit})

Rewrite depth (chaff fix-plan --depth): light — words and sentences; the structure and the voice stay

This page is built from the rule's definition file:packages/chaff/rules/translationese-density.yaml