Multilingual

Field Extended API is an API module whose goal is improving the developer experience (DX) of the core Field API, which is currently in a pretty bad shape due to field language handling.

This issue is being addressed in #1260640: Improve field language API DX. Meanwhile this module provides a way to experiment and find out the right API functions to introduce in core.

Provides links on one site that point to a specific page on another site.

This module enables you to match pages across sites, and in the case where there is no match take a best guess at a match.

User Case

A common user case is that you run example.com (US), example.co.jp (Japanese), and example.co.de (German). You want to have links at the top of each page of these sites pointing to the equivalent page on the other sites.

Instructions

Instructions in the module README.txt file

Description

This module allows you to present visitors of your website with a landingpage / splash page where they can select the language of their choice, based on the languages that have been enabled on your Drupal site.

This is useful in situations where you don't want to enforce a default language to users (e.g. because of political or corporate sensitivities) if they come to your website without a language preference available (url, cookie, ...)

The language selection page can be overridden through Drupal's template system.

This module contains new date/time field that supports other calendar systems.
There is also a views integration module.

Requirements
Date
Calendar systems

Comment translation utilizes the Microsoft Translator to create translations of submitted comments on nodes that have existing translations available. Translated comments are placed in moderation for review.

Comment translation will also synchronize comments when a node becomes translated, automatically translating the published comments to the node. Combined with another translation module (such as ELI) for nodes, it can allow a site to operate a fully localized discussion blog or forum.

[EN]

This is my first drupal project

Small module that solves the following specific use case:

When you translate a node that has one or more Entity Reference fields that reference other nodes, the translation form contains default values that point to nodes in the originating language.

This might result into an error that the referenced entity is invalid if you don't remove the references, or adds the burden of having to look up the translated versions of the referenced nodes manually.

Allows translation and localizing of Panels pane titles that were specified in the Panels UI.

Aren't there other ways to solve this?

Absolutely, and I don't necessarily recommend this module for all cases. Ideally, you would be managing the pane title via a token or a generated title callback in the content_type plugin.

That being said, there are plenty of instances where you're forced to type the title in manually, or have parts of the title be literal strings while the rest is replaced with tokens. And in those cases, on a multilingual site, you're going to want a way to translate those strings.

TMGMT Server extends the industry standard TMGMT Workflow to remote instances (http://www.drupal.org/project/tmgmt). It can be activated on a Drupal installation different from the on that contains the contents you want to translate. The exchange of information is done through services.