<html><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:10pt"><div>Hi :)</div><div>Moving away from MS formats seems a pretty smart move around now. There are so many different versions of XlsX (2007's version, 2010's and now presumably 2013's). <br><span></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;">I thought Keith's post was interesting because it seems people have spent some serious money just to find out what we already felt was the case. I think Google still are a supporter of TDF but seem to have lost their way a bit. <br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family:
verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;">Regards from</div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;">Tom :) <br><span></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><span></span></div><div><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div style="font-family: verdana, helvetica, sans-serif; font-size: 10pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Keith Curtis <keithcu@gmail.com><br> <b><span style="font-weight: bold;">To:</span></b> Zeki Bildirici
<zeki@ozgurlukicin.com> <br><b><span style="font-weight: bold;">Cc:</span></b> marketing@global.libreoffice.org <br> <b><span style="font-weight: bold;">Sent:</span></b> Tuesday, 5 March 2013, 22:50<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [libreoffice-marketing] Google and ODF support!<br> </font> </div> <br>That is amazing. Google wrote this in their analysis of OpenXML:<br>(<a href="https://forums.scc.ca/forums/scc/dispatch.cgi/public/showFile/100294/d20070705225348/No/objections%20by%20Google.pdf" target="_blank">https://forums.scc.ca/forums/scc/dispatch.cgi/public/showFile/100294/d20070705225348/No/objections%20by%20Google.pdf</a>)<br>-----<br>"Although OOXML may formally comply with Ecma, it was clearly not<br>designed with an “open” spirit. Comparing the current with the future<br>situation, interoperability is likely to become more difficult instead<br>of easier. The implementation of a fully compatible ODF
importer (the<br>current efforts regarding .doc and .xls) is not an easy task, but it<br>is dwarfed by the implementation of a fully compatible OOXML importer,<br>which we estimate to take something between 50 – 500 person years, or<br>even longer. Therefore, although it is theoretically possible to<br>generate an OOXML document, this document will probably only use a<br>very small subset of the standard.<br>In sum, OOXML can be compared to Microsoft giving access to a<br>labyrinth to which it alone owns a map; moreover, certain tunnels<br>within this labyrinth are not accessible without a key that only<br>Microsoft has, and that third parties would need to replicate first.<br>(And, in doing so, these third parties would not know whether they<br>would violate any rights that exposes them to litigation)."<br>-----<br><br>It is sort of sad Google would reverse course and act against their<br>own interests. Also, I wonder why they didn't help to port
LibreOffice<br>rather than buying QuickOffice. The current Android efforts in<br>LibreOffice are less than one person I believe. Imagine what Google<br>could have done with 5-10, let alone buying the proprietary<br>QuickOffice which employed 400 people.<br>(<a href="http://seattletimes.com/html/localnews/2018361838_apustecgoogleofficeapps1stldwritethru.html" target="_blank">http://seattletimes.com/html/localnews/2018361838_apustecgoogleofficeapps1stldwritethru.html</a>)<br>I suspect part of their decision was that they didn't want to take a<br>risk on "LibreOffice", but it does seem they have too much money.<br><br>-Keith<br><br>On Tue, Mar 5, 2013 at 1:38 PM, Zeki Bildirici <<a ymailto="mailto:zeki@ozgurlukicin.com" href="mailto:zeki@ozgurlukicin.com">zeki@ozgurlukicin.com</a>> wrote:<br>> Hi,<br>><br>> As you know Google currently is not supporting Open Document Format<br>> native in its services. Today i saw this article<br>> <a
href="http://www.muktware.com/4529/why-google-killing-open-document-formats#.UTYr7U44lHE.twitter" target="_blank">http://www.muktware.com/4529/why-google-killing-open-document-formats#.UTYr7U44lHE.twitter</a><br>> and remembered this issue.<br>><br>> This article explains the situation quite well. I don't know the<br>> reason why Google does not support ODF, maybe it was discussed here<br>> before. But i think we may try to push Google to support ODF.<br>><br>> I don't think there is a reasonable explanation for ignoring ODF and<br>> supporting MS Office formats and forcing people to convert their ODF<br>> to Google Docs format.<br>><br>> Btw for comparasion, -yes not Skydrive of course- Yandex company with<br>> growing popularity in Turkey and Russia supports ODF in its Disk<br>> service. It may be an example for good aproach to ODF.<br>><br>> What do you think about Google's positioning for ODF? Can we
manage to<br>> force/attract Google to support ODF? I've mentioned and asked<br>> htps://twitter.com/cdibona about this matter but no replies yet<br>><br>> Best regards,<br>> Zeki<br>><br>><br>> - <a href="http://support.google.com/drive/bin/answer.py?hl=en&answer=2423485" target="_blank">http://support.google.com/drive/bin/answer.py?hl=en&answer=2423485</a><br>><br>> --<br>> Unsubscribe instructions: E-mail to marketing+<a ymailto="mailto:help@global.libreoffice.org" href="mailto:help@global.libreoffice.org">help@global.libreoffice.org</a><br>> Problems? <a href="http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/" target="_blank">http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/</a><br>> Posting guidelines + more: <a href="http://wiki.documentfoundation.org/Netiquette" target="_blank">http://wiki.documentfoundation.org/Netiquette</a><br>> List archive: <a
href="http://listarchives.libreoffice.org/global/marketing/" target="_blank">http://listarchives.libreoffice.org/global/marketing/</a><br>> All messages sent to this list will be publicly archived and cannot be deleted<br>><br><br>-- <br>Unsubscribe instructions: E-mail to marketing+<a ymailto="mailto:help@global.libreoffice.org" href="mailto:help@global.libreoffice.org">help@global.libreoffice.org</a><br>Problems? <a href="http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/" target="_blank">http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/</a><br>Posting guidelines + more: <a href="http://wiki.documentfoundation.org/Netiquette" target="_blank">http://wiki.documentfoundation.org/Netiquette</a><br>List archive: <a href="http://listarchives.libreoffice.org/global/marketing/" target="_blank">http://listarchives.libreoffice.org/global/marketing/</a><br>All messages sent to this list will be publicly archived and
cannot be deleted<br><br><br> </div> </div> </blockquote></div> </div></body></html>