Changes

{{Version|7.7.2}}: the conversion rules have been updated and aligned with the JSON parser:.

The conversion of CSV data is based on the following rulesconverted to XML as follows:

# The resulting XML document has a {{Code|<csv/>}} root nodeelements. # Rows are represented via {{Code|<record/>}} nodeselements. # Fields are either named represented via {{Code|<entry/>}} or (if elements. The value of a field is represented as text node.# If the CSV {{Code|header }} option is set to {{Code|true}}, the first text line is parsed) named by as table header, and the {{Code|entry}} elements are replaced with the corresponding column namefield names:## Empty field names are represented by a single underscore ({{Code|&lt;_&gt;...&lt;/_&gt;}}), and characters that are not valid in element names are replaced with underscores.## Underscore If the {{Code|lax}} option is set to {{Code|false}}, invalid characters are will be rewritten to an underscore and the character’s four-digit Unicode, and underscores will be represented as two underscores ({{Code|__}}). The resulting element names may be less readable, but can always be converted back to the original field names.## A character that cannot If {{Code|format}} is set to {{Code|attributes}}, field names will be represented as NCName character stored in name attributes. If the JSON parser is selected in the Database Creation dialog of the GUI, a simple example is rewritten displayed to an underscore and its four-digit Unicodeshow the effects of the available options.