View Single Post
Old 12-08-2014, 05:31 PM   #7
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,465
Karma: 8025600
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by kaufman View Post
It shows: {0:,}
This is indeed a CC bug, caused by my misunderstanding of format defaults. In python, "{0:,}" for any number column is equivalent to "{0:,d}" where the "d" means decimal number. I didn't account for this default in CC.

There are two possible fixes:
1) You change the column definition to {0:,d}. Of course, this will force a full metadata calibre->CC send on the next connect.
2) I change CC to detect this special case. I will do this, but it may be a few weeks before I make another release.

In case it matters, {0:,} will not work correctly in calibre for floating columns because the default is to format as integer.
chaley is offline   Reply With Quote