← Back to blog

June 18, 2026 · Bill · 1 min read

Why we built ParlanceKit

Localization tooling has a habit of treating your source files as a dumping ground — flattening structure, dropping comments, handing back something you have to clean up by hand. We wanted the opposite.

The file is the contract

ParlanceKit round-trips your file: same structure, same ordering, same plural shape. A .xcstrings catalog comes back as a .xcstrings catalog.

Translation should fill in the blanks, never paper over them with source text.

What's next

More formats, deeper plural support, and a few things we're not ready to talk about yet.