<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.networkworld.com/community" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Microsoft Word</title>
 <link>http://www.networkworld.com/community/taxonomy/term/8491</link>
 <description>Showing new posts in a forum view</description>
 <language>en</language>
<item>
 <title>How to keep Word from loading dangerous RTF files</title>
 <link>http://www.networkworld.com/community/node/27846</link>
 <description>&lt;p&gt;Even if your users are completely trained to never  open Word files with funky extensions, dangerous documents can come&lt;img src=&quot;/Micronet images/security-lock.jpg&quot; border=&quot;1&quot; alt=&quot;&quot; hspace=&quot;1&quot; vspace=&quot;1&quot; width=&quot;66&quot; height=&quot;70&quot; align=&quot;right&quot; /&gt; disguised with a friendly &amp;quot;.doc&amp;quot; extension. The &lt;a href=&quot;/subnets/microsoft/&quot;&gt;May Patch Tuesday&lt;/a&gt; included an update that fixed a hole in Word relating to malicious RTF and HTML files, says &lt;a href=&quot;http://blogs.technet.com/swi/archive/2008/05/13/file-block-and-ms08-026.aspx&quot;&gt;a post in the Microsoft Security Vulnerability Research &amp;amp; Defense &lt;/a&gt;blog. However, if your users don&amp;#39;t use, or rarely  use, Word to open RTF or HTML documents, you may be better off blocking those files from loading in Word altogether. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/27846&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;</description>
 <comments>http://www.networkworld.com/community/node/27846#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/123">Microsoft</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/12064">file blocking</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/4769">Microsoft security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/8491">Microsoft Word</category>
 <pubDate>Thu, 15 May 2008 16:44:14 -0400</pubDate>
 <dc:creator>Microsoft Subnet</dc:creator>
 <guid isPermaLink="false">27846 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>Word 2007 documents don&#039;t meet OOXML standard</title>
 <link>http://www.networkworld.com/community/node/27101</link>
 <description>&lt;p&gt;Now that Microsoft has gotten Office Open XML (&lt;a href=&quot;/Micronet%20images/documents.jpg&quot;&gt;OOXML&lt;/a&gt;) accepted as a standard by the International Organization for&lt;img src=&quot;/Micronet%20images/documents.jpg&quot; border=&quot;1&quot; alt=&quot;&quot; hspace=&quot;1&quot; vspace=&quot;1&quot; width=&quot;66&quot; height=&quot;66&quot; align=&quot;right&quot; /&gt; Standardization (ISO), it has found itself in an interesting dilemma. Changes were made to OOXML at the ISO ballot resolution meeting and because of this, Office 2007 documents no longer conform to the current standard (ISO/IEC 29500). So says Alex Brown, leader of the ISO group responsible for maintaining the OOXML standard, &lt;a href=&quot;http://www.griffinbrown.co.uk/blog/PermaLink,guid,3e2202cd-59a3-4356-8f30-b8eb79735e1a.aspx&quot;&gt;in his blog&lt;/a&gt;. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/27101&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</description>
 <comments>http://www.networkworld.com/community/node/27101#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/123">Microsoft</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/8491">Microsoft Word</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1279">ODF</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/4673">OOXML</category>
 <pubDate>Mon, 21 Apr 2008 14:15:48 -0400</pubDate>
 <dc:creator>Microsoft Subnet</dc:creator>
 <guid isPermaLink="false">27101 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>Vista Update Craters Microsoft Word</title>
 <link>http://www.networkworld.com/community/node/23685</link>
 <description>I came downstairs this morning to find my Vista computer applying fixes and  then rebooting. Yesterday six new updates were installed automatically by  Windows Update. &lt;p&gt;&lt;img style=&quot;float: right&quot; src=&quot;http://theconvergingnetwork.com/images/Word_stopped_working.jpg&quot; alt=&quot;Word stopped working&quot; width=&quot;379&quot; height=&quot;173&quot; /&gt; &lt;/p&gt;&lt;p&gt;Since that update, Microsoft Word no longer functions properly. Clicking a  .doc document results in Word starting but not opening the file. Dragging a file  into the open Word application window will open the file, but the scroll bars do  not function. Eventually without too much effort Word will simply crash and then  restart itself. Even just closing Word can cause it to crash. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/23685&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</description>
 <comments>http://www.networkworld.com/community/node/23685#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1035">General discussions</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/123">Microsoft</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1614">Microsoft Office</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/8491">Microsoft Word</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/8492">Windows Update</category>
 <pubDate>Wed, 09 Jan 2008 14:31:17 -0500</pubDate>
 <dc:creator>Mitchell Ashley</dc:creator>
 <guid isPermaLink="false">23685 at http://www.networkworld.com/community</guid>
</item>
</channel>
</rss>
