Fortunately following our call, many of you took the time to write up your ideas and frustrations about trying to set up multilingual sites with Drupal and other content management systems. The matter of fact is that many of the Drupal developers already went and done some content translation solution in the past (sometimes coupled with menu, categories and other translation possibilities). While we are brainstorming about what should be supported, we should also think about the connection between the frontend and the underlying technology.

For this reason, I have took the time to review four existing solutions for your Drupal content translation needs. All of them have their own weak points, and most of them have very good ideas to carry on into Drupal core. Specific implementation and interface details will be discussed at the internationalization group site. By publishing this report, I am trying to visualize what are the common approaches taken and what alternative paths are tried to support different needs. Hopefully we will be able to select a proper set of these which allow for versatile user interfaces to be built around content and navigation translation.

In case you find any errors or omissions in the comparision table, feel free to point them out.