Thread: Reality check
View Single Post
Old 02-28-2008, 02:56 AM   #33
HarryT
eBook Enthusiast
HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.
 
HarryT's Avatar
 
Posts: 85,557
Karma: 93980341
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
Quote:
Originally Posted by tompe View Post
Actually I do not think you should support proprietary formats but I do not see MobiPerl as a support of MobiPocket. For me the important format is what you archieve the book in and that should probably be something like epub. So Mobipocket can be used to convert from MobiPocket to some suitable base format. Convertingt from HTML to Mobipocket ör manipulating MobiPocket files I see just like something you do for your current display device and just a practical way to solve a problem that exists now.
Certainly I agree with you that Mobi should be regarded as a terminal format, not a long-term storage format. That's why, when I create books, I always store the original source files (text, HTML, or whatever) in addition to the converted book. I may not be able to read my MobiPocket files in 20 years' time, but I'm sure that I'll be able to convert the source files into whatever I'm using at that time.
HarryT is offline   Reply With Quote