![]() ![]() ![]() Sometime, it can be a permission weirdness. And some OS sandboxed/isolated the app from ever touching outside of it own home directory unless explicitly permitted to do so. And sometime when the file are being used and when calibre try to modify/something to the file, it can lead to unpredictable situation such as data corruption. Filesystem and OS have their particular way of how it manage the files. It boils down to database and robustness. Before I was dead-set against his idea, and now I understand why it is the best for calibre. I happened to read Kovid justification of this kitchen-sink approach few days ago and I agreed with Kovid. There's alot to be said for UNIX philosophy and fighting bloat, but sometimes having everything you could conceivably need for a given purpose in one well-maintained program is comforting. Again, maybe it's not ideal (I've never tried producing an e-book start-to-finish through it), but for some quick edits, it just works. And for that, the e-book editor tool is more than capable. Then there's that rare occasion in which I might actually need to edit an ebook, because the ToC is broken or I spotted an annoying typo that I feel compelled to fix. It's not great, and I wouldn't use it over some dedicated programs to read an entire book, but it gets the job done. When I want to test whether the conversion was successful, the built-in ebook viewer is there. I spend most of my time in Calibre just managing my library or converting ebooks between formats (particularly if I'm pulling ebooks off my Kindle or Kobo to strip their DRM). It's a one-stop shop for pretty much everything related to e-book management, conversion, or creation. ![]() ![]() Calibre is one of those rare examples of software where the kitchen-sink approach is absolutely warranted. ![]()
0 Comments
Leave a Reply. |