LoreString

Localization that doesn't break your build.

Your engine never changes. Keys stay anchored, placeholders stay intact. Only the language table swaps.

Ships toSteamiOSAndroidmacOSWindowsitch.io

ENGLISH
Watch it happen

The keys never move. Only the text does.

locale_table.json0%
BTN_CLOSEKAPATCLOSE
CAT_FORGEDEMİRCİFORGE
COND_RESTEDDinlenmiş (70%+)Rested (70%+)
HUD_0_RATION{0} Erzak{0} Rations
LOG_ADDEDGünlüğe eklendi: {0}Added to the log: {0}
SET_DAYGün {0} olarak ayarlandı!Day set to {0}!
MSG_TO_CAMPKampa 200 adım!200 steps to camp!
Numbers from a project we delivered:~1,900 keysa fifth with placeholders0 engine changes
This is your game to a player who cannot read its language.
quest_log
— and this is what it could look like.
The gap

They are already playing. And they are complaining.

Make your game speak.
The Binding of Isaac: Rebirth
0
reviews written in Russian
✕ no Russian support
Undertale
0
reviews written in Simplified Chinese
✕ no Chinese support
Don't Starve Together
0
reviews written in Turkish
✕ no Turkish support
Terraria
0
reviews written in Korean
✕ no Korean support
Stardew Valley
0
reviews written in Polish
✕ no Polish support
Undertale
0
reviews written in French
✕ no French support

"Great 2D platformer, the story is legendary — the only bad part is there's no Turkish language support."

— Steam review · Hollow Knight
original: "kardeşim 2d güzel bir platform oyunu hikayesi de efsane sadece türkçe dil desteği yok bir o kötü" · translated by LoreString
“Eleven years on and the author still hasn’t added Chinese. I knew this game back in primary school — I’m grown up now and I still want to finish it myself. But please, I’m begging you: add Chinese.”
Steam review · Undertale · Simplified Chinese为什么11年过去了作者还没有更新中文,游戏内容虽然小学就知道了但是现在长大了还是想自己通关,但是求你了,更新一下中文吧
“I’d recommend it if it were in Polish — as it is, I have to translate with my phone.”
Steam review · Stardew Valley · PolishPolecam jakby była po polsku a ja muszę telefonem tłumaczyć
“Really good story — a shame only two languages are available. Otherwise, a gem.”
Steam review · Undertale · Frenchtrès bonne histoire mais dommage que il n’y a que 2 langues a disposition. Sinon PEPITE
“Solid game. If it had Russian it would be on fire. Still great as it is — recommended.”
Steam review · Undertale · RussianИгра зачет только если был бы русский язык был бы огонь а так тоже имба советую
“It’s fun, I do recommend buying it. … They told me I have to beat the game once before I can install the Korean file. I’ve been at it for eight hours and I’m still playing in English. I’m furious.”
Steam review · The Binding of Isaac: Rebirth · Korean재미는 있습니다. 구매추천합니다. but 발컨이라도 깰 수있다고 한사람 나오세요. 발컨은 못깸니다. 한번 이겨야 한글파일 깔 수있다고 해서 깨는데 지금 8시간동안 하고있는데 아직영어로 게임중입니다. 화나죽겠네.
“Really good game — but it has been more than ten years since Undertale came out and there is still no Spanish translation.”
Steam review · Undertale · Spanishmuy buen juego pero como que ya pasaron mas de 10 años que salio undertale y falta la traduccion al español

Originals shown under each quote · translated by LoreString

These are the demands we read — in whatever language they are written. Different games, different countries, the same sentence underneath: I want your game, and I cannot play it in my language.

Closing that is the work. Turkish and English stay in house, start to finish; every other language goes to a translator who is a native speaker of it.

Translation is easy.
Not breaking the game is the hard part.

The four traps

What actually breaks a localized build.

01

Keys stay anchored

Every key is pinned once and never regenerated. UI_NO_HORSE_IN_STABLE stays exactly that, forever. Without it, one re-export shifts the whole table and every translation lands on the wrong line.

02

Placeholders are verified

Every {0} and {1} is counted before and after — count and order both. A line that comes back short is rejected automatically, not discovered by a player.

03

Data is never translated

Some strings aren't text — they're values your code compares and saves. Translate r.surface === 'Grass' and the game breaks silently. These are separated and translated only at display time.

04

Names are generated, not translated

Horses, jockeys, towns, guilds. A translated name pool reads like a machine wrote it. We build a native pool per language so generated content sounds like it belongs there.

Mobile

Mobile breaks differently. We know how.

Same job, harder traps. A string table is a string table — but on phones a wrong specifier doesn't look odd, it terminates the app.

Format specifiers

Android writes %1$s, iOS writes %@. Translate one into the other and the app doesn't render wrong — it crashes. Every specifier is counted and typed before and after.

Phone

Plurals

Android <plurals> and iOS stringsdict carry one entry per quantity rule. Turkish and English do not split those rules the same way: one direction has to collapse entries, the other has to add them. Get it wrong and the count silently disappears from the sentence.

Tablet

Overflow

Across the strings we have moved between the two, Turkish runs roughly 20–30% longer than English — and that cuts both ways. Into Turkish, a label sized for a 360 dp button comes out clipped; into English, the same label leaves the button half empty. Length is measured per string against the widget it lives in. Length is measured per string against the widget it lives in.

