Multilingual

The Views Languages Field module provides a Views field displaying the languages a node is already translated in or can be translated in

Allow to use special chars in Twitter filters for hashtags and usernames.

Geolocation

This module allows you to specify a language fallback for each defined language, so translation can fallback to another language.

This module is being written for content that is using Entity Translation so that the path for a node is the same for all languages.

The sales pitch

Do you use a node for your 404 page?

Do you hate how translating the node behind the 404 page (or 403 page, or front page) doesn't actually work the way you'd think it would? By default, everyone will see the 404 page you configured under Site Information by default. To show translated versions for other languages, you have to turn on the Internationalization Variable submodule from the Internationalization module. You then have to tell it which node to use for each language where it isn't the default-language node.

UNTIL NOW!

Internationalization 404 leaps into action just before your 404 (403, front) page is served and changes it to the translated version instead.

But wait, there's more! It actually checks to see if you have configured a different node with the help of the Internationalization Variable module, and respects that setting.

This module was developed because featurizing variables containing node paths didn't seem like the way to go. If we already have translated content, why should we also have to translate the variables? We only need to know the source node, and there is less chance for human error in configuring that.

Installation