Quote:
Originally Posted by Godzil
But until now they where able to only read Mobi file, and the Mobi SDK is able to read DRMed and unDRMed Mobi file, so why bother to add another Mobi reader that will be usefull for nothing more than duplicate the code and possibly have bug on one version and bug on the other.
|
Because they can't use it together with Adobe SDK. It will have bugs, right, but they can fix the bugs and they can add features, which they can't with the Mobi SDK. I'm not saying they have to develop something from scratch, but they should have something they can freely modify.
Quote:
|
That the same for ePub, now they have access to the Adobe SDK that provide well made ePub reader, why did they need to bother to make another ePub reader that will introduce bugs that the other may not have?
|
Because Adobe ePUB reader is not perfect and they might want (or rather we, the users, want) to add other features like custom CSS, or support for oeb-page-head and oeb-page-foot, or remove the page numbers from the margin... or just use it with Mobi DRM support.
Quote:
|
Making a eBook format reader is not like cliking a checkbox... I don't know how much code Mobi or ePub parser need to be functional, but it surely need a lot month of man work to do them...
|
I don't say it's easy, I don't think it's easy, but it's not the most difficult task either. I'm sure basic (X)HTML/CSS/SVG parsers already exist that they could use for a start, and Kovid made a decent ePUB reader himself, so it should be feasible even for a small company.
But don't misunderstand me, I'm not saying they should develop an independent reading software, I just wish they'd have the time and resources to do it.