Hi,
e-letter wrote on 2011-09-11 10:54:
Following discussion on the users mailing list (search subject field
above and posts 'Should LibreOffice even support Microsoft secret
formats?' 10-09-2011; 'ignore m$ legacy?' 20-07-2011, it is requested
to create a mailing list for users who are_not_ interested in
compatibility other software, but the primary concern being superior
behaviour of LO in creating odf documents.
Suggested mailing list name:usersodf@...user support list for LO
users that want to create documents primarily in the native odf.
I don't see a real need for this list. The users list is about using
LibreOffice, including all its features and functions. Of course, the
primary focus is on ODF, as ODF is our primary document format - having
a second list will only split the knowledge and lead to more confusion.
Just my two cents, happy to hear other thoughts...
Florian
--
Florian Effenberger <floeff@documentfoundation.org>
Steering Committee and Founding Member of The Document Foundation
Tel: +49 8341 99660880 | Mobile: +49 151 14424108
Skype: floeff | Twitter/Identi.ca: @floeff
--
Unsubscribe instructions: E-mail to website+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/website/
All messages sent to this list will be publicly archived and cannot be deleted
Context
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 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.