Import / Export / Text Import

For backup, sending to translation agencies, using offline tools, etc.

Within the content dashboard, we provide you with an ability to import and export phrases and translations.

Importing Phrases

You can import your source language phrases to use our translation management system and translation workflow, allowing your translators to add/edit translations. You can also import phrases and order professional translations from one of our third party providers directly through our platform.

You can also directly import your phrases and translations if they were done outside of Localize. When you upload these translations, your library gets updated. Existing translations will be overwritten, and new translations will be added from the file you upload.

To import, simply go to this link to begin managing resources.

Import compatibility

  • XLIFF
  • JSON
  • YAML
  • CSV
  • PO
  • iOS Strings
  • XML
  • RESX

If your import fails you can view the error here under Import History.

Exporting Phrases

Localize detects all the content found in your application. You can export your translations for backup purposes, to send to your translators (who can translate your content using a third party tool) or to delegate the translation process to a translation service of your choice.

To export, simply go to this link to begin managing resources.

Export compatibility

  • XLIFF
  • JSON
  • YAML
  • CSV
  • PO
  • iOS Strings
  • XML
  • RESX

If you have more questions or want to suggest a file format contact us.

File Types and Formatting

CSV

  • All CSV files must be comma delimited.
  • Strings with spaces must have double quotes around them.
  • They can contain an optional languages header which defines the source and target languages at the top of the file.
  • They must include a header above the data at the top of the file which contain names corresponding to the fields in the file.
    • e.g.: phrase,translation,description,phraseId
    • optional header fields: labels,source-language,target-language
    • (this header would be below the optional languages header if included)

For example:

source-language,target-language
en,fr
phrase,translation,description,phraseId
Hello source phrase, Hola translated frase
another phrase, another translation, a description, 56bb755f9cf47fbd0ebb8677

If you see errors such as "Invalid closing quote at line 1; found "\"" instead of delimiter "," you may be missing a comma in one of your lines, or have an extra one.


XML

XML String Resource files.

<?xml version = "1.0" encoding="UTF-8"?>
<!-- Generated by Localizejs.com App Localization -->
<resources>
    <source-language>en</source-language>
    <target-language>fr</target-language>
    <string name="Hello source phrase">Hola translated frase</string>
</resources>

YAML

For YAML files, the importer will handle one language per file. YAML is currently the only format that supports phrase keys, which can be nested.

en:
  welcome: Hello
  signup: Sign up
  contact:
    email: Email address

Exporting YAML will preserve the key structure which has been imported.


XLIFF

XLIFF is a format that's used to exchange data between participants in a translation project. This special format enables translators to concentrate on the text to be translated, without worrying about text layout.

<?xml version = "1.0" encoding="UTF-8"?>
<xliff version="1.2">
<file original="main" source-language="en" target-language="es">
<head></head>
<body>
<source xml:lang="en">Hello souce phrase</source>
<target xml:lang="es">Hola translated frase</target>
</trans-unit>

JSON

{
  "sourceLanguage": "en",
  "targetLanguage": "es",
  "dictionary": [
    {
      "translation": {
        "Hello souce phrase": {
          "value": "Hola translated frase"
        }
      }
    }
  ]
}

Text Import

Notice: Text Import Feature is Currently Unavailable

This feature is currently being rebuilt from the ground up in response to increased security requirements. The previously available functionality was not associated with any specific security incidents, but in an effort to maintain high standards for account and data protection, this functionality was suspended. We expect to release a new version of this functionality in the first quarter of 2019. The extended unavailability of this feature is a result of the sudden discovery of a Common Vulnerabilities and Exposures (CVE) report surfaced by our automated security scan relating to a software dependency that was formerly in use in relation to this functionality. The CVE was not confirmed as a security vulnerability in the Localize platform itself, and has not been a source of other security incidents prior to suspension of the functionality. However, it is our internal policy to take precautions to proactively mitigate potential security vulnerabilities -- while our mission is to build and deliver services that streamline and simplify localization workflows, our standard for maintaining an adequately secure platform to protect your account and your data takes precedence.

Please contact support if you have further questions, or if you would like to be notified when this functionality is restored.

Please visit the page linked below for an alternative mechanism for text import.


What's Next

Looking for a workaround for the Text Import functionality which was suspended earlier this year? Contact support, or visit the page below.

Text Import Workaround