Issue: Rendering embedded images results in incorrect size and placement

[archer-gh]

Description: When reading epubs with small embedded images for stylized section header/breaks, the icons that are meant to be small and tiny (no bigger than text size) render huge and takes up the height and width of the page which makes for 1.) a jarring experience when flipping pages, and 2.) repositions text in incorrect ways. When using other e-reader software, the icons render correctly at the proper size and placement (see attached screenshots).

Steps to Reproduce: Might be book specific, but this affects the copy of "Wind/Pinball" by Haruki Marakami.

Expected Results: Small embedded images are rendered at the proper size and positioning to improve the visual representation of the books as well as improve the flow when reading and swiping between pages.

Additional Context and Screenshots:

Image 1: The table of contents from the book as rendered in a competitor application. The book contains small images of a rightward pointing triangle as a break indicator. Everything appears to render correctly here.

Image 2: The same table of contents from the same book as rendered in Aquile. The small image renders huge and pushes the text associated with the image into the image itself.

Image 3: A section break page rendered in the competitor application. This time the image is wider, and is a complete arrow shape.

Image 4: The same section break page rendered in Aquile. The same issue seems to occur where text is pushed into the image.

Image 5: This, and the following screenshot, perhaps shows the problem the best. This is how the book is rendered on the competitor app with the small right-facing arrows rendered correctly as part of the chapter headings (right above the bolded "2" and "3" chapter breaks). The flow of text is uninterrupted and the small icons are barely noticeable.

Image 6: This same page rendered in Aquile. The triangle icon is huge and takes up the entire height and width of the page. If this was on single column mode, the triangle shows as its own page, which is hugely jarring when reading with my device in Portrait orientation and a page turn results in seeing a huge triangle image across the entire screen, and nothing else. You can barely make out the "2" embedded inside the image after the text got pushed into it.

Image 7: Finally, to cap off to content as rendered in Aquile versus the competitor application, you can barely make out the "3" embedded inside the image here.

Image 8: What the rendering looks like in Portrait orientation.

[OptimiliaStudios]

Thanks for reporting the issue. Are you using the enhanced rendering mode? If not can you try that mode and see if the issue reproes there also? Also, can you share the epub file with us at optimilia.studios@gmail.com, we will try to reproduce the issue locally and attempt a fix.

[archer-gh]

Thanks for looking into this issue.

Enabling Enhanced Rendering does not resolve the rendering issue.

File has been sent as requested.

[archer-gh]

Hi OptimiliaStudios,

I'm wondering if there has been any progress made on this issue. I've previously sent the ePub file across and can resend it again if required.

Thanks.

Sent from Outlookhttp://aka.ms/weboutlook

---

From: OptimiliaStudios @.> Sent: Tuesday, May 3, 2022 5:30 AM To: OptimiliaStudios/AquileReader @.> Cc: archer-gh @.>; Author @.> Subject: Re: [OptimiliaStudios/AquileReader] Issue: Rendering embedded images results in incorrect size and placement (Issue #87)

Thanks for reporting the issue. Are you using the enhanced rendering mode? If not can you try that mode and see if the issue reproes there also? Also, can you share the epub file with us at @.**@.>, we will try to reproduce the issue locally and attempt a fix.

— Reply to this email directly, view it on GitHubhttps://github.com/OptimiliaStudios/AquileReader/issues/87#issuecomment-1116044288, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFLCGODNDAC3I2E3JJMPCNTVIEL5FANCNFSM5TUA2IBA. You are receiving this because you authored the thread.Message ID: @.***>