Reyero.net

This module provides full multilanguage support for Drupal. This is having content objects -nodes- and categories which have one language, some navigation elements to select desired language, and then showing only the content in the right language in each page.

Multilingual content

Currently, language has been added for nodes, taxonomy terms and vocabularies. For other objects, like menus or blocks, it may be added in the future.
There are options to have language information or not for selective node types, and also language for taxonomy is not mandatory, thus allowing for terms which will be shown for only one language or for all of them
Some translation information can be added, defining relations between objects in different languages.
One of the main design goals for this module has been the ability to enable/disable i18n without breaking the site at all. If i18n is disabled, all the content will be still available, but having then no separation of languages.

Keeping language in path

Currently, language information is kept in the URL itself as a path prefix, which is removed for incoming URL's and added for outgoing ones. While old versions of the module used some other alternatives -like session- to keep current language, these have been removed, because keeping language in path has a number of advantages and meets some design goals:

+ URL consistency, that is, same URL takes to the same page in the same language. This is important for search engines, and also when sharing links between users.
+ Language aware URL aliases and links, so you can define URL alias which have language information in it, but also language-less aliases or links are allowed, getting then the language from the browser or the user settings

Other Features

- Language block to select language. This one can be used also for anonymous users to select interface language.

- Clear separation of interface and content. Allows mixed interface/content languages. This can be useful for administrators or for translators, who can be viewing a node in any language while keeping the interface in their preferred language.

- Language dependent variables. A list of variables which will be kept separated for each language can be defined in the main configuration file.

- Language field is not mandatory, so you can always have language-less nodes and taxonomy terms. These will show up for all languages.

- Basic interface for nodes and taxonomy translation.

- Path aliases can be defined with and without language preffix. They will work someway ;-)

- Initial language is taken from: url, user, browser, drupal default -in this order-

- The language code is added *always* to the url, thus incoming links should work smoothly

- Integration with locale's defined languages.