We're getting off topic here, but it's worth having a discussion anyway. > in
that case you should translate the documentation first to something> people
might read. people might read 4 or 6 pages. 60+ pages is simply> insane and
exactly nobody will read beyond page 3. Well, I think all I can say to that is
that you and I have very different ideas on what documentation is supposed to
be and do. Also, creating a "shorter" version of the documentation would not
be translating, it would be editing. > there may be legitimate reasons to
write 60+ pages documentation on a> simple PRTSCR program like for follow up
developers. The PRTSCR documentation is for users, not developers. The source
code, and especially the comments in the source code, is for developers. There
is documentation for developers (like the documentation of the USB API), but
that is not what PRTSCR.DOC is for. > however exactly no user will read it.
users fall asleep after ~2 pages> reading, if even that. Not true. I've
gotten comments from users who actually enjoy reading the documentation and
even find it "entertaining". I've never had anybody actually read it and say
it was a complete waste of time and wish they'd never done it (though I believe
some may feel that way, nobody's ever told me that). > this should be really
shortened. really. That's not going to happen, at least not be me. If
somebody else wants to edit it for their own purposes, they can do that.
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
