<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Creating a rich Wordprocessing Document from a database</title><link>http://blogs.msdn.com/b/brian_jones/archive/2006/08/24/718743.aspx</link><description>I've been planning to start pulling together some real world examples around the ways in which people are using the Office Open XML formats to make document generation much easier. There are a lot of examples from Office 2003, and we're starting to see</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title> Brian Jones Office Extensibility Creating a rich Wordprocessing | fix my credit</title><link>http://blogs.msdn.com/b/brian_jones/archive/2006/08/24/718743.aspx#9764722</link><pubDate>Wed, 17 Jun 2009 05:16:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9764722</guid><dc:creator> Brian Jones Office Extensibility Creating a rich Wordprocessing | fix my credit</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://fixmycrediteasily.info/story.php?id=2775"&gt;http://fixmycrediteasily.info/story.php?id=2775&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9764722" width="1" height="1"&gt;</description></item><item><title>re: Creating a rich Wordprocessing Document from a database</title><link>http://blogs.msdn.com/b/brian_jones/archive/2006/08/24/718743.aspx#723565</link><pubDate>Fri, 25 Aug 2006 17:17:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:723565</guid><dc:creator>I'm Brian Jones</dc:creator><description>A,&lt;br&gt;&lt;br&gt;Actually, we did talk about that, and in the latest version of the spec we actually only write out an element once (if it has a matching name and complex/simple type). It has definitely cut back on a lot of the duplication.&lt;br&gt;&lt;br&gt;-Brian&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=723565" width="1" height="1"&gt;</description></item><item><title>re: Creating a rich Wordprocessing Document from a database</title><link>http://blogs.msdn.com/b/brian_jones/archive/2006/08/24/718743.aspx#722866</link><pubDate>Fri, 25 Aug 2006 15:59:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:722866</guid><dc:creator>A</dc:creator><description>I was actually wondering about that, after all I was getting lost just reading the thing :)&lt;br&gt;&lt;br&gt;Are there any plans to remove duplications from the documentation? &amp;nbsp;For example, the &amp;quot;spPr&amp;quot; element in the PresentationML is used by a large number of entities, but instead of having it documented only once, it gets duplicated for almost every entity that uses it. &amp;nbsp;At the very least, removing duplicates would cut down on the number of pages.&lt;br&gt;&lt;br&gt;Keep up the good work! &amp;nbsp;The documentation has proven to be invaluable so far and a huge step up from working with the binaries.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=722866" width="1" height="1"&gt;</description></item></channel></rss>