[GUI Plugin] Quality Check

[paulfiera]

Originally Posted by kiwidude

Something like this perhaps... ?

It coudn't get better than that !

[theducks]

I ran the QC for xpgt links.

After it was done the search bar said:
marked:epub_inline_font_face
instead of: inline_xpgt_links

[kiwidude]

Here's a version for you to play with containing the new "Search ePub" feature. Let me know how it goes... the search text is a regular expression, the last 10 are remembered.

Thx theDucks, thats a cosmetic issue but I've included the fix in this version.

[theducks]

Originally Posted by kiwidude

Here's a version for you to play with containing the new "Search ePub" feature. Let me know how it goes... the search text is a regular expression, the last 10 are remembered.

Thx theDucks, thats a cosmetic issue but I've included the fix in this version.

Thanks, I had already fixed (hacked ) mine

[Pierre Menard]

Originally Posted by kiwidude

Here's a version for you to play with containing the new "Search ePub" feature. Let me know how it goes

Fantastic, thanks! I do think I may have found an issue, though perhaps not specific to this search.

I went to search my most recently added books. I highlighted 25 books, set the search scope to "Selected book(s)," and searched for "sigil" with "OPF manifest" checked. I got the following error:

calibre, version 0.8.50
ERROR: Unhandled exception: <b>NameError</b>:global name 'check_has_jacket' is not defined

Traceback (most recent call last):
File "calibre_plugins.quality_check.dialogs", line 49, in do_book_check
File "calibre_plugins.quality_check.check_epub", line 155, in evaluate_book
NameError: global name 'check_has_jacket' is not defined

Then I filtered my library by things added in the last day (yielding the same books as above, plus a few more), set a "restrict to" for those search results, changed the search scope to "Library," and re-ran the same thing. This time, no error.

Eventually I realized that one of the books was a mobi file (I don't usually have them, so I hadn't even thought to look). And I could run the plug-in search with "selected titles" on any individual title in the group except that one. I know the plug-in doesn't work on mobi files, but so far when I'd used it it would just ignore them. That doesn't seem to happen now with the "selected title(s)" option.

[kiwidude]

@Pierre - yeah thats a simple copy/paste error thanks, will be fixed in the next version. You will get it any time you select a book which does not have an epub format (or the physical epub file is missing, being out of sync with your library). So stick to books with epubs (or set the search scope to be whole library) and you should be fine.

I'm in the process of adding a couple of MOBI checks - "Check missing EBOK cdetype" and "Check missing ASIN identifier". I'll put a new beta including that up shortly...

[kiwidude]

Ok, here is a new beta version to replace the one I posted earlier. This has my first attempt at the checking of MOBI files for EBOK and ASIN, which was requested recently on this thread by CRussel, for users who have a Kindle Fire.

I don't have such a device myself so I have had to guess at a few things in conjunction with Kovid's tips in his post, but I *think* it is right. Hopefully someone (CRussel?) can give it a whirl and let me know if the results you see gel with what you know about books that do and don't place correctly on your Fire.

[ElizabethN]

Originally Posted by kiwidude

Ok, here is a new beta version to replace the one I posted earlier. This has my first attempt at the checking of MOBI files for EBOK and ASIN, which was requested recently on this thread by CRussel, for users who have a Kindle Fire.

I don't have such a device myself so I have had to guess at a few things in conjunction with Kovid's tips in his post, but I *think* it is right. Hopefully someone (CRussel?) can give it a whirl and let me know if the results you see gel with what you know about books that do and don't place correctly on your Fire.

Thank you! I'm currently using java mobi meta editor find & fix ebok/asin issues but having the ability to check from inside calibre would be great.

After much trial & error and examination with mobi meta editor one weekend, I found that I need the following to have non-amazon mobi files show up under books rather than documents on the fire...file must have Field 501 CDEContentType = EBOK and Field 113 ASIN = value, “fake” asin works, Field 504 ASIN not needed...so far field 504 only seems to matter if you want to "share" rather than "sync" files on kindle keyboard.

