On Mon, Jul 7, 2014 at 1:12 PM, Joel Rees <joel.r...@gmail.com> wrote: > On Mon, Jul 7, 2014 at 7:54 PM, Nuno Magalhães <nunomagalh...@eu.ipp.pt> > wrote: >> On Mon, Jul 7, 2014 at 4:09 AM, Joe Pfeiffer <pfeif...@cs.nmsu.edu> wrote: >>> My typical experience is that when people distinguish "text" vs >>> "binary" files, they mean the whole file can reasonably be made sense >>> of in a text editor (that's not a precise definition, of course, but I >>> think it serves the purpose). When I open an SQLite database I have >>> handy with emacs, it is rife with nulls and other non-printing >>> characters. >> >> That's what i meant by "text", yes. >> >> Perl::DBI + SQLite seems to be taking the lead. > > Uhm, so, you mean, you can reasonably make sense of it with hexdump > -C? (Or a custom hexdump that handles your brand of multi-byte > characters, perhaps?)
If it's really that mission-critical to you, the quotation part i was referring to is this: >> On Mon, Jul 7, 2014 at 4:09 AM, Joe Pfeiffer <pfeif...@cs.nmsu.edu> wrote: >>> My typical experience is that when people distinguish "text" vs >>> "binary" files, they mean the whole file can reasonably be made sense >>> of in a text editor (that's not a precise definition, of course, but I >>> think it serves the purpose). Not this: >>> When I open an SQLite database I have >>> handy with emacs, it is rife with nulls and other non-printing >>> characters. It was obvious - to me of course. My bad, i should've trimmed it. -- "On the internet, nobody knows you're a dog." -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cadqa9uzhf_mf-dmdonsdhkqyql2hst3f27a5qrxl44d4x85...@mail.gmail.com
