Quote:
Originally Posted by AliceWonder
Wasn't suggesting to use it for the paragraph text, but ePub uses html and both 'pre' and 'code' elements are suppose to render with a monospace font.
So like it or not, readers that do not have a monospace font have incomplete support for the specification which unfortunately requires books that do use pre and code to include a monospace font to deal with those readers.
Maybe not very many books need those tags, but they are part of the standard.
|
Forget pre and code. They can be a rather large fail. I've seen too many instances where the text it too long for the width of the screen and it just goes off to the right not to be fully seen. You cannot control this as you won't know what font size is going to be used or what size screen is going to be used.
What is it you need to use a monospace font for? Is it something you can use the default sans-serif font instead?
Also, Hitch is a professional and knows what she is talking about when it comes to fonts. I agree as I've seen plenty of embedded fonts that are a big fail. What to do is make a test eBook that embeds the fonts you want and try them with a 300DPI eInk Reader and see how they look. Do they have enough weight? My guess is no they don't.