Quote:
Originally Posted by kovidgoyal
Or are you saying that you want your users to read your manual only on large screens?
|
Basically, yes.
Quote:
Originally Posted by kovidgoyal
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.
|
There aren't that important
now, but who knows what the manual will contain six months from now.
And even if I had just
one code listing, having it as an unreadable and ugly mess is just not acceptable.
Quote:
Originally Posted by kovidgoyal
No I'm saying that I see no reason why a technical manual cannot be produced in EPUB.
|
I'm saying the same thing. I could produce this manual in epub format, but I'd be sacrificing a lot of what I wanted to achieve. There are other manuals out there that wouldn't have to sacrifice anything.
Quote:
Originally Posted by kovidgoyal
And I'm not a EPUB zealot, I am however a reflowable format zealot.
|
That's the point I was trying to make. The reflowable vs. fixed war which I think is borderline retarded. Both have their pros and cons, and accordingly both have their uses.
The world is not black and white.
Quote:
Originally Posted by kovidgoyal
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.
|
You got the wrong sense. Have I mentioned I make about a hundred epubs a year, all in "direct" HTML + CSS without the use of Sphinx?
Quote:
Originally Posted by kovidgoyal
In other words, you are not presenting a coherent case for why you can't make the manual in EPUB.
|
I'm tired of this argument and I won't try to convince you anymore.