Quote:
Originally Posted by Milica Who
I checked that box before I even attempted to download metadata, and the problem I had with xml tags was still present. Believe me I tried everything before I posted the question, and so far only the plug-in worked...Just now I tried it on a book that already came with its own metadata, but also with those problematic xml tags in content.opf. And the plug-in worked on that book, too.
|
Quote:
Originally Posted by Milica Who
In HTML source of metadata they don't...aside from <p class="description">, they still have for example <div> for paragraphs and <br> for line breaks. The problem was that Calibre translated < and > into < and > respectively in the content.opf which should have no tags at all. With plug-in that doesn't happen - there's no <p class="description">, <div> and <br> tags in the description section of content.opf, you just have bare text but separated in paragraphs following the <div> tag pattern of the HTML source. The same goes for line breaks.
|
@
Milica - if calibre isn't removing
all the markup in your downloaded Comments when the setting is checked then IMO that's a defect that should be rectified. Perhaps you could report the issue at
Bugs : calibre with details of a book and metadata source that has the problem.
I did a spot check on one book and the result was fine - the dc:description was free of any HTML markup. I don't use the metadata download feature much, what's more I normally have Comments unchecked.
BTW - I am not suggesting that the setting obviates the need for Terisa's plugin, in fact I've suggested it be made a registered plugin.
BR