> It's much less likely that content is going to include ASCII 28 to 31 than that it will include a comma or a tab. But you're right, certainly not impossible.

> It's much less likely that content is going to include ASCII 28 to 31 than that it will include a comma or a tab. But you're right, certainly not impossible. Yeah, that's the same problem as UTF-8's almost-compatibility with ASCII. Things work, until they break spectacularly. Ultimately, you either have to solve the issue properly, or keep it visible enough that people are forced to handle it.