A new block has appeared today on top right corner of the php-gtk.eu pages, with three little flags : they show you can now navigate the site in one of these languages and, more importantly, automatically find the translated versions of all articles when they exist ... or contribute one yourself if you are logged in to the site.

Right now they offer English, French and German and they're still working on translating some parts of the UI of the site, but the articles and content should be translated over just fine.

A week after the release of the new plugin system, a lot of activity has taken place. More than 30 plugins were created, and 51 new releases were published on 27 different plugins. Based on the feedback I have received from the community, I have made some tweaks to the system.

These tweaks include a newly designed homepage, the inclusion of RSS feeds and a special URL to view the older wiki documentation for some plugins.

The second post describes more enhancements based on other feedback (on the previous post). Updates based on this information include an new "overview" field to describe the plugin, a download of the Markdown syntax to make the documentation conversion easier and a "stric mode" validation if you upload a PEAR package.

One frequently received suggestion is to redesign the site. As I explained before, changing the site design is not a big issue. The greatest challenge is to change the current design to another that pleases more users than the number of users the change may displease.

So, to keep things interesting, he's had a contest out of it with the winner, besides having their design applied to the site, will get their every own elePHPant and a prize of at least $1000 USD. The winning design will be the main one for the site, but it is possible that paying subscribers could have the ability to define their own.

More to come on the contest in the following weeks...

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.

He defines a few terms - 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.

This Packt book takes the reader through installing the Drupal software, configuring and theming, adding content and deploying a Web site. It is aimed at the end user who is looking to setup and customize Drupal's themes, but not actually write their own modules, which would be a topic for book on its own.

The review talks about some of the origins of the content management system, the contents of the book (use cases, introductions to the functionality, etc) and how to manage your site.

symfony 1.1 introduces native support for different formats and mime-types. This means that the same model and controller can have different templates based on the requested format. The default format is still HTML but symfony supports several other formats out of the box as defined in the factories.yml file.

Using this system, it's easy to add new output formats by adding to the default layouts the framework comes equipped with. The Content-Type can be changed and layouts can be disabled as needed. This lets you make a custom definition just for use with the iPhone without a lot of hassle.

They also include an example of how to make one of these optimized layouts, including some iPhone "screenshots" of the resulting pages.

I thought that, seeing as this is a programmer community, the people who have not had the privilege to have access to the forums where these things were discussed or access to the code itself might be interested in knowing a bit about the underlying technology and code that powers this website

Some of the technologies they use include the Zend Framework running on a CentOS with PHP5.2. Some of the highlights in the coding process included updates to Zend_Auth, using Zend_Acl for access management, content management and other various packages (like Zend_Feed, Zend_Form, Zend_Db, etc).

So I attended the PEAR2 presentation and had a chance to bug the guys behind PEAR/PECL. There's definitely exciting stuff happening and they are pushing forward with many exciting ideas.

His suggestions include updates to documentation, crrection broken parts of the API and a "Package News" feature with the ability to leave comments on them.

He's also posted another suggestion - the ability of the authors of the project to provide other links besides the ones just for the project (external documentation, tutorials, etc)

For years I've wanted to run a personal Web site but never found the time to do it. A couple of weeks ago a few Zenders and I started leasing a dedicated server which gave us each a bit more hosting flexibility. Once we got the machine up and running I decided it was finally time to actually launch my own personal Web site.

He lists the technologies he's using including the Zend Framework, the Zend_Gdata component and the Zend_Cache (for local caching of his blog feeds from Blogger).

This book is a tutorial guide to Joomla! 1.5. It was written and published during the development of Joomla! 1.5. It is intended for Web developers, designers, Web masters, content editors and marketing professionals. It is suitable for anyone starting out with Joomla! 1.5, for people who upgrade to Joomla! 1.5, and for those who just want have a good printed manual at hand.

R.L. (the reviewer) goes through some of the chapters, detailing their content including some of the software mentioned in them (like Fireboard and DOCman). He recommends the book to anyone looking for a good in-hand Joomla! resource but notes that a chapter on security would have been a nice addition.