Localizer: Build Multilingual Sites (Drupal 5 only)

Last updated November 5, 2012. Created by EdInJapan on December 15, 2006.
Edited by frederickjh, sylvain_a, quicksketch, Roberto Gerola. Log in to edit this page.

The Localizer module extends Drupal's ability to handle human languages. It provides control over a site's user interface language, the ability to enter and control content in multiple languages, and the ability to display the correct language content needed. The module has been designed so that only the features needed for a particular site need be implemented. Some of the more significant features are as follows:

Language selection

• A language switch block is provided (optional) so visitors can click to change desired language
• Automatic language selection is provided (all optional):
  1. via the preferred language setting of the browser
  2. via hostname: it.example.com, en.example.com
  3. via preference settings in My account
• "Fallback language" functionality is provided to allow display of content in another language in the event that the translation for the language being viewed does not exist.

Multi-language content handling

• Provides repositories (nodes) where content can be translated into other languages, and keeps track of the relationship between the content of all languages
• Provides the ability to see which translations have been created for a specific node
• Allows user menus to be translated
• Allows user variables to be translated
• Multi-language taxonomy is supported both for terms and dictionaries

Preference handling

• The method for choosing the default language of the front page, the default display language for content, and the ability to separate user interface language display from content language display can all be configured for the site
• Registered visitors can set their own preferences (in My account) for both user interface language and for language content to be displayed

Translation management interface and language-specific access control

• A management interface for both site string translations (site variables, etc.) and for content translations is provided
• Access to translation management can be limited by role to one or more languages to allow limited roles for translators

Accessibility and extendability

• The localization engine has an API that can be used to work with other modules
• The Views module is supported

Miscellaneous information

• Localizer uses this order to determine which language to display

1. from the Select language block (if present)
2. from the preferred locale set in the visitor's browser preferences
3. from the user preferences (if the visitor is logged in)
4. from the site's global preference settings

• An automatic procedure to activate and deactivate core patched modules has been implemented
• The module is now more cache compatible, because it automatically appends language prefix to the url (as it will be in the upcoming Drupal 6)