Quote:
Originally Posted by JSWolf
Actually, it is the case for Mobipocket. Some devices have an older version of Mobipocket Reader that will not work well or at all with current version Mobipocket files.
|
Yea that is not really the same thing. The issue your pointing out is due to obsolescence. That is going to happen as long as technology is involved. ... Right I mean the PRS-500 doesn't support ePUB
What I'm talking about is current solutions. SONY is not obsolete in fact it's the only eInk device that supports ePUB. Yet there are ePubs that will not work with SONY.
Quote:
Originally Posted by kovidgoyal
Actually EPUB is as loosely defined as XHTML+CSS which is plenty successfull. And the fact that there isn't one company guiding it's development is an advantage not otherwise. It will reach the level of maturity of MOBI (a much simpler format) far more quickly as a result. As for the 300K file limit that everyone keeps complaining about, it's really not an issue. It just requires tool support in epub creation tools.
|
I think your not seeing my point, and I'll agree it's not too obvious. I just want one solution that works. I'm tired of dealing with all the different formats out there. I can't standardize on one format since often I can only finding certain books under MOBI/PDF/LIT/eReader/<your format here>.
I want ePUB to succeed esp since it has done a good job for the most part, but I find it failing in some key areas. Which leads to abuse from companies, the very nature of this post is an example.
What I'm gripping about is for the ePUB standard to fix this to prevent future abuse, or future misinterpretation of standards.
For me it's not so much SONY's 300KB file size limit that cause me concern, itt's the failed expectation that as long as I have an ePUB file I can read it on any ePUB device.
Quote:
Originally Posted by netseeker
I would have to re-read the specification documents to discuss this further, but i guess you are right. What i don't get is why the sony developers didn't choose another way to solve the memory issues. They must have been very "uninspired"...
Yes, that's my worry too. I hope that the FBReader team will improve it's ePub-implementation and that a lot of other projects will add standard conforming (and well working) implementions soon.
PS: Sorry for my assumption that you aren't (or weren't) a sw developer...
|
No worries this board is quite diverse message board.
=X=