Development Seed

To cater to the needs of multilanguage websites, Drupal and other content management systems should take into account the different uses of these sites and the unique content and interfaces they provide. For example, a search site where content will not be translated might need different languages in its interface, while a personal blog where posts are entered in different languages might need many different features.

Image

Development Seed is one of the (as far as I see) lesser known Drupal solution providers, who mainly concentrate on intranets, mobile stuff, aggregation and all kinds of good causes to use Drupal for. They are working with smart people of whom some are well known in the community.

Having a great website management system like Drupal that has built-in content translation tools is an achievement in itself. But content is not always born in Drupal, and it’s most certainly not translated in Drupal. This makes it necessary, particularly in the context of multilingual websites, for Drupal to support interfacing so it can link in with external translation tools and their translation workflows.

Over the past few months I’ve been researching how TYPO3, Joomla, Plone, and Drupal currently support multilingual content. Since this work was in part supported by Development Seed, I happily accepted the request to guest blog some of my findings.