Quote:
Originally Posted by Hitch
My take on that is, if it changes down the road (the standard, for whatever reason), great, change the accursed things then. For the time being, like Occam's Razor, the simplest answer is usually the right one. Embedding symbol fonts for something that can be accomplished with plain old vanilla html is, I think, just over-the-top. PLUS, you don't have the pesky 1.05 epub validation thing to worry over, at least about this.
Good luck!
|
While I agree with your statement in principle, Kivgaen appears to being do this as a publisher. And as a publisher Occam's Razor is usually on the side of doing things correctly the first time and not having to waste time & manpower going back in a couple of years to search through their entire catalog to find and correct things.
But it is a tradeoff they have balance. Maybe getting the product out the door quickly now is worth the costs involved in possibly having to go back and fix things in the future. Keep in mind reputation is a cost too. Will you be known for putting out top-quality ebooks? or for pushing stuff that only works on iPads? or Kindles? and work poorly, if at all on other devices?
That being said, the four symbols mentioned are extremely basic and I would expect them to be in any unicode font deserving of the name. But if there's any risk - embedding a font is trivial.
Troy