Date: Fri, 29 Mar 2024 14:31:33 +0000 (UTC) Message-ID: <567716921.7.1711722693178@node2041-mqi-confluence.web.inetsolutions.cloud> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6_1996610139.1711722693177" ------=_Part_6_1996610139.1711722693177 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
CSV files must contain at lea= st three columns. One of the columns has the column header "id", and contai= ns a unique ID for each CSV line. Another column has the column header "sou= rce" and contains the source language. All other columns with column header= s are treated as the target language columns and imported. In this case, th= e column header name is arbitrary. Columns without a filled column header i= n 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 fi= le is exported en the same encoding as it existed during import (Note: For = a translation into non-Western European languages therefore utf-8 should al= ready be selected as the import encoding).
The column header name of the ID column (by default mid) and the source la= nguage column (by default quelle) as well as the column separator and the t= ext delimiter can be overridden in the installation-specific system configu= ration translate5. Search in your SQL database of translate5 with the= following statement to find the csv-related configs:
SELECT *= FROM `Zf_configuration` WHERE `name` LIKE '%csv%'