Changes

Jump to navigation Jump to search
542 bytes added ,  13:30, 14 August 2016
no edit summary
==Options==
 
{{Mark|Updated with Version 8.6}}: improved Excel compatibility
 
The following options are available:
|- valign="top"
| {{Code|quotes}}
| Specifies if how quotes are parsed:* Parsing: If the option is enabled, quotes at the beginning start and the end of a field should value will be treated as control characters. Separators and newlines within the quotes will be detectedadopted without change.* Serialization: If the option is enabled, and generated as such the value will be wrapped with quotes. Quote characters in the outputvalue will be encoded according to the rules of the {{Code|backslashes}} option.
| {{Code|yes}}, {{Code|no}}
| {{Code|yes}}
|- valign="top"
| {{Code|backslashes}}
| Specifies if how quotes and other characters are escaped by backslashes, or if quotes are encoded by a second consecutive quote:* During parsing, if Parsing: If the option is enabled, <code>{{Code|\r</code>}}, <code>\{{Code|n</code> }} and <code>{{Code|\t</code> }} will be replaced with the corresponding control characters. All other escaped characters will be adopted as literals (e.g.: <code>{{Code|\"</code> }} <code>{{Code|"</code>}}). If the option is disabled, two consecutive quotes will be replaced with a single quote (see the <code>{{Code|quotes</code> }} option for exceptions).* Serialization: If the option is enabled, {{Code|\r}}, {{Code|n}}, {{Code|\t}}, {{Code|\"}} and the separator character will be escaped with a backslash. If the option is disabled, quotes will be duplicated.
| {{Code|yes}}, {{Code|no}}
| {{Code|no}}
=Changelog=
 
;Version 8.6
 
* Updated: [[#Options|Options]]: improved Excel compatibility
;Version 8.0
Bureaucrats, editor, reviewer, Administrators
12,235

edits

Navigation menu