Lionbridge Translation Provider is an external translation service for the Translation Management Tool module. It allows users to send content directly from their Drupal site into Lionbridge onDemand for professional translation by the world's largest translation firm.
D8 port for Translation Access (i18n_access)
This module adds context filtering capabilities to the core translation interface.
Allow to filter the translated strings by context.
Allow to export strings for a specific context.
Provides a field for language combinations.
Originally a sub-module of Translation Management Tool and tweaked to work as a standalone module.
The purpose of this project is to provide custom developed modules the means to get translations into the Drupal's Multilingual (Locale) system. It does this by providing a hook where modules can declare their custom strings and the translations in different languages.
The actual handling of translation is then achieved via a custom drush command that takes the strings and add them into locale with their translation.
The Shamsi module convert Gregorian date of contents to the Persian or Iranian date format without hacking core.
Generally when we are using i18n module for translation then we always want to associate every content with some language. If you notice while adding/editing any node or term by default Language Neutral option appears in Language dropdown.
This module allows to integrate language switches into standard Drupal menus, e.g. Main Menu
The module extends multilingual support for menus on the basis of the i18n package.
* Language switcher items in standard menus
* Automatic update of link path for language switches
* Exclude and include language switches based on "all paths except defined" or "only listed paths"
* Up to 4 language menu sets
This module provides possibility to translate node metatags via TMGMT (metatags
will be extracted from "parent" entity and added to the same job);
