Quote:
Originally Posted by sophieturgeon
I just tried to add the page and word info to 121 books. It work for all but 4 books. I believe the problem for these 4 books is because thy are from a publishing company for which we don't have a plugin yet. Of course it was a user problem: all the columns were created correctly except the names of the columns had the # in front of it. And I had put a 1 in the Format for Numbers field. Again, Thank you so very much!
|
The '#' in front of the Custom column lookup name is needed in searching, templates etc, but not when specifying the Custom column. I think the '#' acts as signal to calibre processing code that the column in question is a Custom column rather than a Built-in column.
If you're happy with 34567 then there is no need to format, but if you wanted 34,567 or 34.567 you would use "{:,}" or "{:.}" as the format. You may find this blog post on python formatting easier to comprehend than the the one in the calibre documentation ==>>
Python String Format Cookbook. It covers the 10% of what I need to know, to do 90% of what I need to do.
It would be 'good' if the PI computed a word count if it can't download one. I use computed values - its generally faster than downloading from Goodreads, besides most of my books aren't on Goodreads. I only use the Word Count as a 'clue' as to the relative size of the book.
BR