<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sat, 05 Jul 2008 06:13:04 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Dokeos Blog: mbstring vs iconv]]></title>
      <guid>http://www.phpdeveloper.org/news/10034</guid>
      <link>http://www.phpdeveloper.org/news/10034</link>
      <description><![CDATA[<p>
In <a href="http://dokeoslead.wordpress.com/2008/04/22/mbstring-vs-iconv/">this post</a> on the Dokeos blog, there's a comparison of the <a href="http://www.php.net/mbstring">mbstring</a> function and the <a href="http://php.net/iconv">iconv</a> library as it pertains to their use on multi-byte strings.
</p>
<blockquote>
I was wondering today why use mbstring rather than iconv in Dokeos, and honestly I didn't remember exactly why I had chosen mbstring in the past, but finding information about the *differences* between the two. [...] Searching a bit more, I found a <a href="http://www.nyphp.org/content/presentations/smallworld/April2006-nyphp-Presentation.ppt">PPT presentation</a> from Carlos Hoyos on Google.
</blockquote>
<p>
Essentially, it boils down to how the library is integrated - mbstring is bundled and iconv is pulled from an external source. So, if you're looking for maximum portability, he recommends mbstring.
</p>]]></description>
      <pubDate>Thu, 24 Apr 2008 11:18:08 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[SitePoint PHP Blog: Living Dangerously with PHP and UTF-8]]></title>
      <guid>http://www.phpdeveloper.org/news/4457</guid>
      <link>http://www.phpdeveloper.org/news/4457</link>
      <description><![CDATA[In <a href="http://www.sitepoint.com/blogs/2005/12/06/living-dangerously-with-php-and-utf-8/">this new post</a> on the SitePoint PHP Blog today, <i>Harry</i> looks at why it's "living dangerously" to use PHP with UTF-8.
<p>
<quote>
<i>
Quick oneā"knocked up a list of "dangerous" functions and functionality in PHP, in relation to the use of UTF-8, available at <a href="http://www.phpwact.org/php/i18n/utf-8">http://www.phpwact.org/php/i18n/utf-8</a>. These are for a "default" PHP setup without the <a href="http://www.php.net/mbstring">mbstring</a> overloading or PHP6 (where charset problems "magically vanish" ;) ).
<p>
This follows on from (unfinished) stuff <a href="http://www.phpwact.org/php/i18n/charsets">here on charsets (tending towards UTF-8)</a>, which should help explain some of this.
</i>
</quote>
<p>
He <a href="http://www.sitepoint.com/blogs/2005/12/06/living-dangerously-with-php-and-utf-8/">also notes</a> that you can't rely on mbstring to be there, so he <a href="http://phplens.com/phpeverywhere/?q=node/view/98">offers an alternative</a>...]]></description>
      <pubDate>Wed, 07 Dec 2005 07:45:38 -0600</pubDate>
    </item>
  </channel>
</rss>
