no small caps?

[fbrzvnrnd]

I'm reading an ebook with small caps text, but KOReader fails to render it.
It is a bug or I'm missing something?

[JSWolf]

Originally Posted by fbrzvnrnd

I'm reading an ebook with small caps text, but KOReader fails to render it.
It is a bug or I'm missing something?

KOReader does do small-caps. In CSS you want to use

 font-variant: small-caps;

Most eBooks use simulated small caps which is also not a problem in KOReader.

[fbrzvnrnd]

Mh, weird. If I choose to turn off 'fonts embedded' KOReader show me the text in small caps. If I turn on 'fonts embedded', KOReader show me the text in lowercase. In HTML I have:

<p class="_0-Corpo-del-testo ParaOverride-18"><span class="CharOverride-28">agriculture / agricoltura</span></p>

In CSS:

span.CharOverride-28 {
font-family:"Simoncini Garamond Std", serif;
font-style:normal;
font-variant:small-caps;
font-weight:normal;
text-transform:none;
}

and..

@font-face {
font-family:"Simoncini Garamond Std";
font-style:normal;
font-weight:normal;
src : url("../Fonts/SimonciniGaramondStd.otf");
}

If I open the same ePub in Adobe Edition, I can see the small caps...

[NiLuJe]

I assume this simply means that the embedded font has borked/trimmed OpenType features.

[fbrzvnrnd]

Originally Posted by NiLuJe

I assume this simply means that the embedded font has borked/trimmed OpenType features.

If were borked/trimmed features, Adobe Digital Edition too would have the same problem. But I can see small caps on Ade and others readers.

[NiLuJe]

I wouldn't necessarily be sure about that. Adobe has the best font engine in the business, it might be doing some black magic to coerce features out of a funky font .

More interesting is your "other readers" comment: which ones? ;o).

Another train of thought: is the embedded font actually detected *at all*? Or is it falling back to a fallback font?

[fbrzvnrnd]

Originally Posted by NiLuJe

I wouldn't necessarily be sure about that. Adobe has the best font engine in the business, it might be doing some black magic to coerce features out of a funky font .

I tried other ebook readers (see after)

Originally Posted by NiLuJe

More interesting is your "other readers" comment: which ones? ;o).

I tried Adobe, iBooks and Thorium on Macintosh and Adobe, Namo Reader, Google Play Books and Gitden Reader on Android. All show the small caps.

Originally Posted by NiLuJe

Another train of thought: is the embedded font actually detected *at all*? Or is it falling back to a fallback font?

I checked: all the ebook reader are using the Simoncini Garamond. Only KOReader fails to show the small caps...

UPDATE: also Moon+Reader and ReadEra fail to show the small caps...

[NiLuJe]

Hard to say more without having the font on-hand to take a look at its feature table, though.

One thing you can try is ripping the font out of the ePub and installing it as a KOreader font, to see if the behavior is specific to how embedded fonts are loaded or if it's specifically an issue with this font

[fbrzvnrnd]

Originally Posted by NiLuJe

Hard to say more without having the font on-hand to take a look at its feature table, though.

One thing you can try is ripping the font out of the ePub and installing it as a KOreader font, to see if the behavior is specific to how embedded fonts are loaded or if it's specifically an issue with this font

Good point. I analyzed the font. It weighs only 15k, so it's a subsetting and, looking at the characters inside, I don't see the small caps (so I have to correct myself: the font I see reading the ebook is Simoncini except the small caps texts). My guess is that Adobe, Apple or Google, when they realize that an embedded font does not have subsetting related to a feature, such as small caps, they fallback on the second font. Not KOReader: if it does not find the small caps it does not fallback and fails to render the property indicated in the CSS.

It seems to me a KOReader bug: the CSS states to use Simoncini with small caps or fallback to Serif with small caps if Simoncini with small caps is not present. KOReader uses Simoncini without small caps and does not fallback to Serif with small caps.

[NiLuJe]

I'm indeed fairly confident that a missing `font-variant` doesn't trip a fallback codepath in CRe (as opposed to a missing glyph).

Our resident CRe wizard @poire-z will probably chime it at one point to say how feasible something like that would be .

(Or, more generically, if it even makes sense and/or what the actual specs say about the canonical behavior (if there is one) in such an instance ).

[fbrzvnrnd]

Originally Posted by NiLuJe

I'm indeed fairly confident that a missing `font-variant` doesn't trip a fallback codepath in CRe (as opposed to a missing glyph).

Our resident CRe wizard @poire-z will probably chime it at one point to say how feasible something like that would be .

(Or, more generically, if it even makes sense and/or what the actual specs say about the canonical behavior (if there is one) in such an instance ).

IMHO the small caps variant is typographically and visually important enough to require a fallback. Apple, Adobe and Google follow this road...

[roger64]

Hi

To learn about the open-type features of any font, I found the following site very useful:

https://wakamaifondue.com/

[JSWolf]

Originally Posted by roger64

Hi

To learn about the open-type features of any font, I found the following site very useful:

https://wakamaifondue.com/

That's a very useful site.

[JSWolf]

Simoncini Garamond Std does not support small caps. So the solution is to use simulated small caps.

span.CharOverride-28 {
font-family: "Simoncini Garamond Std", serif;
font-size: 0.8333em;
}

[Jellby]

... and apply that style only to the "small" caps, i.e. not to large caps, not to spaces, not to punctutation...