Why do German speakers write «become» when they mean «get» or «receive»?

Because the German verb «bekommen» means to get or to receive, and it looks almost identical to English «become». So «When will I become my results?» comes out for «When will I get my results?». It is the signature German false friend, and it sits in a cluster: «eventually» (eventuell = possibly), «actual» (aktuell = current), and «also» (also = therefore). Diglot flags each as German false-friend transfer and supplies the intended English word.

Why do I capitalize nouns in the middle of English sentences?

Because German capitalizes every noun — «der Tisch», «die Methode», «das Ergebnis» — so the habit carries into English as «the Results show the Method is robust». English capitalizes only proper nouns and sentence starts. Diglot flags mid-sentence common-noun capitals as a German orthography-transfer pattern rather than as random typos, which is why it keeps catching them across a draft.

Why is there a comma before «that» in my writing, and why «since five years»?

Both come from German grammar. German requires a comma before a «dass» (that) clause, so «We argue, that the model converges» carries a comma English drops. And German «seit» covers both «since» and «for», so a duration becomes «since five years» instead of «for five years». Diglot removes the comma before «that» and splits «seit» into «for» + duration and «since» + start point, flagging both as German-L1 transfer.

How does the translator handle the «become»/«bekommen» false friend?

It renders the intended meaning, not the look-alike. A literal translation keeps «bekommen» as «become», which is wrong in English — the verb means to get or to receive. Diglot's translator outputs «get» or «receive» because it knows the German source word and its true English equivalent rather than matching on spelling, and it does the same for «eventuell» → «possibly» and «aktuell» → «current».

Will the translator fix word order, «seit», and over-capitalization?

Yes. It reorders German verb-final and verb-second clauses into natural English subject-verb-object, renders «seit» as «for» with a duration or «since» with a start point, and lowercases the common nouns German capitalizes. These German conventions are stripped so the English output reads native rather than as transliterated German.

German · L1-aware

AI Translator for German Speakers

L1-aware grammar, paraphrasing, and translation tuned to the specific transfer patterns German speakers face when writing English — from academic abstracts to business correspondence.

Try Diglot free About AI Translator

What makes English harder for German speakers?

English writing problems for German speakers cluster around a few systematic transfer patterns — the «become»/«bekommen» false friend, over-capitalized nouns, «seit» for both since and for, a comma before «that», and German word order surfacing in English clauses.

German and English are both Germanic, which lulls writers into trusting look-alikes that drifted apart. «Bekommen» means to get or to receive, not «become», so «When will I become my results?» appears for «When will I get my results?» — the single most recognisable German-speaker error. «Eventuell» means possibly, not «eventually»; «aktuell» means current, not «actual»; «also» means therefore, not «also» in the additive sense. Each look-alike says something subtly different from what the writer meant.

The second cluster is convention carried straight from German orthography and punctuation. German capitalizes every noun, so «the Results show that the Method is robust» picks up stray mid-sentence capitals; and German requires a comma before a «dass» (that) clause, so «We argue, that the model converges» carries a comma English does not use. The third cluster is grammar: «seit» covers both «since» and «for» (so «since five years» appears for «for five years»), German treats «Informationen» as countable so «informations» slips in, and German verb-second and verb-final word order leaks into English subordinate clauses.

Diglot's Grammar Checker is tuned for these German → English patterns specifically — the «become»/«bekommen» and «eventually»/«actual» false friends, over-capitalized nouns, «seit» → since/for, the comma before «that», and word-order transfer. It names the German-L1 reason behind each correction rather than treating it as an isolated slip.

What AI Translator specifically does for German writers

Translation for German speakers is partly a meaning problem and partly a word-order one. A literal render keeps «bekommen» as «become», «eventuell» as «eventually», and «aktuell» as «actual», and it preserves German verb-final and verb-second order so the English reads back-to-front. Diglot's translator outputs «get», «possibly», and «current», and reorders the clause into natural English subject-verb-object instead of stranding the verb at the end.

