Quote:
Originally Posted by JSWolf
If the embedded font has the characters needed, then they will display on a nook as nook uses some older version RMSDK (but new enough for hyphens so it's at least equivalent to 2.0.1)
|
Great.
Pity about 1/2 width spaces for numbers and units, or thin spaces either side of dashes (not hyphens). Still, it's one less difference between eink and paper publishing sorted.
I was thinking this morning that everyone that designed ebook formats too much concentrated on existing displays, fonts in PDAs etc and current HTML at the time rather than putting a complete set of typography support and specifying how the renderers should fall back to use the local device or display limitations.
Another strange limitation lacking that could have been in ebooks from the beginning was client side image map HTML. It's dead simple. Rather than a single link with an image you have rectangles defined for each link in the image. No javascript, CSS or complex processing needed other than subtracting location selected from image location on page.