View Single Post
Old 08-16-2023, 11:58 AM   #82
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,238
Karma: 148951761
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
Old-style number support in e-readers is definitely bad, especially considering that if you have a half-decent HTML/CSS renderer and an OpenType font that is set up for them, it's actually easy:
Code:
font-feature-settings: "onum" 1;
There are some readers that support this, but others ignore it. Worse, though, is Kindle, which will silently do the equivalent of the above line with the following CSS:
Code:
font-variant: small-caps;
text-transform: lowercase;
This is a common method used to end up with small caps when the source text is all uppercase. But, Kindle gives it what might be an unwanted side-effect.
The correct CSS for smallcaps is...
Code:
text-transform: uppercase;
font-variant: small-caps;
You need the text top be uppercase before it can be converted to smallcaps.
JSWolf is offline   Reply With Quote