Skip to content

Commit d2dbe78

Browse files
committed
Update rules.md
1 parent fb71aa2 commit d2dbe78

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/home/rules.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,23 +30,23 @@ In the table bellow all the rules of [RFC-4180](https://www.ietf.org/rfc/rfc4180
3030
</tr>
3131
<tr>
3232
<td style="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-
<td style="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+
<td style="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>
3434
</tr>
3535
<tr>
3636
<td style="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>
3737
<td style="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>
3838
</tr>
3939
<tr>
4040
<td style="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-
<td style="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+
<td style="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>
4242
</tr>
4343
<tr>
4444
<td style="text-align: left;"><em>Fields containing line breaks (CRLF), double<br> quotes, and commas should be enclosed in double<br> quotes</em></td>
4545
<td style="text-align: left;">In the same way. Also accepts fields enclosed by<br> the apostrophe char.</td>
4646
</tr>
4747
<tr>
4848
<td style="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-
<td style="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+
<td style="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>
5050
</tr>
5151
</tbody>
5252
</table>

0 commit comments

Comments
 (0)