microsoft/nmarc

csv output not RFC 4180 compliant

Opened this issue · 0 comments

The csv files that are generated by this tool are not compliant with RFC 4180, specifically the part of the RFC that stipulates that:

Each line should contain the same number of fields.
Fields that contain a special character (comma, CR, LF, or double quote), must be "escaped" by enclosing them in double quotes (Hex 22)> .

Since none of the field values are encapsulated in double quotes in the CSV that is created by the NMARC tool, it means that "," characters in field values will be parsed as a delimiter, and not as an "escaped" coma...which causes problems for field values like "this is, a field value, with many comma's". The comma's in a field value like that should not be parsed as a delimiter, but as an "escaped coma".