[Plugin] epubveri - Simple epubveri wrapper

[BeckyEbook]

@KevinH: I'll answer for myself. It's simply about getting faster feedback. After all, an extra "reminder" here wouldn't hurt.
Of course, I could add the task of checking for a file size limit to another validation plugin or just take a look at the Reports, but since using epubveri is becoming part of my daily routine, I can skip one step during EPUB analysis.

[KevinH]

Do you ever split files on that filesize? I have not done that for years.

[BeckyEbook]

The last time was last month. It was just a logical division; I wanted each chapter in a separate file.

[KevinH]

That I understand. I just haven't run into an e-reader that still exhibits these problems in years. But better safe than sorry.

[DNSB]

Just for the heck of it, I generated a ePub3 omnibus with all the book text all stuffed into a single file. The text file uncompressed is 1,355,406 bytes. The ereaders and apps I tested it on had no issue other than my KLC sitting on loading for too long but it does that on the first open with most files since the update to v6.0.274403 firmware.

[KevinH]

That is valuable data. E-readers have evolved over time to fix that 260K limitation.

[Kayadelenium]

New devices are significantly better thanks to more powerful hardware, but what about the older ones? We need to examine which devices are affected by the issue. Furthermore, what is their market share? We should consider this before making a decision.
Personally, I would prefer to dedicate my energy to a project that benefits a larger number of people.

[DNSB]

For me, since I prefer to split on chapter boundaries, I don't think I have any ePub files that have overly large files. Since calibre's Quality Check plugin already has a function that checks for oversize HTML files, I'm not sure if spending your time to create a similar function in epubveri is actually needed.

The attached images is from a temporary library I use for importing Humble Bundle and other blocks of ebooks before moving them to my Intake library for finishing. In this case, 41 books by Brian Aldiss, two of which had oversized files.

[Kayadelenium]

Thank you all for answering, and DNSB for testing it. I am not adding ADV-013, now.

KevinH and DNSB settled it with data: a 1.3 MB single-file book opens without trouble on today's readers, and the readers that had trouble with larger files are very old. The size question also has good homes already: in Sigil, Tools / Reports lists every HTML file's size and sorts by it; in calibre, Check Book and the Quality Check plugin report large files. A limit that belongs to a reading system rather than to the EPUB format is not a validator's job. That is where I started in the epubveri thread (#350), and it is where I am staying.

@BeckyEbook, I understand the "one step fewer" argument. For now, Reports is that step. Nothing changes in the plugin.

[JSWolf]

Originally Posted by Kayadelenium

Thank you all for answering, and DNSB for testing it. I am not adding ADV-013, now.

KevinH and DNSB settled it with data: a 1.3 MB single-file book opens without trouble on today's readers, and the readers that had trouble with larger files are very old. The size question also has good homes already: in Sigil, Tools / Reports lists every HTML file's size and sorts by it; in calibre, Check Book and the Quality Check plugin report large files. A limit that belongs to a reading system rather than to the EPUB format is not a validator's job. That is where I started in the epubveri thread (#350), and it is where I am staying.

@BeckyEbook, I understand the "one step fewer" argument. For now, Reports is that step. Nothing changes in the plugin.

I did find an instance recently where a large HTML file caused a page break where it should not be in RMSDK on my Kobo. So an overly large HTML file can cause a problem.

[KevinH]

It inserted a pagebreak. It did not fail to present the epub, right?

[JSWolf]

Originally Posted by KevinH

It inserted a pagebreak. It did not fail to present the epub, right?

Yes, it inserted a pagebreak. The person who was reading the ePub was trying to find out the cause of the pagebreak. Turns out the problem wasn't obvious because it was down to the size of the HTML file.

I have seen a number of Kindle eBooks (self-published) where they were some HTML where together and some where it was just one HTML instead of separated by chapter. The most recent ePub from a big publisher was a Discworld ePub where the HTML were not properly split.

[Turtle91]

I'm definitely on the team of: "It's an ePub validator, not a fix all coder's mistakes."

I'm pretty sure the Discworld books didn't have any chapters, right?? So the coder would need to manually split wherever they felt like it.

[JSWolf]

Originally Posted by Turtle91

I'm definitely on the team of: "It's an ePub validator, not a fix all coder's mistakes."

I'm pretty sure the Discworld books didn't have any chapters, right?? So the coder would need to manually split wherever they felt like it.

Discworld books have no chapters. The best place to split for Discworld is at a section break and there are a lot of those.

[Kayadelenium]

@JSWolf, I have answered the splitting question in the epubveri thread, since it is about what epubveri does rather than about this plugin: here.