ooh... this new DeDRM_WinApp is handy. I don't need to copy/paste my pid/serial anymore as it saves my preferences, and it handles more ebook drm than just Amazon's.
It does, however, rename the file to .mobi
but I can rename that easily.
I don't like it when Calibre does it because I have to remove/add the ebook in Calibre after I change the file extension anyway and it bothers me to have to add it twice.
[edit] I do wish that there was a standalone version of this, so that I could use it in the case that I was on the go and away from a machine with python on it. [/edit]
Quote:
Originally Posted by sadievan
Can't you set calibre to convert to .azw?
|
Nope. You can convert
from .azw but not
to it in Calibre. Technically, .azw and .mobi are the same thing anyway, so Calibre doesn't bother to include both file extensions as an output option, only .mobi. In a way, this is a bonus for me as having .azw files in Calibre ensures that I have a source copy of my Amazon-bought ebooks which will never be overwritten by Calibre.
Quote:
Originally Posted by FF2
I thought Calibre did not alter the original file in any way. I thought it reads the original and then processes that information and creates a new file in whatever format you have selected. I would imagine you could change the file's extension (maybe outside of the calibre process/library)
|
My experience has been that if an .azw has drm on it, Calibre's k4mobidedrm plugin breaks the file and has Calibre add it to the library as .mobi. It's not
altering the file in changing the extentsion because .azw and .mobi are basically the same thing. However, I
want azw files in Calibre to use as my primary input files.
Yes, I can open the liberated file's location, change the extension, delete the original entry in Calibre and re-add the ebook to Calibre again, but it means fewer steps if I just use drm removal tools outside of Calibre instead.