× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Fri, Jun 4, 2021 at 8:02 PM Roger Harman <roger.harman@xxxxxxxxxxx> wrote:

If it were properly escaped, it would be a non-issue. However, most any printable character could be possible in the "real" data.

I don't understand the second sentence in relation to the first. I
mean, both statements are plainly true, but why the "however" there?

That's why I prefer *TAB delimited or fixed width. It's pretty hard to screw those up.

But Excel does something most people would not expect with tab
delimiters, which might count as screwing it up. And since lots of
people use Excel, I would say it's pretty darn easy to screw up
tab-delimited files.

Fixed width has the problem of whether you are talking about
characters or bytes. In today's UTF-8-dominated world, each character
has a variable number of bytes.

This is why *I* say: people should stop rolling their own. Yes, you
can come up with a "technically superior" scheme than Excel or whoever
else. That doesn't mean other people will adhere to it, especially if
it means they have to roll their own to do it.

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.