BookFab

[xyzzy_foo]

BookFab is an audiobook creation and DRM removal application developed and sold by China's DVDFab.

After the audiobook creation feature was initially released, the application focused on Amazon Kindle.
However, due to the expansion of supported platforms, it is no longer appropriate to handle topics for it in the Amazon Kindle Sub-Forum. Therefore, I have decided to create a new thread here for BookFab.

Currently, BookFab includes the following products:

• BookFab Kindle Converter
• BookFab Kobo Converter
• BookFab Audible Converter
• BookFab AudiobookJP Converter
• BookFab AudioBook Creator
• BookFab AudioBook Cloud Enhancer
• BookFab Calibre Plugin (Free)

Additionally, it has already been announced that BookFab will support Japan's DMM Books and BOOK☆WALKER in the future.

[JSWolf]

Does BookFab support LCP DRM (all versions)?

Has it been fixed to remove the DRM from Kindle eBooks using the latest K4PC and K4MAC?

[xyzzy_foo]

Originally Posted by JSWolf

Does BookFab support LCP DRM (all versions)?

As of now, BookFab does not support Readium LCP DRM. Readium LCP 1.0 DRM was previously supported by DeDRM, but this support was dropped following a DMCA takedown.
Epubor claims it can independently remove Readium LCP 2.5 DRM. It's possible to extract the files and reconstruct the EPUB by debugging Thorium Reader with DevTools, and I believe the recently DMCA-takedown-targeted open-source solution could also do this.

Since they are trying to counter DRM removal attempts through legal means rather than technical ones, there is a potential incentive for BookFab to support it. Furthermore, it's possible that Rakuten Kobo might abandon KDRM + Adobe ADEPT DRM in favor of Readium LCP DRM. If that happens, BookFab will have no choice but to support it. And for a certain reason, I'm hoping that comes to pass.

Originally Posted by JSWolf

Has it been fixed to remove the DRM from Kindle eBooks using the latest K4PC and K4MAC?

Since BookFab is a Windows-only app, I don't think it supports K4MAC, naturally...
It's Epubor that claims to support K4MAC via their Epubor Ultimate macOS version. Both are currently based on the solution developed by Satsuoni, and while the old BookFab had its own solution, which caused some problems, it should be more reliable now.

[JSWolf]

Kobo would not drop RMSDK. If they did, they would not be able to support OverDrive or ePub from their store. Sure they could change the ePub from Adept to LCP, but that would cause more trouble then it's worth. Kobo would not tank their business. Maybe Kobo could add LCP, but I cannot see Kobo taking away Adept DRM.

[xyzzy_foo]

Originally Posted by JSWolf

Kobo would not drop RMSDK. If they did, they would not be able to support OverDrive or ePub from their store. Sure they could change the ePub from Adept to LCP, but that would cause more trouble then it's worth. Kobo would not tank their business. Maybe Kobo could add LCP, but I cannot see Kobo taking away Adept DRM.

Since I'm Japanese, I've never tried the RMSDK renderer. I convert everything to KEPUB and use the EPUB3 renderer. EPUB3 is essential for Japanese eBooks.
There's no question that Rakuten Group's development team is deeply involved with Kobo eReader's EPUB3 renderer. It supports Japanese extremely well and perfectly handles Shueisha's manga EPUBs, which have a unique structure that can't even be opened by calibre's viewer.

By the way, the reason I dislike Adobe ADEPT DRM is that even though it's easy to remove, the resulting EPUB file is always altered from the original. I wish eBook stores in the West would commonly adopt Readium LCP DRM instead of Adobe ADEPT DRM.

Incidentally, Japan primarily uses its own DRM or commercially developed DRM solutions (the exception is Reader Store, which uses Marlin DRM. Also, BookLive! uses ExpressPlay DRM, an implementation of Marlin DRM, but only for fixed-layout books.).

However, the Japanese government is considering requiring businesses to adopt Readium LCP DRM from an accessibility standpoint.

[xyzzy_foo]

Originally Posted by xyzzy_foo

There's no question that Rakuten Group's development team is deeply involved with Kobo eReader's EPUB3 renderer. It supports Japanese extremely well and perfectly handles Shueisha's manga EPUBs, which have a unique structure that can't even be opened by calibre's viewer.

Originally Posted by DNSB

Misleading? Kobo's renderer (originally the ACCESS NetFront BookReader v1.0 EPUB Edition renderer which ended up being donated to the Readium project and moving on to their current Readium/webkit based version) has excellent ePub3 support for both reflowable and fixed layout ePub3s.

