Describe the problem

The spec mention that "Each line must end with a CRLF or LF linebreak character." Would be nice if the validator could detect malformated files.

We had a user crafting a GTFS file with a script and with bad linux format, windows format interaction, ended up with CRCRLF as the end of line, crashing a standard CSV parser like papaparse. It tried the file in the validator, but got no error report.

Describe the new validation rule

For each line of each .txt file
If EOL char != "CRLF" or "LF"
report error

Need to also detect extra CR or LF.

Sample GTFS datasets

No response

Severity

No response

Additional context

No response