|Perl: the Markov chain saw|
Re^8: Native newline encodingby sauoq (Abbot)
|on May 28, 2012 at 17:40 UTC||Need Help??|
Well, that is simply incorrect. It's not incorrect to say it is a text format, of course. It's just incorrect to say that it isn't binary. Textual data is binary even if not all binary data is textual. I imagine you know this, but on computers,† even text is represented with two values.‡
The only time drawing a distinction between text and binary data actually matters is when when working on a platform that was designed with the questionable choice to arbitrarily support two different sets of semantics.
What you should learn from all the "unicrap" stuff is that text was just never a very meaningful term to begin with. It's only precise use is as an instruction to handle the data in a platform specific manner.
Furthermore, on those platforms where it is meaningful, it's a relic from an era when the only data presented for human consumption was textual. Nowadays, that's just not the case; and the appropriate question is simply: "what format?" Is it an old word document? A spreadsheet? ASCII? ASCII with CRLF line endings? UTF-8? JPG data? Etc.
† Almost all computers in use today, that is.
‡ Hence, even the term 'binary data' is generally redundant.
"My two cents aren't worth a dime.";