Importing localization files

Importing your localization files to Localazy is an easy alternative to uploading files using our CLI. You can import new keys for your source language or map existing translations to the current source keys.

The web import service supports all the available formats and integrations, and most import features available when using the CLI method.

Importing through file management 🔗

In an application where you have the Owner role, you have access to the file management section.

There is a + button in the upper right corner, which opens the Import & create new files modal.

Upload one or more localization files to begin the import process. In the next step, you will be able to add more or delete staged files for the import.

The import wizard will try to guess which languages the localization files represent, but you can also set these manually.

Additionally, a unique name for the new Localazy file will be generated, which you can modify, along with the file path. The file name and path combination must be unique, and the file name cannot be empty.

Lastly, a common file format or integration type is determined upfront for you, but you may modify it.

The last step consists of two options categories. The Format import/export options are format-specific options that modify how the imported files and their phrases are treated during import and export.

The Other import options are common options for all the format types and integrations.

Common options 🔗

Mark phrases excluded from this batch as deprecated 🔗

When checked, any existing source key that is not included in the imported files will be marked as deprecated. Deprecated phrases are still available but are not visible to translators.

Import all translations as new 🔗

When checked, every imported translation has to go through a review process. When unchecked, imported translations are marked as current without the necessity to review them. This option does not affect files with the source language.

Skip translations that copy source language 🔗

When checked, phrases that are the same as in the source language are not imported. This is important for platforms like iOS, where localizable files contain the source phrase where the translation is not available. This option has no effect while importing files in the source language.

Localazy file 🔗

When you import multiple files, you may be surprised to see only a single file in the file management table. Localazy files are different from the localization assets you’ve uploaded.

Without going into too much detail, in Localazy, the file doesn’t represent a single separate language file you might find in your project. The Localazy file contains all translations. Therefore, you will see a single file in the list even if it exists in many localized versions. Each file in Localazy is uniquely identified by the file’s type, filename, and path.

The provided filename is the actual name you will see when you download the file, either manually through our CDN or using the CLI method. Additionally, if you provide the path, you can use it in your CLI configuration.

Update existing localization files 🔗

If you wish to add new source keys or translations or update existing ones, you may use the Import content to file option under the Localazy file’s dropdown options.

This import wizard is a simplified version of the import wizard for a new file.

Adding a new source key to a file 🔗

You can add a new source key into a file when navigating to the file detail. There is a table with all source keys contained in the file.

Find a + button in the top-right table corner. A modal with Key, Source translation and Translation note fields should appear. Remember that the keys must be unique for the file and the Source translation cannot be blank.

Structured keys

Keys containing . will be interpreted as nested structures in formats that support nesting.

For example my.key in JSON will be interpreted as:

{
  "my": {
    "key": "..."
  }
}

If you don’t want this behaviour, simply don’t use dots to separate words or uncheck the “Use dot (.) to create nested keys” checkbox and the key will be created as following:

{
  "my.key": "..."
}