Hello
Why are there missing words and spelling errors in some LibreOffice
manuals/texts? Are these drafts?
Because it's powered by a group of volunteers working countless hours to
provide a free product...are you interested in helping to correct the
errors?
Best,
Joel
Hi 
More to the point, is it possible to point out some of the alleged errors?
Is it just one of the published guides, such as the first iteration of the
Base Handbook? It's very rare to hear of any errors with the published
guides as found on these pages;
https://wiki.documentfoundation.org/Documentation/Publications
http://www.libreoffice.org/get-help/documentation/
These guides are often found to be by far the best documentation for
LibreOffice.
If you are referring to the inbuilt help then it makes more sense because
those are carefully written to make it easier to translate into man
different languages. The work for those is done by a tiny team of
non-English speakers and they tend to be a little geeky sometimes.
Similarly with the wiki-pages which tend to focus on just achieving a task
rather than necessarily being perfect English, if such a thing exists
anyway.
This is a truly multinational and multilingual project. People at all
levels come from a wide variety of countries, backgrounds and levels of
English. If you would rather see documentation in your own language then
you will find the in-built help tends to be far better - and the main
website is available in a multitude of different languages too
Regards from
Tom
Which _specific_ manuals/texts are you referring to here? Some of the
publicly available is at has been through multiple copy-edits, style
edits, and line edits. Most of the documentation is somewhere between
those two points.
jonathon
Due to my semi-retirement and other time constraints, I haven't done any LO editing anytime recently. However, my guess for any "missing" words and such in LO's working documentation could be related to some conditional or hidden text being used. LO Writer is somewhat limited in its conditional text, though. So, it's likely that there is none.
When I was a technical editor at Motorola (and its Freescale Semiconductors subsidiary), working on their firmware-developer user guides for the assemblers, compilers, linkers, and SDKs for the numerous, various families of their embedded microcontrollers, they employed master working documents using Adobe FrameMaker conditional text for almost all of those developer manuals, some of which had over two dozen output versions, depending upon with semiconductor family was covered.
If viewing a master document that was not properly set up for viewing any conditional text, that document would have literally thousands voids of "missing" text--or if set up differently (showing all of the conditional text simultaneously), that document would cover all the variations of conditional text for all those semiconductor families--one huge jumble of multicolored text, in numerous, separate colors for each output version.
HTH,
Gary