i18n: elements site in Spanish, Japanese and Arabic (landing v1 shipped, follow-ups) #96

Activity

1. sapatmohit

   added

   enhancementNew feature or requestNew feature or request

   websiteLanding page, docs site, or contentLanding page, docs site, or content

   on Nov 1, 2026
2. sapatmohit

   self-assigned this

   on Nov 1, 2026
3. sapatmohit commented on Nov 1, 2026

   

   sapatmohit

   on Nov 1, 2026

   MemberAuthor

   More actions

   Docs are translated (es, ja, ar) in #98. Remaining follow-ups from that work:

   • Fumadocs UI strings. "Search", "On this page", "Table of contents" and the other Fumadocs labels are still English on translated pages. Fix: `RootProvider` i18n with `defineTranslations` per locale.
   • Search language. `/api/search?locale=ja` returns Japanese results, but the search dialog doesn't pass a locale yet, so it searches English. This gets fixed together with the `RootProvider` i18n above.
   • Language switcher on docs. There's no way to switch language from a docs page. Unprefixed URLs are always English now (the cookie redirect was removed in feat: Spanish, Japanese and Arabic docs #98), so the switcher only needs to change the URL prefix.
   • Native-speaker pass on ja and ar. The translations are Haiku output, checked for markup only. Flagged as awkward: "Readable {p0} clever." (strikethrough wordplay, rulebook) in all three languages.
   • Hreflang for docs. The proxy sends `Link` alternates for every page, but there's no `alternates.languages` in `generateMetadata` and no hreflang in the sitemap.

   Re-translating after an edit: `babelize translate --docs-only --to es,ja,ar` re-translates only the changed paragraphs (`.babelize/local/docs-lock.json`).
4. sapatmohit commented on Nov 1, 2026

   

   sapatmohit

   on Nov 1, 2026

   MemberAuthor

   More actions

   All code follow-ups are done:

   Item	PR
   Docs in es, ja, ar (MDX via Babelize, Fumadocs i18n)	#98, #99
   Language dropdown on the landing page (desktop and mobile) and in the docs sidebar	#100
   Hand pass on the landing translations (Haiku), plus the strings that had no translation (4/16/9)	#101
   Translated metadata, hreflang, sitemap for every language (212 URLs), per-language canonical	#102
   Fumadocs UI strings, and search in the page's language	#103

   From the follow-up comment above, these are also done:

   • Fumadocs UI strings (feat: docs UI text and search in the page's language #103)
   • Search language (feat: docs UI text and search in the page's language #103)
   • Language switcher on docs (feat: language dropdown on the landing page and docs #100)
   • Hreflang for docs (feat: translated metadata, hreflang and a sitemap for every language #102)

   Still open: a native-speaker pass on ja and ar. Everything is Haiku output, checked for markup and glossary only. Spots worth a look:

   • "Readable {p0} clever." (rulebook wordplay)
   • the Japanese hero line order (`ローカライゼーション UI コンポーネントReact 向け。`)
   • Arabic letters joined directly to Latin brand names (`وreact-intl`)

   Translations are pinned in `.babelize/local/babelize-lock.json` (`metadata.manual`) and `docs-lock.json`. A reviewer's fixes can go straight into `public/locales/*.json` or the docs pages; for docs, also update the matching lockfile entry so Babelize keeps the fix.
5. sapatmohit commented on Nov 1, 2026

   

   sapatmohit

   on Nov 1, 2026

   MemberAuthor

   More actions

   Closing: all code follow-ups are done (#98–#103). A native-speaker pass on ja and ar can happen any time without this issue; the flagged spots are listed in the comment above.
6. sapatmohit

   closed this as completedon Nov 1, 2026