You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 24, 2022. It is now read-only.
Some tools produce unnecessary escapings, making it difficult to distinguish between genuine differences resulting from data transformation and spurious differences resulting from such escapings.
As an exemple that is still in my mind, Gocsv transforms 2021-03-21 into 2021\-03\-21.
Unless I'm mistaken, Scrubcsv doesn't offer such kind of normalization.
It would be nice if it did.
The text was updated successfully, but these errors were encountered:
Do you have a specification describing any "standard" normalizations that should be performed? I suspect there's a list of these normalizations floating around somewhere, with a specific focus on ensuring that Excel doesn't treat certain character sequences as "magic." But I don't have a trustworthy and complete version of that list.
But in any case, it might be best to handle this in a separate tool. scrubcsv is not intended to replace CSV toolkits like xsv or gocsv. Its job is to get data into a clean, normalized format so that it can be piped into other tools.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Some tools produce unnecessary escapings, making it difficult to distinguish between genuine differences resulting from data transformation and spurious differences resulting from such escapings.
As an exemple that is still in my mind, Gocsv transforms
2021-03-21
into2021\-03\-21
.Unless I'm mistaken, Scrubcsv doesn't offer such kind of normalization.
It would be nice if it did.
The text was updated successfully, but these errors were encountered: