Quote:
Originally Posted by JSWolf
Thing is, the code in the ePub has been heavily modified. It very well may not display properly in a number of different ePub renderers. It's not what we expect to get when we buy it. When we buy Lock In, we expect to get the code as it came from the publisher. We don't expect to get Kobo heavily modifying it.
|
Hmmm... most of the programs and I've used to test epubs are quite happy with Kobo's modified epubs. The mass of locator spans does nothing visually and they don't know what to do with the .js files so again no effect. The only time there is an issue with Latin language ebooks is when the kepub is DRMed since only Kobo programs and devices are supposed to be able to display them. <cough>
«rant mode on»
As for the code as it came from the publisher? Do we really need 4 p.xxxx classes with identical contents? Specifying widows and orphans in multiple spots? Forcing wide top, bottom, right and left margins? One of the reasons I got into editing my ebook collection was that, in my opinion, the average publisher at that time knew little about laying out ebooks nor did they seem concerned with any consistency -- nothing like reading a series where each book has it's own layout and style. That has changed to an extent but still not up to the average quality level of dead tree books.
«rant mode off»