Comments on: Internationalized Domain Name support on the trunk http://simplepie.org/blog/2006/06/14/internationalized-domain-name-support-on-the-trunk/ Behind the scenes of SimplePie development. Fri, 02 Dec 2011 11:36:40 +0000 hourly 1 http://wordpress.org/?v=3.4-alpha-19861 By: Ryan Parman http://simplepie.org/blog/2006/06/14/internationalized-domain-name-support-on-the-trunk/comment-page-1/#comment-179 Ryan Parman Fri, 16 Jun 2006 03:07:02 +0000 http://simplepie.org/blog/2006/06/14/35/#comment-179 Bob, it has been enabled on the <i>trunk</i> demo, accessible via the PHP4 and PHP5 links towards the bottom of the post. And you're right: we should try to autodetect it. The only reason why I added it as an option that is disabled by default is because it relies on a 3rd party library to work. We've already got a solid list of stuff to add for 1.0, so at worst it'd be part of 1.1. Bob, it has been enabled on the trunk demo, accessible via the PHP4 and PHP5 links towards the bottom of the post.

And you’re right: we should try to autodetect it. The only reason why I added it as an option that is disabled by default is because it relies on a 3rd party library to work.

We’ve already got a solid list of stuff to add for 1.0, so at worst it’d be part of 1.1.

]]> By: Bob Aman http://simplepie.org/blog/2006/06/14/internationalized-domain-name-support-on-the-trunk/comment-page-1/#comment-178 Bob Aman Thu, 15 Jun 2006 17:33:56 +0000 http://simplepie.org/blog/2006/06/14/35/#comment-178 I might be misunderstanding you, but it seems the demo page is still returning: <blockquote>Error: A feed could not be found at http://www.???.com/feed</blockquote> Seriously though, James' feed doesn't seem to parse perfectly in my parser either. Unfortunately, that's a limitation of Ruby's terrible URI parsing class, and short of rewriting that entire class, I don't have a good work-around. Instead of using the correct domain name, FeedTools ends up prefixing the links on James' blog with "file:///", which is obviously wrong. Also, you might want to try to autodetecting IDN support instead of having people manually enable it. It's been awhile since I did any PHP, but I don't think that should be terribly hard, or at least, it shouldn't be much harder than it is in Ruby. I might be misunderstanding you, but it seems the demo page is still returning:

Error: A feed could not be found at http://www.???.com/feed

Seriously though, James’feed doesn’t seem to parse perfectly in my parser either. Unfortunately, that’s a limitation of Ruby’s terrible URI parsing class, and short of rewriting that entire class, I don’t have a good work-around. Instead of using the correct domain name, FeedTools ends up prefixing the links on James’blog with “file:///”, which is obviously wrong.

Also, you might want to try to autodetecting IDN support instead of having people manually enable it. It’s been awhile since I did any PHP, but I don’t think that should be terribly hard, or at least, it shouldn’t be much harder than it is in Ruby.

]]>