Quote:
Originally Posted by Jellby
Only "dangerously close", not quite there 
What I mean is that you want too much control on the typesetting, and that's something that the readers (both software and human) should have a say on.
With a real typesetting engine like (La)TeX, you can control on a global scale how much hyphenation you want, or how much whitespace you allow.
I dream of a day when my ebook reader will let me set up something similar and decide, given my preferred font family and size, what kind of hyphenation I find acceptable (maybe not more that two consecutive hyphenated lines, maybe not fewer than 4 characters from a word left in a line, maybe only if the word spaces are stretched to 1.5 times their natural size...). And I being an idealist after all, keep writing my ebooks so that they'll work in such a day.
It seems CSS3 at some point offered that kind of control, but not at the current stage. Prince does offer more options, if you want a PDF. |
Jellby:
You know I love ya, but, dude: we already
have PDF. The more "geeky" reading apps are approaching this type of customization, but what you guys have to think about is, the less the reader (human) can customize the end-product to be what THEY want, the more likely they are to bitch about it.
We already hear about readers who want to be able to change absolutely everything (visit the Calibre forum on any given day for a sampling)--font, font-size, hyphenation, no-hyphenation, margins, no margins...the closer you get to "forcing" the reader to use what you want, the further away you get from younger and younger readers, all of whom want to be able to manipulate the text to their unique requirements.
Just sayin'.
Hitch