View Single Post
Old 09-15-2022, 12:00 AM   #69
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 Turtle91 View Post
Personally I would just use a couple very simple regex to convert the ALL CAPS to sentence case (or Mixed Case) then apply small-caps. But that is just me.
Yep.

The other method has 95% of the same disadvantages as F<small>AKE</small> C<small>APS</small>.

It's only better because you see some proper smallcap letters!

But you get all the mess with:
  • red squigglies
  • impossible-to-read code
  • a lot more chances to introduce errors
    • Don't ask me how many times I've seen T<small>YPO'S</small> in captions.
    • (I'd be able to afford to purchase my own M<small>C</small>D<small>ONALDZ</small>!)
    • (And captions are only a handful of words! I can't imagine an entire book full of D<small>IE-UH-LOG</small>!)
  • ...

And if you're already going through creating all that disgusting markup... why not just substitute in one of our lowercasing/titlecasing regexes and fix the text itself!

Clean, crisp, maintainable code... always the right decision!

Last edited by Tex2002ans; 09-15-2022 at 12:06 AM.
Tex2002ans is offline   Reply With Quote