View Single Post
Old 05-26-2016, 10:48 AM   #30
pdurrant
The Grand Mouse 高貴的老鼠
pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.
 
pdurrant's Avatar
 
Posts: 74,209
Karma: 317184274
Join Date: Jul 2007
Location: Norfolk, England
Device: Kindle Oasis
Quote:
Originally Posted by dwig View Post
While there are people that will argue otherwise, faking small caps by scaling the regular caps, whether in ebooks or print, is a cheap kluge that results in less than the best appearance as the scaled caps are lighter than either the full size caps or full size lower case. It is true that there is no consistent way to do "cheap and dirty faux" smallcaps, but this tread is about good design.
I agree that good smallcaps relies on having a properly designed smallcaps version of a font.

What is absent from the major ePub rendering software (ADE) at the moment is any support for the smallcaps CSS attribute. A good ebook renderer would

(a) support the text attributes that it is required to do by the standard
(b) use a small cap font to do so when it's available.

One can, I agree, embed a proper smallcaps font, but this does not actually help when the user of the reading software chooses a different font for the body text.

Good ebook design should not depend on the use of a specific body text font.
pdurrant is offline   Reply With Quote