[GUI Plugin] Quality Check

[w00dent0p]

Hi, I'm running into an issue with unsmartened punctuation in some books flagged by Quality Check, always in the nav.xhtml file in each book. When I try to edit any of these books and run 'Smarten punctuation', I get 'No punctuation that could be smartened found'.

Any ideas? Perhaps nav.xhtml should be excluded from this check? Seems like it's somehow a special case.

Thanks.

[kiwidude]

Originally Posted by w00dent0p

Hi, I'm running into an issue with unsmartened punctuation in some books flagged by Quality Check, always in the nav.xhtml file in each book. When I try to edit any of these books and run 'Smarten punctuation', I get 'No punctuation that could be smartened found'.

Any ideas? Perhaps nav.xhtml should be excluded from this check? Seems like it's somehow a special case.

Thanks.

If you PM me a link to one of such books I can take a look. I wouldn't be surprised at all about the calibre book editor having different "rules" about punctuation - it didn't exist when I wrote this plugin.

[kiwidude]

Release Notes:
https://github.com/kiwidude68/calibr..._check-v1.13.2

Thanks to w00dent0p for reporting this issue.

[JSWolf]

Originally Posted by elPedr0

Thanks for the reply JSWolf.

Is there any material risk associated with using Modify ePub to set ePubs to UTF-8? Or can I safely apply it to my whole catalog of ePubs - thereby sidestepping the need to identify which ePubs require the modification?

There is no risk at all.

[w00dent0p]

Originally Posted by kiwidude

Release Notes:
https://github.com/kiwidude68/calibr..._check-v1.13.2

Thanks to w00dent0p for reporting this issue.

Thank you very much. All my previously failing books now pass this check.

[momus]

Hi, from version 1.13.1+ I have problem with "Fix ASIN for kindle fire". Last version that works is 1.13.0.

calibre, version 6.9.0
Error: Nieznany wyjątek: <b>ValueError</b>:unsupported format character 'k' (0x6b) at index 2

calibre 6.9 embedded-python: True
Windows-10-10.0.19044-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.19044')
Python 3.10.1
Windows: ('10', '10.0.19044', 'SP0', 'Multiprocessor Free')
Interface language: pl
Successfully initialized third party plugins: DeACSM (0, 0, 16) && Gather KFX-ZIP (from KFX Input) (1, 50, 0) && DeDRM (10, 0, 3) && Package KFX (from KFX Input) (1, 50, 0) && Goodreads (1, 7, 1) && Hyphenate This! (0, 1, 3) && KFX metadata reader (from KFX Input) (1, 50, 0) && KFX Input (1, 50, 0) && Set KFX metadata (from KFX Output) (1, 65, 0) && KFX Output (1, 65, 0) && KindleUnpack - The Plugin (0, 83, 1) && LubimyCzytac (2, 2, 28) && Quality Check (1, 13, 1)
Traceback (most recent call last):
File "calibre_plugins.quality_check.action", line 193, in perform_check
File "calibre_plugins.quality_check.check_fix", line 44, in perform_check
File "calibre_plugins.quality_check.check_fix", line 362, in fix_mobi_asin
ValueError: unsupported format character 'k' (0x6b) at index 2

[kiwidude]

@momus - looks like a problem by the translator. You are using Polish translations right?

[kiwidude]

Release Notes:
https://github.com/kiwidude68/calibr..._check-v1.13.3

This should fix the Polish translation issue reported by momus

[momus]

Originally Posted by kiwidude

Release Notes:
https://github.com/kiwidude68/calibr..._check-v1.13.3

This should fix the Polish translation issue reported by momus

Thanks, works like a charm.

[ownedbycats]

When running various checks, one fanfic with a comically long name results in the dialog stretching out and going halfway off the screen. Is this something fixable on QC's end with some truncation, or is it a Calibre thing?

[JSWolf]

I've found an issue with the Quality Check's search. It doesn't work when I try to search for a.m. or p.m. It does find books that have a.m. or p.m., but it also find a lot of books that don't. I've tried using plain text and regex and it fails. What's needed is an exact text search.

Can this be added in so these searches work properly? Thanks.

[ownedbycats]

SmartEject had to update the default search query after the Calibre update that changed how puncuation works in searching, so could it be something like that?

[JSWolf]

Originally Posted by ownedbycats

SmartEject had to update the default search query after the Calibre update that changed how puncuation works in searching, so could it be something like that?

If that is the reason why QC is now broken, what's the workaround to put in the search for a.m. or p.m.?

[ownedbycats]

does "~a\.m\." work? I got zero results so not sure if failure or not having it.

[JSWolf]

Originally Posted by ownedbycats

does "~a\.m\." work? I got zero results so not sure if failure or not having it.

Failed for me as well. I wish this search change in Calibre would be undone.

There are too many people who want a change that causes more problems then it's worth and this is one of them.