[Hitch]

Originally Posted by ValTim

Hi Hitch,
Thanks for your answer. I chose Quicksand because it is the closest free alternative I found to VAG Rundschrift. If you know another one, please tell me.

I'll have to think about it. I have a font library of over 11,000 faces and I tend to license for use, so...

The file with encrypted fonts do pass EPUB check. I use the pagina EPUB-Checker. It has no errors or warnings, but there is a message stating that the fonts cannot be decrypted.

I know for a fact you can't use that with KDP. There were limitations on that for forever and if you try to upload them, KDP rips them out of the file and that's that. That's a NoFlyZone right there. When you encrypt fonts in INDD, the head table is missing, AFAIK. (Famous last words...I've probably forgotten.)

Which version of Pagina are you using? When I run ePUBcheck (pagina, 2.04) against an encrypted ePUB, it gives me a ton of error messages. Are you assuming that "passing" is the same as "usable"? It'll validate, but you'll get a ton of INFORMATION notes. You don't see those?

(n.b.: that used to cause it to fail; now it's information. I don't know when/how that changed--one of the Nerd Birds here will know.)

The HTML for the title is just this:

<p class="Numero-capitulo2">Capítulo dos</p>

There is no div around. I kept the body CSS from ID stylesheet:

body, div, dl, dt, dd, h1, h2, h3, h4, h5, h6, p, pre, code, blockquote {
	margin:0;
	padding:0;
	border-width:0;
}
body {
	-epub-hyphens:auto;
}

According to its Asset Guide, Apple Books supports font obfuscation. The publishing guide for Kindle does not say anything against encrypted fonts, although I suppose Amazon does not display them after publication in KDP.

I don't see where you assigned a font to this. Not something other than a) the default font chosen by the user or b) a class you created somewhere that inherits. I see nothing in either in the p class or the body. What's the styling for the "Numero-Capitulo2" style?

Hitch