Thread: Embedded fonts and inline style
View Single Post
Old 02-26-2012, 01:16 PM   #3
paulfiera
Addict
paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.
 
paulfiera's Avatar
 
Posts: 387
Karma: 3102
Join Date: Dec 2010
Location: EU
Device: Kobo Aura ONE, Kobo Libra H20
Quote:
Originally Posted by JSWolf View Post
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.

Quote:
Originally Posted by JSWolf View Post
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...
Last edited by paulfiera; 02-26-2012 at 01:23 PM.
paulfiera is offline   Reply With Quote