View Single Post
Old 10-31-2019, 08:40 AM   #6
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,690
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by carmenchu View Post
If other viewers don't respect it, I feel strongly that they should...
Epub doesn't actually work on strong "feels" and W3Schools is not EpubSchools.

But regardless ... this isn't an issue of respecting or rendering. Sigil's Preview handles (and correctly honors) pre code-wrapped content sections just fine (including the pre-wrap css attribute you mentioned). The issue is whether Sigil's Prettyify html feature (found under the Reformat HTML menu) can potentially alter how that same content renders. And the answer is yes... it sometimes can.

Luckily, though; un-Prettified xhtml renders just as correctly in Sigil's Preview. If you have complex pre/code sections with nested html inside that renders precisely how you want it to, it's in your best interest NOT to try and "Prettify" it with any kind of automatic tool.

This kind of situation is exactly why we made "Reformat HTML" an optional, manual choice, rather than the continuously running process it used to be: so people could always choose "correct" over "pretty."

Last edited by DiapDealer; 10-31-2019 at 08:44 AM.
DiapDealer is offline   Reply With Quote