View Single Post
Old 03-15-2026, 07:25 AM   #39
ElMiko
Fanatic
ElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileRead
 
ElMiko's Avatar
 
Posts: 541
Karma: 65460
Join Date: Jun 2011
Device: Kindle Voyage, Boox Go 7
Quote:
Originally Posted by JSWolf View Post
@Horus01 is incorrect. The CSS code he posted does work in ADE/RMSDK. So if you do want to use it, there's no reason not to.
Horus01 is correct. You are mistaken.

The code does not work in ADE 2.X. In fact, it gets REALLY funky. The "auto-centering" fails, but it also then duplicates all the text and displays each line as a separate cell in a row. And the top and bottom margins fail. (Also, with my modified "inline-block" attribution, this doesn't get aligned right, either). See imageADE-H attached.

RbnJrg's code also fails to "auto-center", applying the 85% max-width constraint right-to-left rather than 7.5% on either side. It also ignores the "fit-content" property. See imageADE-RJ attached.

And in my modified code, which steals a bit from RbnJrg and a bit from Horus01, the auto-center effect fails (although in this particular case it gives the illusion of centering because of the right-aligned attribution), as does the "fit-content" property. See imageADE-EM attached.

Spoiler:
Code:
blockquote.bqibEM {
    margin: 1em auto;
    padding: 0 2em;
    display: block;
    width: fit-content; 
	}


However, in both RbnJrg's and my FrankenCode, it doesn't produce any MAJOR readability issues that I can discern. It just doesn't look as nice as it would in an application that isn't total trash.

So, in summary:
1) The only code that you endorsed (other than your own, which didn't address any of the concerns in the original post) has serious readability issues in ADE, which Horus01 rightly pointed out from the jump.
2) The apparent readability of RbnJrg's and my new code (courtesy of RbnJrg's and Horus01's tips & tricks) means that your constant refrain that we use code optimized for ADE 2.X is basically taking the position that ebooks should look mediocre across all platforms rather than looking good in several and mediocre only in ADE. I can comfortably say: this is a weird take.
3) Thank you again to RbnJrg and Horus01 for their help. Teamwork apparently does make the dream work.

EDIT: P.S. in my code snip above, I'm defining the L/R boundaries in em units because I want the max-width to be relative to paragraph indents (which i usually set at 1.5em) rather than the width of the screen. However, if I used % units to define paragraph indents (e.g. "text-indent: 5%;") I think one could basically acheive the same result as RbnJrg's original code by using "padding: 0 7.5%;" instead of the max-width property... I think. I'll let RbnJrg confirm or clarify this, though.
Attached Thumbnails
Click image for larger version

Name:	imageADE-H.jpg
Views:	9
Size:	279.1 KB
ID:	221778   Click image for larger version

Name:	imageADE-RJ.jpg
Views:	9
Size:	327.6 KB
ID:	221779   Click image for larger version

Name:	imageADE-EM.jpg
Views:	9
Size:	331.2 KB
ID:	221780  

Last edited by ElMiko; 03-15-2026 at 09:05 AM.
ElMiko is offline   Reply With Quote