...
Changes can be tagged in CSV in the export using HTML syntax.
Encoding
Multiple target columns
translate5 supports multiple target columns in the translate5 editor. If the imported CSV file has multiple target columns, they are imported and exported accordingly.
Format specifications
CSV files must contain at least three columns. One of the columns has the column header "mid", and contains a unique ID for each CSV line. Another column has the column header "quelle", (German for source) and contains the source language. All other columns with column headers are treated as the target language columns and imported. In this case, the column header name is arbitrary. Columns without a filled column header in the CSV file are ignored during import.
Column separator of CSV is a comma "," text delimiter is a quotation marks (").
Line separator of CSV is a Linux, Mac or Windows newline.
Encoding of the CSV file can utf-8, iso-8859-1 or windows-1252. The CSV file is exported in the same encoding as it existed during import (Note: For a translation into non-Western European languages therefore utf-8 should already be selected as the import encoding).
Overwriting of format specifications
The column header name of the ID column (by default mid) and the source language column (by default quelle) as well as the column separator and the text delimiter can be overridden in the installation-specific system configuration translate5. When importing, the encodings UTF-8, ISO-8859-1, and WINDOWS-1252 are supported. For more on CSV as an import format, please refer to Information about operation of translate5.
Star Transit NXT language pairs
translate5 supports the Start Transit NXT language pairs for import and export.
Track changes
...
Changes can be tagged in Transit language pairs in the export using HTML syntax (be careful: this is not useful inside Transit and may break it. It is only for use on file level).
...