Translation file formats
Push the files your apps already use. Glossa reads plurals, comments and placeholders in each format, translates them, and writes every locale back in the same format.
Built in
Xcode String Catalog
Xcode String Catalogs: every locale, plural variation and comment in one JSON file.
Flutter ARB
Flutter Application Resource Bundles with ICU messages and @key metadata.
JSON (key/value, i18next)
Flat or nested key/value JSON, including i18next with its _one/_other plural suffixes.
YAML (Rails i18n)
Rails-style YAML locale files with a root locale key and nested scopes.
Apple .strings
Apple .strings files: "key" = "value"; pairs per lproj folder.
Apple .stringsdict
Apple .stringsdict plist files for plural rules.
Android strings.xml
Android res/values/strings.xml with <string>, <plurals> and <string-array>.
Gettext PO/POT
GNU gettext .po and .pot catalogs with msgctxt, plurals and translator comments.
XLIFF 1.2 / 2.0
XLIFF 1.2 and 2.0 bilingual files with source, target and notes.
Java .properties
Java .properties resource bundles, including Spring messages files.
.NET RESX
.NET RESX resource files with <data> entries and comments.
CSV / TSV (multi-locale)
CSV and TSV spreadsheets with a key column and one column per locale.
Formats it has never seen
A file no built-in format can read starts a learn_format job. The AI studies a sample and writes a declarative template: which parts are keys, values, comments and plurals. The template is validated against your file, filed as a task for you to keep or retire, and from then on reads every similar file without a model call.
Details in the formats guide, or call detect_format to see how a file would be read before you push it.
Push your first file
Glossa is free for one app. Sign in, push a translation file, and pull it back in every language.