@JSWolf
This is all nice and fine but involves manual labor. There is no way to do this just by using calibre.
For example I have a book in Serbian formatted as pure html. I cleaned it up with tidy making it fully standard compliant. Than I added this inside head tag:
Code:
<style type="text/css">
@font-face { font-family: dejavu; font-style: normal; font-weight: normal; src: url(DejaVuSans.ttf) }
body {font-family: dejavu,sans-serif}
p {font-family: dejavu,sans-serif}
</style>
And placed font dejavu.ttf in the same folder as html. Opened it in Safari (one of the few browser to support font embedding) everything looks fine.
Start calibre (0.5.14) and import book.
Convert book to the epub and result does not show embedded font on the device nor on desktop Adobe DE.
Decompress the epub and verify css.
This is the generated css:
Code:
@font-face {
font-family: dejavu;
font-style: normal;
font-weight: normal;
src: url(resources/DejaVuSans_0_0.ttf)
}
body {
font-family: dejavu, sans-serif
}
p {
font-family: dejavu, sans-serif
}
.calibre_class_1 {
display: block;
page-break-after: always
}
However if I change the path to this:
Code:
@font-face {
font-family: dejavu;
font-style: normal;
font-weight: normal;
src: url(DejaVuSans_0_0.ttf)
}
Than it starts working.
I hope this will be fixed in 0.6, but until that is done it is far from user frendly.
It is not just point that it can be done, but what matters also is that it is easy enough for everybody.