You can use Cleaning Comments to remove HTML.īottom line: I am not convinced that it is worth my trouble. If the changes are per-device then you can use Reading List to help manage which S/R to run. If needed keep the "real" comments in a custom column and modify the built-in comments field. You can use search/replace to change comments or construct another custom field however you want, especially with template mode. Adding comments means a maintenance problem, feature requests e.g., to do html processing in the plugboard, and who-knows-what such as "Why stop with comments? Why not allow plugboards to change any metadata field?" No reader that I know of uses comments for that purpose. Plugboards exist to permit people to put non-standard data into standard device-specific fields that readers use to categorize books. But, I haven't tested it with anything other than a Kobo device.īut, lets wait and see if chaley had a reasonīecause I didn't see the point, and TBH I still don't see the point. It is a very, very simple change and I have been using it for a long time with no problems. If I could do this via a metadata plugboard, it would happen whenever I sent a new book to the device.Īnd for the record, I have added comments to the metadata plugboard in my dev environment.
CALIBRE READER CHANGE TO LANDSCAPE UPDATE
Then, connect the device and update the comments using the plugin. To do that, I have to send the book to the device, eject the device and let it process the books. That has rating, page and word count and tags added at the start of the comments. This post has a screenshot of this from a Kobo device.
I currently use the Kobo Utilities plugin to do this, but directly updates the database on the device. And I do want to "jam" other unsupported fields into it. I thought the whole purpose of the plugboard was to Jam data from other (unsupported) fields into a standard field, otherwise, the standard file name templates would suffice I don't know of anything other than Calibre Companion that uses them in any way. But, they are pretty much useless anywhere else.
If you want to store extra information about the books, in the library, they are probably the way to go. I don't find either of these very compelling reasons for not including the comments in the metadata plugboard, so maybe I am missing some other reason.Īs to user columns, they are great for the calibre library.
CALIBRE READER CHANGE TO LANDSCAPE CODE
But, calibre already has code that can be used to mitigate this (type incorrect HTML into the metadata editor and save it and then look at what is produced). The other is the risk of broken HTML going into the field. Firstly, not enough devices actually display the comments and hence it wasn't worth it. The only thought of two reasons that the comments field is not supported in the metadata plugboard. Most of this is in custom columns, but I also add the rating which is a calibre standard column. For me, I want to be able to add the information that the the device doesn't display to the comments. Or to strip the HTML from the comments because the device doesn't support them. Maybe they want to clear the field when sending to the device as their device cannot display the comments or limit it to the first 500 characters.
That size might actually be why someone wants to fiddle with the comments.
Yes, the comments can be huge, but they are already put into the book when it is sent to the device (if the format supports it). Not a great plan in the plugboard for general release.Ī user column at least, has better control of what is put there.
0 kommentar(er)
