View Single Post
Old 08-16-2023, 10:33 AM   #78
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: 528
Karma: 9529956
Join Date: Aug 2013
Location: Hamden, CT
Device: Kindle Paperwhite (11th gen), Scribe, Kindle 4 Touch
Quote:
Originally Posted by Liudprand View Post
In fact, as far as I know they're not supported at all (except when the default figures in a typeface already resemble text figures).
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.
nabsltd is offline   Reply With Quote