3 ms·
That’s only a complaint for people who use CSV. If you use the ascii characters for record, file, unit, and group there are no problems with data payload
by wombatpm 4y ago
That’s only a complaint for people who use CSV. If you use the ascii characters for record, file, unit, and group there are no problems with data payload
- zokier 4y ago> If you use the ascii characters for record, file, unit, and group there are no problems with data payload Unless your data happens to contain record, file, unit, group separators... Which is kinda the whole problem; ASCII does not have any proper separation/layering between the data and control characters.
- rep_lodsb 4y agoIf your fields are supposed to be human-readable text, there might be a reason for them containing tabs, but not these control characters. Obviously you need a more elaborate protocol for embedding arbitrary data, but ASCII isn't the right place to define that.
- bhaak 4y agoThe TAB character is not any different from the separator control characters. It is as non human readable as the other ones. It's just that it got more support historically. If e.g. Microsoft had used the separator control characters for CSV you can bet those control characters would have even better support than TAB does today.