ghrt wrote:
Gary Schnabl wrote:
ghrt wrote:
I think it will be a good idea to have different folders for
different OOo versions. A guide with some chapters on 2.2 and others
on 2.3.0-dev, with diffs between the software versions, it will be
at least unusable.
Version 2.3, being readily available and being actively pushed for
volunteers to test it, means that it is nearly ready for stable
distribution. Drafting documents for 2.3 should be the norm instead
of writing/editing the documents for a version that will soon be
technically obsolete.
Yes, i agree, but i said another thing: to have different folders for
different software versions, ie 2.2, 2.3 and so on. As a translator,
i'm always "a little late" and I might get half a book with 2.2 and
the other half with 2.3. Of course, i took all the chapters from the
beginning with the same version, but mixing them at oooauthors makes
impossible to get latest version on 2.2 since only 2.3 is on site.
That's the idea. Now I think we have diff folders only for major
changes, like 1.x and 2.x.
Sorry for my english.
A major problem at OOo and OOoAuthors is that the current documentation
is usually quite a bit behind the then-current implementation. What is
passed off as being 2.2 or whatnot is not really as current as it seems.
Any changes in the GUI or new functions are not always covered, and some
elements apparently have never been covered in the docs or in the online
help--especially the online help.
That is obviously due to a shortage of writers, mostly. Personally, I do
some technical editing but little writing outside of rewriting poor
English or repairing obvious technical errors or omissions.Also,
occasionally some of the procedural steps leave holes because they tend
to be incomplete or don't cover all the GUI components or functions.
Also having various pigeon holes for parking docs for the various
incremental or major versions would necessarily be rather incomplete and
would accomplish little worthwhile, to my way of thinking. It's best to
always be at the cusp of the latest version--even if that means using
beta or RC versions. Using the current implementation for writing would
mean that catching up would be very difficult and might fall even
further behind. Besides, I never saw any practical sense of maintaining
anything of the older, obsolete versions of the docs.
--
Gary Schnabl
2775 Honorah
Detroit MI 48209
(734) 245-3324
