Thread: Underlining
View Single Post
Old 11-23-2015, 04:35 PM   #16
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Quote:
Originally Posted by DiapDealer View Post
True. But the button is there because there was a wysiwyg cry for such a thing. And making the button underline text in a spec-compliant AND sane method would be nothing but trouble: do we create inline styles; do we create a new class in the css file for each occurrance (do we create/link a css file if one doesn't already exist)? Do we parse existing css (both inline and external) to see if a suitable class to be used already exists? What if inheritance from a pre-existing class clobbers Sigil's efforts to create the underline? It's a nightmare any way you look at it.
Here endeth the lesson; the reason that SO MANY people are unhappy that BookView persists. This is the exact reason. The "need" for insta-underlining and other "instant" push-button features--that are actually now WRONG. To use it--if you're a pro, or simply determined to do it correctly--you have to use it, then create some class for it, then regex the u's into spans with the correct name, and of course the closing tag, as well. If ever a nice simple argument for "why BookView can, not necessarily does, suck," this is it.

Quote:
My personal preference would be to give U tags a free pass in Sigil's well-formed check, if at all possible. Let the epub validators do all the barking about them. Short of that, I guess I'd like to see it (the button) made unavailable in documents where Sigil/gumbo deems them un-spec-worthy.

Good stuff!
I think that's about all we can do, if the BV persists and PV doesn't win out as replacing same. Those of us who know and who check, can replace the "u" if we do something stupid, forget and use it; those who don't...well, don't. And won't. They'll either find out when they go to upload it (assuming arguendo it has to pass ePUBcheck), or they'll just build a mobi with it...and I can't now remember if i, u, b, will build uncomplainingly in KG or not. (We don't use them, so...).

In fairness to all, however, I have to say that my fingers still reach for i,u,b. I have to remind myself to NOT do it. (And what will happen is, just as soon as I finally remember without prompting, we'll all be working in ePUB3, ha!).

Hitch
Hitch is offline   Reply With Quote