[jackie_w]

Originally Posted by Morkl

Do you have font-variant: small-caps definitions that work on the PRS-T1? Care to share?

If you were expecting an elegant 'solution' look away now The font-variant property just doesn't work in the ADE reader so a workaround was necessary.
My main aim was to correctly display SmallCaps in epubs created from my own HTML/CSS files which are written like

HTML file: <p>...<span class="smallcaps">this text displays in SmallCaps</span>...</p>
CSS file: .smallcaps {font-variant: small-caps}

For this very specific case, including this in css/style.css does the trick

@font-face {font-family: "SCfont"; font-weight: normal; font-style: normal; src: url(res:///ebook/fonts/../../mnt/sdcard/reader/fonts/xxx.ttf)}
@font-face {font-family: "SCfont"; font-weight: normal; font-style: italic; src: url(res:///ebook/fonts/../../mnt/sdcard/reader/fonts/xxx-Italic.ttf)}
@font-face {font-family: "SCfont"; font-weight: bold; font-style: normal; src: url(res:///ebook/fonts/../../mnt/sdcard/reader/fonts/xxx-Bold.ttf)}
@font-face {font-family: "SCfont"; font-weight: bold; font-style: italic; src: url(res:///ebook/fonts/../../mnt/sdcard/reader/fonts/xxx-BoldItalic.ttf)}

.smallcaps {font-family: "SCfont", serif; font-variant: normal}

However, in commercial epubs I've rarely (if ever) seen .smallcaps {font-variant:small-caps} in the CSS file. It's much more likely to be .smallcaps {font-size:0.75em} with the relevant text in the HTML file already in UPPERCASE.

The crude solution above should still work to use the specified SmallCaps font but the biggest problem is that they rarely use an obvious descriptive name like smallcaps as the css selector name. I've settled on the following in my style.css

.smallcaps, .smallcaps1, .smallcaps2, .small-caps, .sc, .fsc, .smallCaps, .Smallcaps, .SmallCaps {
    font-family: "SCfont", serif;
    font-variant: normal}

It still doesn't catch all of them, but those that are missed are still displayed as font-size 0.75em in the standard body text font, i.e. the publisher's own crude work around.

Originally Posted by Morkl

...or I could just redefine the nomenclature, and make the "Font selector" a "Style selector" ...

So, which way do you think would be the best?

Simple is good. The 'make the "Font selector" a "Style selector"' option would suit me. You would have your choice of 7 .css files. Infinite is better, but may not be worth your time and effort. Speaking for myself only, your custom Font Sizes feature has greatly reduced the number of CSS files I need.

Originally Posted by Morkl

Pros: CSS selector integrated in the Reader that remembers the setting for each book
Very easy to implement

I like the book 'remembered setting' feature. We didn't have that with PRS+ and the earlier Sony models.

Originally Posted by Morkl

Cons: CSS files need to be kept for each style

Not much of a Con for PRS+ users. We've always done it this way. Creating your first CSS file is the hardest. It's mainly copy/paste with minor tweaks for the rest.