On 08/11/2011, at 4:04, David Nelson <email@example.com> wrote:
On Mon, Nov 7, 2011 at 12:24 PM, Jean Weber <firstname.lastname@example.org> wrote:
And I'm not sure who is in charge of the Help, but I don't think it's us.
Erm, actually, the devs do seem to think it is us, which I find fairly
logical. That's why they keep CC'ing me all bugs involving the
I guess we could currently consider me to be first custodian of
built-in help issues, although *anyone* is welcome to work on them.
I'll be happy to foster anyone wanting to tool up for the job.
Ah, OK. That brings us back to the original question: where are the Help source files? And related
questions about how/where/when to write/edit the Help. Is this work all tracked through the
issue/bug system? Devs say "here is a new or changed function or dialog box which needs Help
I'd like to add something, even if (at this point) brief and general, to the Documentation
Contributors Guide. I know little or nothing about it, but I do recall discussion at several times
over the past year. And i know that, because the Help is shipped as part of the product, it's
handled differently from the user guides and other docs we deal with here.
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
Re: [libreoffice-documentation] LibO Documentation · David Nelson
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