[Tex2002ans]

Originally Posted by eggheadbooks1

Thanks, Tex, for taking the time to create a test book, screenshots, and the code for embedding a font. Much appreciated.

Originally Posted by eggheadbooks1

I am curious, though, as to why you included SSs of Kindle. Kindle reads the Unicode without the need to embed the font. (I am naming my firstborn after Doitsu for that.)

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.

Many of us try to settle on solutions that work across formats, instead of having to annoyingly create format- and vendor-specific EPUBs (one set of code for Apple, one set of code for ADE, one set for Nook, one set for Amazon, [...]).

Originally Posted by eggheadbooks1

I do know how to embed a font, but I wrongly thought the symbol was only available in Webdings (which the author used), and Webdings is copyrighted.

I believe almost all of Webdings symbols have an equivalent UTF-8 character. Here is a giant table of equivalents:

http://www.alanwood.net/demos/wingdings.html

Side Note: I forget if Toxaris's EPUB Tools handles the conversion of Webdings -> UTF-8? I know that Toxaris implemented the Symbol font -> UTF-8 after we came across some Greek/Math shenanigans.

Originally Posted by eggheadbooks1

The problem with font embedding is 1) not all ereaders support font embedding; 2) if the user turns off publisher formatting, the symbol will disappear; 3) if the ereader does not read CSS, the symbol will disappear.

Indeed indeed. If I didn't lay out my typical list of Pros/Cons in that Apple Symbol topic, I would add that as a Con for the Font Embedding method. I typically like to organize all of the Pros/Cons I can think of, and leave it up to you to decide which method you want to go with.

Personally? I have settled on using the UTF-8 characters + Font Embedding. If the device doesn't handle UTF-8 reasonably AND can't handle fonts? Too bad, that is on them.

Side Note #1: Similar to your music notes, I run into this situation all the time with Polytonic Greek characters. Many fonts/devices don't have some of the more obscure accented Greek characters. That won't stop me from actually using the actual UTF-8 characters. All of the Pros of actual characters heavily outweighs the Pros of a bitmap (in my mind).

Would you rather read this?

[...] cannot therefore conceive that social institutions could have arisen in any way except through the intervention of a ‘world shaper’ of the Platonic

or this?

[...] cannot therefore conceive that social institutions could have arisen in any way except through the intervention of a ‘world shaper’ of the Platonic δημιουργὸς.

I don't believe I can upscale that image in ems on MobileRead, but you can imagine how crappy that would look compared to the pure text. The problem with bitmaps only gets worse the higher DPI becomes as well.

(This was an example of Greek Images used in one of the latest books I fixed.)

Side Note #2: Back in 2014, we also had a nice discussion about Image/SVG/HTML Tables:

https://www.mobileread.com/forums/sho...69#post2850269

Almost all of the same exact arguments apply here (as you can probably guess, I am in the HTML Tables camp). :P You can also see example images where I changed the background to black + red font.