Christian Lohmaier wrote: > > Referring to other documentation is a good sign that the procedure is > > complicated. > > No. It is just a sign that there are many ways to achieve things.
You just proved that you are not familiar with writing documentation. Giving people a dozen pages to read to "give them choice" is incredibly counter productive. Jean is an expert at writing documentation, she has been doing it professionally for 40 years. Please take her advice. > > But only at the expense of yet another barrier. > > What barrier? Requiring Win users to learn Cygwin is another barrier. A big one. > And a personal note as well: I don't think that anyone confident with > linux/unix will have problems with these instructions. > The only thing is that you must be willing to read the /whole/ thing. This is a very good example of what's wrong with your attitude. You are blaming the user for not understanding the documentation. I am confident with Unix/Linux, I have been using it exclusively for several years. I program in it, I write shell scripts every day, I already even had experience with CVS, through my involvement in the Mono project. And I had a very hard time plowing through this. Second: Your target audience is *not* "confident Unix users". Do you see that? You cannot assume that the user is confident with a Unix shell. You can't assume that the user knows what the heck a Unix shell is. And as long as you don't see that, the documentation will remain un-useful. -- Daniel Carrera | I don't want it perfect, Join OOoAuthors today! | I want it Tuesday. http://oooauthors.org | --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
