After uploading CSV or XLSX files to the project, they require additional configuration before the system could import the content of these files.
To configure CSV or XLSX files, follow these steps:
The same configurations mentioned in this article are also applicable to the TSV file format. The main difference between CSV and TSV files is that they use different delimiters between columns (i.e., comma in CSV and Tab in TSV).
When configuring XLSX files, you’ll have the following options:
Import all cells - import each cell as a separate source string. Additionally, you can use Content Segmentation to split the source file’s content into shorter text pieces, mostly sentences and short paragraphs. This is helpful when translating content units consisting of several sentences because it will be easier to translate smaller pieces of text. Segmentation Rules eXchange (SRX) are used for automatic content segmentation.
Configure columns for import - specify the preferred column order.
When configuring CSV or XLSX file with Configure columns for import option, you can specify the following column types:
Once you open the configuration dialog for source files in CSV or XLSX formats, the system automatically detects the file scheme based on the column names specified in the first row. The identification is performed in a case-insensitive manner. Columns that weren’t detected automatically will be left as Not chosen for manual configuration. Automatic column identification is especially helpful when you upload multiple multilingual spreadsheets that contain many languages and additional columns (e.g., Context, Labels, Max. Length).
To get the most out of the automatic column detection, we recommend that you name the columns in your CSV or XLSX source files using the values displayed in the table below:
|Column type||Expected value|
|Source String|| |
|Source String/Translation|| |
|Max. Length|| |
|Language (for multilingual files)||Language name (e.g., Ukrainian), Crowdin language code, Locale (e.g., uk-UA), Locale with underscore (e.g., uk_UA), Language code ISO 639-1 (e.g., uk), Language code ISO 639-2/T (e.g., ukr)|
By default, during scheme configuration, the system treats CSV and XLSX source files as monolingual. To autodetect file scheme for multilingual source files, follow these steps:
If multiple files have the same configuration scheme, save your current configuration as a template by clicking Templates > Save as template, then specify the template name and click Create. You’ll be able to apply the template to the newly imported files.
If you don’t want to translate the column headers, select Do not import the first row (header).
If you’d like to start the spreadsheet configuration over, click Reset configuration.
If your file contains several columns with translations into different languages, select Multilingual spreadsheet and map the languages to the appropriate columns.
By default, when you configure the multilingual spreadsheets, the Import translations option is selected. If you’d like not to import the existing translations from the file, you can clear this option.
If your multilingual source file doesn’t contain enough columns for all project target languages, click Add column. To remove one of the added columns, click Delete selected column.
To configure several selected CSV or XLSX files, right-click and select Configure files.
To configure all CSV or all XLSX files at once, click Configure All.
In the configuration window, you’ll be able to switch between the selected files to preview and verify if the applied configuration is correct for all files.
You might want to update CSV or XLSX files and change the initially configured scheme. The scheme update might be needed when you add a new target language to your Crowdin Enterprise project.
To change the scheme for your source file, follow these steps: