Post by Joe BernsteinPost by Jibini Kula Tumbili KujisalimishaOn Friday, July 27, 2018 at 5:13:54 AM UTC+1, Ted Nolan
In article
Post by m***@sky.comI have an old Kindle which will handle .txt files, and which
appears as a USB drive when plugged in to a computer. Stuff
that I download from Project Gutenberg or buy from Baen I
turn into .txt and copy to the documents folder of the
Kindle. Sometimes that garbles a few non-ascii characters,
but I usually don't care about that (It did become slightly
irritating with "Mission to Methone" where the e is
non-ascii due to an accent).
In Heaven's name, why are you doing that?!? Use the .mobi
downloads from Gutenberg and Baen!
I feel that if I store .txt, or something I can generate txt
from with commonly available software (such as .rtf) then I
can expect everything to work reasonably well, and I'm not at
the mercy of specialised software that might not be supported
in future, or on a different platform. Also, I don't notice
much of a difference in readability between stuff I buy or
download via .txt and stuff I buy from amazon as .azw.
I feel like I should point out that .epubs are HTML in a .zip
file, and HTML is text with tags that are easily stripped out
if need be (and .zips can be opened directly as a file folder
in most OS's).
I run into problems with zipped files intermittently in my
current situation (i.e., without a computer I control other than
my phone).
That's really not a problem with zip files, though, so much as
"computers I can't control" problem.
Post by Joe BernsteinAnd this may not be relevant to .epubs, but is relevant to some
things I've encountered lately: there are pseudo-zips too.
These, I routinely have trouble with. (gzip, most obviously.
The most important single reason to run Linux if you can is not
something useful Linux does, it's dealing with the Linux uber
alles assholes who use gzip.)
There is a free program for Windows called 7zip that can handle
damn near anything used for compressing files. It laughs at gzip
(while unzipping it handily). There's even a command line version,
if you need to automate it.
Post by Joe BernsteinWhich is sorta the point. Text editing is wondrously portable;
many other things, less so. Competent text editing needn't
degrade HTML nor for that matter accents, unless your system is
from the 1980s.
As I said. .epub is HTML, which is text. The markup contains
information, and losting is a loss. But it's still ASCII text. And
if it falls entirely out of use, the documentation for it will
still be available. You could write your own renderer if you had
to. Or strip out the markup.
Post by Joe BernsteinI gather the standard for e-mail is now IMAP.
If you say so. But IMAP isn't a file format, it's a transmission
protocol. And Gmail still has POP3 access available, though I
believe you have to turn it on. (I think you have to turn on IMAP,
too, now that I think about it.)
Post by Joe BernsteinSooner or later,
I'll have to use that to download all my Gmail e-mail - and then
find a way to convert it to mbox so I can actually read it, and
process it into permanent storage, using a text editor, more
efficiently than with ever-changing e-mail programs.
Gmail's archive system actually exports to mbox (in a zip file - it
archives *everything*, email, drive, Calandar, Chrome favorites,
Address book, *everything* into 2 GB chunks, but somewhere in there
will an .mbox file) by default, but tgz is also available).
Go to https://takeout.google.com/settings/takeout and play around.
The really, really fucked up thing is that mbox is the *only* way
to archive Gmail offline (even on commercial account), but Gmail
can't *import* an mbox file. If I have to dig through an archived
email file for a termed employee, I have to load it into
Thunderbird. Sigh.
--
Terry Austin
Vacation photos from Iceland:
https://plus.google.com/u/0/collection/QaXQkB
"Terry Austin: like the polio vaccine, only with more asshole."
-- David Bilek
Jesus forgives sinners, not criminals.