<?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: Is Python going bad? or The curse of unicode&#8230;.</title>
	<atom:link href="http://www.daniel-lemire.com/blog/archives/2004/05/27/is-python-going-bad-or-the-curse-of-unicode/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.daniel-lemire.com/blog/archives/2004/05/27/is-python-going-bad-or-the-curse-of-unicode/</link>
	<description>Daniel Lemire's blog is about life in academia, research in Computer Science, wondering how we can reconcile fast databases and algorithms with the informal and asemantic nature of the world around us. It is broadcasted from Montreal (Canada).</description>
	<pubDate>Mon, 01 Dec 2008 23:01:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: kent sin</title>
		<link>http://www.daniel-lemire.com/blog/archives/2004/05/27/is-python-going-bad-or-the-curse-of-unicode/#comment-3686</link>
		<dc:creator>kent sin</dc:creator>
		<pubDate>Tue, 28 Feb 2006 23:19:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.daniel-lemire.com/blog/archives/2004/05/27/is-python-going-bad-or-the-curse-of-unicode/#comment-3686</guid>
		<description>Sometimes, for example, when reading RSS feeds, even the programmer do not known what is the encoding. 

I agree with you that unicode is very bad support in python, but that is the best scripting language support we can find.</description>
		<content:encoded><![CDATA[<p>Sometimes, for example, when reading RSS feeds, even the programmer do not known what is the encoding. </p>
<p>I agree with you that unicode is very bad support in python, but that is the best scripting language support we can find.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jbalague</title>
		<link>http://www.daniel-lemire.com/blog/archives/2004/05/27/is-python-going-bad-or-the-curse-of-unicode/#comment-3642</link>
		<dc:creator>jbalague</dc:creator>
		<pubDate>Wed, 08 Feb 2006 14:01:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.daniel-lemire.com/blog/archives/2004/05/27/is-python-going-bad-or-the-curse-of-unicode/#comment-3642</guid>
		<description>I agree with you as well.
I'm going mad reading and writing XML Unicoded files!!!
-- jbalague</description>
		<content:encoded><![CDATA[<p>I agree with you as well.<br />
I&#8217;m going mad reading and writing XML Unicoded files!!!<br />
&#8211; jbalague</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ianaré sévi</title>
		<link>http://www.daniel-lemire.com/blog/archives/2004/05/27/is-python-going-bad-or-the-curse-of-unicode/#comment-3237</link>
		<dc:creator>ianaré sévi</dc:creator>
		<pubDate>Mon, 17 Oct 2005 05:53:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.daniel-lemire.com/blog/archives/2004/05/27/is-python-going-bad-or-the-curse-of-unicode/#comment-3237</guid>
		<description>I totally agree with you, this whole encoding thing is a real pain. I am in the process of writing an application that will, amongst other things, rename an mp3 file according to its id3 tag. This is how I got into the horribly confusing world of python encoding, as so far all the mp3's I've come across are in latin-1, and turning that into something I can manipulate has been problematic. The fact that I'm going cross platform with this doesn't help. I also want to add support for other encodings (utf-16,utf8, etc...). Like you said, how am I supposed to know what encoding was used in the mp3? I'm thinking about a series of try: except:, or maybe a loop that tries each encoding ?!?  It'll get done eventually, but for now latin1 will have to do - at least I can rename my Brassens titles without crashing my app.
Anyway I would like to say that this page was informative by giving me a list of things to try out all in one conveniant package, rather than searching through cryptic python doc pages. Merci l'ami !

- ianaré</description>
		<content:encoded><![CDATA[<p>I totally agree with you, this whole encoding thing is a real pain. I am in the process of writing an application that will, amongst other things, rename an mp3 file according to its id3 tag. This is how I got into the horribly confusing world of python encoding, as so far all the mp3&#8217;s I&#8217;ve come across are in latin-1, and turning that into something I can manipulate has been problematic. The fact that I&#8217;m going cross platform with this doesn&#8217;t help. I also want to add support for other encodings (utf-16,utf8, etc&#8230;). Like you said, how am I supposed to know what encoding was used in the mp3? I&#8217;m thinking about a series of try: except:, or maybe a loop that tries each encoding ?!?  It&#8217;ll get done eventually, but for now latin1 will have to do - at least I can rename my Brassens titles without crashing my app.<br />
Anyway I would like to say that this page was informative by giving me a list of things to try out all in one conveniant package, rather than searching through cryptic python doc pages. Merci l&#8217;ami !</p>
<p>- ianaré</p>
]]></content:encoded>
	</item>
</channel>
</rss>
