CSV files¶
CSV files can contain a simple list of source and translation. Weblate supports the following files:
Files with header defining fields (
location
,source
,target
,ID
,fuzzy
,context
,translator_comments
,developer_comments
). This is the recommended approach, as it is the least error prone. Choose CSV file as a file format.Files with two fields—source and translation (in this order). Choose Simple CSV file as a file format.
Headerless files with fields in order defined by the translate-toolkit:
location
,source
,target
,ID
,fuzzy
,context
,translator_comments
,developer_comments
. Choose CSV file as a file format.Remember to define Monolingual base language file when your files are monolingual (see Bilingual and monolingual formats).
Hint
By default, the CSV format does autodetection of file encoding. This can be unreliable in some corner cases and causes performance penalty. Please choose file format variant with encoding to avoid this (for example CSV file (UTF-8)).
Warning
The CSV format currently automatically detects the dialect of the CSV file. In some cases the automatic detection might fail and you will get mixed results. This is especially true for CSV files with newlines in the values. As a workaround it is recommended to omit quoting characters.
See also
Multivalue CSV file¶
Added in version 4.13.
This variant of the CSV files allows storing multiple translations per string.
Example files¶
Example file:
Thank you for using Weblate.,Děkujeme za použití Weblate.
Weblate configuration¶
Typical Weblate Component configuration for bilingual CSV |
|
---|---|
File mask |
|
Monolingual base language file |
Empty |
Template for new translations |
|
File format |
CSV file |
Typical Weblate Component configuration for monolingual CSV |
|
---|---|
File mask |
|
Monolingual base language file |
|
Template for new translations |
|
File format |
Simple CSV file |