[GUI Plugin] Quality Check

[theducks]

Originally Posted by johnelle

I experimented with this plugin a little but it seems like you have to become an expert in ebook formats to understand how to use it effectively. I read through the first 100 replies or so but I didn't encounter much "check for <this> and then correct with <that>" instruction.

Would be really helpful if somebody had a little crib sheet of checks with corrections with a brief explanation. Even a "top 10" would be helpful.

Any takers?

Did you click Help in the Quality check icon menu?

[darrenmcg]

I asked about this in the main Calibre forum, but thought it might me more useful here... I don't suppose a function to clean the formatting in the metadata comments section could be implimented?

Currently I clear all formatting but I'm usually left with something like:
<p class="description">blah,blah,blah</p>
or:
<p>blah,blah,blah</p>
I'd like to get rid of all that and just have:
blah,blah,blah

I'm trying to have a "clean" <dc:description> in the epubs content.opf file and Clibre's comments section.

[theducks]

Originally Posted by darrenmcg

I asked about this in the main Calibre forum, but thought it might me more useful here... I don't suppose a function to clean the formatting in the metadata comments section could be implimented?

Currently I clear all formatting but I'm usually left with something like:
<p class="description">blah,blah,blah</p>
or:
<p>blah,blah,blah</p>
I'd like to get rid of all that and just have:
blah,blah,blah

I'm trying to have a "clean" <dc:description> in the epubs content.opf file and Clibre's comments section.

You are trying to remove HTML from the comments part of the OPF?

Calibre can already 'Remove formatting' in the Metadata Comments in the Library. (Only available in single book MDE mode)
Once that is done. You Polish to get the Book updated

Modify EPUB can clean non-DC metadata

[JSWolf]

Originally Posted by theducks

You are trying to remove HTML from the comments part of the OPF?

Calibre can already 'Remove formatting' in the Metadata Comments in the Library. (Only available in single book MDE mode)
Once that is done. You Polish to get the Book updated

Modify EPUB can clean non-DC metadata

But if you clean out the non-DC metadata you clean out the cover metadata that some programs need to know about the cover. So that's a rather bad idea to use that option.

[eschwartz]

Modify EPUB is irrelevant. It uses calibre to embed metadata, and draws on the book record's "comments" field.

dc:description is a DC element.

...

The OP is correct that there is currently no way to do what he wants.

What is needed is some way to modify the contents of the "comments" field. See this thread for reference: https://www.mobileread.com/forums/sho...d.php?t=268119

[theducks]

Originally Posted by JSWolf

But if you clean out the non-DC metadata you clean out the cover metadata that some programs need to know about the cover. So that's a rather bad idea to use that option.

Any person who wants to remove all traces of anything not pure cares less about those unclean devices.

[darrenmcg]

I've managed to find a solution to cleanup the comments. Thanks.

[PiotrK]

Can I make a feature request here? If not here, then how?

Please add joint MOBI file detection (e.g. files which contains both MOBI6 and MOBI8). Such files are problematic because calibre can't reliably change metadata. See https://bugs.launchpad.net/calibre/+bug/1532161 for details / example of such file. Kovid Goyal suggested this FR.

Thanks.

[lousi]

I'm very sad to find this plugin does not work with calibre 2.49(64bit). Nothing found. it works well till 2.48.

[davidfor]

Originally Posted by lousi

I'm very sad to find this plugin does not work with calibre 2.49(64bit). Nothing found. it works well till 2.48.

I don't use the plugin much, but I just tried a few checks and they all worked.

What didn't work for you?

[theducks]

I will confirm: (for the following) W10x64
Page count: Adobe

Readability:
Flesch-Kincaid
Gunning Fox

Other:
Estimate Page/Word
Always overwrite

[edeniz]

Question, because something confuses me:

What could be the reason if the plugin doesn't find the searched-for term in the epub?

For example, it's happened some time ago, that a searched-for text inside the epub body was not found, so I thought it maybe wasn't in any of the books in my library, but I found what I was looking for at a later date by sheer coincidence. It wasn't even like there were some special irregular, non-ASCII characters or some such in the text I was looking for.

Similarly, today I thought to do a search to find this in my epub:

Spoiler:

</td></tr></tbody></p>

and while there should have been at least one epub with it, the search returned empty. So, yeah, I'm confused. Something obvious I'm missing?

I realize this description may be far too vague. If so, sorry. But the point is, I have no idea what the criteria are that could cause the plugin to not recognize a search, and I have not found anything about it in the help file, so maybe someone could point me in the right direction?

[theducks]

Originally Posted by edeniz

Question, because something confuses me:

What could be the reason if the plugin doesn't find the searched-for term in the epub?

For example, it's happened some time ago, that a searched-for text inside the epub body was not found, so I thought it maybe wasn't in any of the books in my library, but I found what I was looking for at a later date by sheer coincidence. It wasn't even like there were some special irregular, non-ASCII characters or some such in the text I was looking for.

Similarly, today I thought to do a search to find this in my epub:

Spoiler:

</td></tr></tbody></p>

and while there should have been at least one epub with it, the search returned empty. So, yeah, I'm confused. Something obvious I'm missing?

I realize this description may be far too vague. If so, sorry. But the point is, I have no idea what the criteria are that could cause the plugin to not recognize a search, and I have not found anything about it in the help file, so maybe someone could point me in the right direction?

I don't believe the PI does REGEX because that might be what you need)
the \s* allows for 'pretty' (indented/multiline) coding
But ???
why not search for JUST </table> and avoid the multi-line issue?

I assume that you want to edit books that HAVE tables

</td>\s*</tr>\s*</tbody>\s*</p>

[edeniz]

Originally Posted by theducks

I don't believe the PI does REGEX because that might be what you need)
the \s* allows for 'pretty' (indented/multiline) coding
But ???
why not search for JUST </table> and avoid the multi-line issue?

I assume that you want to edit books that HAVE tables

</td>\s*</tr>\s*</tbody>\s*</p>

Yeah, no, I don't think it does regex either, which is half the problem. But the thing is, that line? is not a multiline. It's a single line, that is present in the ebook in exactly the form I've written it down. I can't just look for </table>, because I have a lot of books that have multiple tables in them, and I am looking for a specific few ones. Actually, the line I was looking for is far longer, but as regex won't work, the bit I mentioned is basically the only thing I can search without getting too many false positives, so to say. But having nevertheless tried that too, as well as <table>, I can honestly say even that search turns up negative.

Also, that doesn't explain why utterly normal text (well, normal aside from the fact that it is inside a table, come to think of it) will not be found by the plugin either.

There has to be a reason, so if there are reasons, like say, tables are inherently unsearchable or something, I'd like to know for future reference.

[DaltonST]

Yeah, no, I don't think it does regex either, which is half the problem.

@edeniz:

You can use the Multi-Column Search plug-in to do full-text searches (using regular expressions) on selected epubs after converting them to .txt files, but still with the original html tags. Pandoc can do that.

See the attached example which includes the explanatory ToolTips.


DaltonST