Skip to content

Commit ff24b92

Browse files
committed
fixing UTF-16 version and command line example
1 parent 554f511 commit ff24b92

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -167,10 +167,10 @@ npm start -- --entries-filter --from-date <YYYY-MM-DD> --to-date <YYYY-MM-DD> --
167167

168168
#### Byte Order Markers in CSV Files
169169

170-
The extraction client has built-in handling of byte order markers for CSV files in UTF-8 and UTF-16 encodings. When using CSV files in other encodings, if you experience unexpected errors be sure to check for a byte order marker at the beginning of the file. One way to check is to run the following command from the command line:
170+
The extraction client has built-in handling of byte order markers for CSV files in UTF-8 and UTF-16LE encodings. When using CSV files in other encodings, if you experience unexpected errors be sure to check for a byte order marker at the beginning of the file. One way to check is to run the following command from the command line:
171171

172172
```bash
173-
cat -v file.csv
173+
cat -v <file.csv>
174174
```
175175

176176
If there is an unexpected symbol at the beginning of the file, then there is a byte order marker that needs to be removed.

0 commit comments

Comments
 (0)