Manual Export

How to Manually Export Files from the Applanga Dashboard

This Article will show users how and where to manually export files from the Applanga dashboard. Users can export a file from a given project and language(s.) Applanga supports the following file formats for exports:

.csv, .tsv, .ini, .js, .json, .properties, .po, .pot, .resw, .resx, .strings, .stringsdict, .xls, .xlsx, .xliff, .xlf, .xml, .yaml, .yml, .arb, .tmx, .tbx, .php, .qt, .ts, .toml, .md

See the Supported File Formats section for more details.

Table of Contents

1. How to Export Strings from the Project Page
2. How to Export Strings from the String Management Interface
3. How to Export Specific Strings from the String Management Interface
4. Exporter Options
5. Exporting .TS Files

How to Export Strings from the Project Page

1. Navigate to the project page
2. Click Export Bundled Translations
3. Select the appropriate file format, languages, and options for download then click Start Export

Back to Top

How to Export Strings from the String Management Interface

1. Open the String Management Interface then click Export
2. Select the appropriate file format, languages, and options for download then click Start Export

Back to Top

How to Export Specific Strings from the String Management Interface

1. From the String Management Interface use the tag, filter, or search options to find the specific strings for export
2. Mark the checkboxes for the specific strings for export
3. Click the More dropdown and then select Export Selected
4. Select the appropriate file format, languages, and options for download then click Start Export

Back to Top

Exporter Options

1. File Formats: .csv, .tsv, .ini, .js, .json, .properties, .po, .pot, .resw, .resx, .strings, .stringsdict, .xls, .xlsx, .xliff, .xlf, .xml, .yaml, .yml, .arb, .tmx, .tbx, .php, .qt, .pdf, .md
2. Languages: The languages included in the project. Users can export individual or all languages.
3. Options: Export options are file format specific. Export Options available for all file formats include the following:
   • Use Source File Name: If strings were manually imported, Use Source File Name will export translations into a file with the same name as the originally imported file only adding a language indication. If multiple files were imported and this option is set, the strings included in the export will split into the same sets per file as they have been imported.
   • Only with Translation: This option only exports the translated strings, source strings are excluded from the export file.
4. File Specific Options:
   • Include Context URL: This option includes a direct link to the screenshot(s) on which a string or strings appears (where available.) This option is only available for .xliff.
   • Export Status: A string’s status can be set to Rejected, Needs Translation, Needs Review, Accepted, or any previously defined custom workflow status.. This information will be included in the .xliff export if Export Status is selected. This option is only available for .xliff.
   • Include Metadata: If this option is selected, the exported file will also contain any custom metadata fields associated with the string. This option is available for .xliff, .csv, .tsv, .xlsx (both single and multi-language excel files.)
   • Include Status & Comment: A string’s status can be set to Rejected, Needs Translation, Needs Review, Accepted, or any previously defined custom workflow status. This information will be included in the export if Export Status is selected together with the latest comment for a particular string. This option is only available for .csv, .tsv, .xlsx (excluding multi-language excel files.)
   • Convert Placeholders: This option converts iOS and Android placeholders during export. It is only available for Android (.yml) and Apple (.strings) files. See the Placeholder Coversion article for more information.
   • Screenshot Export Options: Refer to the Screenshot Export article for detailed steps and description of export options.

Back to Top

TS File Considerations

While it is possible to export any content from Applanga into a .ts file, the .ts file format behaves a little differently than most other formats in order to be compatible with Applanga.

If the content was created via a .ts file import, the resulting export will contain values in the <name>, <source> and <comment> fields.

If the content was NOT created via a .ts file import and is exported as .ts file, the file will contain the Applanga key/string Id as part of the <message> field (e.g. <message id="......">)

All strings exported will always be in the <translation> field, including source content.

See the TS file documentation for more information.

Back to Top