Multilingual

Internationalisation Helper (i18n_helper) provides additional useful functions to i18n

1. CCK Fields synchronised by i18n_sync may be configured to be hidden or read-only in node views and node edit forms.
2. CCK Fields not synchronised by i18n may be configured to be blank when new translations are created.
3. A "Create translation stubs" action is provided, which when executed by a VBO (Views Bulk Operations) or Rule allows bulk or automatic creation of new translations.

USAGE:

Language Switcher for Drupal 7 is an enhancement for core language switcher block in local module. It's very useful for websites with multi-languages where you want to display content in different languages side-by-side. Watch this video to better understand the concept.

Features:

Divide your website page to a number of sections where each sections contains nodes in one language (see the screenshot).

User's IP address as a Context condition.

Requirements

• Context 3.0 or higher
• GeoIP API

Sponsored by BloomIdea. Drupal 7 port by Int3c.com: Multilingual Drupal Development.

Ukrainian Stemmer algorithm for internal Drupal Searching for Ukrainian language

Обговорення модуля на офіційному сайті українських друпалерів

This module allows sites to have multilingual books.

Users can translate book pages in any language, without adding the translation to a new book outline.

Why

In Drupal, book outlines are not translated by the Internationalization or Locale modules. Before this module was coded, the solution was to create multiple books, one for each language. But this is very cumbersome and not effective at all, especially when having many languages.

Pages module allows you to create dynamic pages (nodes) from static text files.

It's a simple module, and useful when working with installation profiles.

Pages grabs the files from two locations:

• "files/pages" directory
• "modules/pages/pages"

You can put the files inside folders to organize them, e.g.:

Aggregates a user's profile nodes into one.

You have several different pieces of profile information about your users regarding to their work, eating habits, leisure time, and so on, all of which are considered to be semi-private (ie. may be hidden from eg. unauthenticated users). You may want to make (some part of) their profile data merged into one node per user, possibly with some considerably different layout and/or access control. You have set up different content types: 'work', 'eating', 'leisure', and 'public_profile', all of them set up with Content Profile module--but how to merge the first three into the fourth?

Here comes profile_aggregator.module handy. Just select the source profiles ('work', 'eating' and 'leisure'), select the target profile ('public_profile') with the appropriate format, and let the users update their pieces of profile information while having Drupal do the merge part of the work!

Translation Workflow is a translation management and workflow for Drupal 7. Based on the new Content Translation which introduces entity/field translation for the new translatable fields capability in Drupal 7.

Features

Drupal 8 Version

The 8.x-dev version currently is undergoing a massive streamlining in the translations-export and translaions-import commands to eventually move this component to core (#1820542: Make customized translations deployable). Please check on updates for syntax changes. If you want to track this or help, see #2922656: Roadmap to stable D8 release.

Overview

Drush commands allowing languages to be added, switched, enabled, disabled, imported, exported and update prefix from the commandline. This module only provides drush commands, so you will see no functionality in the UI.

Translation own nodes provides users with the possibility to translate their own content without giving them any global translation permissions.