View Single Post
Old 08-18-2023, 01:23 PM   #99
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,070
Karma: 147983159
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by nabsltd View Post
This is another one of the many problems that could be solved if people who edit eBooks bothered to take the time to learn how reading software works.

Using font-variant: small-caps and lowercase text will always result in small caps on all modern CSS renderers. If the reading font has the "scap" OpenType feature, then the software will use real small caps (or at least those supplied by the font). OTOH, if the reading font doesn't have "scap", then the renderer will synthesize small caps by using reduced height uppercase.

So, by always using "real" small caps, you end up with the best possible display...either true small caps, or the exact same display you get with uppercase text and font-size: 0.8em.
It's actually better to use simulated smallcaps. You don't know what font is going to be used and you don't know what reading software is going to be used.
JSWolf is offline   Reply With Quote