Quote:
Originally Posted by kiwidude
Yeah I've mentioned that as a possibility previously. However the biggest problem is not so much adding another UI option for running multiple checks so much as presenting the results in a meaningful way.
Think about the issues involved - lets say you select 10 books and run 5 checks against them, and get all sorts of permutations of issues with those books. How on earth are you going to clean them up in a meaningful way knowing what was wrong with each book? At its crudest it would have to be a log file listing by book all the things found wrong with it perhaps (and the search shown at the end are all the books that had "something" wrong). That leaves the onus on the user to copy that log text to notepad and have it open side by side while they go through and fix stuff, selecting different combinations of books manually if they are using Modify ePub to do so. It's a bit icky really.
However there is no doubt that if you have a certain "set" of checks that you think are appropriate for your library, and you want to sanity check either your whole library or books added since a certain date every now and then, that being able to bulk run like this would be less painful than individually running them all. So it will happen one day, it just needs some thought on how it should work.
|
Well, what I think is to run whatever is selected against each book and then if any issue is found, present it to the user for that one book. Then when that is over, move on until the next book has an error. That would do in the short term until a better way can be figured out.
Quote:
|
Well... not really. QC still ran to completion didn't it? It has just told you that you have a badly formed epub with the opf file inside it.
|
Sure, the ePub in question may have some file that's not UTF-8, but to the user, it looks like it's crashed. The OPF & CSS were encoded in ANSI and when I converted them to UTF-8 without BOM, the crash stopped. Another check you can add in is for proper UTF-8 without BOM encoding. Also, to not have it blow up on ANSI.