Quote:
Originally Posted by Barty
IMO, they need to a) redesign the reading screen so they do not have huge space wasted on top and bottom ; b) total user control of margin and line line spacing ; c) fix HTML/ rendering annoyances, like the widow/orphan bug.
Until they get these right, nothing else matters to me and I will not buy a kobo.
|
There is very little wasted space at the top of the screen with the current firmware. The space at the bottom has been part of the Kobo ereader screen since the original Kobo. Kepubs still have the wide top margin as they have always had.
Line and margin spacing? Give the user total control and take it away from the ebook publishers who have an idea (vague and misdirected though it might be) as to what they want the ebook to look like.
Widows and orphans are not a
bug. They were a part of the CSS 2 specification and Adobe was simply following that standard when they included widow/orphan support with a default of 2. And please note that Adobe not Kobo supply the Adobe Reader Mobile SDK.
To quote from "Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification":
Code:
13.3.2 Breaks inside elements: 'orphans', 'widows'
'orphans'
Value: <integer> | inherit
Initial: 2
Applies to: block container elements
Inherited: yes
Percentages: N/A
Media: visual, paged
Computed value: as specified
'widows'
Value: <integer> | inherit
Initial: 2
Applies to: block container elements
Inherited: yes
Percentages: N/A
Media: visual, paged
Computed value: as specified
The 'orphans' property specifies the minimum number of lines in a block container that must be left at the bottom of a page. The 'widows' property specifies the minimum number of lines in a block container that must be left at the top of a page. Examples of how they are used to control page breaks are given below.
Only positive values are allowed.
Regards,
David