Quote:
Originally Posted by Valloric
That doesn't do what you think it does. An HTML character reference is merely a convenient way of specifying the use of a character that is not easily written using ASCII alone. Basically, aside from comfort and user preference, there is no difference in using a character reference instead of a "real" UTF-8 character.
You still need a font with the required glyph to render a non-ASCII char.
There is no "HTML" font.
|
{sigh}. Yes, I know that. I guess what I was trying to determine was whether Luise had a
unique symbol-rendering problem; something that isn't normally available in the "usual suspects" like TimesNewRoman or Arial, etc.
AND,
I should have added that I'd already been down the rabbit-hole with Apple, those jacka$$e$, and knew that the embedded-font-thing was a killer for them. (And don't get me started on the whole "you have to have a Mac computer to be an authorized publisher" rant that I have stored up!!)
And, @troymc, while I agree with you in principle, my clients don't. They want to be on iPads, iBooks, iSuck, whatever. They want two things, and two things only: Kindle and Apple, no more, no less. Oh, and the occasional Nook (epub, obviously). So if the 900-lb. gorilla is going to make the sign of the (vampire) cross at embedded fonts, I'm not going to use them.
Hitch