The following file extensions are supported when setting up file format configurations for CSV: .csv.
For more information, please see the following sections:
Default CSV Configuration
Every file format has a default configuration to ensure that a file can be translated; however, it does not handle every complex property that could be thrown your way when translating a source file. The default configuration for CSV files does the following:
- Handles monolingual content.
- Uses UTF-8 encoding.
- Translates all columns using a comma as the default separator.
- Uses SRX rules for segmentation and splits text at line breaks.
- Does not show leading and trailing whitespaces.
Custom CSV Configurations
If you use CSV files for translations, a custom file format configuration might be necessary to achieve the right results in your target file. Outside of the default configuration selections, Wordbee Translator offers additional choices for:
- Translation of monolingual and multilingual CSV files.
- Configuring what will not be translated (i.e. columns & rows).
- HTML content extraction.
- Handling whitespaces and symbols.
To learn more about available file format configurations for CSV, please see the CSV Configuration Options page.
A Few Examples
The following are just a few examples of what you can do with a custom CSV configurations in Wordbee Translator. For more advanced examples, please see our CSV Questions and Answers page.
Translating Multilinqual CSV Files
The default configuration is designed to translate monolingual files; however, a custom configuration will be necessary when needing to translate a multilingual CSV file.
Changing the Default Character Encoding
The default configuration is automatically set up to use UTF-8 encoding. In some instances, the file may be using a different type of encoding and a custom configuratoin is necessary to ensure a proper translation.
Configuring Specific Columns and Rows for Translation
In some instances, only specific columns or rows within the CSV file will need to be extracted for translation. For example, maybe only Columns B and D need to be translated and the extraction should start on another row other than Row 1. In order for the translated target file to be correct, a custom configuration must be created to accomplish this task.
For more information, please see the following pages: