Code:
Ligatures (like swash caps, text figures and other typographic variants)
are not part of the UTF spec and you can't rely on programs to recognise such font-specific alternative characters.
If you want to use them, make sure they're embedded as explicit escape sequences from the start.
Ah. Makes sense - finally - thanks. So much for that idea.
Code:
Code:
font-family:"Minion Pro","Dutch801 Rm BT","Times New Roman","Goudy Old Style","Baskerville Old Face","Georgia",serif;
Are these font part or the ePub or are they just installed in your system?
That's the ccs I'm using in the epub, which "should" represent a preferred font sequence. I've got some weirdo ideas about compensating for double quotes that the indent numbers only work with certain fonts on, and without embedding, I've got to depend on the idea that someone else has the 'right' font(s) installed on their system.
If I make the call
Code:
font-family: serif;
then I am increasing the chance they won't have a font defaulted to on their system that works with my metric design on their system, having the overall look get slaughtered, and run the risk of further complaints and ridicule.
Oh, like I'm not gonna get that anyway for having such a lame idea.
-bjc