View Single Post
Old 08-04-2024, 07:41 AM   #13
d3m0sth3n3s
Member
d3m0sth3n3s shares his or her toysd3m0sth3n3s shares his or her toysd3m0sth3n3s shares his or her toysd3m0sth3n3s shares his or her toysd3m0sth3n3s shares his or her toysd3m0sth3n3s shares his or her toysd3m0sth3n3s shares his or her toysd3m0sth3n3s shares his or her toysd3m0sth3n3s shares his or her toysd3m0sth3n3s shares his or her toysd3m0sth3n3s shares his or her toys
 
d3m0sth3n3s's Avatar
 
Posts: 23
Karma: 5854
Join Date: Jun 2012
Location: Spain
Device: Kindle DX, Kindle Paperwhite, and Kindle Scribe
Quote:
Originally Posted by BetterRed View Post
It has nothing to do with whether they were edited - mainly to do with what was embedded in the format file that was used to create the book in the calibre library.
Yes, you are right. My explanation was incomplete/misleading.

I just think that if calibre turns a simple comment into HTML code just by, for example, simply adding a comma with no styling involved, whenever you edit comments with the GUI metadata editor, then it would be better for consistency to just store them all in HTML from the very beginning, no matter how comments were defined in the description embedded within the source e-book file you import into your library. That’s just my opinion on the subject.

Last edited by d3m0sth3n3s; 08-04-2024 at 07:44 AM.
d3m0sth3n3s is offline   Reply With Quote