mirror of
https://github.com/parsecsv/csv-spec.git
synced 2026-02-19 08:56:38 +00:00
Making certain terminology words bold was a horrible idea >_<
This commit is contained in:
15
README.md
15
README.md
@@ -67,8 +67,8 @@ character used in any given input CSV-like formatted file/data.
|
||||
|
||||
### Rules
|
||||
|
||||
1. Each **record** is located on a separate line, each line ending with a
|
||||
**line break** (CRLF or `\r\n`). For example:
|
||||
1. Each record is located on a separate line, each line ending with a line
|
||||
break (CRLF). For example:
|
||||
|
||||
CSV:
|
||||
|
||||
@@ -85,7 +85,7 @@ character used in any given input CSV-like formatted file/data.
|
||||
```
|
||||
|
||||
2. Though recommended, the last record in a file is not required to have a
|
||||
ending **line break**. For example:
|
||||
ending line break. For example:
|
||||
|
||||
CSV:
|
||||
|
||||
@@ -101,11 +101,10 @@ character used in any given input CSV-like formatted file/data.
|
||||
["xxx", "yyy", "zzz"] ]
|
||||
```
|
||||
|
||||
3. There maybe an optional **header** line appearing as the first line of the
|
||||
file with the same format as normal **record** lines. This **header** will
|
||||
contain names corresponding to the **fields** in the file and should
|
||||
contain the same number of **fields** as the **records** in the rest of
|
||||
the file. For example:
|
||||
3. There maybe an optional header line appearing as the first line of the
|
||||
file with the same format as normal record lines. This header will contain
|
||||
names corresponding to the fields in the file and should contain the same
|
||||
number of fields as the records in the rest of the file. For example:
|
||||
|
||||
```csv
|
||||
field_1,field_2,field_3¬
|
||||
|
||||
Reference in New Issue
Block a user