View Single Post
Old 12-22-2012, 12:00 AM   #329
kiwidude
calibre/Sigil Developer
kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.
 
Posts: 4,228
Karma: 1334002
Join Date: Oct 2010
Location: London, UK
Device: Kindle Paperwhite 3G, iPad 3, iPad Air
@Needlehawk - no, that metadata.opf file you find in your calibre folder is nothing to do with the internal metadata manipulated by this plugin for an epub. That opf file is primarily a *backup* of the data stored in your calibre database for your book, in order to facilitate an emergency restore of your library data should the original metadata.db database become corrupted.

Inside an epub file (if you unzip it) you will find a .opf file which contains the actual metadata used by the epub readers. It is that internal .opf file that this plugin manipulates.

As for removing non DC: metadata, it is an option really only targeted at a small subset of users who are sharing/publishing their epubs externally and require all traces of application specific metadata such as from calibre or Sigil removed.
kiwidude is offline   Reply With Quote