"All theory, dear friend, is gray, but the golden tree of life springs ever green." -Goethe If CSV were indeed always comma-separated, my hair would be at leas

"All theory, dear friend, is gray, but the golden tree of life springs ever green." -Goethe If CSV were indeed always comma-separated, my hair would be at least 5% less gray. Alas, most programs emit semicolon-separated "CSV" in some locales (MS Office, LibreOffice, you-name-it-they-got-it). Of course, I understand that your academic position "if it chokes the RFC-compliant parser, it's not a True CSV and should be sent to /dev/null" tautologically exists - but for some reason, users tend to object to such treatment (especially when they have no useful tools that would emit your One True Format for them). TL;DR: there is no single standard fitting all the things that call themselves "CSV".