"This post has some general tips that I’d recommend to anyone wanting to write a multilingual web application. The majority of my code these days is PHP, but I think these tips are applicable to most web programming languages."

Complete Story

For some months ago i started with this project that based on Cmsmadesimple.

CMSMS  has some disadvantages - low speed , needs much memory , a very bad module api.

Now i have made several Versions of PowerCMS and changed many from the original.

And now PowerCMS is gone his own way.

The default language is german.

• A very memory efficient CMS, that works without problems on Web server with 8MB memory limit - typically less than 1 mb needed in the frontend
• A very fast CMS with very small generation times - the values are 0.00075507164001465 ... 0.04244296073913 seconds on shared Webservers
• Will run from PHP 4.3.1, including PHP 5.xx versions - no need of PHP 5

Not long ago, Development Seed posted a fantastic comparison of multilingual handling between Drupal 5 and Drupal 6.

Many people who’ve heard the buzz about multilingual features making it into Drupal core have asked me if they should go ahead with their multilingual projects on Drupal 5 or push them back to wait for Drupal 6 to be released. Of course there are many factors to consider, but with multilingual websites there’s no doubt that two big factors are workflow and contributed modules.

Jose just pulled together an excellent comparison chart that should help make that decision easier. The chart below compares the multilingual support with Drupal 5 to Drupal 6.

One of the criticisms of many open source CMS is that they're not fully "international", especially for those languages that are written/read from right to left. Many projects, are quickly addressing the critics by placing significant focus on improving the multilingualism in their CMS. For example, not only will Drupal 6 (still under development) have improved multilingual support but so will Joomla 1.5 (nearing release candidate stage).