Korean, Japanese and Chinese that keep up with every patch.
Send your string export after each update. The desk localizes new and changed lines, keeps one glossary, writes store-page and patch-note versions, and gives you an in-context check list. You import and publish.
Join the waitlistEstimate from desk research, not a measured result.
This update at your localization desk · example
- 412 new or changed strings in KO / JA / ZHWe localize
- Glossary: 9 new item and skill namesWe update
- Steam patch notes in 3 languagesWe write
- Lines likely to overflow UI boxes flaggedWe flag
- Import strings · publish store page and notesYou click
The whole localization job around each update
What a small studio does per update to keep three Asian languages current. Hours are our estimate, not measured from customers.
| Task | Hours / week (estimate) | What the desk does |
|---|---|---|
| Export new and changed strings, send to translators, chase returns | 1–2 h | You send one export; we handle the rest |
| Translation of new and changed lines (KO, JA, ZH) | outsourced or skipped | We localize with a consistent glossary |
| Glossary and style decisions (names, items, UI terms) | 1–2 h | We keep one glossary per language |
| Store page and patch notes per language | 1–2 h | We write them for each update |
| In-context check: truncation, placeholders, fonts | 1–3 h | We check files and give you a screenshot checklist |
| Player feedback on translations | 0.5–1 h | We review reported lines and fix them next update |
Who it is for: Indie and small studios shipping in English that want Korean, Japanese and Simplified Chinese kept up to date with every patch.
How an update works
Once
Send your string files (CSV, JSON, PO, XLIFF or similar), current translations if any, and a short game description.
Every update
Send the new export. The desk returns updated files, glossary changes, store and patch-note text and a check list. Korean is reviewed by a native Korean speaker; Japanese and Chinese review arrangements are confirmed in your quote.
You click
You import the files, build, and publish on Steam or other stores.
You still click
- Importing files into your build
- Publishing store pages and patch notes
- Replying to players
- Releasing the update
Not included
- Voice-over, audio or video subtitling timing.
- Console certification or age-rating submissions.
- Any promise of reviews, wishlists or sales.
- Posting on stores or communities for you.
- Access to your source code or store accounts.
Planned price
Per game · Korean, Japanese and Simplified Chinese · up to 15,000 new or changed words a month. Planned pilot price.
Payment: Payment by PayPal invoice once the desk starts. Nothing is charged on this page and there is no payment link yet.
Questions
Which file formats?
Common string exports such as CSV, JSON, PO and XLIFF. Tell us your engine and we confirm before starting.
Who translates?
Machine-assisted drafts with human review. Korean is reviewed by a native Korean speaker. For Japanese and Chinese we confirm the reviewer setup in your quote.
What if an update is bigger than the monthly words?
We quote the extra words before starting. Nothing is charged without your OK.
Do you test the build?
We check files and give you a checklist of screens to capture. Running the build stays with you, or you send us a build key.
How do we talk?
By email only.
Join the waitlist
Leave an email and your game. We reply by email with a sample of 50 of your strings in one language. No calls.