|
Note that the bug fixed might not be what you think it is.
The problem was that calibre was not consistent is setting author_sort for 'null' authors. The GUI set author_sort correctly, but it was erased when copied to one of the subprocesses such as save-to-disk or send-to-device. This caused the author_sort value to be erased no matter what it was set to in the GUI or no matter what was in the database. The fix is to make the two processes consistent. Creating a metadata record for a book with a null author will now set author and author_sort to the same value, which is what the GUI does.
There are at least two side effects. One is that changing the author_sort for a book with author "Unknown" will not have any effect on save/send. If the author is null (Unknown), then the author_sort will be "Unknown" as well. I might take a look at the GUI to prevent changing author_sort for a null author, but I suspect that there would be ways around it. Second is that people who depended on author_sort being empty for null authors will need to adapt their template.
Setting the author_sort to empty for a book with a non-null author should work correctly. The empty author_sort will be passed around just like any other author_sort.
|