Troy Hunt has posted ten reminders for "uncultured web developers" out there to think about when they're developing applications for a world-wide audience.

What a lot of this boils down to is culture, or more specifically, lack of cultural awareness. I’m talking about making assumptions based on what a developer may personally hold to be true but in the broader global context is incorrect and often marginalises their audience. In the pursuit of a more globally harmonious online experience, let’s take a look at 10 lessons relating to aspects of web development with a cultural bent. Some of this may not be new to you, but all of it is relevant if you want to play nice with people from all cultural walks of life.

Among the list of his ten tips you'll find things like:

• Firefox and Chrome command 91% of the market
• Almost always, 8/7 comes before 7/8
• Country code top level domains give context
• Time zones matter (and they’re not universally understood)
• Don’t deprioritise your international audiences

Check out the rest of the list in his full post.

Taylor Luk submitted some info about a project he's been working on for a while and is ready to release into the wild and see how useful it can be for others - H2o Template, a Django-inspired templating system.

I have been developing this for quite a while, started as a fun project to do django like syntax and compiles down to php code. Unlike the last django-like template for Zend Framework, this one is more stand alone. After couple major rewrite, now i am releasing 0.3 beta.

The syntax of the templates is pretty similar to Django and it includes a built-in caching driver, an extension system that allows for external filters/tags/extensions to be added in easily and internationalization support. He's currently using it on a CakePHP website in a view class on a production system.

Get more details and access the source on the project's github page.

In this new post to the Symfony blog, Nicolas Perriault shows how to quickly and easily internationalize your Propel forms in your Symfony application.

It has never been so easy to internationalize your Propel forms. In this post, you will learn how to leverage the new form framework bundled with symfony 1.1 to develop an interface to edit articles in several languages.

He uses a basic form layout and shows how to build out the files (via a build-all) and what it ends up looking like. He configures the two languages - English and French - that he wants to use in the form and pushes it through the CRUD generator to make a full web interface for it.

In a new post on the PHP 10.0 Blog, Stas mentions his posting of a beta version of the Internationalization extension for PHP.

I've posted the first beta of PHP Internationalization extension, bringing support for some ICU functions to PHP. Documentation can be read in PHP manual, and the downloads are available on PECL site.

His goal is to have it all ready and waiting (and included) for when PHP 5.3 is set to roll off the line. The extensions consists of four major parts that do the work for you - the collator, number formatter, normalizer and a locale component.

In a new post on the PHP 10.0 Blog, Stas mentions his posting of a beta version of the Internationalization extension for PHP.

I've posted the first beta of PHP Internationalization extension, bringing support for some ICU functions to PHP. Documentation can be read in PHP manual, and the downloads are available on PECL site.

His goal is to have it all ready and waiting (and included) for when PHP 5.3 is set to roll off the line. The extensions consists of four major parts that do the work for you - the collator, number formatter, normalizer and a locale component.

On the IBM developerWorks site, there's a new article looking to help you internationalize your applications easily.

Localizing an application can be planned, or it can happen as a rushed afterthought. Discover techniques and tools such as gettext, XML, XSLT, and design patterns that can help when retrofitting localization into a mature product or planning for localization up front.

They start with a bit of a guide on how to assess the situation and see what would need to be considered before even starting on the process (looking at a Yahoo RSS feed). There's a brief look at some terminology, then its right into the code - retrofitting your content (the RSS feed) via XML content and the gettext functionality.

The also include a design pattern for localization in the MVC style that handles the transformation automatically.

On the IBM developerWorks site, there's a new article looking to help you internationalize your applications easily.

Localizing an application can be planned, or it can happen as a rushed afterthought. Discover techniques and tools such as gettext, XML, XSLT, and design patterns that can help when retrofitting localization into a mature product or planning for localization up front.

They start with a bit of a guide on how to assess the situation and see what would need to be considered before even starting on the process (looking at a Yahoo RSS feed). There's a brief look at some terminology, then its right into the code - retrofitting your content (the RSS feed) via XML content and the gettext functionality.

The also include a design pattern for localization in the MVC style that handles the transformation automatically.