Thread: Interpreting column as HTML AND Markdown
View Single Post
Old 03-12-2023, 10:22 AM   #12
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,467
Karma: 8025600
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by DaltonST View Post
Chaley totally owns custom column development, and he nixed the idea in a previous post.
I said I wouldn't do it. You are welcome to make (and them maintain) the changes in base calibre. I certainly won't get in the way.

I would guess that you would:
  • Add 'Mixed' or some such to the choices in "Interpret as" in calibre/gui2/preferences/create_custom_column.py
  • Add your code to calibre/ebooks/metadata/book/render.py somewhere around line 134
  • Add your code to the content server: calibre/srv/metadata.py around line 59.
chaley is offline   Reply With Quote