View Single Post
Old 11-12-2019, 06:42 PM   #16
Tex2002ans
Wizard
Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.
 
Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
Quote:
Originally Posted by AlanHK View Post
So I learned that Pretty did not parse CSS, only respected default tags.
JSWolf recently mentioned something similar in Calibre's Editor:

Bug in the code editor showing bold/italic

Calibre makes the text in Code View bold/italic between the <b> + <i> (a very nice touch), but JSWolf wanted it expanded to recognize:

Code:
<p class="bold">
<span class="bold">
Kovid explained why parsing CSS like that would be a serious performance issue.

Quote:
Originally Posted by KevinH View Post
Since users can change what css is active by changing the css file, it is never perfectly clear when to prettify, so we only use the tags.

Last edited by Tex2002ans; 11-12-2019 at 06:45 PM.
Tex2002ans is offline   Reply With Quote