05-21-2012, 08:26 AM | #481 | ||
Calibre Plugins Developer
Posts: 4,637
Karma: 2162064
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
|
Quote:
And while there are times where you might work book by book, there are other users/times where doing the fix in bulk makes sense across a batch of books. After all it is easier to select a bunch of books and use modify ePub once against them with the common settings checked, than it is to book by book do various combinations. It may be that the ultimate solution is going to have to involve another window (modeless), allowing the user to view the results in various ways such as by issue or by book etc. I've been trying to avoid doing that for various reasons but it might be the most appropriate solution here. In Find Duplicates I took the approach of using highlighting groups, but that had the advantage of the context being identical between and across groups. Another possibility would be to store the data about what is wrong with a book in the database with that book, but a user would still need to choose a menu item to actually see that info which is a bit clumsy to use. So my gut feel at the moment is that some sort of navigational window allowing the filtering of results in various ways and displaying of the associated log data for that result set is going to be the way to go. But alternative ideas welcomed... Quote:
There is however probably something I can do with the xml parser to have it avoid that error situation, which I will experiment with. Thanks for posting the exact details of what triggered it/solved it. As for having a check for UTF-8 without BOM, I'm not quite sure how feasible that is. From what I know and have googled in the past, it isn't possible to tell from a file what encoding it actually has. You can attempt to open it (like with an xml parser) and see if it errors (like has happened here) but I'm not sure what else you can do to identify it. Perhaps Kovid or someone may have a suggestion... |
||
05-21-2012, 09:33 AM | #482 | |
Resident Curmudgeon
Posts: 74,188
Karma: 129333564
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
05-21-2012, 12:35 PM | #483 |
Grand Sorcerer
Posts: 27,561
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
|
05-21-2012, 05:23 PM | #484 |
Resident Curmudgeon
Posts: 74,188
Karma: 129333564
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
But I've not seen it get UTF-8 without BOM wrong. So at least that code is working properly. And if you say there are issues determining the encoding, then the puglin should stop as maybe it could get it wrong (non-UTF-8).
|
05-31-2012, 01:24 PM | #485 |
Addict
Posts: 378
Karma: 3102
Join Date: Dec 2010
Location: EU
Device: Kobo Aura ONE, Kobo Libra H20
|
SVG Covers
@kiwidude
Did you ever implement checking for SVG covers in the calibre generated titlepage.xhtml? I'd love to update all my ePubs to have an SVG cover. Many thanks ! |
05-31-2012, 03:10 PM | #486 |
Resident Curmudgeon
Posts: 74,188
Karma: 129333564
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
I cannot seem to find an option to check for broken links. I see options for checking broken image and ToC links. Also, does checking for broken ToC links get the ncx and the internal ToC? If it only does the ncx file, then a rename of the option is in order.
Last edited by JSWolf; 05-31-2012 at 04:27 PM. |
05-31-2012, 03:48 PM | #487 |
Calibre Plugins Developer
Posts: 4,637
Karma: 2162064
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
|
@paulfiera - no, obviously not yet. Thousands of lines of code related to Modify ePub has soaked up most of the last few weeks, and there have also been multiple releases of Count Pages, Generate Cover, & Reading List. Then add to that Extract ISBN got broken with calibre 0.8.53... oh yeah, I do have a day job too...
@JSWolf - correct, there is no option for general broken link checking. With recent releases of this plugin I have started tumbling down the slippery slope of all sorts of potential internal ePub content validation. My initial additions to this plugin were focused around things that calibre had responsibility for breaking (until recent fixes), like broken image links and broken NCX links. Having opened the door a crack with those, it is not unreasonable to consider other things eventually. Of course it is pretty much replicating some of FlightCrew validation, the difference being that this plugin would allow you the 50,000 foot view of which books have issues across your library, that you can then open in isolation to fix. As for the TOC/NCX naming, that was deliberate on my part for historical consistency but it is a fair point. The issue is that the very first option I had for QC was "Check TOC with < 3 entries". That was named that way so as to not bamboozle users with the term NCX, as I would suggest only a very small subset of users would understand what an NCX is. However you are 100% technically correct that all three of those options should state NCX. Perhaps a good compromise is "Check NCX TOC with < 3 entries", and then if we ever have checks related to an inline TOC we say "Check inline TOC ..." Oh look, 3000 posts... |
05-31-2012, 04:11 PM | #488 | |
Well trained by Cats
Posts: 29,836
Karma: 54837878
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
Quote:
Wishing for Cake, It would be nice if it returned a Count of errors (that I coud save in a custom column) so I could prioritize repairs |
|
05-31-2012, 04:31 PM | #489 | |
Resident Curmudgeon
Posts: 74,188
Karma: 129333564
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
As for the TOC/NCX naming, that was deliberate on my part for historical consistency but it is a fair point. The issue is that the very first option I had for QC was "Check TOC with < 3 entries". That was named that way so as to not bamboozle users with the term NCX, as I would suggest only a very small subset of users would understand what an NCX is. However you are 100% technically correct that all three of those options should state NCX. Perhaps a good compromise is "Check NCX TOC with < 3 entries", and then if we ever have checks related to an inline TOC we say "Check inline TOC ..." Oh look, 3000 posts...[/QUOTE] I agree to renaming the remaining ncx checks (if you implement my suggestion above) to NCX ToC. |
|
05-31-2012, 05:03 PM | #490 |
Resident Curmudgeon
Posts: 74,188
Karma: 129333564
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
I've noticed one other thing left out that's a constant issue especially with a lot of publisher ePub. Incorrect guide types. A lot of guide entries are made with invalid types.
|
05-31-2012, 06:44 PM | #491 |
Well trained by Cats
Posts: 29,836
Karma: 54837878
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
IMHO this is flightcrews realm. to flag incorrect use, when the proper way is to precede with other. (took me a bit to realize I needed the dot ) .
|
05-31-2012, 08:57 PM | #492 |
Resident Curmudgeon
Posts: 74,188
Karma: 129333564
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
|
05-31-2012, 09:21 PM | #493 |
Well trained by Cats
Posts: 29,836
Karma: 54837878
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
but many are just superficial (yellow items) in Flight crew.
Flight crew could care less if there are 3 or 30 TOC items, as long as they are done correctly so there is only a few that really point to a malformed EPUB... That is no good reason to proliferate the overlap. BTW I am in favor of a fully populated NCX, not just that which is needed to pass the check. |
06-01-2012, 10:25 AM | #494 |
Member
Posts: 17
Karma: 10
Join Date: Sep 2010
Location: Texas
Device: Kindle 3
|
Does the ASIN Check look at EXTH 113, 504 or both? Is there a way to designate which on is checked as I have been editting with mobi meta editor and putting matching numbers from Amazon in both as I go along. I would like to be able to do more edits as I have free time than just for books I am fixing to put on my Fire. Is there a way to add a quick fix that would make 113 and 504 the same? Also, can the ASIN be extracted directly from Amazon Kindle versions in the metadata editor rather than or in conjunction with the ISBN number?
|
06-01-2012, 10:45 AM | #495 |
Zealot
Posts: 125
Karma: 769546
Join Date: May 2012
Device: none
|
Nice job, I am working on a web app that will search the internet based on a photo or image and find a person using the data in it. It would be nice to be able to do the same thing with cover data from a book, but harder to accomplish in the end.
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[GUI Plugin] Clipboard Search | kiwidude | Plugins | 29 | 04-02-2024 10:05 PM |
[GUI Plugin] Search the Internet | kiwidude | Plugins | 433 | 04-01-2024 05:48 PM |
[GUI Plugin] Open With | kiwidude | Plugins | 403 | 04-01-2024 08:39 AM |
[GUI Plugin] Kindle Collections (old) | meme | Plugins | 2070 | 08-11-2014 12:02 AM |
[GUI Plugin] Book Sync **Deprecated** | kiwidude | Plugins | 111 | 06-07-2011 07:47 PM |