Quote:
Many people here create their MOBIs by feeding an EPUB into KindleGen. I just wanted to show that the font embedding for those musical notes works in EPUB + MOBI at the same exact time.
|
But I was reading on another thread that people are having trouble with font embedding with Kindle after the file is uploaded, likely due to Amazon's decision to strip out font family information (that others leave in not knowing this interferes with the user's ability to change fonts). So even though Amazon say you can have font embedding, they are screwing people's files up by automatically removing the font family information from the CSS; their automatic system cannot seem to tell the difference between font-family information not attached to an embedded font, and that which is. WTF Amazon? (Don't know if they've fixed it since.)
I, too, wish it were possible to create an ePub that works across all platforms, but that has become a fantasy ever since device manufacturers began using image coding as their new DRM.
And since Kindle is a format all its own I don't worry about making the ePub work with Kindle. I also use Kindlegen to make my mobi files from ePubs, but I modify a copy of the ePub to make it Kindle-specific before conversion.
Thanks for the link to the Unicode Webding equivalents. Will bookmark that for later reference.
I am also in the HTML table camp. I believe the more you can do in HTML, the better. But in this case, the symbol worked well when I put the em value in both the CSS and the HTML -- no matter the ePub reader, whether it reads CSS or not, this works (at least in the few options I have to test; the author is testing on her boyfriend's Mac). And it's only the one symbol. Your Greek issue is a whole other can of worms. Yikes.