Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


On Fri, Nov 9, 2012 at 8:22 AM, Florian Monfort
<florian.monfort@gmail.com>wrote:

I suggest we actually get in touch with Google itself.

Here's the thing:
On the Google and Open Source Keynote [1] at the LibreOffice conference, a
similar topic was brought up by an audience member, and the reason why
Google's focusing efforts on OOXML instead of ODF is simply because there
isn't visible demand for ODF -- hence the idea to make #WeWantODFSupport
trend on Google's own social network.

On Fri, Nov 9, 2012 at 12:59 AM, Adolfo Jayme Barrientos <
fitoschido@gmail.com> wrote:

I’m not sure, isn’t that a bit too much political? Don’t think it’s
appropriate for the official G+ page. Also, it’s kind of unrelated to
design.


As above, I believe having #WeWantODFSupport trend is the best bet for
getting Google to support ODF, and the only way to get that is through the
official LibreOffice pages, I believe.

Any alternative suggestions appreciated, though.

[1]
http://conference.libreoffice.org/program/wednesday-premier-track/keynote

-- 
Unsubscribe instructions: E-mail to design+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/design/
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.