In a recent blog entry titled The future of Drupal interface localization lies in install profiles I showed you a proof-of-concept way for a new Drupal interface translation packaging format. As the Drupal 5 release is closing on us, and we were able to fix quite a few small glitches around interface translation related problems, I decided to clean up the packaging scripts and release them to the public, so other translation groups can try this distribution format and we might eventually get this up at drupal.org as the default.
I am that adventurous type to try to update weblabor.hu from Drupal 4.6 to Drupal 5.0 directly. This type of update is not recommended, because it is not ensured that everything will work fine. Unfortunately this time the direct update is not possible without some tweaking of the system.install files, but it seems to be doable.
Drupal 5 comes out with a nifty new feature (among a lot of others): it only creates database tables and imports CSS files for modules turned on. It is a logical step to do the same with interface translation files. The practice up to Drupal 4.7 was to generate smaller translation template files for translators, so they can better work with strings and collaborate with version tracking tools. These smaller files were merged into one big translation file, which was given to end users to import if they needed the Drupal package work in their language. What should be the new model, and how do we support it? Do I have a working (starter) solution? Yes. Read on!
Matt Mullenweg (the man behind Wordpress) says in a conversation:
The next version of Drupal is coming out with a pretty neat theme,
called Garland. Here's a demo page where you can customize it and save
This is pretty darn neat. Anyone interested in porting it? The toggle,
logo, and shortcut icon bits are probably superfluous, but the color
picking functionality is great.
As far as I know, this is the first time that a Drupal theme is ported to Wordpress. There is the feeling of some bad taste in the Drupal community about this port being done before Drupal was able to release this in Drupal 5 though. This still is a historical step in my opinion.
The results are announced (with my emphasis).
The final result, as voted for by judges from The Open Source Collective, MySQL, the Eclipse Foundation, and 16,000 users on www.PacktPub.com saw a tie for first place between Joomla! and Drupal. In the event of a tie, a fourth independent judge would be brought in. This was Apoorv Durga who is a member of CMSPros and runs his own blog [http://apoorv.info/] on portals and content management. This crucial vote ended up with Joomla! triumphing over Drupal by one point.
The final result was as follows:
1. Joomla!- $5,000
2. Drupal - $3,000
3. Plone - $2,000