View Single Post
Old 03-03-2017, 03:02 PM   #30
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 7,645
Karma: 5433388
Join Date: Nov 2009
Device: many
If we add a setting, should we then also try and honour it in CodeView as well?

Most of CV formatting code is done manually, so we should be able to make it use the span and inline style approach as well for underline, strike, subscript, superscript, etc, etc after checking the setting. A bit more work but it would at least allow the user to control things in both BookView and CodeView.

What do you think, worth the trouble or just hard code the horrible spans for BookView only?
KevinH is online now   Reply With Quote