06-17-2013, 06:45 PM | #451 |
Well trained by Cats
Posts: 29,784
Karma: 54830978
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
Now I see where you are going
Code:
# Save original file when converting/polishing from same format to same format |
06-26-2013, 03:37 AM | #452 |
Groupie
Posts: 164
Karma: 3100
Join Date: Sep 2011
Device: Kobo Auro H2O, PRS-T1
|
I've just edited some of my custom columns in one library. I wanted to copy the epubs to a different library that may have the epub already, but the metadata I edited reverts back to the original metadata.
I have automerge set to overwrite exsisting duplicate formats. I tried using this plugin (Modify epub), checking Update metadata. I tried using the Polish feature, checking: update metadata in the book files, update the cover in the book files, add metadata as a 'book jacket' page. However, when I tried to copy the book to the new library, none of the edited metadata stuck. Am I missing something? How do I get metadata from custom columns to stick to the book when I copy it to a different library? |
06-26-2013, 07:43 AM | #453 | |
null operator (he/him)
Posts: 20,557
Karma: 26954694
Join Date: Mar 2012
Location: Sydney Australia
Device: none
|
Quote:
I hope I'm wrong because it's something I'd like to able to do too BR |
|
06-27-2013, 01:03 PM | #454 | |
Plugin Developer
Posts: 6,307
Karma: 3966249
Join Date: Dec 2011
Location: Midwest USA
Device: Kindle Paperwhite(10th)
|
Quote:
I believe calibre tucks copies of all columns and metadata inside the epub in some non-standard tags. |
|
06-27-2013, 01:22 PM | #455 | |
Well trained by Cats
Posts: 29,784
Karma: 54830978
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
Quote:
If you have created the destination using with the using Copy Structure from the current (assumes you will use it as the source ), Calibre will do everything. If you manually created or have modified the other Library: you will need to bring the field structure into synch by hand. NOTE: Custom columns containing 'Fixed values'. The destination needs to include ALL values used in the source table . |
|
06-27-2013, 08:33 PM | #456 | |
null operator (he/him)
Posts: 20,557
Karma: 26954694
Join Date: Mar 2012
Location: Sydney Australia
Device: none
|
Quote:
They are in the metadata.opf file in the book folder, they're 'tucked away' as entries of the form <meta name="calibre:user_metadata:#columnname".... I think the content of the embedded metadata is defined by conventions/standards, see Wiki link in my previous post. But maybe there could be something that would allow one to put custom columns into the 'book jacket' - maybe something like Generate Cover. BR Last edited by BetterRed; 06-27-2013 at 08:46 PM. |
|
07-06-2013, 02:54 AM | #457 | |
null operator (he/him)
Posts: 20,557
Karma: 26954694
Join Date: Mar 2012
Location: Sydney Australia
Device: none
|
Quote:
I prefer that the jacket be at the back of the book, so I changed the Add/Replace code to do that. However, I also prefer to be using factory code, so could an option be added to position the jacket at the back of the book, rather than after the 'titlepage'. Thanks BR |
|
07-26-2013, 04:40 PM | #458 | |
Wizard
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
|
Old feature, new user...
Quote:
Also, bug report: the "convert HTML to UTF-8" option produces HTML files without byte order marks. (EDIT: This seems to be an artifact of going through Calibre 0.9.40's repacking routine.) Another useful feature would be a more general TOC fixer, which could:
Last edited by Rev. Bob; 07-26-2013 at 07:20 PM. |
|
07-26-2013, 04:51 PM | #459 |
Well trained by Cats
Posts: 29,784
Karma: 54830978
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
@Rev Bob
Have you tried the 'Edit ToC' PI . Sometimes, just opening and saving claens things up. Extra line feeds in the code area is a cosmetic the normal reader does not see. |
07-26-2013, 05:04 PM | #460 | ||
Wizard
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
|
Quote:
Quote:
|
||
07-26-2013, 05:18 PM | #461 |
Grand Sorcerer
Posts: 6,208
Karma: 16534692
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
I wasn't aware that the calibre TOC Editor added any metadata. It's the ncx file being edited, not the opf file, isn't it? Can you give an example of what you mean by "dirtied up"?
|
07-26-2013, 05:23 PM | #462 | |
Wizard
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
|
Quote:
EDIT: As for an example, I just added an EPUB into my Calibre library, did nothing to it, and used Save to Disk to make a copy. It made the following OPF changes that I consider "dirtying it up":
Last edited by Rev. Bob; 07-26-2013 at 05:48 PM. |
|
07-26-2013, 06:08 PM | #463 | |
Grand Sorcerer
Posts: 6,208
Karma: 16534692
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
|
|
07-26-2013, 06:26 PM | #464 | |
Wizard
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
|
Quote:
Yes, granted, setting up the context menu option was a bit of a hassle, but once that was done... EDIT: Inspecting the Calibre version of the above example in place, I do find that the OPF is intact there; it's even still a true UTF-8 file. However, the "open and save the TOC in Calibre's editor" recommendation resulted in a broken TOC, in that the dtb:depth had been improperly changed from 2 to 3. In addition, the !DOCTYPE had been removed, Calibre had added itself in as a new dtb:generator element, and (oddly) the content and name attributes of the meta elements had switched places, which serves no purpose beyond making the data hard to decipher. The only reason I can imagine why that should happen is that the parser is mindlessly alphabetizing attributes, which is a bad idea in this context. Further, looking at the actual navPoint elements, all of the perfectly good, logical ID values (like "copy" for the copyright page, "intro" for the introduction, "pt03" for Part 3, "ch05" for Chapter 5, et al.) had been replaced with mile-long UUID values. That is in no way the "minimal change" level that I'm after; I want a process that does exactly what it's told - no more, and no less. Last edited by Rev. Bob; 07-26-2013 at 06:51 PM. |
|
07-29-2013, 05:26 AM | #465 | |
Addict
Posts: 254
Karma: 69786
Join Date: May 2006
Location: Oslo, Norway
Device: Kobo Aura, Sony PRS-650
|
Quote:
|
|
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 |