This is probably too niche of an issue to do anything about, but just to make you aware that the use of a comma (",") as the field separator for columns (as in Comma separated text like tags) conflicts with the Author Sort use of the comma.
Specifically I have an import/export function in my plugin such that users can import collection names from their Kindle into a custom column name. They can then export/create collections on their Kindle from this column once they add/remove/edit/etc collection names/books.
If their collection names on their device have commas in them (e.g. "LN, FN"), then when they import they have to use a simple text field custom column - otherwise calibre splits the name on the comma into multiple and incorrect values ("LN" and "FN"). The custom column will look reasonably ok with multiple collections for the book (e.g. "FN, LN, Mystery"), but when they export using the data all of the entries will be sent as one joined name so they end up with different names than expected (they get "FN, LN, Mystery" instead of "FN, LN", and "Mystery).
Is there a way to change the separator character (per field?) to something other than comma? Or some other simple way around this? (other than saying collection names shouldn't have commas in them or there will be problems
)