Embedded fonts and inline style

[paulfiera]

Whenever I have some epubs with embedded fonts I usually run the Modify epub plugin to remove them and then I do a conversion.

Doing that, the resulting epub always generates an inline style with these font definitions:

@font-face {
font-family: "Charis";
font-style: normal;
font-weight: normal;
src: url(fonts/CharisSILR.ttf)
}
@font-face {
font-family: "Charis";
font-style: normal;
font-weight: bold;
src: url(fonts/CharisSILB.ttf)
}
@font-face {
font-family: "Charis";
font-style: italic;
font-weight: normal;
src: url(fonts/CharisSILI.ttf)
}
@font-face {
font-family: "Charis";
font-style: italic;
font-weight: bold;
src: url(fonts/CharisSILBI.ttf)
}

Then I open the epub in Sigil and replace all these occurrences.

I've tried checking the checkbox "fonts" in Look & Feel -> Filter Style Information hoping that no fonts would be declared in the inline CSS but that doesn't seem to do the trick.

Is there any way I can prevent calibre to declare these non existing fonts?

Not really a show stopper. Mostly so I can avoid doing the search & replace with Sigil after a conversion.

[JSWolf]

Load the ePub into Sigil, remove the font code from the CSS. Remove the fonts, remove the font code in the OPF and forget about the modify ePub plugin (doesn't seem to work). Then you can do any other editing you need/want to do via Sigil.

Doing a conversion from ePub > ePub can cause problems you don't want. So this is why it's best to do the font removal via Sigil and forget converting. It's already ePub. It doesn't need to be remade into ePub.

[paulfiera]

Originally Posted by JSWolf

Load the ePub into Sigil, remove the font code from the CSS. Remove the fonts, remove the font code in the OPF and forget about the modify ePub plugin (doesn't seem to work). Then you can do any other editing you need/want to do via Sigil.

Thanks, JSWolf.

That's what I'm currently doing - more or less. I was just wondering, generally, why calibre has to declare fonts inline that actually do not exist.

Originally Posted by JSWolf

Doing a conversion from ePub > ePub can cause problems you don't want. So this is why it's best to do the font removal via Sigil and forget converting. It's already ePub. It doesn't need to be remade into ePub.

I'm aware of that, but sometimes I like to get better covers for the epubs I convert, or generate a TOC if it isn't present, or change the look & feel of h1, h2 headings, etc...

[JSWolf]

Originally Posted by paulfiera

Thanks, JSWolf.

That's what I'm currently doing - more or less. I was just wondering, generally, why calibre has to declare these fonts in an inline style - no matter if these fonts are present or not.

Calibre take any @ code like @font-face and @page and puts them in every XML file and removes them from the CSS. That to me is the wrong way to do it. Because it then means any changes have to be done to every XML file. This is one of the issue you can get going ePub > ePub.

[paulfiera]

Originally Posted by JSWolf

Calibre take any @ code like @font-face and @page and puts them in every XML file and removes them from the CSS. That to me is the wrong way to do it. Because it then means any changes have to be done to every XML file. This is one of the issue you can get going ePub > ePub.

So that's how it works!

I guess I'll follow your advice on the sequence: Remove the font code from the CSS. Remove the fonts, remove the font code in the OPF.

Many thanks JSWolf