|
I've been thinking about Import/Create and the use of collection names with commas in them. They are a challenge.
If we take Author Sort as an example (which has the format "Lastname, Firstname"), Create Collections can create these on the Kindle without any issue.
But if you import collection names that have commas in them, then you are forced to use a basic text column (one that is not comma separated like tags). Otherwise Calibre thinks that the comma means you have 2 separate collections, one called "Lastname", and one called "Firstname", instead of one called "Lastname, Firstname".
But this means you can't have multiple collections per book in the same custom column - all the collection names get treated as one big name with commas between them. So if you had a book in collection "Lastname, Firstname", and "Mystery", when you imported them you get an entry in the column like "Lastname, Firstname, Mystery". Which is okay if you just use the column to see what you have on the Kindle. But if you want to use Create Collections with the column, it will create a collection called "Lastname, Firstname, Mystery" on your Kindle (and even if you split on the "," it creates 3 separate collections instead of 2).
I can check for commas and warn users - but its not clear how you can actually keep things sensible if your collection names have commas in them if you want to import/export from the same custom column. It may not be anything I can 'fix' with code, so I'll look into how to explain it as I can see it can create some confusion.
|