When converting a database to 4D v11 SQL, textual data are converted into Unicode. In order for the conversion to be carried out correctly, 4D must know the source character set. By default, the character set corresponding to the current system language is used.
Every 4D database has a language. All data will be stored in the current script of the operating system unless otherwise specified. This can be an issue if your database has data from multiple languages. If your data file contains a field with some Japanese characters and another with some Russian characters, the conversion will convert all characters to the current system language by default.
Before conversion you must specify which language script should be used via a text file placed at the same level as the data file to be converted. This file must have the following characteristics:
|Encoding||ANSI or Mac Roman||Do not use Unicode|
|Format||table_number separator field_number separator subfield_number separator dialect_code CRLF||The "subfield_number" entry is optional.|
|Line Endings||CR or CRLF||Each row must be ended with a carriage return, empty rows and spaces are allowed.|
You cannot define 2 language scripts for one field. In other words, it will not work if the same field contains some Japanese and Russian characters.
See the "Conversion Guide" for dialect codes: