Quote:
Originally Posted by Valloric
That's not the only reason Kovid. There are aesthetic ones as well.
|
Yes, but the aesthetic ones are only relevant if the reading area is large. Or are you saying that multiple columns of one word length look good?
Quote:
I've bolded the relevant bit.
|
I agree it's not ideal, but is it really that bad?
Quote:
Yes, in that case it will flow of the edge of the screen. That's far, far worse.
|
As opposed to PDF? Or are you saying that you want your users to read your manual only on large screens? In which case, I say, that code samples are not the most important thing in your manual and sacrificing reader flexibility for them, is the wrong trade-off.
Quote:
You remind me of the PDF zealots. You know, the people who say that epub is useless and that everything should be typeset by hand and provided as PDF? You're just doing the reverse.
|
No I'm saying that I see no reason why a technical manual cannot be produced in EPUB. And I'm not a EPUB zealot, I am however a reflowable format zealot. I think that any document that claims to disseminate information in the form of language should not restrict the the ability of the user to consume/manipulate that information as flexibly as possible.
In other words, you are not presenting a coherent case for why you can't make the manual in EPUB. The sense I get is that you tried sphinx, didn't like its methodology/output and so decided to give up on producing a reflowable manual.