<rdf:RDF
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns="http://purl.org/rss/1.0/"
 xmlns:sy="http://purl.org/rss/1.0/modules/syndication/">
	<channel rdf:about="my.afterdawn.com/latest_blog_entries.cfm">
		<title>Blogs by tag: conversion</title>
		<link>http://my.afterdawn.com/latest_blog_entries.cfm</link>
		<description>All blogs are stored at my.afterdawn.com.</description>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>2</sy:updateFrequency>
		<items>
			<rdf:Seq>
				<rdf:li rdf:resource="http://my.afterdawn.com/drd/blog_entry.cfm/2884/convert_utf8_data_stored_in_latin1_table_to_latin1_data_in_latin1_table"/>
			</rdf:Seq>
		</items>
	</channel>
	<item rdf:about="http://my.afterdawn.com/drd/blog_entry.cfm/2884/convert_utf8_data_stored_in_latin1_table_to_latin1_data_in_latin1_table">
		<title>Moving UTF-8 encoded data from latin1 table to another latin1 table..</title>
		<link>http://my.afterdawn.com/drd/blog_entry.cfm/2884/convert_utf8_data_stored_in_latin1_table_to_latin1_data_in_latin1_table</link>
		<description>
			Encountered weird problem today, when moving data from an ancient Wordpress installation to AfterDawn&apos;s own table structure. Apparently, for whatever reason, WP&apos;s tables were set by default to be in latin1 encoding, but the data that WP inserted to those ...
		</description>
	</item>
</rdf:RDF>