Further investigations reveal that, after switching on the device, the database is not read until something is altered in the DB, e.g. by moving some slider.
Without the line height patch, the line height is taken from the global configuration file. With one of the two patches applied, it is probably also taken from there, but the line height becomes a certain smaller proportion of that, say 75%.
After moving some slider, or connecting with USB and disconnecting, the values are taken from the database.
Until firmware version 2.8.1, a line height of 1.35 was common. But from 2.10 on, line heights were displayed much wider, so 0.88 became optimal. But 1.0 remained the minimum value that could be set with the slider, so that's why the patch became wanted.
Quote:
Originally Posted by GeoffR
Are you reading epubs or kepubs?
|
Only epubs.
Quote:
Originally Posted by GeoffR
What other patches do you have enabled?
|
Probably not relevant, but here they are:
Custom reading footer style
Custom left & right margins
Custom font sizes
Search in Library by default
Unitless ePub line height
Custom footer
Fix page breaks bug
Quote:
Originally Posted by GeoffR
Are you using full-screen reading mode?
|
This is unknown to me. Only present in kepubs I guess?
Quote:
Originally Posted by GeoffR
The other thing that would be interesting to check for anyone having similar problems is the line spacing value stored in the database for the book in question. You can do this with a SQL query such as:
SELECT ReadingLineHeight FROM content_settings WHERE ContentID=='file:///mnt/onboard/H/Holdstock, Mythago Wood.epub';
|
These fields contain the correct line height values, 0.88 in my case.
But, as explained, these are only read after something in the database has been altered.