Quote:
Originally Posted by eschwartz
|
Using pattern matching in a stylesheet is an efficient - and elegant - thing to do. A pity few converters make good use of it...
Quote:
Originally Posted by Jellby
.../...
- For goodness' sake, do not force a base font..../...
|
I would say it a little differently. I propose: "
Do not name a base font without providing an easy way out". I think that any reader worth this name can change easily a base font if it's only named once in the
body. I have two reasons for doing so:
1. - Not all the fonts provide "
espaces fines" (nnbsp) even if readers using ADE 2.0 and above can read them automatically. So, I have been used to provide one font that does it as a base font. I'll add it as an attribute in the
body once for all.
There is a draw back that I heard of: some few ebook-readers - like the Nook I think? - do not recognize such an attribute in this place, but I think it's valid and standard compliant code, so I just do not pay it more attention than to some iBooks quirks (To be true, I sell nothing
).
2. - The other reason is that I like to provide PDF too (using a very nice Jellby's script) straight from my EPUB. For PDF, it's better to provide a base font because it will do nothing on its own.