> The issue with CSV, as far as I am concerned, is the escaping. And that isn't minor from either a readability or parsing point of view. For parsing I'd agree

> The issue with CSV, as far as I am concerned, is the escaping. And that isn't minor from either a readability or parsing point of view. For parsing I'd agree, as you've eliminated the need to handle escaping by declaring some characters off-limits. But for manual editing, to start a .usv file with most editors people would be copying the characters from google rather than just being able to type commas and newlines. > Are \u001F or \u001E even legal filename characters on any OS? These codes could turn up by chance in a blob of binary data. But it isn't intended for binary data. Generally I believe NUL and / are the only ASCII characters considered safe to never occur in file/directory names.