Thread: Why not a metadata editor sigil-style?
View Single Post
Old 07-16-2018, 07:56 AM   #4
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Sam Sahara View Post
It shouldn't has to be a duplication. The metadata editor should has to manage the Dublin Core metadata element set (the full set) into the "dc:" tags of the "content.opf" file.
But, that is what the metadata editor is doing. It just isn't doing it directly to the book. It is doing it in the calibre library. Calibre will then update the book with the metadata at various times, some automatically, and some when you trigger it. The ways I can think of are: Embed metadata, Polish books, conversion, Modify ePub plugin, send to device, save to disk and opening the editor. That makes a metadata editor in the editor a lot less necessary than it is in a stand-alone tool like Sigil.
davidfor is offline   Reply With Quote