Quote:
Originally Posted by davidfor
The author problem is probably two things. Firstly, calibre writes multiple authors into the metadata in separate dc:contributor tags. But, the firmware only reads the first tag. Hence, you will only get one author on the device and it will be whatever is in the first tag. The workaround for this is to use a metadata plugboard to set the author during the send-to-device. This changes the metadata during the update to use a single tag with all of the authors. The one I suggest using is:
Code:
program: raw_list('authors', ', ')
That will set the author to look like "FN1 LN1, FN2 LN2" which the device will parse as two authors. |
Yeah, I never noticed this until I switched away from using Calibre to transfer books (because on reconnect, your plugin would fill in everything correctly), only because on this netbook, it'll take forever to scan on device connect (again, ridiculously large collection with an even more ridiculously sized database), which is fine if I was uploading a batch of books from time to time, but not if it was a book at a time multiple times a week (orders of magnitude and all that).
Quote:
|
The other problem is that calibre does not automatically update the book file with any metadata changes. It only does this when the book is being sent out of the library (Save-to-disk or Send-to-device), during a conversion or when you use the Embed metadata tool. If you are using kepubify to transform a book in the calibre library to kepub, you need make sure the metadata is written to the file first.
|
But that's what I do; Save to Disk and then drag to kepubify. It does save the book description so I know that part works. It was just the weirdness with the author field and I figured it had to be something like you described above.
Just curious: Can a plugboard like you suggested above be used to alter the author metadata on Save-to-Disk instead to populate that first field properly? I'm using one to append Word and Page count to the description already (I think you might have provided the sample code in another thread way back in the day, so thanks!), but I don't really understand how the plugboard system works and if it's all the same or how to alter multiple fields (for example, is it safe to have two rules that affect any format, Save to Disk that affects different Destination fields? The warning Calibre throws when you try to do so confuses me).