Quote:
Originally Posted by Turtle91
....although that brings up the question of WHY you want an image to be on it's own page??
InsertImageSVG |
The reason is because that's pretty standard for images that are intended to take up a whole page, not all images are, that's why I specified images that have the word "insert" in them since in the ones I'm dealing with all full-page images are named
insert1.jpg or
insert_1.jpg while ones that are part of the page, like an image under a title, are generally named something different.
I have found that many, if not most, official books have this format with a new xhtml for the image & another after the image. I'm not opposed to a different approach, but that seems to be a common industry standard for professionally done ePubs, so I have no intention of reinventing the wheel, there's probably a reason they do it that way, that way looks nice from my experience, & looks nice across different devices, so unless there's a different way that is clearly better for some reason I'll stick to the tried & true method personally.
As far as the SVG goes... I'm not exactly sure what that's supposed to do. All I know for SVG is the Vector Graphics format & the images I have are not vector graphics. From the code you shared it looks like the image is being scaled to a specific resolution, which seems unnecessary & gives the same problem I'm trying to solve with compatibility.
The issues that cause a desire for the images to be on separate pages?
Sometimes the image is just under the resolution of the screen being used, for example if the epub was made from images sized to the old PW1 & are displayed on a PW3 you end up with 1-3 lines of text above or below the image. this is annoying & completely avoided when using a separate page for the image. I have run into the issue a few times where images were made smaller than my PW3 screen & they don't fill the page, but instead leave a blank area around it, that's not ideal, but better, IMO at least, to having the image with a single or 2 lines of text. Even when it had 4 lines I'd rather the text just start on the next page.
If I were to use your SVG code then the image would be scaled to
width="400" height="600" or
height="99vh" width="99vw" which doesn't sound like it is going to be good unless it is made for only a single device & not intended to be used on another device. As someone who has 2 PW3s, 2 PW1s, my Dad's old Kindle that is lower resolution, & people who use tablets & iOS & Android phones in my house building to a single dimension for one device leaves problems for other devices.
With that in mind,
would you be able to give a brief explanation on why the SVG thing is what you think is better? I'm new to Sigil so I'm very much still learning. I just don't understand what it benefits from adding all that extra code when it doesn't seem to be better than what most pro-books do. Is there something I'm missing?
I'm also still trying to figure out what SVG means in your context, Scalable Vector Graphics are nice, but they have major limitations, you can't really have vector graphics with a lot of detail, & they take a lot more processing power to display than JPG or PNG images, with the more detail an image has requiring more processing power, & with illustrations that is gonna be a lot, even more than WEBP possibly. So if you are converting images to SVG that sounds problematic & definitely won't be supported across many devices. Is it something else?