View Single Post
Old 06-24-2016, 08:29 AM   #4
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
@BR:

Calibre throws datatype=comments to the bottom of the detail view with no labels.

The root cause of @excaliber's problem is that Calibre does not support a Custom Column datatype of "non-normalized, simple text".

Because of the missing datatype, ZMI has to use datatype=comments to ensure that Calibre does not crash when the Zotero data is imported because of dubious or unreliable data quality.

Because ZMI uses datatype=comments, they get thrown to the bottom of the detail view with no labels.

Perhaps someone could create an enhancement request for Calibre to at least add labels. I understand exactly why it throws them to the bottom because the standard Calibre Comments column can be huge. However, they should still have labels.


DaltonST
DaltonST is offline   Reply With Quote