<?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"
	>
<channel>
	<title>Comments on: Numerical data in Movable Type</title>
	<atom:link href="http://www.gustavholmberg.com/magnitude/2004/01/08/numerical-data-in-movable-type/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gustavholmberg.com/magnitude/2004/01/08/numerical-data-in-movable-type/</link>
	<description></description>
	<pubDate>Fri, 10 Oct 2008 20:17:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Pappan</title>
		<link>http://www.gustavholmberg.com/magnitude/2004/01/08/numerical-data-in-movable-type/#comment-1732</link>
		<dc:creator>Pappan</dc:creator>
		<pubDate>Mon, 08 Mar 2004 15:57:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.gustavholmberg.com/magnitudenew/?p=77#comment-1732</guid>
		<description>There really should be an easier way of expanding the dataset provided by MT. What if the standard set (Title, Main Entry Text etc) could be expanded with user customized fields? We could add fields to our hearts' content and use these fields for sorting, metadata etc. Plug-ins could use these fields for more advanced purposes, such as the example you cite.</description>
		<content:encoded><![CDATA[<p>There really should be an easier way of expanding the dataset provided by MT. What if the standard set (Title, Main Entry Text etc) could be expanded with user customized fields? We could add fields to our hearts&#8217; content and use these fields for sorting, metadata etc. Plug-ins could use these fields for more advanced purposes, such as the example you cite.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
