[benatespina]

The author reads English and Spanish, not Japanese or Portuguese. This makes the blog's languages simpler to read and honest about where each version comes from.

On the page.

• The language row leaves the head of the post. The original lists its translations in one line under the text (Also in Español · 日本語 · Português).
• A translation keeps one note above the text. Spanish, reviewed by the author: Traducido del original en inglés · Leer el original. Japanese and Portuguese: machine translation of the English original · Read the original · Report a mistake, the last link opening a new issue titled Translation (<locale>): <slug>.
• No page redirects by language: search engines pick the version through hreflang (and the existing x-default to the original), and each shared link points at its language. The blog index keeps its language switcher.

Consistency. src/content/translations/GLOSSARY.md fixes how each language renders Bounda's vocabulary (taken from the posts already published) and how a machine translation is checked before publishing. The README's blog section says how the languages work.

A back-translation of both posts found and fixed:

• ja, right to be forgotten: the description said 何が漏れるか (what leaks) for what it misses; now 何を取りこぼすか.
• pt-BR, right to be forgotten: a claim about Brazil's LGPD (Art. 18) the original never makes, removed; dobrar for fold and em claro for in the clear replaced; « » quotes and one missing subjunctive.
• pt-BR, A command is a file: for one TypeScript app had lost one; the tryIt label and the description reworded.
• ja, A command is a file: nothing to fix.

Checks. pnpm check and pnpm build pass; one x-default per page; checked in pnpm dev on the original and on the three translations.