View Single Post
Old 11-06-2018, 10:39 AM   #17
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,476
Karma: 8025702
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by masp View Post
Got it: thanks! I suppose there's no way to hard-code comma as the separator, but then allow for that to be replaced by ampersand if requested? Or to introduce a new type of list (ampersand-separated) so existing lists would be unaffected (still hard-coded to comma) but users could choose to create lists of the new (ampersand-separated) type if they wished? (Just clutching at straws!)
Sure, it can be done. I just don't want to pay the price. Adding a new list type or adding a new column behavior parameter *will* break software, possibly calibre, possibly other programs that process the calibre database. For me, this cost is significantly higher than the benefit.
chaley is offline   Reply With Quote