On Mon, 05 Feb 2007 12:15:58 -0500 William Case wrote: > Hi Dan; > > Thanks for your reply. I wasn't initially looking for a response. My > post was mainly a Monday morning vent. However ... > > On Mon, 2007-02-05 at 10:05 -0600, Dan Lewis wrote: > > On Monday February 05 2007 9:47 am, William Case wrote: > > > Hi; > > > > > > I just spent most of Sunday building two sets of permanent > > > 'Styles'. > > > > [snip] > > > I know these remarks are very general, but much of what I finally > > > got was through dumb luck and I doubt if I could purposefully > > > reproduce all the individual problems and mis-understandings here > > > for comment > [snip] > > If your reply was simply a warning not to frighten the dog, I will > take it as that and drop the whole matter. If on the other hand I can > be useful by taking a few hours over the next couple of days > recreating my Black Sunday and analyzing where and how my problems > arose I would be glad to do so and submit them wherever useful in the > hope that any of these further comments don't just disappear into the > aether. > > > One thing that did get through is this: you are very > > frustrated. > > Yup! > > > Then again, you also created a problem for someone else: the > > person or persons who wrote the documentation. Now they can be just > > as frustrated as you. That is because they do not know where to make > > any changes to make the information more understandable: you have > > not told them. > > I thought this mail list was ignored by the real fixers and changers. > > > Specifically, what did you consult in the documentation when > > looking for help on styles? (Specific name please.) Give some > > examples of some of the problems you ran into that took so much time > > to solve. > > 'Help' = Styles > 'Manual' = Chapters 4, 6,7. > > > Did you also consult the information about templates? If so, > > what > > manual? (Templates are used to create a new document with a specific > > list of included styles.) > > 'Manual' = Chapter ? Subsection ? Templates > > I also used suggestions made on this list several months ago when I > was trying to make some minor style changes. > > > You see, without specific information as to your problems, > > there > > is no way to make sure the next person will not have the same bad > > experience. Then the time you took to write your email will have > > been wasted because no really long lasting result will have come > > from it. > > > > I am willing to help. ( My previous background is in writing reports > and analysis of many and varied non-IT subjects. i.e. businesses and > communications plans). But I don't want my time to be wasted. I > don't mind if suggestions are not used because they are wrong headed > or better answers exist. But I don't want them to be completely > ignored and just be an exercise in futility. >
With many Open Source Projects the area that gets the least input is usually documentation. The documentation team, i am sure, would welcome anyone wishing to contribute. http://contributing.openoffice.org/index.html -- Michael Those that can, do; those that can't, teach. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
