View Single Post
Old 09-02-2022, 06:17 PM   #33
Turtle91
A Hairy Wizard
Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.
 
Turtle91's Avatar
 
Posts: 3,363
Karma: 20212733
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
Quote:
Originally Posted by enuddleyarbl View Post
That looks really nice. I keep seeing publishers doing all kinds of weird capitalizations and spans (like you pointed out later in our post) that I end up having to manually remove. I'm going to look into applying your first-line stuff automatically:
Code:
h2 + p::first-line, ...	{
  font-variant:	small-caps;
  font-size:	1.15em;
  }
I'll still have to manually remove the source all-caps, but this is a good semi-automatic replacement for what I think the publishers were trying to do.
Coolio!

Just a reminder that some devices don't play well with small-caps, or pseudo-elements...that's why those publishers reverted to those spans - for maximum compatibility across the most devices. But if your device works with it (as mine does) then it is a great tool!

Also, as mentioned in other locations, if you can embed a font that is a true small-caps font, then things look even better to the discerning eye. I'm not that discerning yet....

Last edited by Turtle91; 09-02-2022 at 06:20 PM.
Turtle91 is offline   Reply With Quote