Guides on translation file formats, framework i18n, and where AI actually helps in a localization workflow – written for the people who ship the code.
Subscribe via RSSHow ICU message format handles plurals, gender and nesting, with accurate CLDR plural categories, common pitfalls, and which JS libraries really support it.
Read articleWhat XLIFF is, how a 1.2 file is structured, the pitfalls that corrupt a translation round trip, and how to export and import it without losing data.
Read articleGiving a coding agent real, branch-scoped tools for translation work through MCP, instead of letting it hand-edit locale files and drift out of sync.
Read articleA shared locale file leaks unreleased copy and wastes review time; translation branches, named merge strategies and role-gated merges fix it.
Read articleTranslatize and Phrase compared on branching and merge behaviour, software file formats, developer automation, review state and pricing shape.
Read articleTranslatize and Crowdin compared on developer workflow, branching and merge behaviour, review state, software file formats and pricing shape.
Read articleTranslatize and Lokalise compared on branching and merge strategies, file format coverage, developer automation, roles and permissions, and pricing shape.
Read articleWhich AI translation tools are worth using for software localization, how they differ from raw machine translation, and how to judge output quality honestly.
Read articleTranslating YAML locale files without breaking them: nesting and interpolation, pluralization rules, the anchors and multi-line traps, and automating the round trip.
Read articleHow Laravel’s two translation file formats work, when to use each, and how to add AI-assisted translation without losing review control.
Read articleVue I18n setup for Vue 3 and Nuxt, message format and pluralization, lazy-loading locales, and keeping translation files maintainable as the app grows.
Read articleWorking with Flutter’s ARB format and gen_l10n: key naming rules, placeholders and plurals, metadata for translators, and automating the translation round trip.
Read articleSetting up react-i18next properly, structuring translation keys that survive refactors, and connecting the app to a workflow translators can actually use.
Read articleRouting, message loading and translation workflow for Next.js App Router with next-intl – including how to keep locale files in sync as the app grows.
Read articleWhere machine translation belongs in a release process, how to gate AI output behind review, and the branching model that keeps unreviewed copy out of production.
Read articleHow the three best-known translation management platforms differ on workflow, file format support, branching, automation and pricing – plus a fourth option, Translatize, for teams that want git-style branching with permission-guarded merges.
Read articleAn honest comparison of translation management platforms, i18n libraries and CLI tooling in 2026 – what each is actually good at, and when you do not need one at all.
Read articleA practical guide to translating JSON locale files with AI: preserving placeholders and nesting, handling plurals, reviewing output, and keeping keys in sync.
Read article