View Single Post
Old 04-10-2018, 07:34 PM   #15
Tex2002ans
Wizard
Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.
 
Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
Quote:
Originally Posted by wlashack View Post
I use Moon+ Reader for Android to read ebooks and this application can display "original formatting". So it can displays the document the same way as Sigil, with all the bullets and numbers.
No, Moon+ is the exact opposite of "Original Formatting". What they do is throw away almost everything in the book's CSS, and overwrite it with Moon+'s settings. They also don't follow any sort of standard, and try to smush ALL document formats into Moon+'s way of doing things.

As DiapDealer said, Bookari is one of the standards-compliant readers on Android (it uses the same engine as the EPUB ereaders).

Gitden is also a pretty decent Android EPUB2/3 reader.

Quote:
Originally Posted by wlashack View Post
But for some reason it can display only one chapter at a time in this mode so to "turn page" to another part of the document, you need to switch to "normal" view, open chapter and switch to "original formatting" again. A little bit frustrating.
... mostly because the code generated from that Google Doc is horrifying. There is a giant block of hundreds of CSS classes all smushed together into a single line, and who knows what is in there:

Quote:
.lst-kix_5lzjr43cw69v-3>li{counter-increment:lst-ctn-kix_5lzjr43cw69v-3}ul.lst-kix_b56rwjgjsre-8{list-style-type:none}.lst-kix_2dpmixc6z6cd-8>li{counter-increment:lst-ctn-kix_2dpmixc6z6cd-8}ol.lst-kix_yfjv4tvanyan-1.start{counter-reset:lst-ctn-kix_yfjv4tvanyan-1 0}.lst-kix_2dpmixc6z6cd-2>li:before{content:"" counter(lst-ctn-kix_2dpmixc6z6cd-2,lower-roman) ". "}.lst-kix_jsljq9wvyxl9-7>li{counter-increment:lst-ctn-kix_jsljq9wvyxl9-7}.lst-kix_2dpmixc6z6cd-3>li:before{content:"" counter(lst-ctn-kix_2dpmixc6z6cd-3,decimal) ". "}.lst-kix_2dpmixc6z6cd-4>li:before{content:"" counter(lst-ctn-kix_2dpmixc6z6cd-4,lower-latin) ". "}.lst-kix_2dpmixc6z6cd-5>li:before{content:"" counter(lst-ctn-kix_2dpmixc6z6cd-5,lower-roman) ". "}ul.lst-kix_b56rwjgjsre-5{list-style-type:none}.lst-kix_xhtrpcql5mbs-7>li:before{content:"\0025cb "}.lst-kix_2dpmixc6z6cd-8>li:before{content:"" counter(lst-ctn-kix_2dpmixc6z6cd-8,lower-roman)
[...]
I'm assuming what's causing the odd page breaks is the page-break-after:avoid floating around in there.

Side Note: The CSS alone is about 6 times larger than your actual text... talk about a bloated mess!

Last edited by Tex2002ans; 04-10-2018 at 07:39 PM.
Tex2002ans is offline   Reply With Quote