Yes, the RMSDK renderer has very poor ePub3 support since Kobo has not updated that renderer in quite a while. For the most part, the RMSDK renderer is being used to allow support for Adobe ADEPT DRM protected ePubs. OTOH, virtually all the ePub3 ebooks using more advanced features display without issue on the Kobo webkit-based renderer.

Originally Posted by DNSB

Basically, RMSDK was not capable of handling this and so Kobo licensed the ACCESS NetFront BookReader v1.0 EPUB Edition for use on their devices/apps. Later ACCESS code was done with the Readium project SDK which resulted in the PUBPLUS™ Reader v2.0 EPUB.

Later versions of the Kobo renderer were based on the Readium/webkit and Readium 2 SDKs.

DNSB knew the detailed technical background. It seems they were using ACCESS's technology.

[Aleron Ives]

Originally Posted by xyzzy_foo

the reason I dislike Adobe ADEPT DRM is that even though it's easy to remove, the resulting EPUB file is always altered from the original.

How is the resulting file altered?

[ownedbycats]

Originally Posted by xyzzy_foo

By the way, the reason I dislike Adobe ADEPT DRM is that even though it's easy to remove, the resulting EPUB file is always altered from the original. I wish eBook stores in the West would commonly adopt Readium LCP DRM instead of Adobe ADEPT DRM.

Oh no. ADEPT is breakable, while Readium aggressively DMCAs anyone who tried to break theirs. I don't want books I can't strip DRM from.

[Sirtel]

Originally Posted by ownedbycats

Oh no. ADEPT is breakable, while Readium aggressively DMCAs anyone who tried to break theirs. I don't want books I can't strip DRM from.

Yes, this. I would never buy an ebook I can't remove the DRM from.

As to altered files, can't say I care. I modify all my ebooks myself rather aggressively, by editing the formatting, deleting ads and excerpts, embedding customized metadata and so on.

[JSWolf]

Originally Posted by xyzzy_foo

Since I'm Japanese, I've never tried the RMSDK renderer. I convert everything to KEPUB and use the EPUB3 renderer. EPUB3 is essential for Japanese eBooks.
There's no question that Rakuten Group's development team is deeply involved with Kobo eReader's EPUB3 renderer. It supports Japanese extremely well and perfectly handles Shueisha's manga EPUBs, which have a unique structure that can't even be opened by calibre's viewer.

By the way, the reason I dislike Adobe ADEPT DRM is that even though it's easy to remove, the resulting EPUB file is always altered from the original. I wish eBook stores in the West would commonly adopt Readium LCP DRM instead of Adobe ADEPT DRM.

Incidentally, Japan primarily uses its own DRM or commercially developed DRM solutions (the exception is Reader Store, which uses Marlin DRM. Also, BookLive! uses ExpressPlay DRM, an implementation of Marlin DRM, but only for fixed-layout books.).

However, the Japanese government is considering requiring businesses to adopt Readium LCP DRM from an accessibility standpoint.

The Japanese Government is WRONG! DRM does not make an eBook accessible An eBook is more accessible without DRM. For example, without DRM, the ePub can be edited as the Reader wants. With DRM, you can't. Without D|RM, you can use the eBook in more places. With DRM, you are stuck with just apps that support that DRM.

[Sirtel]

Originally Posted by JSWolf

The Japanese Government is WRONG! DRM does not make an eBook accessible An eBook is more accessible without DRM. For example, without DRM, the ePub can be edited as the Reader wants. With DRM, you can't. Without D|RM, you can use the eBook in more places. With DRM, you are stuck with just apps that support that DRM.

The point is, they're already using DRM - just that every store is using a different DRM scheme. The government wants them to use the same DRM everywhere, which is certainly better than 10 different DRM schemes.

[JSWolf]

Originally Posted by Sirtel

The point is, they're already using DRM - just that every store is using a different DRM scheme. The government wants them to use the same DRM everywhere, which is certainly better than 10 different DRM schemes.

The government is using a BS excuse. They should just say no to DRM and problem solved.

[Sirtel]

Originally Posted by JSWolf

The government is using a BS excuse. They should just say no to DRM and problem solved.

I'm not sure they can do that, as the publishers would rise up in arms (so to speak). It may not even be legal to force publishers to sell their goods without any protection.

[JSWolf]

Originally Posted by Sirtel

I'm not sure they can do that, as the publishers would rise up in arms (so to speak). It may not even be legal to force publishers to sell their goods without any protection.

Why would it not be legal for the Government to say no DRM on eBooks?

[Sirtel]

Originally Posted by JSWolf

Why would it not be legal for the Government to say no DRM on eBooks?

No idea, but why has no government done it, then?