[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-documentation] Base Guide


Tom, these chapters still need a HUGE amount of work before they are suitable for release to users. John's rebranding is only a start. So don't get too excited. :-)

Jean

On 03/08/2011, at 5:34, Tom Davies <tomdavies04@yahoo.co.uk> wrote:

> Wow!!
> I must have missed this! Good work on the toughest app to write for :)
> Thanks and regards from
> Tom :)
>
>
>
>
> ________________________________
> From: John Cleland <john@john-cleland.co.uk>
> To: documentation@global.libreoffice.org
> Sent: Sat, 16 July, 2011 23:09:36
> Subject: [libreoffice-documentation] Base Guide
>
> Hi David/Jean
>
> I have rebranded the existing base documents and renamed them according to the
> the conventions in the guide. Can the existing open office ones be deleted.
>
> Thanks
>
>
> John
> --
>

--
Unsubscribe instructions: E-mail to documentation+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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

References:
[libreoffice-documentation] Base Guide"John Cleland" <john@john-cleland.co.uk>
Re: [libreoffice-documentation] Base GuideTom Davies <tomdavies04@yahoo.co.uk>
Privacy Policy | Impressum (Legal Info) | Copyright information: 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 GNU Lesser General Public License (LGPLv3). "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.