Quote:
Originally Posted by ElMiko
Yes, that's what I said. The "fallback" for this solution (i.e. <span>ing) doesn't result in any loss. It creates less elegant code (and is more cumbersome to apply), but there's no loss... so if I'm going to <span> anyway as a nominal fallback, I might as well make it the principal code because incorporating the nicer/easier code is redundant. In this case.
|
The advantage to the <span> is that it does not rely on the font you've chosen to embed. Any program/plaform that can override embedded fonts would mean that your ePub3 code would fail.Witht he <span>, it will work regardless of what font is used.
These are the sorts of things you have to think of. So don't do anything where you need the font you've chosen to embed. Make it work with any font if possible.