Fix reading text files with carriage return symbols
NONE
Discussed in #622, fixed in #715. Closing the issue. Thanks @lhoestq, it works now! 👍 
2020-10-05T13:49:29Z
https://github.com/huggingface/datasets/pull/713#issuecomment-703645003
https://api.github.com/repos/huggingface/datasets/issues/713
MDEyOklzc3VlQ29tbWVudDcwMzY0NTAwMw==
https://api.github.com/repos/huggingface/datasets/issues/comments/703645003/reactions
2020-10-05T13:49:29Z
https://api.github.com/repos/huggingface/datasets/issues/comments/703645003
https://avatars.githubusercontent.com/u/6762769?v=4
https://api.github.com/users/mozharovsky/events{/privacy}
https://api.github.com/users/mozharovsky/followers
https://api.github.com/users/mozharovsky/following{/other_user}
https://api.github.com/users/mozharovsky/gists{/gist_id}
https://github.com/mozharovsky
mozharovsky
MDQ6VXNlcjY3NjI3Njk=
https://api.github.com/users/mozharovsky/orgs
https://api.github.com/users/mozharovsky/received_events
https://api.github.com/users/mozharovsky/repos
https://api.github.com/users/mozharovsky/starred{/owner}{/repo}
https://api.github.com/users/mozharovsky/subscriptions
User
https://api.github.com/users/mozharovsky
public
The new pandas-based text reader isn't able to work properly with files that contain carriage return symbols (`\r`). 

It fails with the following error message:

```
...
  File "pandas/_libs/parsers.pyx", line 847, in pandas._libs.parsers.TextReader.read
  File "pandas/_libs/parsers.pyx", line 874, in pandas._libs.parsers.TextReader._read_low_memory
  File "pandas/_libs/parsers.pyx", line 918, in pandas._libs.parsers.TextReader._read_rows
  File "pandas/_libs/parsers.pyx", line 905, in pandas._libs.parsers.TextReader._tokenize_rows
  File "pandas/_libs/parsers.pyx", line 2042, in pandas._libs.parsers.raise_parser_error
pandas.errors.ParserError: Error tokenizing data. C error: Buffer overflow caught - possible malformed input file.
```

___
I figured out the pandas uses those symbols as line terminators and this eventually causes the error. Explicitly specifying the `lineterminator` fixes that issue and everything works fine. 

Please, consider this PR as it seems to be a common issue to solve.