Quote:
Originally Posted by theducks
NO
The Metadata update comes from the Library, if it is the same, you see no change.
|
I should have made it clear that it happens when importing an epub.
I viewed the original epub content.opf description entry and it was plain text with blank lines between paras. When Calibre imported it the text it was changed to multiple <p class="description"> elements, using the blank lines to delimit the paras, and the <p> elements were wrapped in a <div> element.
I edited the file to remove the <div> elements and re-imported the epub. This time Calibre combined the <p> elements with a <br> element.
I have also seen Calibre wrap multiple<p> elements with a <div> element when editing the description using the metadata editor in Calibre.
Quote:
Originally Posted by eschwartz
I have noticed that calibre adds a div around the comments metadata if there is certain types of html in it, which I assume is because of sanitizing. If calibre does it I trust there is a good reason.
|
I can't think of any good reason to wrap using a <div> element.
The OPF spec doesn't state any specific requirements, and there is nothing in the HTML spec that would require it either.
Neither can I think of a good reason to specify a class attribute on the <p> element. The class attribute is useless without an entry in an associated CSS file, and there doesn't seem to be anything in the OPF spec to allow a CSS file to be provided for the .opf file.