View Single Post
Old 09-15-2013, 04:38 PM   #13
Doitsu
Wizard
Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.
 
Doitsu's Avatar
 
Posts: 4,066
Karma: 12828160
Join Date: Dec 2010
Device: Kindle PW2
Quote:
Originally Posted by Jellby View Post
But Kindles do not read ePub, even if the inside of a KF8 file is similar to ePub. And Sigil is an ePub editor.
For all intents and purposes the KF8 format is ePub2 plus most non-interactive HTML5/CSS3 elements. Both KindleGen and Calibre will convert valid ePubs without changes to the source code just fine and both hobbyists and professional ebook designers use Sigil to create Kindle books.

In many ways the current Kindle devices offer more layout features than ADE-based devices. And, as your many posts in the Known ADE bugs forum show, you of all people should be fully aware of the many bugs and limitations in ADE.
IMHO, Adobe just got lucky, because nobody else bothered to develop competing DRM solutions and most ereader manufacturers need to buy an RMDSK license for DRM support alone.

Quote:
Originally Posted by Jellby View Post
Any future "improvement", I'm afraid, will be in the way of bells and whistles, animations, facebook and one-touch buying, and not in better CSS support, spec compliance or layout control (for the user).
I'm not so pessimistic. While new ereaders will doubtlessly come with a plethora of social network and in-app buying features that nobody wanted, ebook manufacturers will eventually discover ePub3 as a marketing tool and will demand that the firmware of their ereaders support ePub3/HTML5/CSS3.

And since the solution suggested by RbnJrg will already work on two different "ecosystems" (iBooks and Kindle/KF8) I fail to see why he shouldn't post them here just because purists insist on Kindles not being "real" ePub2 readers.

@RbnJrg: Keep your often innovative solutions coming.
Doitsu is offline   Reply With Quote