Quote:
Originally Posted by Dave_S
In that case you are most likely going to have to keep your "legacy" ebook reader in good working order, because it is highly unlikely that any developer is going to waste much time supporting obsolete formats. Your position is reminiscent of someone with a vinyl record collection demanding that ipods work with unconverted vinyl recordings.
|
I'm not going to keep debating this with you, let's agree to disgree.
We have differing views about the definition of legacy and how best one should handle that at least in the short term.
Ultimately I may have to convert the ebooks but as I've tried to explain, my experience has been that conversion was not good enough because of formatting issues - so the conversion tools are
not a no-brainer to justify a big effort converting to epub especially if we have epub superceded by the next 'standard' format in a year or 2.
Using an analogy, you can convert DVDs to .MP4 or .MKV using the latest H.264 codec, but the conversion will degrade the video quality slightly. Alternatively you can get a video player program that can play both DVD and .mp4 which covers both the older files and the newer ones you buy.
And if you retain the original file you can convert to a future .MP5 format with the minimum of quality loss compared to a conversion of DVD -> MP4 -> MP5. And you might still get a player that supports dvd, mp4 AND mp5.
I basically don't agree that .LIT is obsolete (yet) which was somewhat supported by the later posts too, and some of the later posts demonstrate that the format is pretty standards based too, so adding support is not too big a deal for a developer.
As I've said all along - it will be up to the developer (and not you or me) to decide what he does or doesn't do re additional ebook format support. I'm OK with whatever he decides.
But I have tried to make a case for why some people (and not just me) would prefer to find a reader that can read both .LIT and .PDB ebooks too. It's clearly not that hard technically to add support (at least for non-drm which is all I want) so the programming effort should not be too onerous. Let's just let Buggins decide to add .LIT support, or not, as the case may be.