Quote:
Originally Posted by JSWolf
I made a slight mistake. I read The Girl with the Dragon Tattoo from an ePub made from a Mobipocket edition. But the other two Larsson eBooks I read from original ePub. #2 & #3 do have embedded fonts. So I incorrectly thought # would as well in an original ePub. So give one of the other 2 a try and see what happens. If I am not mistaken, they put the font declaration in body which is not incorrect.
|
Luckily, I did indeed purchase all three books, so I downloaded the epub versions of them, as well as of Millenium falcon and Under the Dome (this last one is giving me problems to decrypt though..). the two other Larson books give me the same results as the first. Arial is embedded in the fonts folder, but the font that's actually defined is Times new Roman.
The reason I picked up the other two books (although I was only able to check the StarWars one) is I wanted to see if maybe during the decription process, something was being changed, but it actualy had a different Font. It's embedded font was CharisSIL, and while @font-face, none of the actual styles were, so they were all like:
Code:
h1.contents {
font-size: medium;
text-align: center;
font-style: italic;
font-weight: bold;
}
instead of what I've seen in the other three books:
Code:
.h1
{
font-family: "Times New Roman",serif;
font-size: 200%;
margin-top: 4em;
margin-bottom: 0.5em;
text-align: center;
I'll play around with the Starwars book because I don't know if the omission of the embedded code means it defaults to them or the machines fonts, but I believe it's probably the latter. I'll change the font that's easily recognizable as I did with my first test and see. But it really does seem that if the ebook is not coded properly, and it would seem like this is the case, then they are not going to show embedded fonts, even if they are present in the container. This isn't a bug in the device(s), it's publisher lazyness, which unfortunately isn't all too surprising