Desktop & laptop
strings.xml · .xcstrings · .strings · .stringsdict · JSON · CSV · PO — store listings too: title, description, keywords.
What actually breaks

A missing brace is a crash, not a typo.

Every line is counted before and after translation — placeholder count and order both. One of these ships. The other never leaves the pipeline.

✓ PASSED — 1 placeholder in, 1 out
UI_RACE_ADDED
source · Race added to the bulletin: {0}
translation · Yarış bültene eklendi: {0}
Order preserved, count matched. Goes into the build.
✕ REJECTED — placeholder lost
UI_WEEK_SET
source · Week set to {0}!
target · Hafta ayarlandı.
The number vanished. A player would read "Week set." forever and never learn which week. Caught automatically — it never reaches your build.
How it works

Three steps. Your engine is never touched.

The pipeline is built once, and that is the part that takes the time. Extraction, placeholder checks and the merge back into your format are ours; the Turkish is written by a translator whose first language is Turkish. For a language outside the English–Turkish pair, the pipeline and the verification are still ours, and the translation is written by a native speaker of that language, hired for the job.

Extract

Your build is scanned, every visible string catalogued and given a permanent key. Data values are separated out. The catalogue comes back for you to review.

Translate

Native translation with a locked glossary, placeholder checks and UI-length control, so a label that runs longer or shorter than the source is caught before it breaks the button it sits in.

Merge & verify

The table is merged back in your format, then verified line by line. You get a build that runs identically — in another language.

Pricing

One rate. No minimum you can't afford.

Agency translation runs $0.09–$0.18 per word; we sit at the bottom of that range. Then localization engineering lands on top as a separate line — $5,000 to $20,000 when a game wasn't built to hold translations, typically 25–35% of the whole budget. That line is the job here, not an extra.

typical agency quote
$0.18
per word · delivered in your format
  • JSON, CSV, PO, XLSX, .strings — your call
  • Locked glossary and consistent terminology
  • Placeholder and UI-length verification included
  • Credit in your game's credits, if you want it
  • Patch and DLC updates per job or monthly
Pipeline setup · one time, valid 12 months
up to 10,000 words$750
10,000 – 30,000 words$2,000
30,000+ words$3,500

Keys anchored for life, placeholders mapped and verified, data values separated from text, your engine untouched. This is the line agencies call localization engineering. They do it by hand. We built the pipeline once — so you pay once, and not five thousand.

Already have a string table? The setup drops, often to zero. I tell you after looking at your build — free, before any quote.

A Turkish game that does not speak English yet

This is work we have already shipped: a full Turkish game taken to English before it reached Steam — around 1,900 keys, a fifth of them carrying placeholders, zero engine changes. Keys stayed where they were, placeholders were matched and checked one by one, and the build went back the same day.

Talk about it

Review counts and language support read from each game's Steam store page on 4 October 2026; a studio may add Turkish at any time. Other figures: Steam Hardware & Software Survey (Sept 2026) · industry localization cost reports, 2026.

Two invoices

Same words. One line instead of four.

Typical agency
  • Translation · 18,000 words$1,620
  • i18n engineering$5,000+
  • Linguistic QA · hourly$900
  • Format delivery & glossary$400
Total$0
Lorestring
  • Translation · 18,000 words$1,620
  • Pipeline setup · one time$2,000
  • Placeholder & UI-length verificationincluded
  • Format delivery & locked glossaryincluded
Total$0
Second language, same game
Typical agency$2,920
Lorestring · setup already paid$1,620

You pay for the pipeline once. After that a second language is the word rate alone — verification included, no engineering, no second setup. The translation itself is done by a native speaker of the target language, hired for the job.

Agency figures are the published market range for a game that was not built to hold translations. Yours may be lower — ask them to quote the engineering line separately and compare.

If the number doesn't fit

Four ways in that aren't a discount.

Budget is a real constraint for a small studio. None of these lower the quality — they change what you trade.

01
best value

Two games, one setup

Shipping more than one game? The second game's pipeline setup is free — the glossary, the format adapter and your conventions are already built. You pay words only. Built for studios with something still unreleased.

02

Founding studio · first 5 games

Setup fee halved. In exchange: a credit line in your game's credits, permission to name the game as a reference, and two sentences about the work when it ships.

03

Interface first, story later

Menus, buttons, errors, tutorial — the fifth of the text that makes the game playable. The rest ships in a later pass. Same rate, smaller job.

04

Setup paid at launch

The setup fee waits until the game is selling. For studios with a release date and no cash before it.

Checker

Drop your own file. See what would break.

Placeholders, missing keys, plural rules, overflow risk — the same checks that run on every job. One file gives you a structure report; two files compare source against translation.

Nothing is uploaded. The check runs inside your browser and the file never leaves your machine.

Prefer a page of its own? The checker also lives at /arac/ — same engine, shareable link.

UI_NO_HORSE_IN_STABLE = "No horse in the stable."
UI_HORSE_READY = "{0} is ready to race."
The key never moves. The placeholder never moves. Only the value swaps.

Send 500 words. Judge for yourself.

Pick your messiest 500 words. They come back as a side-by-side report: every line, every key, every placeholder verified. You judge the quality. The build-ready file comes with the order.

[email protected]
Or check your own file first → Free, no sign-up, nothing leaves your browser.