The translator also fixes the conventions German carries over: it lowercases the common nouns German capitalizes, removes the comma before a «that» clause, and renders «seit» as «for» with a duration or «since» with a start point. The Glossary pins German compound terms and author names to one English rendering across the document, and you can toggle between a close render and a more idiomatic one — so a German source lands as natural English without losing the author's precision, umlauts, or citations.

Top German-to-English transfer patterns Diglot catches

Pattern	Example error	Corrected
False friend «become» (bekommen = get)	"When will I become my exam results?"	"When will I get my exam results?"
False friend «eventually» / «actual»	"The actual data will eventually be enough."	"The current data will possibly be enough."
Over-capitalized nouns	"The Results show the Method is robust."	"The results show the method is robust."
«seit» → since/for	"We have run this experiment since five years."	"We have run this experiment for five years."
Comma before «that»	"We argue, that the model converges."	"We argue that the model converges."

Ready to write better English?

Diglot combines L1-aware grammar checking, paraphrasing, translation, and originality verification in one workspace — built for German speakers writing English.

Try Diglot free

Common writing tasks for German speakers

Concrete Diglot workflows by writing task — each tuned to German-to-English transfer patterns.

Writing an essay in English for Russian speakers Writing a research paper in English for Chinese (Mandarin) speakers Writing business emails in English for Spanish speakers Writing a cover letter in English for Arabic speakers

How Diglot compares to alternatives

If you're evaluating writing tools, here's the honest head-to-head — when the alternative wins, when Diglot wins.

Diglot vs Grammarly Diglot vs QuillBot Diglot vs Wordtune Diglot vs Copyleaks Diglot vs DeepL Write Diglot vs GPTZero

AI Translator for speakers of other languages

Each L1 has its own transfer-pattern profile — pick yours for the patterns Diglot specifically addresses.

Arabic Chinese (Mandarin) Japanese Korean Russian Spanish

Frequently asked questions

Why do German speakers write «become» when they mean «get» or «receive»?: Because the German verb «bekommen» means to get or to receive, and it looks almost identical to English «become». So «When will I become my results?» comes out for «When will I get my results?». It is the signature German false friend, and it sits in a cluster: «eventually» (eventuell = possibly), «actual» (aktuell = current), and «also» (also = therefore). Diglot flags each as German false-friend transfer and supplies the intended English word.
Why do I capitalize nouns in the middle of English sentences?: Because German capitalizes every noun — «der Tisch», «die Methode», «das Ergebnis» — so the habit carries into English as «the Results show the Method is robust». English capitalizes only proper nouns and sentence starts. Diglot flags mid-sentence common-noun capitals as a German orthography-transfer pattern rather than as random typos, which is why it keeps catching them across a draft.
Why is there a comma before «that» in my writing, and why «since five years»?: Both come from German grammar. German requires a comma before a «dass» (that) clause, so «We argue, that the model converges» carries a comma English drops. And German «seit» covers both «since» and «for», so a duration becomes «since five years» instead of «for five years». Diglot removes the comma before «that» and splits «seit» into «for» + duration and «since» + start point, flagging both as German-L1 transfer.
How does the translator handle the «become»/«bekommen» false friend?: It renders the intended meaning, not the look-alike. A literal translation keeps «bekommen» as «become», which is wrong in English — the verb means to get or to receive. Diglot's translator outputs «get» or «receive» because it knows the German source word and its true English equivalent rather than matching on spelling, and it does the same for «eventuell» → «possibly» and «aktuell» → «current».
Will the translator fix word order, «seit», and over-capitalization?: Yes. It reorders German verb-final and verb-second clauses into natural English subject-verb-object, renders «seit» as «for» with a duration or «since» with a start point, and lowercases the common nouns German capitalizes. These German conventions are stripped so the English output reads native rather than as transliterated German.