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


Wayne,

Sorry for the delay, I didn't realize that the mailinglist was filling
up my Gmail inbox, overflowing into pages and pages of unread messages
that can only been seen by paging Older Messages. I am being
overwhelmed by the mailinglist, and had to unsubscribe to get it back
under control. I will try the digest later, after I get caught up.

About that Gates memo. I have boxes containing towers of CDs -- that
memo is on one of the discs. The collections got all mixed up through
a couple of moves, and I have no idea where the key CD is. I don't
relish having to look for that. That's why I suggested Googling ODF
vs. OOXML. The memo appeared genuine, but I didn't try to verify its
authenticity. Still, Microsoft's attempt to supplant the established
ODF standards with a complicated OOXML standard is well-documented by
many independent industry observers. My point was that we should avoid
supporting that suspect "developing standard," and do all we can to
encourage document sharing in legacy Office formats or the universal
ODF standards.

This is strictly my opinion. I do not claim any special expertise in
the document format war.

On Sun, Apr 17, 2011 at 7:35 PM, Wayne Borean <wborean@gmail.com> wrote:
Roger,

Do you still have a copy of that memo?

Wayne


On Sun, Apr 17, 2011 at 7:03 PM, Roger T. Imai <roger.t.imai@gmail.com>wrote:

Problems with OOXML conversions could be seen as intended by design by
Microsoft, which is attempting to supplant the simpler OpenDocument
Format standard with its own complex inscrutable standards.

Years ago, I found a copy of a memo that appeared to be written by
Bill Gates in response to an accidental posting of the proprietary
MSOffice Document standards on a public board -- the standard was
quickly grabbed by programmers, and shortly after all the MS Office
competitors released versions that were completely Microsoft Office
XP-compliant.

But, you can probably find better information that I can provide here
by Googling  ODF vs OOXML .

I believe that the legacy Office formats are handled quite well by
open source Office applications because they had the original coding
for it, and that Microsoft is attempting to re-establish
format-dominance with its version of OOXML which is so complicated
that it is difficult to convert.


The OOXML format doesn't seem to be properly implemented by MS Office
even tho i
thought they drew up the specifications for it (i could easily be wrong
about
that and don't care if i am).  Ahh well.  Hopefully it will all settle
down a
bit soon.
Regards from
Tom :)

--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be
deleted


--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be deleted



-- 
Unsubscribe instructions: E-mail to users+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
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.