View Single Post
Old 08-31-2014, 10:10 AM   #114
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,561
Karma: 150249619
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by oj829 View Post
You can open Calibre 2.0 on XP, run it without crashes, but then be surprised down the line by a specific circumstance or book.

e.g., I have XP/SP3, a CPU which supports SSE2, and Calibre2 with the updated version (6.0.9) of the tools.

I thought I was buzzing along, doing everything I could do before, but eventually I opened a specific epub to read in the calibre reader (9MB, published by "Author & Company", OverDrive-->ADE2.0-->Tools609-->Calibre Library), which crashes qtcore5.dll when the reader attempts to load the book's "flow".

I could even do epub-->epub conversion in Calibre, and reload the Calibre-created, license-stripped epub back into ADE 2.0 and read it, but attempts to read or edit the title in Calibre? Out of the question.

Not a lecture, just a story.

Also, soon there will be developments in epub format, device drivers, etc. You have to weigh how important those things are in your book workflow when considering what to do in the future.
Very well said. Another thing I can see happening is new plugins/drivers not supporting Qt4.
JSWolf is offline