MobileRead Forums - View Single Post - Google Play Books and Nested Lists

Quoth · 08-24-2021, 10:15 AM

No-one should be reading ebooks (actual epub files) or PDFs in a browser. You can't insure against people using the wrong programs.

A "cloud" reader isn't the same thing.

We actually tried to craft special HTML samples for people that insist on doing things in a browser. But we removed them because it didn't make sense.

If it works in real Apps, Calibre Viewer and real ereader then stupidity of browser extensions is irrelevant.

See samples here https://www.corvidspress.com/fiction...ne-of-destiny/
and https://www.corvidspress.com/fiction...ntices-talent/

The epub samples are the same source as the full book edited in LO Writer (odt format) and an extra "Save As" in "docx" format, imported to Calibre and converted with our defaults to epub2. No edits to CSS or HTML

The PDF is not a final version, but a quick mock up of the source "odt" edited as a separate "odt" file and exported as a PDF, all with LO Writer.

If I was doing something that needed CSS & HTML edited (i.e. a more complicated book than is possible automatically from docx to epub2) I'd use Sigil rather than InDesign, which is really a desktop publishing tool for paper via PDF to the printing company that's been kludged to make Kindle or epub ebooks.

I've not looked at "PlayBooks_NestedLists_Test_V03.epub" so I can't comment on the specific example except to say I'd never waste my time looking at an epub with a browser extension.

I don't remember doing more than one level lists in a novel. But certainly I've done nested lists in reports, technical documents and manuals and I'd not have read any of those in a browser. The most evil technical document I did was exporting a powerpoint to HTML for a website after it was presented in person to the intended audience using MS Office XP on a laptop.

I might put a heading on a list with a Page Break Before, but of course on a 4.3" screen or a 600x800 eink (5" and older 6" screens) a large list will break in the middle, or someone might increase the font size. You only have total control of layout on a PDF and inherently if the screen isn't large enough it's rubbish. The entire idea of a PDF is to proof on a screen big enough for a whole page, or ideally two side by side pages, of what is going to be printed on paper.

That's why Mac originally had laser printer, Display Postscript and giant screens to capture the print publishing market. Adobe InDesign might have been Aldus Pagemaker then. It's long ago and back then I was more involved with CAD/CAE schematics and PCB layout on PCs and later networking Mac OS9 machines to Windows Server, HP plotters and Lasers and making presents of three button PC USB mice to Mac users with the awful single button puck. But OS9 and earlier was better than Win98, though not as good as even NT 3.51 never mind NT 4.0. The first OS X (Mac OS 10) was a huge improvement under the GUI.

08-24-2021, 10:15 AM	#61
Quoth Still reading Posts: 14,145 Karma: 105212035 Join Date: Jun 2017 Location: Ireland Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper	No-one should be reading ebooks (actual epub files) or PDFs in a browser. You can't insure against people using the wrong programs. A "cloud" reader isn't the same thing. We actually tried to craft special HTML samples for people that insist on doing things in a browser. But we removed them because it didn't make sense. If it works in real Apps, Calibre Viewer and real ereader then stupidity of browser extensions is irrelevant. See samples here https://www.corvidspress.com/fiction...ne-of-destiny/ and https://www.corvidspress.com/fiction...ntices-talent/ The epub samples are the same source as the full book edited in LO Writer (odt format) and an extra "Save As" in "docx" format, imported to Calibre and converted with our defaults to epub2. No edits to CSS or HTML The PDF is not a final version, but a quick mock up of the source "odt" edited as a separate "odt" file and exported as a PDF, all with LO Writer. If I was doing something that needed CSS & HTML edited (i.e. a more complicated book than is possible automatically from docx to epub2) I'd use Sigil rather than InDesign, which is really a desktop publishing tool for paper via PDF to the printing company that's been kludged to make Kindle or epub ebooks. I've not looked at "PlayBooks_NestedLists_Test_V03.epub" so I can't comment on the specific example except to say I'd never waste my time looking at an epub with a browser extension. I don't remember doing more than one level lists in a novel. But certainly I've done nested lists in reports, technical documents and manuals and I'd not have read any of those in a browser. The most evil technical document I did was exporting a powerpoint to HTML for a website after it was presented in person to the intended audience using MS Office XP on a laptop. I might put a heading on a list with a Page Break Before, but of course on a 4.3" screen or a 600x800 eink (5" and older 6" screens) a large list will break in the middle, or someone might increase the font size. You only have total control of layout on a PDF and inherently if the screen isn't large enough it's rubbish. The entire idea of a PDF is to proof on a screen big enough for a whole page, or ideally two side by side pages, of what is going to be printed on paper. That's why Mac originally had laser printer, Display Postscript and giant screens to capture the print publishing market. Adobe InDesign might have been Aldus Pagemaker then. It's long ago and back then I was more involved with CAD/CAE schematics and PCB layout on PCs and later networking Mac OS9 machines to Windows Server, HP plotters and Lasers and making presents of three button PC USB mice to Mac users with the awful single button puck. But OS9 and earlier was better than Win98, though not as good as even NT 3.51 never mind NT 4.0. The first OS X (Mac OS 10) was a huge improvement under the GUI.