Quote:
Originally Posted by kovidgoyal
If you do want to implement this, I woudl instead suggest making a plugin like the open with plugin that opens your external editor of choice with the contents of the custom column and updates the column when the editor exits.
|
- I like the idea of a plug-in better than putting it the core, but I think I'll just make it read an HTML file and write what it finds into the custom column. I don't want Calibre to be the primary container of the HTML.
- Will having screeds of HTML in a custom column have any serious impact on Calibre performance. My understanding is that it will be stored in metadata.db. Performance was one of the reasons I thought of having it external. Apart from rendering it in Book Details what else can Calibre do with it. Search it I guess, there's a can of worms lurking there though, "background and style" returns spurious results because it finds HTML keywords, I wasn't expecting it to do otherwise. I searched for "Apple" in Comments once and got a lot of false positives, because there were lots of these in downloaded Comments
Code:
<h3><span class="Apple-style-span" style="font-size: 12px; font-weight: normal; ">
- Maybe longtext columns should be exclude-able from Search.
- What can & can't I do in the HTML that I put in a long text Custom Column. I already know I can do things that the wysiwyg interface doesn't support. I can find out by trial and error, but if there are some guidelines or standards then ...
BTW, I was surprised to find longtext custom columns can appear in the Book List, even though Comments can't, is that by design or by chance. If by design then why exclude Comments ?
BR