View Single Post
Old 01-24-2022, 11:09 AM   #2
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Quote:
Originally Posted by ValTim View Post
I created an EPUB using InDesign CC, and I selected the option of embedding fonts when exporting. Then, I deleted the unnecessary body fonts, and added another one manually (to the package, content.opf and CSS declaration). The EPUB contains now an Adobe font (encrypted) in some paragraphs as well as a Google font (non-encrypted, with free license). The Adobe font should be displayed in the apps supporting encryption (such as Apple Books and ADE), and the Google font, as fallback, in the ones not supporting encryption (e.g. Kindle).
After editing the EPUB, everything is fine in the Kindle Previewer, but I notice that the apps supporting encryption mix characters from both fonts. See attached image.
Here is my CSS:
Code:
@font-face {
	font-family:Quicksand;
	font-style:normal;
	font-weight:normal;
	src : url("../font/Quicksand-Regular.ttf");
}
@font-face {
	font-family:VAGRundschriftD;
	font-style:normal;
	font-weight:normal;
	src : url("../font/VAGRundschriftD.otf");
}
(...)
p.Numero-capitulo2 {
	color:#39a2c4;
	font-family:VAGRundschriftD, Quicksand, sans-serif;
	font-size:3em;
	font-style:normal;
	font-variant:normal;
	font-weight:normal;
	line-height:1.2;
	margin-bottom:45px;
	margin-left:0;
	margin-right:0;
	margin-top:0;
	orphans:1;
	page-break-after:auto;
	page-break-before:always;
	text-align:right;
	text-decoration:none;
	text-indent:0;
	text-transform:none;
	widows:1;
}
Quicksand is the Google font, and VAG Rundschrift D, the Adobe font.
I used the Google font version directly downloaded from the Google Font website (and I did not activate the Adobe Font version in InDesign). I also tried with the OTF version from Font Squirrel, with the same results. The file encryption.xml is kept in the META-INF folder.
Is there a way to make this work as intended without breaking any license agreement? I read the thread about embedding Adobe Fonts in Kindle: https://www.mobileread.com/forums/sh...d.php?t=342147. I do not want to de-obfuscate the Adobe font, but to use the encrypted and non-encrypted fonts together in an EPUB.
Jesus, what is it with Quicksand lately? I feel about it as the infamous "Niagara Falls" skit, Abbott and Costello. Honestly. There's also something hinky about that font. I'd have to ask my guys to refresh my memory, but I just went through hell with it.

One note--the encrypted fonts will NOT pass ePUBcheck, IME. Adobe claims that "of course you can use them for your eBook," but what they mean is, on your computer, or any local computer--not in a retail situation.

So...we remove everything, re-embed fonts, and change the CSS. Having two of the same font seems as though it's asking for trouble.

What's the HTML and CSS around that text, the text in the image?

Hitch
Hitch is offline   Reply With Quote