Multilingual

This is a collection of modules to extend Drupal core multilingual capabilities and be able to build real life multilingual sites. Some features:

• Taxonomy translation (both, per language terms and translatable terms)
• Multilingual variables
• Multilingual blocks (control visibility per language and translate title and content)
• Language selection (when you switch the site language you'll see only the content for that language)
• Requires Variable module 2.x (Drupal 7)

Read a complete feature overview in the Internationalization handbook: Building multilingual sites .

Drupal 7 upgrade

Do read Upgrade from Drupal 6 to Drupal 7
Read more about new features on Internationalization for Drupal 7 and What's new in i18n.

A co-maintainer is badly needed for this project. If you feel qualified to apply, please get in touch!

While working on the new content translation system for Drupal 7, we (the Drupal core i18n team) faced the need to convert node titles to the Field API in order to make nodes fully translatable.

The Taxonomy Filter module is designed to present an easy-to-use interface for narrowing down taxonomy listings to find topics that are tagged by multiple terms. This is helpful for sites that use multiple vocabularies to create a multi-faceted information architecture.

Prior to Drupal 7 (see note in the "Drupal 7.x version" section), the core Drupal taxonomy module has the ability to do this with the following URL format:

/taxonomy/term/x,y,z

This toolkit is a collection of modules which were developed to enable African language content publishing on the Web.

However, it is well suited to manage content in any language on websites focused on taxonomy, terminology and the creation of language tools like a dictionary, a glossary or lexicon.

Technical Support
Left-to-right language support by Suuch Solutions

ATTENTION:
This module violates the Google TOS, in particular point 5.3:

5.3 You agree not to access (or attempt to access) any of the Services by any means other than through the interface that is provided by Google, unless you have been specifically allowed to do so in a separate agreement with Google. You specifically agree not to access (or attempt to access) any of the Services through any automated means (including use of scripts or web crawlers) and shall ensure that you comply with the instructions set out in any robots.txt file present on the Services.

You use it under your own responsibility.

Description

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.

Localizer allows translation of the following system objects:

Drupal 8 status

Alpha10 has been released. It should be considered a major upgrade. See the detailed release notes regarding the upgrade.

See https://github.com/agentrickard/domain for the most current work.

Overview

The Domain Access project is a suite of modules that provide tools for running a group of affiliated sites from one Drupal installation and a single shared database. The module allows you to share users, content, and configurations across a group of sites such as:

• example.com
• one.example.com
• two.example.com
• my.example.com
• thisexample.com <-- can use any domain string
• example.com:3000 <-- treats non-standard ports as unique

By default, these sites share all tables in your Drupal installation.

Installation

Drupal 7

Module installation requires edits to your site's settings.php file. See the online installation guide for details.

Drupal 8

No changes are requires to install the module, but certain configurations need to be edited in services.yml. See the README for details.

Technical background

The module uses Drupal's Node Access system to determine what content is available on each site in the network. Unlike other multi-domain modules for Drupal, the Domain Access module determines user access based on the active domain that the user is viewing, rather than which group or site the user belongs to. For more information about Node Access in Drupal, see http://api.drupal.org/api/group/node_access/7

This module uses some advanced Drupal concepts and requires that you understand and control your site's DNS configuration. See this case-study or this more recent Row Eleven Wine Co. post for more details about using Domain Access.

You can also watch video of the DrupalCON Paris session "Managing Multiple Sites with Domain Access" (from 2009).

If you are looking for a module to provide subdomains to users and groups and do not need to affiliate content, take a look at Subdomain.

The autolocale module and enclosed localized install profile provides a profile to automatically import interface translations in install time and later when modules are enabled / disabled.

Most of the module's functionality (with better implementation) is built into Drupal 6, so there will be no release of this module for Drupal 6. Import and update functionality for translations is maintained in the Localization update module.

This was a placeholder project for the the Internationalization working group work done for Drupal 6. Here people submitted patches against our external repository we used to experiment with solutions at http://svn3.cvsdude.com/devseed/sandbox/i18n/ Drupal 6.0 is out and therefore this project is not used anymore.

The Translation template extractor provides a web based and a command line Gettext translation template extractor interface for Drupal as well as a reusable API to look for translatable strings and translatability errors. This tool is used under the hood at http://localize.drupal.org/ as well to serve as a parsing machine for Drupal.org project releases.