With calibre release 0.8.50, using the AZW3 (kf8) format with sharing unchecked to convert non-mobi files for the fire has so far resulted in files with EBOK in 501 & an "asin" in 113.

I still have many older mobis to look at before sending them to the kindle keyboard, so I'll try the beta version on some of those later tonight or tomorrow.

Thanks again!

[ElizabethN]

Beta works for me - now have a list of mobi files without cdetype and/or asin in the EXTH header that I can clean up before sending to a device.

I went through and validated accuracy by using mobi meta editor on several files, at approx 2000 files I didn't check all.

The 6 files that were showing on the fire in books but that didn't have EBOK and/or ASIN per the report turned out to be 4 books with manually edited EXTH headers and 2 that were from amazon.

this is the only unusual item on the log that was generated during the cdetype report - don't know why the search included one of my Goodread shelves.

Missing EBOK tag: GR currently-reading - calibre
cdetype: NWPR



Now I just need to re-read through the "open with" plugin to figure out if I can add mobi meta editor

https://www.mobileread.com/forums/sho...d.php?t=165729

to the customization list. Something for another day.

Thanks again.

[kiwidude]

"GR currently-reading - calibre" is an ebook in your library, presumably a catalog of some kind? The author being calibre.

Did you find any books in your log that did not have EXTH headers at all (they show as a red error in the log results). I wasn't sure what to do about those (or what that means). Does a MOBI without an EXTH work on the Fire, or should I include it in the output results of the check as a file the user must do something about?

[wallcraft]

Originally Posted by kiwidude

Does a MOBI without an EXTH work on the Fire, or should I include it in the output results of the check as a file the user must do something about?

These must be very early MOBI, or perhaps even PalmDOC, ebooks. See Wiki: MOBI. I don't know if they will work on the Fire, but if so they almost certainly will show up as Docs rather than Books.

Thanks for the MOBI checks, I tested them but all my MOBIs passed both checks. This is the expected result, since they all show up ok on the Fire.

[kiwidude]

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:

1. 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...
2. 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?
3. 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...
4. 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?

[nynaevelan]

Originally Posted by kiwidude

[*]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...

I've just had a chance to play with this and personally I would like for them to stay separate but I have no problem with going along with the consensus of the masses.

I do have a question for you, is there a way to add an option of adding EBOK checks to ignore so that they do not repeatedly show up in the results as problems? For example, I have PDOC and EBSP types, they are correct as they are but they keep showing up as problem files.

[ElizabethN]

Originally Posted by kiwidude

"GR currently-reading - calibre" is an ebook in your library, presumably a catalog of some kind? The author being calibre.

Did you find any books in your log that did not have EXTH headers at all (they show as a red error in the log results). I wasn't sure what to do about those (or what that means). Does a MOBI without an EXTH work on the Fire, or should I include it in the output results of the check as a file the user must do something about?

oops - it was a calibre created catalog - so old that I had forgotten about it. Gone now.

only 1 book had no EXTH header, old file; original was prc (ironically fire shows files as .prc rather than .mobi in the fire book folder). for that book, transferring the mobi without conversion resulting in a document file on the fire, converting it (mobi-mobi) and sending the updated mobi to the fire resulted in a book file.

for someone who is using the check to figure out why a mobi file won't transfer to the fire as a book (or won't sync on a kindle keyboard), the plugin should show the file as one that needs fixing/updating or at least reviewing.

[kiwidude]

Originally Posted by nynaevelan

I do have a question for you, is there a way to add an option of adding EBOK checks to ignore so that they do not repeatedly show up in the results as problems? For example, I have PDOC and EBSP types, they are correct as they are but they keep showing up as problem files.

So you are saying you have docs which are NOT of type EBOK, but you don't want to change them, right?

Just run the check, select the books you want to not see again and use the "Exclude from check..." option