Transglot— home
Start free
Ebooks and reports

Four titles we are writing in the open

None of them is finished. The outlines below are real, and every chapter documents a part of the product that already ships — that is the only reason we can publish them this early. Ask for a title and we will send it when it is done.

Back to the libraryWhat is already published →
4
Titles
28
Chapters outlined
0
Chapters written
The library

Pick a title, read the outline

Each chapter names the shipped surface it is drawn from. If a chapter interests you more than the book does, follow the surface instead — most of them already have a page.

4 titles
EBOOK
·
9 chapters outlined
Not published yet

Localization for engineers

The discipline for people who own the repository: how strings leave the codebase, how they come back, what translation memory is really doing, and why review is a routing problem rather than a headcount problem.

9
CHAPTERS OUTLINED
20
FORMATS COVERED
0
CHAPTERS WRITTEN
Contents
  1. 01Where your strings actually liveFile formats
  2. 02The first import, without a migration projectMigration importer
  3. 03Translating inside CICLI · GitHub Action
  4. 04Translation memory, and what it is worthExact & semantic TM
  5. 05Glossaries and the noun problemGlossary term base
  6. 06Scoring, thresholds and review routingQuality gate
  7. 07Confidence at translate timeConfidence routing
  8. 08Serving strings without shipping a buildRuntime pull endpoint
  9. 09What to measure after the first localePer-language scorecard
Drawn from
Shipped surfaces
  • The twenty file codecs and their capability flags
  • The CLI, the GitHub Action and the signed webhook events
  • The translation-memory write guard: a human edit always wins
Ask for a title

This form has no backend. Submitting opens your own email client with the request pre-filled and addressed to hello@transglot.ai — nothing is uploaded or stored until you send it yourself.

Or write to hello@transglot.ai yourself — it is the same inbox.

  • A person replies from a real inbox, usually within one business day.
  • You get one message when the title you asked for is finished.
  • No call is booked from this address without asking you first.
Who these are for

Written for the person who owns the repository

No chapter explains what localization is. Each assumes you have something in production and a date that has already moved once.

No chapter is a product pitch
ENGINEERING
You own the repositoryFormats and their capability flags, the CLI and the GitHub Action, and what the API does when a key cannot round-trip cleanly.
PRODUCT
You own the marketWhat a locale takes end to end, where the cost sits once memory starts paying for itself, and which failures a reader actually notices.
LEADERSHIP
You own the budgetThe word-based pricing model, metered overage with a cap you set, and what the free tier deliberately does not meter.
LOCALIZATION
You own the qualityThresholds, review routing, glossary governance, and the shared translation-memory disclosure written out in full.
Developers
Resource libraryEverything that is finished: reference pages, release notes and the legal pack.Read →
Developers
BlogThe writing that does exist today, on migration, key structure and QA.Read →
Platform
Quality gateThe scoring and review routing that title three is being written from.Read →
Pricing
Plans and meteringThe word limits, overage and spend cap that title two does the arithmetic on.Read →

Chapter three works better as a repository

The CI chapter will be fifteen pages. The thing it describes is a workflow file and a token, and you can have that today.

Talk to salesSEE PRICING →
No title on this page is finished — the outlines are