Here are my responses.
1. I seldom look at the PDF documentation. Mostly I find what I need
through the F1 key, and also because I forget it's there until I go
searching for an answer online. I'll also go to the PDF when I'm trying
to understand an entire concept (like styles, which still are winning
2. I use the F1 key all the time. I came to LO after using Windows
since it was created and F1 is the first thing I do to get help on any
program. It's nice when it's context-sensitive, but just going to the
built-in help is sufficient.
3. Most of the time I'm using any documentation it's via the F1 key (or
the menu equivalent, if I already have my fingers on the trackpad) and
I'm usually coming from a spreadsheet, looking for the parameters for a
specific function. This is one of the few areas where in my experience
MS Office is actually superior to LO; in MSO the functions are grouped
better for ease in finding what you're looking for (arithmetic
functions, logical functions, etc.). In the LO help you often have to
know what function you want to use, even if what you're looking for is
what function fits your current need -- like having to know how to spell
a word before you can look up its spelling in the dictionary.
4a. Some have suggested videos. Personally, while I have no trouble
with either my vision or my hearing, I hate the trend toward doing
everything on videos. They take longer than reading, they annoy other
people in the office, and usually they're not the best choice for what I
need at the time. They might be useful for longer topics (like those
blasted styles), but not for syntax questions, for example.
4b. My preference is for a manual's information to be available
locally. I'm not always in a location with Internet access, and
sometimes I turn off my modem because I don't want any new mail
downloaded (I have 18 mailboxes to manage, and if I close the email
program before I check them all then the new messages are no longer
flagged as new; unread isn't a sufficient status).
Thanks for asking for our input. I've rewritten seven sets of bylaws
for various organizations, so I don't envy you and the rest of the
volunteers on this project!
On 6/24/2015 09:58, dallen wrote:
I'm an experienced Technical Writer beginning work on LibreOffice's
documentation, but I have some questions for LibreOffice users:
1) Does anyone EVER look at the pdf documentation? If not, why not?
2) Does anyone EVER click the F1 key for help? If not, why not?
3) Do you see any overall issues concerning the documentation?
4) If the presentation of the documentation were to change to make it
more useful, what would it look like?
Thanks for anyone's help.
View this message in context:
Sent from the Users mailing list archive at Nabble.com.
To unsubscribe e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] LibreOffice's documentation (pdf and online) · Dave Liesse
Re: [libreoffice-users] LibreOffice's documentation (pdf and online) · Doug
Re: [libreoffice-users] LibreOffice's documentation (pdf and online) · Gary Collins
Re: [libreoffice-users] LibreOffice's documentation (pdf and online) · James E Lang
[libreoffice-users] Re: LibreOffice's documentation (pdf and online) · CVAlkan
- [libreoffice-users] Re: LibreOffice's documentation (pdf and online) (continued)
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