Thread: Kobo Bug thread
View Single Post
Old 03-01-2017, 01:55 AM   #840
Rev. Bob
Wizard
Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.
 
Rev. Bob's Avatar
 
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
Quote:
Originally Posted by JSWolf View Post
Given that Kobo has a font, font size, margins, & line-height settings, having eBooks made so these work well would be best.
I am staunchly opposed to any set of standards designed around any one company's platform.

Quote:
Originally Posted by JSWolf
I would like no margins, no excessive space wasted for chapter titles, no line-height except as needed, no embedded fonts except as needed, no paragraph spaces, indents of 1.2-1.5em, & no excessive space for offset text.
Taking these one at a time:

- "No margins." On anything? Bad idea. If nothing else, the existing HTML specs define certain default margins; devices should adhere to those rather than defining a new set of defaults that results in contradictions. We'd have the browser wars all over again.

- "No excessive space." Useless, since "excessive" is a subjective definition.

- "No line-height." Setting line-height to zero instantly makes all text unreadable, if strictly implemented. Omitting the parameter for standard-size text is something I can get on board with, but particularly with Kobo, not setting line-height when changing font size is a recipe for disaster. (Ever seen headers that overlap when the text wraps to a second line? That's why that happens. Setting line-height to "normal" when resizing text fixes that.)

- "No embedded fonts except as needed." Please define "need." It's one thing to define it functionally ("I need to display some emoji characters."), but some people will define it cosmetically ("I need to use this font to convey this style.").

- "No paragraph spaces." Back to the browser wars, I see.

- "Indents of 1.2-1.5em." A range is not a number, so here you're getting into "best practices." I agree that paragraph indents should be around that mark - I use 1.5em, myself - but I would strongly resist making that a default value in the reader.
Rev. Bob is offline   Reply With Quote