Curious about i18n translation workflow?

[Kutius]

Frame is a total stunner — UI and stack is clean, modern, and clearly well-architected. Major respect.

I was digging through your i18n implementation (src/lib/i18n/) and noticed that each language lives in its own JSON file with namespace grouping. That's neat and maintainable. At the same time, I didn't spot any automated key extraction tooling.

So I'm curious:

Do you use any tooling to extract keys/sync translations, or is it all manual?
The non-English JSONs look machine-translated — did you use AI or a translation service?
How do you ensure all 9 locales stay in sync when adding new text?

Just trying to understand your process. Thanks!

[addisonking]

reference https://github.com/66HEX/frame/blob/master/src/lib/i18n/index.ts

[66HEX]

i18n in Frame is possible thanks to @dufu1991

For now every thing related to i18n is manual, currently I'm focused too much on optimizations/ML pipeline explorations. Every key is translated with AI so it's possible that some translations are inaccurate. If that's something you want to explore - go ahead 😄. We can use Deepl.com as a translation service, they offer 500000 chars/month of translations for free through their API

[66HEX]

Since there was no follow-up on that thread, I went ahead and implemented the automation myself.

Current i18n workflow in Frame:

i18n-extract.mjs

Scans source code and extracts used i18n keys.

i18n-check.mjs

Validates locale parity (missing/extra keys), placeholder consistency, and key usage coverage.

i18n-sync.mjs

Syncs non-source locales to en-US structure (add missing/remove stale), with write mode.

i18n-translate.mjs

DeepL-based translation pipeline from en-US to all other locales, with:

• placeholder preservation,
• retry handling,
• parser-fallback for problematic batches.

i18n-common.mjs

Shared helpers used by all the scripts above.

Package commands now include:

• i18n:extract
• i18n:check
• i18n:sync
• i18n:sync:write
• i18n:translate
• i18n:translate:write
• i18n:translate:rewrite
• i18n:sync:auto (sync + auto-translate new keys)

[UltraLowBass]

При перетаскивании окна программы по рабочему столу, она как слоупок. Допустим я сделал несколько движений мышкой двигая программу туда сюда, отпустил уже кнопку, а окно программы продолжает повторят все движения что я делал, медленно и долго.
Я так понял это временная проблема?

[66HEX]

This question is unrelated to the i18n discussion, but answering to your question - I suppose you're a Windows user: Window transparency effects in Tauri have documented performance issues on some Windows versions/builds, there's nothing I can't do about it outside of removing that feature completely.

https://crates.io/crates/window-vibrancy