[Tex2002ans]

Originally Posted by LostOnTheLine

I've well aware of the advantages to them, but there are also a lot of limitations, [...] I love vector graphics, don't get me wrong, I just don't think they belong in an eBook reader.

Do you use Sigil's inserted covers?

• Tools > Add Cover

Then you're already using SVG Wrappers. It's the same exact code.

Is the EPUB reader exploding?

Originally Posted by LostOnTheLine

they make sense for things like logos & yes charts & graphs for sure, but using them in an eBook that is intended to be read on a variety of devices that may or may not support them, has low processing power & is generally designed with lower end hardware, & you generally want to conserve processing power to preserve battery life, outweighs it's benefits for this use case IMO.

There are plenty of other reasons for limited uses of SVG (Wrappers), but those aren't any of them.

You do know that fonts are essentially just vectors—math curves that the device will scale to fit the screen...

- - -

And, as a complete sidenote, one of the bugs/quirks of SVG (Wrappers)+Amazon-conversion is giving you exactly what you were wanting... page-breaks before and after all your images! LOL.

Originally Posted by LostOnTheLine

Just like I thing WEBP images are nice, you can get better compression with less quality loss, but there's a big difference in what the device reading it has to do to see it & that makes putting them in an eBook not ideal either.

WEBP as an image format is... meh... (It smooths out too many of the details).

And you definitely want to avoid using them in EPUBs for now (because most readers can't support that format yet/ever).

For more discussion, see:

• 2019: "What about webp images?"

Originally Posted by LostOnTheLine

Now if it's just a wrapper designed to work with vector images that's fine, I just don't see why it's necessary, not that I don't see a use for the technology.

SVG wrappers are perfect for exactly the use-case you want. An image filling up the screen.

Originally Posted by LostOnTheLine

An example of a part of a Professional ePub that has the images do exactly what you are talking about with no need for having the dimensions of the image [...]

[...]

That's pretty typical of the ones that I've altered before I do anything to it.

Raw HTML + CSS scaling, like in your example, will fail for the reasons given in my SVG Wrappers thread.

The second you:

• rotate your device
• have an odd dimension (skinny/tall, short/fat image)

the "cutoff" image or "oompa loompa" effect more easily happens.

While you can try to MITIGATE this, by shoving each image into its own HTML file... that just isn't possible when you're dealing with inline images.

For example, what if you have text that's:

<p>As can be seen in Figure 1:</p>

<div class="image">
	<img [...]>
	<p class="caption">Figure 1: A thing</p>
</div>

<p>the issue can be seen. Also, see Figure 2:</p>

You can't just split the file into dozens of:

• Chapter01.p1.xhtml
• Chapter01.Figure1.xhtml
• Chapter01.p2.xhtml
• Chapter01.Figure2.xhtml
• Chapter01.p3.xhtml
• [...]

Yes, in some books, the single-file-per-image-method might work—like photographs between (or at the end of) each chapter—but in all the ebooks I've worked on, only a handful would even fall into that category.

(I've professionally converted 650+ books, mostly Non-Fiction.)

Originally Posted by LostOnTheLine

[...] probably why the Professional publishers use that format...

Most publishers release garbage code in their ebooks.

Originally Posted by LostOnTheLine

[...] but I'm now confident that it's not something I'm interested in. I'm more concerned with trying to find a way to improve the automation of splitting the images & find a way to automate renaming of pages if possible

Everyone here has given you multiple solutions:

• <hr class="sigil_split_marker" />
  
  • Inserted using Find & Replace, Regex, or Filter Replacements.
• + Edit > Split at Markers (F6)

is the best way.

But you trying to split the files before/after every image is a poor idea.

Better to use good, clean HTML+CSS and rely on page-break-before + page-break-after. See my posts in:

• 2022: "Widows & Orphans won't disappear"
• 2022: "Remove blank pages"