Localization Guides and Reference

strings/library.json6 on the shelf · none gated

library.

en-US · everything we wrote that outgrew a blog post

Reference pages, a cost calculator you can change the assumptions on, and the books we are still writing. Nothing here is gated, and every figure names the file it is read out of.

nothing gated
every figure sourced
reference pages below

nothing here is gated

Everything we have written, free to read.

6 on the shelf. Four are live pages you can open now; two are books still being written, and their cards say so. Nothing here asks for an email address first.

The Boring Localization Book
long formbeing written
The Boring Localization Book
The argument in full: why language should ship on the same rails as code, and what changes in a team when it does.
read the outlinein preparation
A First Multi-Locale Launch
long formbeing written
A First Multi-Locale Launch
Sequencing, right-to-left, pricing pages and support load, in the order a first launch actually meets them.
read the outlinein preparation
The Locale Reference
reference708 ICU locales
The Locale Reference
Every locale the validator accepts, how a tag is canonicalised, and which languages carry their own plural rule set.
open the referencelive page
The Cost Model
modelyour numbers
The Cost Model
The calculator with its assumptions visible and editable, so you can disagree with ours and still get a ledger out.
open the calculatorlive page
The Lexicon
specimenone page
The Lexicon
The whole product set as a dictionary entry: senses, a conjugation table, specimen plates and attested figures.
read the entrylive page
The Dispatch
dispatchpublished as written
The Dispatch
Shorter than a book: pieces on i18n setup, glossary enforcement, QA in CI, and migrating off another tool.
read the dispatchlive page

the evidence

Five numbers, and where each one comes from.

Every figure on this site names the file it is read out of. These five are the ones the product can back, and the right column tells you where to check.

reference pages

The pages worth bookmarking.

Every row here is a page on this site. Free to read, nothing gated, and none of it asks for an address first.

FAQs

What readers ask about this library, and where each answer lives.

Is any of this gated behind a form?

No. Nothing on this site sits behind an email wall, and nothing here will. Every live page above opens on a click, and the long-form titles will become links on the day they are finished rather than lead-capture steps.

Where is the API documentation?

The API overview is at /api: authentication, the endpoints, the rate limit and the file formats. The API changelog at /api-changelog records every release and the deprecation register, which is empty because nothing has been removed.

Which languages can I translate into?

Any language you can name with a BCP-47 tag. There is no supported-languages list, because there is no list: 708 locales sit in the ICU table a tag is checked against, and a structural fallback accepts real tags beyond it. The locale reference has the detail.

How much does Transglot cost?

The free plan is $0 with 100,000 words to start and 10,000 a month after, one project, 15 locales including your source and three seats. Starter is $19 a month, Team is $49 and Business is $149, and words past a plan allowance meter at $0.0008. The cost calculator lets you put your own numbers in.

What file formats can I bring?

Twenty, including JSON, YAML, XLIFF, gettext .po, Android XML, iOS .strings and .stringsdict, Flutter ARB, Java properties, RESX, CSV and XLSX. Seven of them carry plurals, and every one round-trips: the file comes back in the shape it went in.

Do you have a glossary of localization terms?

The lexicon is the closest thing: the product set written as a dictionary entry, with the terms this site uses defined in place. The product also has a glossary feature, which is the list of words the engine may not change in your own content.

When are the books published?

There is no announced date, which is why none is printed. A title moves from "in preparation" to a link on the day the file exists, and the changelog says so when it does. The outlines are on the long-form page now.

Can I quote or reuse these pages?

Quote them with a link and we are happy. A licence will be printed on each long-form title when it is published; until one is, this site claims none, because a licence promised in advance is a licence nobody can check.

How do I find out what shipped recently?

The changelog carries one dated entry per release, newest first, never rewritten after the fact. It is the same list the console reads for its what-is-new marker, so the page and the product cannot fall out of step.