You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/home/rules.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,23 +30,23 @@ In the table bellow all the rules of [RFC-4180](https://www.ietf.org/rfc/rfc4180
30
30
</tr>
31
31
<tr>
32
32
<tdstyle="text-align: left;"><em>There maybe an optional header line appearing as<br> the first line of the file with the same format<br> as normal record lines. This header will contain<br> names corresponding to the fields in the file and<br> should contain the same number of fields as the<br> records in the rest of the file.</em></td>
33
-
<tdstyle="text-align: left;">In the same way. The presence or absence of the<br> header line should be indicated via the optional<br> "HeadersOmission" parameter.</td>
33
+
<tdstyle="text-align: left;">In the same way. The presence or absence of the<br> header line should be indicated via the option<br> <code>headersOmission</code>.</td>
34
34
</tr>
35
35
<tr>
36
36
<tdstyle="text-align: left;"><em>Within the header and each record, there may be<br> one or more fields, separated by commas. Each<br> line should contain the same number of fields<br> throughout the file. Spaces are considered part<br> of a field and should not be ignored. The last<br> field in the record must not be followed by a<br> comma.</em></td>
37
37
<tdstyle="text-align: left;">The class accepts CSV files with different numbers<br> of fields per record. The spaces betwen the<br> fields separator char and a single field is ignored<br> only if that field is enclosed in double quotes.</td>
38
38
</tr>
39
39
<tr>
40
40
<tdstyle="text-align: left;"><em>Each field may or may not be enclosed in double<br> quotes (however some programs, such as Microsoft<br> Excel, do not use double quotes at all). If<br> fields are not enclosed with double quotes, then<br> double quotes may not appear inside the fields</em></td>
41
-
<tdstyle="text-align: left;">In the same way. The class accepts also the<br> apostrophe char for indicate fields needing to<br> be escaped. It's important to notice that a<br> single CSV record may have fields enclosed and<br> not enclosed by the escape char.</td>
41
+
<tdstyle="text-align: left;">In the same way. The class accepts also the<br> apostrophe and tilde char for indicate fields needing to<br> be escaped. It's important to<br> notice that a single CSV record may have fields enclosed and<br> not enclosed by the escape char.</td>
42
42
</tr>
43
43
<tr>
44
44
<tdstyle="text-align: left;"><em>Fields containing line breaks (CRLF), double<br> quotes, and commas should be enclosed in double<br> quotes</em></td>
45
45
<tdstyle="text-align: left;">In the same way. Also accepts fields enclosed by<br> the apostrophe char.</td>
46
46
</tr>
47
47
<tr>
48
48
<tdstyle="text-align: left;"><em>If double-quotes are used to enclose fields, then<br> a double-quote appearing inside a field must be<br> escaped by preceding it with another double quote.</em></td>
49
-
<tdstyle="text-align: left;">Ignored rule. The class accepts the apostrophe<br> as escape char, and follow the specs claims<br> may cause conflict with some abbreviate US<br> slangs (e.g.: "<strong>isn't</strong>").</td>
49
+
<tdstyle="text-align: left;">In the same way. The class also accepts a Unix-style quote escape by preceding the quote with a<br> backslash (<strong>"\"</strong>").</td>
0 commit comments