What do practitioners report about localising ink stories, and is there an official way?
In ink's open issue 514 (2019) users report no built-in way to export all strings for translation; suggestions are playing every path, preprocessing tags or post-processing compiled JSON, and one team translates the ink source directly with non-technical translators, while others worry about word order that ink's syntax cannot reflect. Forum accounts, not measurements.
In ink's open issue 514 (2019) users report no built-in way to export all strings for translation; suggestions are playing every path, preprocessing tags or post-processing compiled JSON, and one team translates the ink source directly with non-technical translators, while others worry about word order that ink's syntax cannot reflect. Forum accounts, not measurements.
Curator qualifications: Code, docs and issue text read 2026-10-22; nothing localised or run. Commenter identities intentionally not recorded. Curator amendment CA-AM-0047 (2026-10-22): Addition (curator, source_statement scoped negative): ink's own Documentation/WritingWithInk.md (readback 0555b6ac64805596) and RunningYourInk.md (readback 94031c0de03ffa6f) at master 35c63e52f1d36060930dc7ed3cfba38ea224b528 contain 0 hits for 'locali' and 'translat'. WritingWithInk has only non-ASCII identifier ranges (L3403 on). No official localisation path is documented in those two files. Issue #514 was still open at the 2026-10-22 re-fetch (readbacks 64ec3ea922df4a50, 1edb788fa8739122; 7 comments, last 2020-10-28). Its no-export statement is 2019 evidence carried by an open issue, not a current maintainer statement. A 2020 comment adds a fourth workaround, localising the compiled JSON, and notes that its keys do not follow the narrative.
Limitations: Code, docs and issue text read 2026-10-22; nothing localised or run.
Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.
Structured fields
{
"citations": [
{
"url": "https://api.github.com/repos/inkle/ink/issues/514/comments",
"note": "GitHub API inkle/ink issue 514 (opened 2019-02-18, state open); issue 514 comments 466632202, 467087030, 472051520, 473105426"
},
{
"url": "https://api.github.com/repos/inkle/ink/issues/514",
"note": "GitHub API inkle/ink issue 514 (opened 2019-02-18, state open); issue 514 comments 466632202, 467087030, 472051520, 473105426"
}
]
}Evidence claims
- [sourced_fact] In ink's open issue 514 (2019) users report no built-in way to export all strings for translation; suggestions are playing every path, preprocessing tags or post-processing compiled JSON, and one team translates the ink source directly with non-technical translators, while others worry about word order that ink's syntax cannot reflect. Forum accounts, not measurements. · locator: GitHub API inkle/ink issue 514 (opened 2019-02-18, state open); issue 514 comments 466632202, 467087030, 472051520, 473105426 source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |