<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>Dancing About Architecture: Microfeed for "Character Encoding in the Trenches"</title>
    <link>http://www.burningdoor.com/eric/archives/000398.html</link>
    <description>Comments and trackbacks for the entry "Character Encoding in the Trenches"</description>
    <language>en-us</language>
    <managingEditor>eric@burningdoor.com</managingEditor>
    <webMaster>eric@burningdoor.com</webMaster>
    <lastBuildDate>Fri, 13 Feb 2004 14:54:48 CDT</lastBuildDate>
    <category>RSS</category>
    <generator>Movable Type v3.14</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title>Character Encoding in the Trenches</title>
      <link>http://www.burningdoor.com/eric/archives/000398.html</link>
      <description>Good timing for this discussion -- I&apos;ve been struggling with the right way to do character encoding just recently. The interaction between the HTTP Content-Type header and the encoding attribute of the XML declaration (and even the machine&apos;s default locale!) creates a confusing environment. Wouldn&apos;t it be nice if there was no ambiguity and the HTTP charset parameter always matched the encoding of the XML feed? Stay tuned ... (evil grin!) Source: Dare Obasanjo aka Carnage4Life - Sex, Lies and XML MIME Types...</description>
      <comments>http://www.burningdoor.com/eric/archives/000398.html</comments>
      <guid isPermaLink="false">398@http://www.burningdoor.com/eric/</guid>
      <pubDate>Fri, 13 Feb 2004 14:54:48 CDT</pubDate>
      <source url="http://www.burningdoor.com/eric/index.xml">Dancing About Architecture</source>
    </item>
    
  </channel>
</rss>