![]() |
#16 | |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 368
Karma: 1000000
Join Date: Mar 2016
Device: none
|
Quote:
|
|
![]() |
![]() |
![]() |
#17 |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 368
Karma: 1000000
Join Date: Mar 2016
Device: none
|
I see what you mean about using centered asterisks, except again it is not what I intend and I am altering what is intended because no real solution is available. I don't like doing that. A space is what I intend, it's achievable with CSS, but it doesn't currently translate for blind people. If I can't achieve what I intend, that's usually a sign to not do an ebook, since a plain text file in Markdown is what I'm forced to provide.
|
![]() |
![]() |
Advert | |
|
![]() |
#18 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
|
There are:
I highly recommend watching the fantastic talk from ebookcraft 2019: "Building Ebooks that Last", which was an editor from Houghton Mifflin describing the realities of long-term ebook production. And read my discussion of that in: This is why you use proper HTML+visual markup. Not relying on pure CSS solutions. |
![]() |
![]() |
![]() |
#19 | |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 368
Karma: 1000000
Join Date: Mar 2016
Device: none
|
Quote:
|
|
![]() |
![]() |
![]() |
#20 | |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 368
Karma: 1000000
Join Date: Mar 2016
Device: none
|
Quote:
|
|
![]() |
![]() |
Advert | |
|
![]() |
#21 |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 368
Karma: 1000000
Join Date: Mar 2016
Device: none
|
I mean people are forever copying stuff of mine and pasting onto the web without bothering to supply my italics. That's beyond my control.
|
![]() |
![]() |
![]() |
#22 | |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 368
Karma: 1000000
Join Date: Mar 2016
Device: none
|
Quote:
|
|
![]() |
![]() |
![]() |
#23 |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 368
Karma: 1000000
Join Date: Mar 2016
Device: none
|
I was surprised that my Kindle Paperwhite loads a humble .rtf file and preserves the limited styling of rich text. Made me wonder what an EPUB was actually offering beyond this, though I suppose other ereaders wouldn't load .rtf.
|
![]() |
![]() |
![]() |
#24 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
|
I highly recommend taking your time and reading through those previous topics.
They cover and discuss the pros/cons of scenebreaks (and others) in-depth. I'd also recommend checking out that ebookcraft talk, where she describes the reality across thousands of books + dozens of storefronts + running across every kind of obscure reader/use-case out there. Hint: A ton of the work is redoing old/crappy/poorly-done ebooks, and "bringing them up to current standards". (That's a huge fraction of the work I do too!) Learn from the mistakes, and try not to repeat them. Do your best to follow the standards, while still keeping in mind the actual readers. (Like use the actual Unicode characters, not ant-sized images of obscure characters!!!) - - - PS. On MobileRead, there's a multi-quote button. It's right next to the QUOTE button. You're able to gather+respond to multiple posts in a single post. It would help keep from flooding the threads with multiple tiny responses minutes after each other. |
![]() |
![]() |
![]() |
#25 | ||
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 368
Karma: 1000000
Join Date: Mar 2016
Device: none
|
Quote:
Quote:
|
||
![]() |
![]() |
![]() |
#26 |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 316
Karma: 3200000
Join Date: Oct 2015
Location: Madison, WI
Device: Kindle 5th Gen
|
Given that you’re concerned about accessibility, quite a lot. RTF files are completely unsemantic and all styling is purely visual. Absolutely nothing is conveyed about the structure of the document.
|
![]() |
![]() |
![]() |
#27 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
|
|
![]() |
![]() |
![]() |
#28 |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 79,786
Karma: 146391129
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
After thinking about it, what you can do is use an image instead of the <hr/> line. That way you can use alt="section break" in the <img code and the accessibility reader should pick up the alt and read it.
Last edited by JSWolf; 07-13-2022 at 05:24 PM. |
![]() |
![]() |
![]() |
#29 | |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 368
Karma: 1000000
Join Date: Mar 2016
Device: none
|
Quote:
|
|
![]() |
![]() |
![]() |
#30 | |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 368
Karma: 1000000
Join Date: Mar 2016
Device: none
|
Quote:
|
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
How to Increase Line Space in Calibre 4.2 Viewer | brown.ml | Calibre | 2 | 10-19-2019 11:07 AM |
Space between First and Second line on the Chapters | nadabutamor | Kindle Formats | 19 | 08-26-2018 02:28 PM |
italic at end of line causes next line to start with a space | ebookreadr | Sigil | 29 | 03-20-2017 11:25 AM |
Glo Line space bug with some fonts | sage79 | Kobo Developer's Corner | 5 | 07-09-2015 03:01 PM |
How to increase the line space in CSS | Sylver | Calibre | 3 | 08-08-2010 01:02 AM |