<?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, 19 Jul 2008 05:47:43 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Wen Huang's Blog: Looking ahead to PHP 5.3 and 6]]></title>
      <guid>http://www.phpdeveloper.org/news/10608</guid>
      <link>http://www.phpdeveloper.org/news/10608</link>
      <description><![CDATA[<p>
<i>Wen Huang</i> has made a <a href="http://blogs.sun.com/wen/entry/looking_ahead_to_php_5">quick post</a> to his blog about some of the comments <i>Andrei Zmievski</i> about the future of PHP, specifically on internationalization and UTF-8's place in it.
</p>
<blockquote>
I attended the SF PHP Meetup last night where Andrei Zmievski (PHP 6 release manager and PHP core team member) gave a talk on PHP 6 and internationalization (i18n). [...] It was evident that Andrei and team have given quite a bit of thought into what i18n means for the PHP world, and as a result, PHP developers everywhere will soon be enjoying a new set of tools to enable faster development of multi-lingual sites.
</blockquote>
<p>
He also mentions the back-port that several of these features will get into the upcoming PHP 5.3 release (along with the much-hyped namespace support). You can check out <i>Andrei</i>'s talk <a href="http://www.gravitonic.com/talks/">on his website</a>.
</p>]]></description>
      <pubDate>Tue, 15 Jul 2008 11:15:30 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[ThinkPHP Blog: Multilingual Websites with PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/10603</guid>
      <link>http://www.phpdeveloper.org/news/10603</link>
      <description><![CDATA[<p>
On the ThinkPHP blog, <i>Florian Eibeck</i> has <a href="http://blog.thinkphp.de/archives/342-Multilingual-Websites-with-PHP.html">posted an overview</a> of some key things to consider when internationalizing your application/website.
</p>
<blockquote>
The biggest problem is that most developers lack knowledge about Internationalisation, Localisation, Character encodings, Unicode and all those terms connected with multilingualism. The following article should give you a basic understanding and show you how to avoid those funny characters.
</blockquote>
<p>
He <a href="http://blog.thinkphp.de/archives/342-Multilingual-Websites-with-PHP.html">defines a few terms</a> - internationalization, ASCII, unicode and the UTF-8/ISO-8859 character sets. He mentions how to accept the utf-8 string into your application and how to use it in both PHP and store it in a MySQL database.
</p>]]></description>
      <pubDate>Tue, 15 Jul 2008 07:55:38 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Matthew Weir O'Phinney's Blog: Zend_Form Advanced Features]]></title>
      <guid>http://www.phpdeveloper.org/news/9931</guid>
      <link>http://www.phpdeveloper.org/news/9931</link>
      <description><![CDATA[<p>
<i>Matthew Weir O'Phinney</i> has <a href="http://weierophinney.net/matthew/archives/159-Zend_Form-Advanced-Features.html">written up a post</a> for his blog outlining some of the other cool little features that were included in the <a href="http://devzone.zend.com/article/3030-Lifting-the-Skirt-on-Zend-Framework-1.5---Zend_Form">recent release</a> of the Zend Framework, specifically with the Zend_Form component.
</p>
<blockquote>
I've been working on  for the past few weeks, and it's nearing release readiness. There are a number of features that Cal didn't cover in his <a href="http://devzone.zend.com/article/3030-Lifting-the-Skirt-on-Zend-Framework-1.5---Zend_Form">DevZone coverage</a> (in part because some of them weren't yet complete) that I'd like to showcase.
</blockquote>
<p>These additional features <i>Matthew</i> mentions are:</p>
<ul>
<li>Internationalization
<li>Element Grouping
<li>Array Support
</ul>
<p>
Check out more of the great features of the component <a href="http://framework.zend.com/manual/en/zend.form.html">in the Zend Framework documentation</a>.
</p>]]></description>
      <pubDate>Tue, 08 Apr 2008 12:13:35 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Northclick Blog: Tutorial for the easy use of gettext for internationalization of PHP Apps]]></title>
      <guid>http://www.phpdeveloper.org/news/7777</guid>
      <link>http://www.phpdeveloper.org/news/7777</link>
      <description><![CDATA[<p>
In a <a href="http://blog.northclick.de/archives/20">new post</a> on the Northclick blog today, there's a tutorial that looks to make it easy to use the gettext functionality that PHP offers to internationalize your site.
</p>
<blockquote>
This tutorial is for people who start or want to optimize the internationalization of their PHP Apps. We wrote it due the lack of useful resources. Although there are many tutorials for gettext out there it is still a very complicated issue.
</blockquote>
<p>
They <a href="http://blog.northclick.de/archives/20">start with</a> the Pros and Cons of using the functionality like "it's the defacto-standard for i18n of unix systems and their applications" versus things like "debbuging gettext can be hard in PHP". The rest of the post is broken up into five steps:
<ul>
<li>Generate Functions and init gettext
<li>Translate your Application
<li>Generate a pot file (Template)
<li>Generate your PO Files from your POT Template and translate
<li>Generate Binaries
</ul>
They also offer some helpful hints too like how to update the translation files and some solutions to some common issues you might come across.
</p>]]></description>
      <pubDate>Fri, 04 May 2007 13:13:14 -0500</pubDate>
    </item>
  </channel>
</rss>
