View Single Post
Old 08-18-2023, 11:28 AM   #96
nabsltd
Fanatic
nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.
 
Posts: 522
Karma: 8500000
Join Date: Aug 2013
Location: Hamden, CT
Device: Kindle Paperwhite (11th gen), Scribe, Kindle 4 Touch
Quote:
Originally Posted by DNSB View Post
Around here, it runs about 75% fake/25% real. A big enough percentage that I'm not going to guess which is used in any new ePubs.
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.
nabsltd is offline   Reply With Quote