02-22-2013, 05:25 PM | #391 | |
Well trained by Cats
Posts: 29,952
Karma: 55705602
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
Quote:
I suspect GiGo . The PI only changes what it was told and does not validate the rest. |
|
02-22-2013, 05:44 PM | #392 |
Resident Curmudgeon
Posts: 74,563
Karma: 129670952
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
I've used Modify ePub extensively and find it works very well. Next time you have a problem, take the ePub (the one before the plugin was used) and validate it with ePubcheck and see what errors there are. Fix the errors and then when it validates, run the plugin again and see what happens.
|
Advert | |
|
02-22-2013, 10:28 PM | #393 |
Guru
Posts: 771
Karma: 6528026
Join Date: Sep 2012
Device: Kobo Elipsa
|
<I've used Modify ePub extensively and find it works very well. Next time you have a problem, take the ePub (the one before the plugin was used) and validate it with ePubcheck and see what errors there are. Fix the errors and then when it validates, run the plugin again and see what happens.>
Thanks, that's a good idea. I'll validate it with ePub Check, fix the errors, and run it through Modify ePub. If I see the problem pop up after that, I'll compare the OPFs. That gives me several things to try. Thanks to everyone who made suggestions. |
03-01-2013, 02:20 PM | #394 |
Tech appreciator
Posts: 23
Karma: 10
Join Date: Jul 2012
Device: Onyx Boox Kepler Pro (wow I love this reader!)
|
I've had the same difficulty that icallaci describes with the plugin, but went a little further in trying to figure out how to work around it. I was able to isolate the result to the "Update Metadata" option. For files that will experience the problem, running the plugin with that option checked will cause the opf to fail and Sigil will create a new one in alpha order. If I re-do the process with the same book, and leave that option unchecked, the resulting opf will be acceptable.
Kiwidude - I have pm'd you links to before and after versions of a file that experienced this. Didn't want to post publicly. Last edited by Barb-B; 03-01-2013 at 02:31 PM. |
03-01-2013, 09:04 PM | #395 | |
Resident Curmudgeon
Posts: 74,563
Karma: 129670952
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
Advert | |
|
03-02-2013, 03:40 AM | #396 |
Tech appreciator
Posts: 23
Karma: 10
Join Date: Jul 2012
Device: Onyx Boox Kepler Pro (wow I love this reader!)
|
I was unable to get 3.0 working on my machine set up as it is, and got tired of futzing around with it. However, was able to use an older version that some nice local folks had put into a GUI wrapper - and it did pass that with no errors.
Oops! (later edit) I just realized I slightly misread your question. The original version of the file passed with no errors. After running through the Modify Epub plugin, the after version produced the following errors: date value '0101-01-01T00:00:00+00:00' is not valid, YYYY[-MM[-DD]] expected unfinished element unique-identifier attribute in package element must reference an existing identifier element id Last edited by Barb-B; 03-02-2013 at 02:12 PM. Reason: additional info |
03-02-2013, 12:16 PM | #397 |
Guru
Posts: 771
Karma: 6528026
Join Date: Sep 2012
Device: Kobo Elipsa
|
Barb B -- Thank you, thank you, thank you!
|
03-02-2013, 09:48 PM | #398 |
Calibre Plugins Developer
Posts: 4,647
Karma: 2162064
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
|
Barb B - I just dragged the epub you sent into calibre, ticked *only* the update metadata option in Modify ePub, and it all works perfectly fine.
As you say in the ePub the date field in that metadata looks a bit screwed up. I would suspect that this comes somehow from the metadata associated with the book as it exists in your calibre library. In my updated ePub this has: Code:
<dc:date>2011-09-26T14:00:00+00:00</dc:date> Try that save to disk and see if you get the result I predicted. Also make sure you are only checking the Update metadata option, in case in fact it is some other option that is somehow disrupting the data. |
03-03-2013, 11:11 AM | #399 |
Guru
Posts: 771
Karma: 6528026
Join Date: Sep 2012
Device: Kobo Elipsa
|
It seems to happen randomly for me, which is why I am having so much trouble tracking it down. The last time it happened (when I posted to ask about it), I reimported the original epub and ran it through Modify ePub, ticking just one box each time, and had no problems. It's not a big deal for me to check the order of files against the original, since it happens so rarely, but it would be nice to figure it out.
|
03-03-2013, 02:19 PM | #400 | |
Tech appreciator
Posts: 23
Karma: 10
Join Date: Jul 2012
Device: Onyx Boox Kepler Pro (wow I love this reader!)
|
Quote:
Remove calibre bookmark files Remove unused image files Remove Adobe .xpgt files and links Remove Adobe resource DRM meta tags Encode HTML in UTF-8 Remove all metadata jackets Remove legacy metadata jackets Remove broken image pages Remove non dc: metadata elements After running these others, and using the Calibre Save to Disk feature, the saved files don't exhibit any trouble with their opf's. Since I care less about the "Update metadata" option than any of the others, I'd just as soon let it go, and get the other results that matter to me. Hope that's helpful if you want to continue pursuing this issue. I'm perfectly happy to continue working around it. Either way, it's still a fantastic tool, and much appreciated! |
|
03-03-2013, 07:17 PM | #401 |
Calibre Plugins Developer
Posts: 4,647
Karma: 2162064
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
|
Barb-B - ok, I think I know what is happening. On my calibre I have read file metadata turned on when adding books, and I am betting you do not. So when I add to calibre, the date field calibre uses to put into the opf file is set, however I am betting you have not updated the metadata for the book, and hence that is why it is storing an invalid date in there.
This is not a bug in Modify ePub, it is really a flaw in calibre in my opinion, though Kovid may not see it that way, either that or Sigil should handle it better. As I predicted above this is the same behaviour you will see if you use the calibre Save to Disk feature to export the book, you get exactly the same "invalid" epub resulting. So... I suggest you raise a bug request for calibre for Kovid and that way it will be fixed for all scenarios, he just needs to store a better "null date" than his current approach I believe. Of course if he disagrees then you should raise a bug request to Sigil, and ask the devs to handle that date value more effectively. Though the fact that epubcheck shows it as an error would indicate to me at least that really calibre should not be putting such a date value in there. So for the record, the issue is occurring when the original book has this in the opf: Code:
<dc:date opf:event="publication">2011-09-27</dc:date> Code:
<dc:date>0101-01-01T00:00:00+00:00</dc:date> |
03-03-2013, 09:48 PM | #402 |
creator of calibre
Posts: 43,999
Karma: 22669822
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
|
<dc:date>0101-01-01T00:00:00+00:00</dc:date> is a perfectly valid date as per the EPUB spec. If epubcheck is complaining about it, epubcheck is, as usual, wrong. http://idpf.org/epub/20/spec/OPF_2.0...m#Section2.2.7
|
03-03-2013, 09:56 PM | #403 | |
Resident Curmudgeon
Posts: 74,563
Karma: 129670952
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
03-03-2013, 10:06 PM | #404 | |
Resident Curmudgeon
Posts: 74,563
Karma: 129670952
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
03-03-2013, 11:11 PM | #405 |
Calibre Plugins Developer
Posts: 4,647
Karma: 2162064
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
|
@JSWolf - well to be fair to Barb-B, she doesn't really care what epubcheck says, she just wants to be open the book in Sigil after doing a metadata update without having the opf corrupted. It was you that asked her to try the epubcheck route
Thanks for the reply Kovid. Given you have checked the spec and what calibre generates is correct, then that would appear to only leave Sigil as the culprit. I will drop an email to the other (i.e. active) Sigil devs and see what they have to say about it. Certainly since I see the exact same behaviour from a simple Save to Disk operation from calibre I don't feel there is anything that needs to be changed in the Modify ePub plugin concerning it. |
Tags |
modify epub |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[GUI Plugin] Quality Check | kiwidude | Plugins | 1184 | 04-17-2024 06:17 PM |
[GUI Plugin] Open With | kiwidude | Plugins | 403 | 04-01-2024 08:39 AM |
[GUI Plugin] Manage Series | kiwidude | Plugins | 166 | 02-13-2024 11:31 AM |
Modify ePub plugin dev thread | kiwidude | Development | 346 | 09-02-2013 05:14 PM |
[GUI Plugin] Plugin Updater **Deprecated** | kiwidude | Plugins | 159 | 06-19-2011 12:27 PM |