MobileRead Forums - View Single Post

kiwidude · 05-09-2012, 05:42 AM

Thx Wallcraft. Sounds like I should include them in the "missing" results then, which they are not currently.

Which brings me onto some more questions:

Is there a need for separate ASIN and EBOK checks? What would people prefer - as it is now or a single check which had the details of what was missing in the log? I don't know what I would call a single check though. If I called it something device specific like "Check invalid for Kindle Fire" then it causes a headache when Amazon releases its next generation of devices...
ElizabethN found an interesting case - catalogs generated by calibre. If you generate in MOBI, it sets the cdetag to be NWPR. What happens to these on a Kindle Fire? Is that desirable? Should I exclude books in your library with the "Catalogue" tag so they don't end up in the results, or should they be included?
How are users going to "remedy" mobi files that need changing? Obviously a MOBI->MOBI conversion is one way, though potentially extreme. I see ElizabethN is mentioning a manual process of a third party tool. It seems to me that perhaps there could either be an addition to the "Fix" menu, or maybe even a "Modify MOBI" plugin. I am hesitant to suggest the latter because it opens up all sorts of cans of worms for the future (like people wanting to then be able to do similar things they can do with Modify ePub such as updating metadata, covers, smarten punctuation etc). That is way more than I want to think about (and since I always keep ePub and my MOBI files are converted from that master ePub I personally would never use it which makes me even less enthusiastic about the time spent on it). So "maybe" an entry on the Fix menu of this plugin is something I would consider... maybe...
If automating such a "fix", replacing the cdetag with EBOK should be straightforward. But what about a missing asin? Where does that come from? Does the value matter?

05-09-2012, 05:42 AM	#402
kiwidude Calibre Plugins Developer Posts: 4,732 Karma: 2197770 Join Date: Oct 2010 Location: Australia Device: Kindle Oasis	Thx Wallcraft. Sounds like I should include them in the "missing" results then, which they are not currently. Which brings me onto some more questions: Is there a need for separate ASIN and EBOK checks? What would people prefer - as it is now or a single check which had the details of what was missing in the log? I don't know what I would call a single check though. If I called it something device specific like "Check invalid for Kindle Fire" then it causes a headache when Amazon releases its next generation of devices... ElizabethN found an interesting case - catalogs generated by calibre. If you generate in MOBI, it sets the cdetag to be NWPR. What happens to these on a Kindle Fire? Is that desirable? Should I exclude books in your library with the "Catalogue" tag so they don't end up in the results, or should they be included? How are users going to "remedy" mobi files that need changing? Obviously a MOBI->MOBI conversion is one way, though potentially extreme. I see ElizabethN is mentioning a manual process of a third party tool. It seems to me that perhaps there could either be an addition to the "Fix" menu, or maybe even a "Modify MOBI" plugin. I am hesitant to suggest the latter because it opens up all sorts of cans of worms for the future (like people wanting to then be able to do similar things they can do with Modify ePub such as updating metadata, covers, smarten punctuation etc). That is way more than I want to think about (and since I always keep ePub and my MOBI files are converted from that master ePub I personally would never use it which makes me even less enthusiastic about the time spent on it). So "maybe" an entry on the Fix menu of this plugin is something I would consider... maybe... If automating such a "fix", replacing the cdetag with EBOK should be straightforward. But what about a missing asin? Where does that come from? Does the value matter?