View Single Post
Old 12-20-2018, 10:27 AM   #2
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,659
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
That is done by design. It's valid code. If you don't want the span code, then don't use the style buttons (or their assigned keyboard shortcuts) in Book View. Book View edits (even simple ones using the same button) are entirely different beasts than Code View edits. That's what people often fail to understand. We can better control what code gets generated by the styling buttons in Code View, but we have very limited options as to what code Qt generates in Book View with the same buttons (and same shortcuts). We've chosen the option that absolutely guarantees spec-compliance.

And the bottom line is: those who make wysiwyg edits don't really get to complain about the code that's generated for them. You can't have it both ways. If you're particular about the code contained in your ebook, then make all of your edits in Code View. It's really that simple.

Last edited by DiapDealer; 12-20-2018 at 10:33 AM.
DiapDealer is offline   Reply With Quote