Blog
Product updates, guides, and customer stories.
GuidesThe EU AI Act transparency Code of Practice: who signed, and what it means for translated content
As of September 9, 2026, the European Commission's Code of Practice on transparency of AI-generated content lists 83 provider and 152 deployer signatories, and the list keeps growing. What the Code is, what signing commits a company to, why not signing is not non-compliance, and what it changes, and does not change, for machine- and AI-translated websites and apps under Article 50.
GuidesWhat is continuous localization? Definition, workflow, and what it does not mean
Continuous localization is a translation workflow that runs in parallel with development: new strings flow from the code to translators or AI automatically, and approved translations reach the running application without a release. The definition, the four stages, how it differs from batch localization, what you need before it works, and what it does not solve.
GuidesWhat is a translation glossary? Definition, examples, and how it is enforced
A translation glossary is the list of terms a product must translate the same way every time, with the approved translation per language. What belongs in one (preferred, allowed and forbidden terms), how it differs from a style guide and from a translation memory, why machine and AI translation need it more than human translators do, how it is enforced with automated checks, how teams build one, and what it does not fix.
GuidesWhen coding agents translate your app: what breaks, what to keep
AI coding agents now add translation keys and draft the translated strings as part of a code change, with more context than most translators ever get. What they do well, what does not carry over time (consistency across releases, review and provenance, terminology governance, QA over the whole corpus), how teams handle it today, and the agent-in-the-loop pattern that keeps the speed without losing the record.
GuidesManaging translation files without manual JSON editing
Nobody decides to hand-edit translation files; teams end up there. What translation file management means, why JSON, YAML and resx files turn into merge conflicts, drift and keys nobody owns, how teams handle it today (code editors, spreadsheets, CI sync, a TMS, coding agents), what removing the manual editing does not solve, and where Locize fits.
GuidesTranslation QA: What Actually Breaks in Translations, and How to Catch It Automatically
Most translation defects are not bad language, they are mechanical: a dropped placeholder, a broken HTML tag, a number that changed, the same term translated three different ways. What translation QA means, which errors appear in real translation data, what manual review keeps missing, and how automated linguistic checks catch the mechanical layer so human reviewers can focus on meaning.
GuidesMany Projects, One Team: Access and Billing When Localization Outgrows One App
The second app is where translation management quietly breaks: the same people re-invited everywhere, offboarding by memory, one invoice per project, and no answer to "who can change the German copy?". What the account layer above your projects has to do, and how organizations in Locize do it.
Guidesi18n Without Translation Files? You Can Do That With i18next Today
A new wave of i18n tools pitches "your code is the source of truth, translation files are build artifacts". The i18next ecosystem has supported exactly this workflow for years: natural-language keys, JSX serialization via Trans, saveMissing reporting, automatic AI translation, and CDN delivery with no locale files in your repo at all. The recipe, the honest trade-offs, and what "no files" does not solve.
Guidesi18n Formatting: Dates, Numbers & Currency with Intl and i18next (2026 Guide)
Hand-rolled "$" + toFixed(2) formatting is a bug in most locales: 1,234.56 is 1.234,56 in German and 1 234 567,89 in French, and yen has no decimal places. This guide covers Intl.NumberFormat, DateTimeFormat, RelativeTimeFormat, and how i18next wires them into translation strings with {{val, number}}, currency, datetime and custom formatters.