Modules for localization and internationalization (Drupal 7 and earlier)

Several modules exist that extend the multilingual capabilities of your site. Apart from the modules documented here, you can browse the multilingual section of the modules list to see all projects, sorted by popularity. You may want to additionally filter by version to see, for example, only modules compatible for the latest Drupal version.

HowTo: Different home page (default front page) for each language

When using Drupal + i18n if your site front page is a node listing, the content for each language will be selected depending on your settings for 'Language selection' (Administer > Languages > Configure > Multilingual system) so nothing else to do on this case.

When using a single node as the front page though, such node won't switch automatically depending on the browser language. For this case, when you want a different node to show up for each language as the home page you need to:

Menu items disappear when you change language

Please be aware that the information on this page is probably out-of-date and no longer reflects a usable workaround to this common problem. This page also needs updating(deletion?) as it conflicts with the documentation Menus and primary / secondary links

Summary: When no translation exists for a page, menu items disappear, or they may be displayed in the wrong language

Quick answer: Always set new content to Language Neutral until you are ready to create a translated version. Read more details below.

Environment: You have the i18n module installed. You made multilingual menus by creating some menu items in all of your site's languages. So a menu contains menu items in several languages, but Drupal displays only the menu items that match the current interface language. (note: this is the 2nd option described on this page)

This problem occurs when you are using these multilingual system settings: Path prefix with language fallback, and Current language and language neutral. It may appear with other settings also, but I haven't checked this.

"Orphaned" languages: How to translate content to a language without translating the user interface to that language

Using the i18n module in Drupal, it is possible to translate content to languages which you do not have enabled on the user interface. The term "orphaned language" is used because the content translation does not belong to a language that's enabled on the UI. For example, if you want your website navigation, footer, header, links, etc. to only be available in English, but you want to translate some articles/content to other languages than English, you can do this; the process is not so straightforward. The purpose of this page is to document the process. For more background information you can refer to XXXX (link to blog post), but please use this Drupal handbook page to get the latest, updated documentation (the documentation in the blog post will be maintained on this page).

Drupal 6 Extended/Orphaned language support

* Enable "content translation" and "locale"

* Enable the "internationalization" module which is a module that's part of http://drupal.org/project/i18n

* Go to admin/settings/language and add a language, for example, Spanish.

* After you add the language, you're back on admin/settings/language. From there, uncheck the "Enable" checkbox for that language in order to disable it as an option on the user interface.

HowTo: Different default languages per domain/subdomain

In Drupal 6 the default language is an object stored in a variable. So if you want to have different default languages for each domain/subdomain, you need:

1. Different settings.php files, one for each domain, see the handbook about multisite set ups, http://drupal.org/getting-started/6/install/multi-site

2. To properly set up the language default variable in settings.php. For English as the default language it would be:

Pages

Subscribe with RSS Subscribe to RSS - i18n