Unsupported

This module makes modifications to the Style Guide module through Style Guide's api.

Project moved to https://drupal.org/project/locale_import_export

This module gives site editors an edit tab for each language that your site supports. Currently it works only for nodes, but the next versions will support different entity types (such as taxonomy and user, among others).

UPDATE: the 7.x-1.1 release brings this module up-to-date with entity_translation. Hurray!

Awesome Features

• Users go directly to the version of the page they want to edit
• Creating a new translation alerts the user there is no previous version and takes them to the add translation page
• For "Language Neutral" pages which need the user to specify the language before it becomes translatable, it will prompt the user to set the language and save before the translation can be created
• Users can post the source translation in any language, the old "Edit" button (renamed to "Source") will always direct the user there
• Now you can enjoy all the benefits of using entity_translation...

Other Modules to Consider for use with Entity Translation

This module is for module writers and has no UI of its own. Unless some other module uses it, it won't add anything to your site. Only install this module if another module requires it.

Drupal 8 converts all entities to full objects so there will be no D8 version of this module.

The field_extract module provides a couple of easy-to-use functions that make extracting data from entity fields much easier - as a developer you don't have to worry about languages and deltas, you just make the call.

It's worth noting that the functionality in this module overlaps with the Entity API wrapper. The object-based wrapper is more elegant than this procedural solution but it's heavier and slower, so you have a choice.

For clarity: this module does not load individual Field API fields for entities, it accesses the contents of Field API fields that are already loaded into entities. That's important because the $user object and taxonomy terms are often loaded by Drupal without their Field API fields. You may need to use the field_attach_load() call to get the fields before using field_extract_value().

Features

• Easy to use - just two functions to choose from
• Support for core fields and popular third party fields built-in

tracking aloha with own patches

This is no longer needed as #1820882 was committed to CTools.

Original description: