<?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>Mon, 08 Sep 2008 03:18: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[Riff Blog: Console encoding in PHP-GTK apps]]></title>
      <guid>http://www.phpdeveloper.org/news/6738</guid>
      <link>http://www.phpdeveloper.org/news/6738</link>
      <description><![CDATA[<p>
PHP-GTKers working in English-related applications, don't have a problem with debugging messages output to a console when debugging, but applications on a more international front have issues with their output. But help has been found in <a href="http://blog.riff.org/2006_11_19_console_encoding_in_php_gtk_apps">this new post</a> on the Riff Blog - a method for correctly encoding PHP-GTK applications.
</p>
<blockquote>
<p>
PHP scripts are typically stored under UTF-8 encoding to limit i18n headaches, while the console in which their output will be displayed is normally configured to some regional encoding, like IBM850 in Windows/XP French.
</p>
<p>
So we need a workaround...
</p>
</blockquote>
<p>
He splits <a href="http://blog.riff.org/2006_11_19_console_encoding_in_php_gtk_apps">the process</a> out into a few steps, each with its own explanation and code:
<ul>
<li>Builtin tools
<li>Buffering
<li>Flushing
<li>PHP-GTK is not PHP for the Web
<li>Auto-flushing
</ul>
All wrapped up with a final solution - using the iconv functionality in combination with some output buffering to correctly display the message.
</p>]]></description>
      <pubDate>Mon, 20 Nov 2006 10:58:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Christian Stocker's Blog: PHP 5, OS X, fink and iconv]]></title>
      <guid>http://www.phpdeveloper.org/news/4622</guid>
      <link>http://www.phpdeveloper.org/news/4622</link>
      <description><![CDATA[<i>Christian Stocker</i> has <a href="http://blog.bitflux.ch/archive/2006/01/06/php-5-os-x-fink-and-iconv.html">a quick new post</a> with a solution for those Mac users out there that would like to use the iconv extension with fink.
<p>
<quote>
<i>
If you want to get the iconv extension properly running with PHP 5 and <a href="http://fink.sf.net/">fink</a> on OS X, you need the following configure option
<p>
--with-iconv=/sw/
<p>
and then it should work.
<p>
Hope that helps others, too.
</i>
</quote>
<p>
And, apparently, it does - given the one comment below it so far that has a positive response...
]]></description>
      <pubDate>Fri, 06 Jan 2006 07:23:47 -0600</pubDate>
    </item>
  </channel>
</rss>
