[GUI Plugin] EpubMerge - Page 37

randy@asa3.org · 08-23-2024, 10:42 PM

Sorry, Calibre7.17 with EM3.1.1 led to a failure also.

JimmXinu · 09-10-2024, 12:05 PM

New Version Released

Version 3.1.0 - 2024-09-10
- Update Translations
- Fix for Calibre plugin CLI, thanks Jeunghun Kim
- Don't require <dc:identifier> to have attribute opf:scheme=uuid when using IDPF font encryption.

JimmXinu · 10-28-2024, 02:40 PM

It's been requested on github that EpubMerge make file names in the merged epub unique to cover for other readers/tools that don't properly implement path names.

I'm not interested in adding that to EpubMerge, but I could call Calibre Convert EPUB -> EPUB after merging.

Convert makes the file names unique, while also completely rewriting the HTML, CSS, etc. UnMerge would not be possible afterwards. Also, by default, Convert leaves the ORIGINAL_EPUB format file, which can cause confusion sometimes.

Any opinions on whether that's a worthwhile option to add to EpubMerge?

Output format appears to be the only Convert setting I can easily control, BTW.

JimmXinu · 01-02-2025, 09:57 PM

New Test Version

2025-01-02
- Add <spine page-progression-direction attr to output iff all input epubs have the same value. #24

JimmXinu · 01-04-2025, 01:45 PM

I've been revisiting the idea of including epub version 3 support natively in EpubMerge.

Currently, EM uses Calibre's Convert to downgrade epub3 to epub2. This works, but Convert is rather intensive with what it changes.

I think I have a handle on how I'd implement epub3 natively in EM. The problem is that I don't really want to deal with epub3 AND epub2 input at the same time, or with epub3 AND epub2 output.

Calibre's Polish Upgrade book internals appears to be much less heavy handed about what it changes when going from epub2 to epub3. The epubs it produces are NOT epub2 back compatible, however. EM output would NOT be epub2 compliant (no NCX TOC). But Convert is still there.

Any opinions on whether reversing EM from epub2 only (albeit with auto-convert) to epub3 only (with auto-polish) is worthwhile?

I will also be looking at epub3 in EpubSplit and FanFicFare (anthology feature, at least).

theducks · 01-04-2025, 01:59 PM

I would rather stay with what I feed it because not all my devices support 3 (well

)
I currently downgrade EPUB3 to EPUB2. But just in case both exist, could it have a Preferred format to use config?

JSWolf · 01-04-2025, 03:22 PM

Personally, I'd like to stay with ePub2 because I use RMSDK (old version) on my Libra 2 because the typesetting is a lot better then the typesetting for KePub.

As for EpubSplit, I'd like the ePub version to not be changed.

Terisa de morgan · 01-05-2025, 05:33 AM

I would prefer to stay at epub2, as not all my devices support epub3 and I find nothing interesting in epub3.

Sirtel · 01-05-2025, 10:55 AM

I would also prefer epub2.

retiredbiker · 01-05-2025, 11:24 AM

I'd also prefer epub2. I have several readers, the newest is about 5 years old, and I have no interest in getting a new reader. I've seen nothing in epub3 that I want anyway.

Martinoptic · 01-05-2025, 01:08 PM

I also would prefer epub2.

DNSB · 01-05-2025, 07:56 PM

Personally I don't really care. I use ePub3 as my preferred format but I also check that books that I have formatted for others work on ePub2 (not to mention Kindle devices).

wjBLqf-_9 · 01-16-2025, 04:08 PM

Thank you for your work on the Calibre plugin "EpubMerge"!

Would you please consider adding the following feature to your plugin?

In the plugin config page, please put a section to programatically configure frequently-performed-follow-up-tasks

For instance...
#1 = Give the end user the ability to configure the plugin how to programatically auto name the new merged epub:
"Series Name" "Lowest Series Index"-"highest series index" "(Anthology)"
eg: "Sword of Truth 01-23 (Anthology)"

#2 = Give the end user the ability to configure the plugin to update the newly merged epub files's series index number to a specified value.

#3 = Give the end user the ability to configure the plugin to regenerate the default cover of the newly merged epub.

JimmXinu · 01-17-2025, 12:43 PM

Quote:

Originally Posted by wjBLqf-_9

Thank you for your work on the Calibre plugin "EpubMerge"!

Would you please consider adding the following feature to your plugin?

In the plugin config page, please put a section to programatically configure frequently-performed-follow-up-tasks

So, the request is to give EpubMerge a post processing feature that the user can configure "programmatically" to do basically anything? From your examples, including, but not limited to:

