<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="http://www.codeplex.com/rss.xsl"?><rss version="2.0"><channel><title>Word2007ToXaml Issue Tracker Rss Feed</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/List.aspx</link><description>Word2007ToXaml Issue Tracker Rss Description</description><item><title>Created Issue: Add output formatting for XAML [4458]</title><link>http://word2007toxaml.codeplex.com/WorkItem/View.aspx?WorkItemId=4458</link><description>It would be nice if there was an option for formatting the XML. Right now, everything is on one line. I know it&amp;#39;s easy to add a post-processing step. This is just a nice-to-have feature request. Thanks.&lt;br /&gt;</description><author>tcl</author><pubDate>Wed, 21 Oct 2009 03:04:28 GMT</pubDate><guid isPermaLink="false">Created Issue: Add output formatting for XAML [4458] 20091021030428A</guid></item><item><title>Created Task: Update to Silverlight 3</title><link>http://word2007toxaml.codeplex.com/WorkItem/View.aspx?WorkItemId=3753</link><description>Update Library version&lt;br /&gt;Implement Drop Shadow in Silverlight 3&lt;br /&gt;</description><author>mscherotter</author><pubDate>Mon, 10 Aug 2009 21:49:00 GMT</pubDate><guid isPermaLink="false">Created Task: Update to Silverlight 3 20090810094900P</guid></item><item><title>Created Issue: Silverlight Conversion needs Tab(indent) and Justification support.</title><link>http://word2007toxaml.codeplex.com/WorkItem/View.aspx?WorkItemId=3728</link><description>Indentations&amp;#47;tabs and alignment are completely stripped when converting to Silverlight XAML. Use of the HorizontalAlignment attribute and Margin attributes could be used to fix this.&lt;br /&gt;</description><author>jhurdlow</author><pubDate>Fri, 07 Aug 2009 16:22:49 GMT</pubDate><guid isPermaLink="false">Created Issue: Silverlight Conversion needs Tab(indent) and Justification support. 20090807042249P</guid></item><item><title>Closed Issue: Word 2007 XAML Generator hanges Word</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1537</link><description>When I try to convert the Attached file &amp;#40;Save As XAML document&amp;#41;, Word hangs after 75&amp;#37; of the conversion process. It can only canceled with the task manager.&lt;br /&gt;The layout of the document is not so complex, but has images and some textboxes.&lt;br /&gt;&lt;br /&gt;Documents with images en plain text convert with no problems.&lt;br /&gt;&lt;br /&gt;I use version 1.0.0.18, Dutch version of Word.&lt;br /&gt;&lt;br /&gt;Thanks&lt;br /&gt;Danny Van Neyghem&lt;br /&gt;Belgium&lt;br /&gt;</description><author>mscherotter</author><pubDate>Wed, 04 Feb 2009 18:44:57 GMT</pubDate><guid isPermaLink="false">Closed Issue: Word 2007 XAML Generator hanges Word 20090204064457P</guid></item><item><title>Closed Issue: Implement Vertical Text in VML Diagrams</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1535</link><description>Vertical text is not showing up in VML diagrams.&lt;br /&gt;</description><author>mscherotter</author><pubDate>Wed, 04 Feb 2009 18:44:56 GMT</pubDate><guid isPermaLink="false">Closed Issue: Implement Vertical Text in VML Diagrams 20090204064456P</guid></item><item><title>Closed Issue: Error if docx file contains Content Controls</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1522</link><description>If a docx file contains &amp;#39;Content Controls&amp;#39; if the XAML conversion fails with the error&amp;#58;&lt;br /&gt;&lt;br /&gt;---------------------------&lt;br /&gt;&amp;#39;Normal&amp;#39; dictionary key is already used. Key attributes must be unique. Line &amp;#39;1&amp;#39; Position &amp;#39;2246&amp;#39;.&lt;br /&gt;---------------------------&lt;br /&gt;&lt;br /&gt;Running the code the error occurs at&amp;#58;&lt;br /&gt;System.Windows.Markup.XamlParseException occurred&lt;br /&gt;  Message&amp;#61;&amp;#34;&amp;#39;Normal&amp;#39; dictionary key is already used. Key attributes must be unique. Line &amp;#39;1&amp;#39; Position &amp;#39;1462&amp;#39;.&amp;#34;&lt;br /&gt;  Source&amp;#61;&amp;#34;PresentationFramework&amp;#34;&lt;br /&gt;  LineNumber&amp;#61;1&lt;br /&gt;  LinePosition&amp;#61;1462&lt;br /&gt;  StackTrace&amp;#58;&lt;br /&gt;       at System.Windows.Markup.XamlReaderHelper.Read&amp;#40;XamlNode&amp;#38; xamlNode&amp;#41;&lt;br /&gt;       at System.Windows.Markup.XamlParser.ReadXaml&amp;#40;Boolean singleRecordMode&amp;#41;&lt;br /&gt;       at System.Windows.Markup.TreeBuilderXamlTranslator._Parse&amp;#40;&amp;#41;&lt;br /&gt;       at System.Windows.Markup.XamlParser.Parse&amp;#40;&amp;#41;&lt;br /&gt;       at System.Windows.Markup.XamlTreeBuilder.ParseFragment&amp;#40;&amp;#41;&lt;br /&gt;       at System.Windows.Markup.TreeBuilder.Parse&amp;#40;&amp;#41;&lt;br /&gt;       at System.Windows.Markup.XamlReader.XmlTreeBuildDefault&amp;#40;ParserContext pc, XmlReader reader, Boolean wrapWithMarkupCompatReader, XamlParseMode parseMode, Boolean etwTracingEnabled&amp;#41;&lt;br /&gt;       at System.Windows.Markup.XamlReader.Load&amp;#40;XmlReader reader&amp;#41;&lt;br /&gt;  InnerException&amp;#58; &lt;br /&gt;&lt;br /&gt;Looking at the XAML being generated the above error is occuring in the Styles, with the Normal style being duplicated as soon as you add a Content Control to the docx file and try to export to XAML.&lt;br /&gt;&lt;br /&gt;Sample file attached was created by inserting a Plain Text Content Control from the Developer tab of Word 2007.  If you remove the Content Control from the Word Doc then the XAML Preview will work, if the Content Control is present you will get the above error.&lt;br /&gt;</description><author>mscherotter</author><pubDate>Wed, 04 Feb 2009 18:44:56 GMT</pubDate><guid isPermaLink="false">Closed Issue: Error if docx file contains Content Controls 20090204064456P</guid></item><item><title>Created Issue: Word 2007 XAML Generator hanges Word</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1537</link><description>When I try to convert the Attached file &amp;#40;Save As XAML document&amp;#41;, Word hangs after 75&amp;#37; of the conversion process. It can only canceled with the task manager.&lt;br /&gt;The layout of the document is not so complex, but has images and some textboxes.&lt;br /&gt;&lt;br /&gt;Documents with images en plain text convert with no problems.&lt;br /&gt;&lt;br /&gt;I use version 1.0.0.18, Dutch version of Word.&lt;br /&gt;&lt;br /&gt;Thanks&lt;br /&gt;Danny Van Neyghem&lt;br /&gt;Belgium&lt;br /&gt;</description><author>Gooftroop</author><pubDate>Wed, 04 Feb 2009 15:06:20 GMT</pubDate><guid isPermaLink="false">Created Issue: Word 2007 XAML Generator hanges Word 20090204030620P</guid></item><item><title>Created Issue: Implement Vertical Text in VML Diagrams</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1535</link><description>Vertical text is not showing up in VML diagrams.&lt;br /&gt;</description><author>mscherotter</author><pubDate>Tue, 03 Feb 2009 17:55:20 GMT</pubDate><guid isPermaLink="false">Created Issue: Implement Vertical Text in VML Diagrams 20090203055520P</guid></item><item><title>Closed Issue: Format { and } in Text correctly</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1527</link><description>&amp;#123; or &amp;#125; in text will cause parse errors with XAML.&lt;br /&gt;</description><author>mscherotter</author><pubDate>Mon, 02 Feb 2009 20:01:43 GMT</pubDate><guid isPermaLink="false">Closed Issue: Format { and } in Text correctly 20090202080143P</guid></item><item><title>Closed Feature: Implement unit testing for test files.</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1526</link><description>For both Silverlight and WPF, implement unit testing so that a directory of .docx test files can be processed &amp;#40;transformed and parsed&amp;#41; to test for errors.&lt;br /&gt;</description><author>mscherotter</author><pubDate>Mon, 02 Feb 2009 20:01:42 GMT</pubDate><guid isPermaLink="false">Closed Feature: Implement unit testing for test files. 20090202080142P</guid></item><item><title>Created Issue: Format { and } in Text correctly</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1527</link><description>&amp;#123; or &amp;#125; in text will cause parse errors with XAML.&lt;br /&gt;</description><author>mscherotter</author><pubDate>Mon, 02 Feb 2009 19:49:25 GMT</pubDate><guid isPermaLink="false">Created Issue: Format { and } in Text correctly 20090202074925P</guid></item><item><title>Created Feature: Implement unit testing for test files.</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1526</link><description>For both Silverlight and WPF, implement unit testing so that a directory of .docx test files can be processed &amp;#40;transformed and parsed&amp;#41; to test for errors.&lt;br /&gt;</description><author>mscherotter</author><pubDate>Mon, 02 Feb 2009 19:48:35 GMT</pubDate><guid isPermaLink="false">Created Feature: Implement unit testing for test files. 20090202074835P</guid></item><item><title>Created Issue: Error if docx file contains Content Controls</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1522</link><description>If a docx file contains &amp;#39;Content Controls&amp;#39; if the XAML conversion fails with the error&amp;#58;&lt;br /&gt;&lt;br /&gt;---------------------------&lt;br /&gt;&amp;#39;Normal&amp;#39; dictionary key is already used. Key attributes must be unique. Line &amp;#39;1&amp;#39; Position &amp;#39;2246&amp;#39;.&lt;br /&gt;---------------------------&lt;br /&gt;&lt;br /&gt;Running the code the error occurs at&amp;#58;&lt;br /&gt;System.Windows.Markup.XamlParseException occurred&lt;br /&gt;  Message&amp;#61;&amp;#34;&amp;#39;Normal&amp;#39; dictionary key is already used. Key attributes must be unique. Line &amp;#39;1&amp;#39; Position &amp;#39;1462&amp;#39;.&amp;#34;&lt;br /&gt;  Source&amp;#61;&amp;#34;PresentationFramework&amp;#34;&lt;br /&gt;  LineNumber&amp;#61;1&lt;br /&gt;  LinePosition&amp;#61;1462&lt;br /&gt;  StackTrace&amp;#58;&lt;br /&gt;       at System.Windows.Markup.XamlReaderHelper.Read&amp;#40;XamlNode&amp;#38; xamlNode&amp;#41;&lt;br /&gt;       at System.Windows.Markup.XamlParser.ReadXaml&amp;#40;Boolean singleRecordMode&amp;#41;&lt;br /&gt;       at System.Windows.Markup.TreeBuilderXamlTranslator._Parse&amp;#40;&amp;#41;&lt;br /&gt;       at System.Windows.Markup.XamlParser.Parse&amp;#40;&amp;#41;&lt;br /&gt;       at System.Windows.Markup.XamlTreeBuilder.ParseFragment&amp;#40;&amp;#41;&lt;br /&gt;       at System.Windows.Markup.TreeBuilder.Parse&amp;#40;&amp;#41;&lt;br /&gt;       at System.Windows.Markup.XamlReader.XmlTreeBuildDefault&amp;#40;ParserContext pc, XmlReader reader, Boolean wrapWithMarkupCompatReader, XamlParseMode parseMode, Boolean etwTracingEnabled&amp;#41;&lt;br /&gt;       at System.Windows.Markup.XamlReader.Load&amp;#40;XmlReader reader&amp;#41;&lt;br /&gt;  InnerException&amp;#58; &lt;br /&gt;&lt;br /&gt;Looking at the XAML being generated the above error is occuring in the Styles, with the Normal style being duplicated as soon as you add a Content Control to the docx file and try to export to XAML.&lt;br /&gt;&lt;br /&gt;Sample file attached was created by inserting a Plain Text Content Control from the Developer tab of Word 2007.  If you remove the Content Control from the Word Doc then the XAML Preview will work, if the Content Control is present you will get the above error.&lt;br /&gt;</description><author>MuzFrancis</author><pubDate>Mon, 02 Feb 2009 07:52:29 GMT</pubDate><guid isPermaLink="false">Created Issue: Error if docx file contains Content Controls 20090202075229A</guid></item><item><title>Closed Issue: WPF &amp; Silverlight transformation error with Content Controls</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1521</link><description>Insert Content Controls into a document&lt;br /&gt;Transform to WPF or Silverlight&lt;br /&gt;Error caused by content controls having duplicate styles in a glossary section.&lt;br /&gt;</description><author>mscherotter</author><pubDate>Mon, 02 Feb 2009 07:37:03 GMT</pubDate><guid isPermaLink="false">Closed Issue: WPF &amp; Silverlight transformation error with Content Controls 20090202073703A</guid></item><item><title>Created Issue: WPF &amp; Silverlight transformation error with Content Controls</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1521</link><description>Insert Content Controls into a document&lt;br /&gt;Transform to WPF or Silverlight&lt;br /&gt;Error caused by content controls having duplicate styles in a glossary section.&lt;br /&gt;</description><author>mscherotter</author><pubDate>Mon, 02 Feb 2009 07:07:46 GMT</pubDate><guid isPermaLink="false">Created Issue: WPF &amp; Silverlight transformation error with Content Controls 20090202070746A</guid></item><item><title>Closed Issue: Change Window to NavigationWindow to support Hyperlink Navigation</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1514</link><description>Hyperlinks do not work unless the WPF preview window has a navigation services.&lt;br /&gt;</description><author>mscherotter</author><pubDate>Sun, 01 Feb 2009 17:08:12 GMT</pubDate><guid isPermaLink="false">Closed Issue: Change Window to NavigationWindow to support Hyperlink Navigation 20090201050812P</guid></item><item><title>Closed Feature: Map the WordML style BasedOn to the WPF Style BasedOn</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1515</link><description>Both WordML and WPF styles support style hierarchies.&lt;br /&gt;Map one to the other.&lt;br /&gt;</description><author>mscherotter</author><pubDate>Sun, 01 Feb 2009 17:08:11 GMT</pubDate><guid isPermaLink="false">Closed Feature: Map the WordML style BasedOn to the WPF Style BasedOn 20090201050811P</guid></item><item><title>Closed Issue: Simple Docuemnt with TOC failing</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1461</link><description>this will not convert to Silverlight or WPF doc.&lt;br /&gt;&lt;br /&gt;It would be good to be able to know what is failing. i debugged it, but because its is XSLT its difficult for me to see what the issues is.&lt;br /&gt;&lt;br /&gt;Maybe you coudl also describe what the toosl are to help debug issues.&lt;br /&gt;</description><author>mscherotter</author><pubDate>Sun, 01 Feb 2009 17:08:11 GMT</pubDate><guid isPermaLink="false">Closed Issue: Simple Docuemnt with TOC failing 20090201050811P</guid></item><item><title>Closed Issue: Support Heading that are linking to TOC</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1446</link><description>At the moment the TOC is converted.&lt;br /&gt;&lt;br /&gt;However the headings linked to the TOC are not. Instead the heading is converted but without the number of the heading.&lt;br /&gt;&lt;br /&gt;this si a very common need as many documents use this convention.&lt;br /&gt;</description><author>mscherotter</author><pubDate>Sun, 01 Feb 2009 17:08:11 GMT</pubDate><guid isPermaLink="false">Closed Issue: Support Heading that are linking to TOC 20090201050811P</guid></item><item><title>Closed Issue: Reorder styles to reflect hierarchy</title><link>http://www.codeplex.com/Word2007ToXaml/WorkItem/View.aspx?WorkItemId=1518</link><description>BasedOn styles must appear before the Styles that reference them.&lt;br /&gt;</description><author>mscherotter</author><pubDate>Sun, 01 Feb 2009 17:08:11 GMT</pubDate><guid isPermaLink="false">Closed Issue: Reorder styles to reflect hierarchy 20090201050811P</guid></item></channel></rss>