Manual Import

How to Manually Import Files to the Applanga Dashboard

This Article will show users how and where to manually import files to the Applanga dashboard. Users can import a file with source or target content (existing translations) to a given project and language. Applanga accommodates the following files for import with a max file size of 20 MB:

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

For more information regarding supported file types and formatting, refer to the File Formats Documentation.

The Applanga dashboard handles imports differently based on the type of file used.

• For .xliff which specifies which languages are contained therein, Applanga will allow the upload to the appropriate language only. Source or target language code in the given xliff has to match the language on the dashboard in the Applanga project.
• For Excel, TSV and CSV files, the user must specify what content is included in the file such as which columns correspond to which kind of content (e.g. column A is source strings, column B is string Id, etc.)
• For native file types e.g. Android string .xml or iOS .strings files, users must import the file in the appropriate language i.e. the Applanga importer will not check if the content in the file matches the selected language.

Table of Contents

1. Importing a File During the Onboarding Dialog
2. Importing a File to an Existing Project
3. Importing a file in the String Management Interface
4. Import Options
5. Importing Excel Files

How to Import a File During the Onboarding Dialog

1. Add a new project by clicking the + Add Project button
2. Complete required fields in the Onboarding Dialog then select Manual Upload
   
3. Drag & Drop or click Browse files in the file explorer to choose the file for manual upload
4. Mark the appropriate checkboxes in the Importer Options pop-up (refer to the Import Option Descriptions below for more detailed information)
5. Click Import

Back to Top

How to Import a File to an Existing Project

1. Open the project in the Applanga Dashboard and click Add Source Files
2. Drag & Drop or click Browse files in the file explorer to choose the file for import
3. Mark the appropriate checkboxes in the Importer Options pop-up (refer to the Import Option Descriptions below for more detailed information)
4. Click Import

Back to Top

How to Import a File in the String Management Interface

1. Navigate to the project in the Applanga Dashboard and open the String Management Interface/Editor by selecting the specific project language
2. Click Import then Drag and Drop or click Browse files in the file explorer to choose the file for import
3. Mark the appropriate checkboxes options in the Importer Options pop-up (refer to the Import Option Descriptions below for more detailed information)
4. Click Import

Back to Top

Import Option Descriptions

1. Import and Overwrite - Applanga imports strings with their values. It also overwrites any existing string values with the new string values found in the imported file. For xliff files, this will also apply to any status, description, and string length restriction defined in the imported file

2. Import only as draft - The strings and the values contained in the file will import as drafts. If the published translation of a given string already has the same value as in the file to be imported, this value is skipped to avoid duplicated content.

3. Import only if text is empty - Only empty strings will have their values imported from the file, skipping all strings which already have a value on the dashboard. This avoids overwrites.

4. Skip locked translations - Strings that are locked will not have any values imported from the file.

5. Skips strings with no translations - Strings which have no value/are empty in the imported file will be ignored for any other purposes. This will avoid overwriting e.g. status or description on Applanga without updating the value too.

6. Disable Plural Support - Plural strings (e.g. ‘one,’ ‘two,’ ‘many,’ and ‘few’) will be treated as regular keys.

7. Change state to - enables users to set a state of ‘Accepted’ or ‘Need Review’ for imported strings

8. File specific options.

   • Import Status from Xliff - sets status based on the status of the string found in the .xliff
   • Create unknown custom states (.xliff files) - Add unknown custom states from the .xliff file to the team
   • Save Source File Name - Saves the file name along with the imported strings so they can be filtered and exported using this file name and split at a later date.

9. Tag with - Adds tags to imported string IDs. Existing tags can be added or new tags can be created.

Back to Top

Importing Excel, TSV, and CSV Files

Please note, these additional steps apply to the following file types only: .csv, . xls, .xlsx. After importing the files and selecting the appropriate Import Options, users must specify which columns correspond with which values.

1. After clicking Import and selecting the appropriate Import Options, users must wait for the Import Spreadsheet pop-up to load. For larger files, this step may take a moment.

2. Navigate to the tab from which content should be imported and select the appropriate dropdown menu option for each column to define how the data in the given column should be imported to Applanga.

   • At least the string Id and one language must be defined
   • Users can also associate each column with the following values: String Identifier, String Length, String Description, translations for languages already present in the Applanga project, and additional Custom Metadata Field values

   

Important Note!

Users can either import only metadata OR import metadata for all strings that also have a language value.

• If you ONLY select a column for string Ids/keys and a column for one or more metadata values, the metadata values for all keys will be imported to the project.
• If you select a column with values for any language, the metadata will only be imported for those string Ids/keys that also have a language value. Ids/keys with no lnaguage value will not be imported to the project.

Back to Top