|
"You also need to create an @fontface rule for EACH of the four font-files (adjusting the properties for font-weight, font-style and the src url accordingly). The font-family name needs to be identical for all four font font-files."
I was to ask how to do that, but I tried it first with just this code:
@font-face {
font-family: Georgia;
font-weight: normal;
font-style: normal;
src: url(../Fonts/Georgia.otf);
}
body { font-family: Georgia, serif; }
And all the bold text and italics display fine.
"Then when you get it working, consider not using embedded fonts for the body text in your epub. There's many reasons it's a bad idea (besides the legal issues you'd run into for distributing the Georgia font with your epub)."
I just wanted to create a PDF file that I could use to promote my book. I figured it would be easier to send a PDF file as an e-mail attachment than six different ePub versions, hoping one would work with whatever epub reader the recipient uses.
But so far, I haven't specified any font families in any of my epubs. Serif appears to be the default, so I just style certain elements to display as sans-serif. My understanding is that Kindle and most other epub readers use custom fonts - or let users choose their font.
But if I want to sell a PDF version of my book, then I have to purchase a license to use Georgia? I'll have to look into that. I did some research on digital rights management (DRM), and it looks like a lost cause. E-junkie has some process for watermarking PDF files, and I'm wondering if that might be the best way to go.
|