undefined | Better HN

0 pointssakjur1y ago0 comments

Look at how it handles escaping of special characters and particularly new lines (RFC 4180 doesn’t guarantee that a new line is a new record) and how it’s written in 2005 yet still doesn’t handle unicode other than via a comment about ”other character sets”.

0 comments

inglor_cz1y ago

"how it’s written in 2005 yet still doesn’t handle unicode other than via a throwaway comment about ”other character sets”"

Yeah, you are spot on with this one (cries in Czech, which used to be encoded in several various ways).

Someone12341y ago

> RFC 4180 doesn’t guarantee that a new line is a new record

Correctly. A good parser should step through the line one column at a time, and shouldn't even consider newlines that are quoted.

If you're naively splitting the entire file via newline, that isn't 4180's fault, that is your fault for not following the standard or industry norms.

I'll happily concede the UNICODE point however; but I don't know if that makes it controversial.

j / k navigate · click thread line to collapse