Lokalise file formats

Mike's Notes

I discovered this list of file formats on the Lokalise website. The files store translation strings and are used by Lokalise for import and export.

I designed Pipi 9 to support any human language and writing system (script) in the future. This is done by separating string storage from the underlying code, data models, etc.

The Language Engine (lng) stores a standard set of strings. One engine per language/script). These engines then interact with the Factory Engine (fac) to build in one language/script.

  • Each engine or object
  • Each plug-in
  • Each DDD module
  • etc

Examples

That means there can be an English-in-Latin script version of the DevOps Engine (dvp), a Kurdish-in-Latin, a Kurdish-in-Hawar, and ;a Kurdish-in-Sorani, etc script version of the DevOps Engine (dvp), etc. The same goes for all plug-ins and SaaS apps; each can be available in many languages/scripts where needed.

Use

This will be very useful when I return to do more work on the Language Engine (lng).

Resources

Repository

  • Ajabbi Research > Library > Software > i18n

Last Updated

12/03/2025

Lokalise File Formats

Updated 2023

File format Name
android_sdk Lokalise Android SDK bundle
arb ARB
csv Comma-separated values
docx Docx
flutter_sdk Lokalise Flutter SDK bundle
html HTML
ini PHP INI
ios_sdk Lokalise iOS SDK bundle
js JavaScript Object
json JSON flat and JSON nested
json_structured Structured JSON
offline_xliff Offline XLIFF
php_array PHP arrays
php_laravel PHP Laravel
plist Objective-C/Cocoa Properties
po Gettext
properties Java Properties
react_native React Native (I18n library)
resx .NET Resources
ruby_yaml Ruby YAML
stf Salesforce Translation
strings Apple Strings
symfony_xliff Symphony PHP XLIFF
ts QT Linguist
xlf Angular i18n XLIFF
xliff Apple XLIFF
xlsx Excel 2007
xml Android Resources
yaml YAML

No comments:

Post a Comment