Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

[News] ODF is the Future, But Microsoft is Caught Lying Again

  • Subject: [News] ODF is the Future, But Microsoft is Caught Lying Again
  • From: Roy Schestowitz <newsgroups@xxxxxxxxxxxxxxx>
  • Date: Wed, 05 Sep 2007 09:13:20 +0100
  • Newsgroups: comp.os.linux.advocacy
  • Organization: Netscape / schestowitz.com
  • User-agent: KNode/0.10.4
OOXML, the past. ODF, the future.

,----[ Quote ]
| ODF was already doing well and now has renewed momentum. Go with it.


Microsoft denies OOXML has 'proprietary hooks'

,----[ Quote ]
| As Australia and various other nations prepare to vote on whether Microsoft's 
| Open Office XML becomes an ISO standard, the Redmond giant is attempting to 
| downplay fears that OOXML adopters will be hooked into the company's 
| technology.   


Wrong. OOXML = Microsoft Office + Microsoft Windows. They try very hard to deny
OOXML's incompleteness. Watch this older item:

Bill Gates on Interoperability

,----[ Quote ]
| Bill Gates is wrong here. Most open source software goes hand in hand with 
| interoperability. Why? Open source software is usually written to open 
| industry standards with the GPL. You don't have to buy an expensive license 
| or sign an NDA to get the specifications to be interoperable. There are no 
| restrictions or barriers to entry, except for whats contained in the GPL. 
| Bill's open source statement is just more rhetoric and FUD.     
| Microsoft is playing catch up with the industry. The industry is tired of bug 
| infested, high cost, security risked proprietary software (Windows and .NET 
| platform). The XML standard is providing the interoperability, not Microsoft.   


Just shows you what Microsoft thinks about interoperability.


[OOXML:] Competition Optional

,----[ Quote ]
| In previous posts I have pointed out numerous "features" in OOXML which 
| cannot be implemented by anyone else but Microsoft. These stem from a variety 
| of causes, including elements lacking definition ("lineWrapLikeWord6") to 
| features that are tied to Windows or Office (e.g., Windows Metafiles) to 
| items that are "merely referenced (OLE, digital ink) to items that although 
| featured prominently in Office marketing materials, are curiously not 
| mentioned at all in the OOXML text (scripts, macros, DRM, SharePoint, etc.). 
| When these issues are raised, the typical response from Microsoft has been 
| along the lines of, "Don't worry, these features are optional. You don't need 
| to implement them. They are there for implementations that know what they 
| mean. If you don't understand them, you can ignore them."          


,----[ Quote ]
| From: Bill Gates
| Sent Sunday, October 06, 1996 11:54 AM
| To: Bob Muglia
| Cc: Aaron Contorer; Richard Fade; Steven Sinofsky; Paul Maritz; Nathan 
| Myhrvold; Brad Silverberg; Adam Bosworth
| Subject: Access, Internet studio, VB and other overlapping products
| ..
| Why is the difference between Internet studio and Access? I can't detect 
| any reasonable difference. Internet studio has taken an approach of 
| putting onto HTML pages the most ugly Microsoft garbage ever seen since 
|              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| COM/OLE programming in C++ was declared a success in order to block 
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| language invocation. i am still blown away by seeing all those ugly
| ^^^^^^^^^^^^^^^^^^^ 
| PARAM statements in the HTML totally confusing anyone who tries to do 
| anything. If something isn't part of the WYSIWYG output then it should 
| be succinct and understandable. This was the opposite of that.


[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index