here's an .epub version of "pride and prejudice".
greg, please enter that in your not-a-tournament. *** since i went on record yesterday as knowing that very few of you are even _looking_ at these files, i feel no need to go through a long exposition of "here's the .html file, and here's the .opf, and...", blah blah blah blah blah blah blah. if you _want_ to look at those files, i assume you already know that an .epub file is a .zip with another extension, meaning you can just unzip it to get all the pieces. so have at it. or not. it makes no difference to me. i'm _showing_ this to you, because i know that you have a major need for this information, but if you want to keep your head stuck "in the sand", fine... but let's be clear: i'm not _building_ this for you. there is a big world out there that _will_ be glad to _use_ the one-source-file workflow i've developed. _glad_, i tell you. heck, perhaps even _overjoyed_. *** oh, and yeah, i'm not going to look at this .epub in a half-dozen viewer-programs, like with the .mobi. i expected those to work the same, more-or-less, since amazon has built a dependable consistency... .epub viewers, on the other hand, are a rat's nest, where i _know_ there will be major inconsistencies. so many, in fact, that i have no interest or intent to address 'em, in any way, shape, or form, thank you. we might be able to ignore these inconsistencies _if_ there was even one program which supported the entire standard, without any exceptions at all. but alas, there isn't even _one_ such app. not one. *** too many _idiots_ bought in to .epub, whole-hog, because it was the "open standard" they wished for. fine, you got your way, idiots, so now we have the "open standard" you always promised us, meaning we have the consistent rendering you promised us. except, no, no we don't. in fact, the _consistency_ resides in the _proprietary_ system from amazon... explain _that_, you idiots. and what have we gotten from "the open standard"? well, there's that inconsistent rendering across apps, of course. but we've also got multiple d.r.m. systems. adobe is wrapping their .epubs in their d.r.m. system. and apple wraps their .epubs in another d.r.m. system. and barnes&noble has their own system, for the nook. and kobo... no one can figure out what kobo is doing, including kobo itself. so the whole notion that you could buy your .epubs at any store you wanted, and read them on any machine? that didn't happen. and if you really thought it would, you're an idiot. because the companies who run stores want you to use their .epubs on their machines... d'oh. because, you know, it's good for their business model. and the companies who sell machines want you to buy your .epubs in their stores, because, surprise surprise, that happens to be good for their business model too. and if you really thought that these _businesses_ would sacrifice their _profits_, so you could buy cheap .epubs one place, and cheap viewer-machines in another place, well, you know, your idealism is nice, but you are naive. a.k.a. stupid. a.k.a. an idiot. a.k.a. a blooming idiot... so we're stuck with d.r.m. in multiple forms. just great. *** and apple, of course, after "embracing" .epub, recently "extended" it, with release of their ibook author tool... most of us know the third "e" in this e-book "strategy". so, is the i.d.p.f. -- the official "parent" of .epub -- concerned about all of this fragmentation? hell no. i.d.p.f. is the tool of corporate publishing dinosaurs, who _want_ e-books to be as complicated as possible, so they can maintain their p-book business for a while. because, you know, they have boat-payments to make... this is what happens when we let capitalists run the show. -bowerbird p.s. this .epub was built from a single 800k .html file, which means that it will choke primitive epub-viewers, like adobe's. maybe i will change that; maybe i won't. we probably should cut the not-ready-for-prime-time, rather than continue catering to adobe's incompetence.