<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Is Microsoft Office in trouble?</title>
	<atom:link href="http://practical-tech.com/business/microsoft/is-microsoft-office-in-trouble/feed/" rel="self" type="application/rss+xml" />
	<link>http://practical-tech.com/business/microsoft/is-microsoft-office-in-trouble/275/</link>
	<description>for practical people.</description>
	<lastBuildDate>Fri, 30 Mar 2012 02:51:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: aristaeus</title>
		<link>http://practical-tech.com/business/microsoft/is-microsoft-office-in-trouble/275/comment-page-1/#comment-97</link>
		<dc:creator>aristaeus</dc:creator>
		<pubDate>Sat, 24 May 2008 08:13:47 +0000</pubDate>
		<guid isPermaLink="false">http://practical-tech.com/?p=275#comment-97</guid>
		<description>I would say they are doing this:

1) Because they actually obfuscated the OOXML code to such a high degree of complexity and IN-OPERABILITY (they lost the *ter* somewhere) that even they can no longer use it.
2) To appease the EU and the UK Government (which as we know, publicly stated that it was transitioning to open source, or at least open standards, just before the latest Microsoft *closed-source, closed-doors*(TM) negotiations started up again.
3) To sell copies of the pricey MSOffice 2007 by promising that it, and only it, will support ODF, eventually.
4) Cleverly, they are actually NOT currently supporting ODF, they are just so far *saying* that they will do this perhaps sometime next year.   To buy time...perhaps to resurrect the specter of OOXML from the ashes of dead code?</description>
		<content:encoded><![CDATA[<p>I would say they are doing this:</p>
<p>1) Because they actually obfuscated the OOXML code to such a high degree of complexity and IN-OPERABILITY (they lost the *ter* somewhere) that even they can no longer use it.<br />
2) To appease the EU and the UK Government (which as we know, publicly stated that it was transitioning to open source, or at least open standards, just before the latest Microsoft *closed-source, closed-doors*(TM) negotiations started up again.<br />
3) To sell copies of the pricey MSOffice 2007 by promising that it, and only it, will support ODF, eventually.<br />
4) Cleverly, they are actually NOT currently supporting ODF, they are just so far *saying* that they will do this perhaps sometime next year.   To buy time&#8230;perhaps to resurrect the specter of OOXML from the ashes of dead code?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

