Problem adding extra lines in text

[DNSB]

Originally Posted by Turtle91

Apparently not on Moon+ (or other readers) which ignore publisher's css completely...

I'm pretty sure that means it'll ignore padding as well as margins

You can set MoonReader+ to use publisher CSS but even then quite a bit of bog-standard CSS is disregarded. I tried it a couple of times on an Android tablet and gave up in disgust.

[JSWolf]

Originally Posted by DNSB

You can set MoonReader+ to use publisher CSS but even then quite a bit of bog-standard CSS is disregarded. I tried it a couple of times on an Android tablet and gave up in disgust.

Is there a good ePub Reader for Android that respects the CSS?

[jugaor]

Originally Posted by JSWolf

Is there a good ePub Reader for Android that respects the CSS?

I tried Lithium with success.

[Turtle91]

Originally Posted by JSWolf

Is there a good ePub Reader for Android that respects the CSS?

If you are creating a book for your own use, then I would definitely use the one that gives the best, most consistent results. I've found that on iOS, and I'm happy... android, not so much...but then I haven't had a lot of time to experiment. For all these professional book makers, they need to provide a decent experience across platforms. Without assuming they are going to use kindle, or books (*shudder*), then the fallback would have to be an asterism of some kind, wouldn't it?

I think the key question would be: Without using CSS (and I'm assuming inline styling is also ignored?), is there a way to center a container for the image/asterisks/etc? Or are they stuck with the *** flush left as Tex mentioned...

[DiapDealer]

Originally Posted by JSWolf

But it is sufficient if you use the correct CSS code.

No. It's not, Jon. It's insufficient because neither--even when coded perfectly, and rendered perfectly--is easily detectable when it occurs on page breaks. THAT is what's being discussed. That vertical space alone is not sufficient for scene-breaks to be noticed in all cases. Forget margin vs padding. It's not relevant to the question of whether vertical spacing, alone, suffices for scene-breaks in ebooks.

[Tex2002ans]

Originally Posted by Turtle91

Apparently not on Moon+ (or other readers) which ignore publisher's css completely...

I'm pretty sure that means it'll ignore padding as well as margins

Correct.

Originally Posted by DNSB

You can set MoonReader+ to use publisher CSS but even then quite a bit of bog-standard CSS is disregarded. I tried it a couple of times on an Android tablet and gave up in disgust.

Correct. I also mostly gave up in disgust.

I was only using Moon+ because it had minimal footprint. My old phone had very low RAM, and the OS itself was becoming too bloated over the years.

Originally Posted by JSWolf

Is there a good ePub Reader for Android that respects the CSS?

Yes, I've been using Gitden Reader, or lately I've shifted to PocketBook.

Been using them for many years now, and they are fantastic.

Both:

• follow publisher CSS
• support lots of EPUB2/EPUB3
  
  • Back when epubtest.org had their "EPUB3 Support Grid", they were both towards the top of the pack.
• RMSDK (EPUB2) / Readium-based (EPUB3)
  
  • or PocketBook also has an optional WebKit-based renderer.
• have lots of functionality built-in
  
  • Most importantly for me: Text-to-Speech.

Most of the other Android "EPUB apps":

• ignore publisher CSS.
• don't support the actual EPUB standards
• try to charge for basic functionality (TTS)

[Quoth]

I've been using Lithium on Android, largely because Calibre and Lithium will see the same files and it works with both separate and integrated SD card mounting.

I was using something else, but an updated version required logging into Adobe before doing ANYTHING.

I was using PocketBook, also for PDF, but it IMPORTS the files, not sensible with huge amount of PDFs and Calibre has no idea what books are in the Pocketbook library.
I use Xodo for PDFs on the tablet now because I can copy the structure of nearly 200 Gbyte of laptop directories and it can browse the 256G byte SDXC card (£37). The XC cards shouldn't be reformatted without special tools. They use a different Partition type.
Also Xodo has tabs per document open. Most of my PDFs are reference materials. Some are old magasines or technical books in the Public Domain.

I only have PDFs that would work as A5 or smaller on the Kobo Libra. One or two old novels and mostly operation/user manuals for gadgets with insane UI.

[JSWolf]

Originally Posted by Turtle91

If you are creating a book for your own use, then I would definitely use the one that gives the best, most consistent results. I've found that on iOS, and I'm happy... android, not so much...but then I haven't had a lot of time to experiment. For all these professional book makers, they need to provide a decent experience across platforms. Without assuming they are going to use kindle, or books (*shudder*), then the fallback would have to be an asterism of some kind, wouldn't it?

I think the key question would be: Without using CSS (and I'm assuming inline styling is also ignored?), is there a way to center a container for the image/asterisks/etc? Or are they stuck with the *** flush left as Tex mentioned...

There is no way I would ever use * * * as that's been spoiled by too may eBook makers who try to duplicate a pBook with a combination of space and * * * for section break markers. I cannot stand that when I get * * * in the middle of the screen sometime and blank space other times.

However, an <hr/> with L/R margins of 45% works well. If the CSS is ignored, you get get a short line left justified, you get a full line across the screen. That to me looks a like nicer. So does the short centered line when CSS is working.

[Tex2002ans]

Originally Posted by DiapDealer

For god's sake, can we move past your padding vs margin obsession? They're talking about blank space provided 100% by css in general not being sufficient. Which exact css properties are being used to achieve that insufficient blank space is irrelevant to that particular conversation.

Oh no, Diap... it's started again. This time it's the new <hr> obsession! Start the countdown for ADE pages next!

[Hitch]

Originally Posted by Tex2002ans

Oh no, Diap... it's started again. This time it's the new <hr> obsession! Start the countdown for ADE pages next!

I'm going to have my own personal meltdown. I just wanna say that.

Hitch

[JSWolf]

Originally Posted by Tex2002ans

Oh no, Diap... it's started again. This time it's the new <hr> obsession! Start the countdown for ADE pages next!

I cannot stand asterisks for section breaks. They look awful. Plus, they remind me of poorly made eBooks.

So without using asterisks, what you you use for a section break that's not empty space?

[pdurrant]

Originally Posted by JSWolf

So without using asterisks, what you you use for a section break that's not empty space?

A fleuron.

[JSWolf]

Originally Posted by pdurrant

A fleuron.

If the fleuron is a graphic image, it can be too small or too large. How do you choose an image size that's just right?

I'm reading Percy Jackson and the Lightning Thief. There is a fleuron used for each chapter under the chapter number. This fleuron is too small. What would be a perfect size for my H2O's screen would be too large for a Kindle Basic.

[pdurrant]

Size the fleuron in ems. No problem.

[Hitch]

Originally Posted by pdurrant

Size the fleuron in ems. No problem.

I realize that we're in the ePUB forum, but I do feel compelled to point out that em-sizing for images doesn't always work in MOBI/PRC/yadda, either.

I remember back when Guido Henkel claimed that was the end-all, be-all solution for early MOBI making, except, it didn't work--at all. On some devices, still doesn't.

Hitch