Setting library metadata on the new such as title and series from in the input data by;
Reading/using the full range of metadata from the input books, and;
Calling other plugins (Generate Cover) or built-in actions (Calibre's generate cover).

At that point you are, IMO, arguably re-inventing Calibre's plugin system. The Action Chains plugin has given it a try and it is hugely complex. I am not interested in adding that level of complexity to EpubMerge.

I might be willing to consider some parts of your specific requests, especially if other users agree they are worthwhile.

Title

Quote:

Originally Posted by wjBLqf-_9

#1 = Give the end user the ability to configure the plugin how to programatically auto name the new merged epub:
"Series Name" "Lowest Series Index"-"highest series index" "(Anthology)"
eg: "Sword of Truth 01-23 (Anthology)"

EM already has code to use the series name for title if all input books share a series.

It should be possible to add code to search the library for the series, compare the number of books found to the number of input books, and to use "Series low-high AnthologyWord" if the number of input books and number of books in series don't match.

That doesn't address cases of skipping numbers, ie, including 1 and 3 but not 2 resulting in a 2 chapter merge titled 1-3.

Series on Merge Book

Quote:

Originally Posted by wjBLqf-_9

#2 = Give the end user the ability to configure the plugin to update the newly merged epub files's series index number to a specified value.

EpubMerge doesn't populate the merged book's Series column. What would it even use? In the case given, merging books in a series, you definitely don't want the same series name.

And EM already opens the "Edit metadata" dialog for you so you can set it as you like.

Cover Generation

Quote:

Originally Posted by wjBLqf-_9

#3 = Give the end user the ability to configure the plugin to regenerate the default cover of the newly merged epub.

Everybody assumes generating a cover is easy.

But then everybody wants to do it a different way and then it isn't easy anymore. I've gone down that path before and I don't plan to again.

I use a shortcut/hotkey to call Generate Cover. I can generate my preferred default cover in two key strokes: 'g' 'Enter'.

DNSB · 01-17-2025, 04:47 PM

For what it's worth, given the complexity that the suggested changes would require and the likely bugs that would be almost inevitable, I would prefer that EpubMerge be maintained as a simple tool instead of trying to add in functionality that calibre and it's plugins already offer.

As for the series name? When I merge books from a series into an omnibus, I use the same series name with the series index set to <first book series index>.<last book series index> so if I merge the first 8 books of a series, the series name would be the same and the series index would be 1.08 while books 9 to 16 would have the series index set to 9.16, etc.

01-04-2025, 01:45 PM	#545
JimmXinu Plugin Developer Posts: 7,136 Karma: 5005503 Join Date: Dec 2011 Location: Midwest USA Device: Kobo Clara Colour running KOReader	Epub version 3.0 Native Support I've been revisiting the idea of including epub version 3 support natively in EpubMerge. Currently, EM uses Calibre's Convert to downgrade epub3 to epub2. This works, but Convert is rather intensive with what it changes. I think I have a handle on how I'd implement epub3 natively in EM. The problem is that I don't really want to deal with epub3 AND epub2 input at the same time, or with epub3 AND epub2 output. Calibre's Polish Upgrade book internals appears to be much less heavy handed about what it changes when going from epub2 to epub3. The epubs it produces are NOT epub2 back compatible, however. EM output would NOT be epub2 compliant (no NCX TOC). But Convert is still there. Any opinions on whether reversing EM from epub2 only (albeit with auto-convert) to epub3 only (with auto-polish) is worthwhile? I will also be looking at epub3 in EpubSplit and FanFicFare (anthology feature, at least).

01-16-2025, 04:08 PM	#553
wjBLqf-_9 Connoisseur Posts: 57 Karma: 12544 Join Date: Jul 2018 Device: None	EpubMerge Plugin: Feature Request Thank you for your work on the Calibre plugin "EpubMerge"! Would you please consider adding the following feature to your plugin? In the plugin config page, please put a section to programatically configure frequently-performed-follow-up-tasks For instance... #1 = Give the end user the ability to configure the plugin how to programatically auto name the new merged epub: "Series Name" "Lowest Series Index"-"highest series index" "(Anthology)" eg: "Sword of Truth 01-23 (Anthology)" #2 = Give the end user the ability to configure the plugin to update the newly merged epub files's series index number to a specified value. #3 = Give the end user the ability to configure the plugin to regenerate the default cover of the newly merged epub.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[GUI Plugin] Open With	kiwidude	Plugins	404	02-21-2025 06:42 AM
[GUI Plugin] Quick Preferences	kiwidude	Plugins	62	03-17-2024 12:47 AM
[GUI Plugin] FanFictionDownLoader	JimmXinu	Plugins	3985	05-09-2015 12:18 AM
eBookCleaner	slobberchopz	Plugins	9	02-23-2012 05:25 AM
[GUI Plugin] Plugin Updater Deprecated	kiwidude	Plugins	159	06-19-2011 01:27 PM

08-23-2024, 10:42 PM	#541
randy@asa3.org Member Posts: 13 Karma: 10 Join Date: Feb 2019 Device: Lenovo desktop Win 10 Chrome browser	Sorry, Calibre7.17 with EM3.1.1 led to a failure also.

09-10-2024, 12:05 PM	#542
JimmXinu Plugin Developer Posts: 7,136 Karma: 5005503 Join Date: Dec 2011 Location: Midwest USA Device: Kobo Clara Colour running KOReader	New Version Released Version 3.1.0 - 2024-09-10 - Update Translations - Fix for Calibre plugin CLI, thanks Jeunghun Kim - Don't require <dc:identifier> to have attribute opf:scheme=uuid when using IDPF font encryption.

10-28-2024, 02:40 PM	#543
JimmXinu Plugin Developer Posts: 7,136 Karma: 5005503 Join Date: Dec 2011 Location: Midwest USA Device: Kobo Clara Colour running KOReader	It's been requested on github that EpubMerge make file names in the merged epub unique to cover for other readers/tools that don't properly implement path names. I'm not interested in adding that to EpubMerge, but I could call Calibre Convert EPUB -> EPUB after merging. Convert makes the file names unique, while also completely rewriting the HTML, CSS, etc. UnMerge would not be possible afterwards. Also, by default, Convert leaves the ORIGINAL_EPUB format file, which can cause confusion sometimes. Any opinions on whether that's a worthwhile option to add to EpubMerge? Output format appears to be the only Convert setting I can easily control, BTW.

01-04-2025, 01:59 PM	#546
theducks Well trained by Cats Posts: 31,267 Karma: 61916422 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	I would rather stay with what I feed it because not all my devices support 3 (well ) I currently downgrade EPUB3 to EPUB2. But just in case both exist, could it have a Preferred format to use config?

01-04-2025, 03:22 PM	#547
JSWolf Resident Curmudgeon Posts: 80,782 Karma: 150249619 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	Personally, I'd like to stay with ePub2 because I use RMSDK (old version) on my Libra 2 because the typesetting is a lot better then the typesetting for KePub. As for EpubSplit, I'd like the ePub version to not be changed.

01-05-2025, 05:33 AM	#548
Terisa de morgan Grand Sorcerer Posts: 6,686 Karma: 12595249 Join Date: Jun 2009 Location: Madrid, Spain Device: Kobo Clara/Aura One/Forma,XiaoMI 5, iPad, Huawei MediaPad, YotaPhone 2	I would prefer to stay at epub2, as not all my devices support epub3 and I find nothing interesting in epub3.

01-05-2025, 10:55 AM	#549
Sirtel Grand Sorcerer Posts: 13,994 Karma: 243829945 Join Date: Jan 2014 Location: Estonia Device: Kobo Sage & Libra 2	I would also prefer epub2.

01-05-2025, 11:24 AM	#550
retiredbiker Evangelist Posts: 454 Karma: 3886916 Join Date: May 2013 Location: Ontario, Canada Device: Kindle KB, Oasis, Pop_Os!, Kobo Forma	I'd also prefer epub2. I have several readers, the newest is about 5 years old, and I have no interest in getting a new reader. I've seen nothing in epub3 that I want anyway.

01-05-2025, 01:08 PM	#551
Martinoptic Bibliophist Posts: 7,536 Karma: 7237230 Join Date: Dec 2021 Location: England Device: none	I also would prefer epub2.

01-05-2025, 07:56 PM	#552
DNSB Bibliophagist Posts: 48,175 Karma: 174315444 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	Personally I don't really care. I use ePub3 as my preferred format but I also check that books that I have formatted for others work on ePub2 (not to mention Kindle devices).

Advert

Advert

01-17-2025, 04:47 PM	#555
DNSB Bibliophagist Posts: 48,175 Karma: 174315444 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	For what it's worth, given the complexity that the suggested changes would require and the likely bugs that would be almost inevitable, I would prefer that EpubMerge be maintained as a simple tool instead of trying to add in functionality that calibre and it's plugins already offer. As for the series name? When I merge books from a series into an omnibus, I use the same series name with the series index set to <first book series index>.<last book series index> so if I merge the first 8 books of a series, the series name would be the same and the series index would be 1.08 while books 9 to 16 would have the series index set to 9.16, etc.