Multilingual

Overview

This module provides an easy and quick way to translate vocabulary terms. When using the Internationalization module to translate the terms of a vocabulary, you might find this very tedious and time consuming. The process will take you trough a couple of screens for each term you want to translate.

Meet "Translate Terms". This module will offer you a tabular overview of all "to be translated" terms as well as the functionality to translate on the fly, within the same screen.

Inspired by #1499526: Remove Detection and Selection local task when a single language is enabled.

It provides a embedded option to write in Bangla Phonetic or in Unijoy format.

This module aims to be a replacement variable handling module for Domain Access, allowing mixed variable realms (domain x language) to be configured.

In other words, it allows setting different variable values for each domain and for each language at the same time.

This module supports almost all of the functionality provided by Domain Configuration, Domain Settings and Domain Theme. Differences are listed in the documentation.

Internationalization contributions is a set of modules that are add ons for Internationalization module to provide compatibility with other contributed modules or some other features.

Features Translations adds a new Features component called Translations that allows to import/export sets of translated strings. String sets can be chosen per language and per text group.

The internationalization module provides a method for synchronizing fields between various translations. This is a wonderful feature, but user experience is horrible.

When creating a new translation for a master node, the translator is presented with all fields on the node, and not just the ones he/she needs to translate. In my opinion this is confusing.

To resolve this, I've created a small helper module, which hides fields which are being synchronized when translating a node.

This module enables block titles and block content to be exported to code (via boxes) and then be translated (via i18n_string).

This is an updated version of the helpful i18nboxes sandbox module by benclark module for Drupal 7.

From benclark's original description:

You need i18n_boxes when

Manages translatable strings with yaml file uploads.

The purpose of this module is to allow the use of .yml (YAML) files with l10n_server.
It adds a connector for uploading .yml files and extract the strings and also allows to import and export yaml translations.

The connector also works as a scanner for .yml files inside a .tar.gz file and will load any strings found into a new project, similar to how l10n_drupal does it.

This module is under active development and i'ts an alpha not ready for production yet.

Change the Default language without changing the default language by using a other language as fallback.