Inlang is an open lix file format for globalizing/localizing software (i18n). One file format, multiple apps, all interoperable.
Simple, adaptable and tiny i18n library that integrates with any framework
Manage translations in a web app with Fink.
Visualize, edit & lint translated strings at a glance via Inline Decorations & Hover Support, and extract new strings with a single click.
Command line interface for inlang projects. Many commands and the possibility to do translation automation.
Inlang is used by multiple large enterprises as well as many small to medium scale projects. The NPM downloads of the @inlang/sdk
provide a an indicator of developers adopting the inlang SDK to build i18n solutions on top of the inlang file format.
Inlang is an open file format for internationalization i18n that provides an SDK for building and integrating localization tools on top of that open file format.
.inlang
files are designed to become the open standard for i18n and enable interoperability between i18n solutions. Such solutions involve apps like Fink, libraries like Paraglide JS, or plugins.
The inlang SDK is the official specification and parser for .inlang
files.
The SDK allows creating, reading, and querying inlang files programmatically. Go to the SDK docs for more information.
Inlang is a file format with no depedency on a tech stack. Hence, it can be used with any tech stack.
The only thing that is needed are import/export plugins for the translation file format that is used by the tech stack. For iOS for example, the XCode strings catalog can be used. For Flutter a .arb
plugin would be the right choice.
Adopting the Inlang format gives you access to an ecosystem of apps, plugins that work together seamlessly. Popular tools already built on Inlang include: