I agree that the aim is to be as comfortable to read as possible. i think
the guides need have a balance between being noob-friendly and being
tolerable for geeks.
A lot of computer-savvy users know the term "how-to" and "read-me" and it
would be good to introduce those terms to people that don't already know
them. Many terms are likely to crop-up elsewhere such as forums. As an
initial introduction and gateway into OpenSource programs such as
LibreOffice (and Firefox) 'should' prepare people by introducing such terms.
Using existing widely used guidelines seems sensible unless they are under
copyright or difficult to access or where they perpetuate inaccuracies or
For people who don't understand English as a 1st language we would hope that
the official documentation gets translated into something they feel more
comfortable with. MTs (Machine translators) are sometimes hilariously wrong
or inept. Their output needs to be at least proof-read by a human being
that understands implications and nuances of the target language.
Btw you can look at the thread in Nabble to see how your post got treated.
It didn't get split up. At least i don't think it did!
View this message in context:
Sent from the Documentation mailing list archive at Nabble.com.
Unsubscribe instructions: E-mail to email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/documentation/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy