search

noDRM / DeDRM_tools

DeDRM tools for ebooks
7.31k stars 323 forks source link

Watermark #59

Open SirGryphin opened 2 years ago

SirGryphin commented 2 years ago

Question / bug report

I noticed that that watermark hex is still hidden in epubs I thought this was removed with your fork? I enabled remove watermark but in epub file on content.opf there is still hidden watermark.

Which version of Calibre are you running?

4.23

Which version of the DeDRM plugin are you running?

10.0.2

If applicable, which version of the Kindle software are you running?

No response

Log output

No Log
ElleKayEm commented 2 years ago

This option isn't on by default. Do you have "remove watermarks" checked in DeDRM's customization?

eta: nevermind. I see you edited your post.

SirGryphin commented 2 years ago

@ElleKayEm Just updated above messages, yes I've enabled it and it still shows in content.opf in epub.

SirGryphin commented 2 years ago

Update: I've got it working now, I've update calibre to latest version and it not working fine. So I will close this issue.

KarellenX commented 2 years ago

Could you tell me where that hex is found in the content.opf?

SirGryphin commented 2 years ago

@KarellenX If you download book from amazon to desktop (using USB PC option) open in calibre and use Kindle Unpack to get epub. Then open it in Calibre Editor, if you go into content.opf in epub you will see a bunch of greyed out hidden meta. The latest calibre DeDRM gets rid of it by enabling remove watermark or you can open epub in sigil and re-save and it does the same.

KarellenX commented 2 years ago

By the sounds of it, the codes are visible but greyed out (so there are no special steps required to reveal them), and if I am not seeing them, it means they have been removed.

Thanks @SirGryphin I'll give that a try.

noDRM commented 2 years ago

Hm, maybe the watermark removal is indeed broken on Calibre 4 - I don't remember if I tested that. I'm going to try this with an Amazon book and see if I can reproduce and fix the bug when using Calibre 4. Thanks for the report. I'm going to re-open this report for now as this could be an actual bug in the plugin that I'd like to fix (even though you got it to work by just updating).

SirGryphin commented 2 years ago

@noDRM No problem, to be honest the only reason I stuck with Calibre 4 is because version 5 uses python3 and DeDRM and other plugins didn't work to begin with, now everything update it just easier keep everything up to date.

Also thanks for keeping DeDRM alive I'm glad someone is updating it.