jonathon wrote:
Dave wrote:
Sophisticated computer software is a technical subject and it's
documentation cannot be reduced to "non-techie" kindergarten level.
The goal that is aimed at, is that somebody who is computer illiterate
can pick up the documentation, and do anything that the software was
designed to use.
does not mean that the documentation is badly written
Since the aim of the project is to provide usable documentation, if a
novice does not understand it, it is badly written. (Incidentally,
this is the reason why programmers should never write documentation.)
xan
jonathon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On these points of "well written" I have to agree with Dave. I have
written user documentation in the past & writing in a manner
understandable by the novice while not completely loosing a more
technical user is a hugely difficult task. Since this is largely a
volunteer supported program I can't fault the authors for targeting
those more familiar with the software. When faced with this I have
always recommended new users of software and/or hardware go out and get
some of the older books on the subject. While the old books may not
address all, or any, of the newer features a novice is not likely to use
them in the beginning anyway. What is gained from reading the older
books is a knowledge of where the new software/hardware comes from and
it is often written at, what would now be termed, a more basic level. I
teach at a junior college and it never ceases to amaze me that so many
of the students lack the very basic understanding of the tool they use
every day. Like driving a car they know how to use a program at the
basic level but never look deeper to see what else it can do. The
authors should not be insulted but neither should they have to spend the
time needed to write to the novice level. A certain degree of
responsibility goes with the user of free software to dig for some of
the answers themselves. M$ has a great many books written about their
software as part of a profit driven machine. Much of that information,
maybe not specifically but at least in part, can be used to understand
much of the free software as well. Two different cars may look
completely different with all the controls, short of the steering wheel
& brake (no clutch these days) found in different locations yet the
basics are still the same. While the description above may be one way
to accomplish the goal it is by no means the only way so the inquisitive
user can generally find one way, or another, to reach their goal.
Sorry for this but I have to much respect for all the contributors of
this, and other GNU, software to remain silent on this matter.
James
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
