Multilingual

Need for phonetic editing has its roots in different keyboard layouts developed and used by different users and multiple fonts which in combination failed to produce unique easy to use compatible typing/editing solution. The problem is more in the area of software solutions being developed for different Indic Languages. Web based Direct editing or phonetic editing is an implementation which allows user to type in the context using phonetic key patterns across different keyboards, browsers and different Indic scripts.

What is gamabhana?

gamabhana is an open source implementation that uses purely client side java script to enable phonetics in editable html tags such as div (not editable in mozilla firefox) , iframe, input, textarea, document so that you can type in the context phonetically in the selected Indic script with transliteration capabilities that support unicode fonts with the help of pre-designed gamabhana maps.

With gamabhana library and gamabhana phonetic maps you can:

* Attach phonetics to editable html tags such as iframe and/or input (single line) and/or textarea and/or document.
* Design your own transliteration maps for any language/script.
* Achieve Unicode support across browsers, applications, platforms.
* Type in the context phonetically ( direct input method) in IE ( V 5 above) and Firefox Mozilla.

At one step you create node with translations. Taxonomy and other cck
fields bind to these translations too.

LangsAtOnce creates additional title, body fields for selected languages. So
when you go "create node" page you face with normal fields and
title/body areas. These additional ares will be added as translations.

For the moment, there will be no port to D8+ for this module. Instead, please check out this one, which is basically the same:

https://www.drupal.org/project/existing_values_autocomplete_widget

This module adds 3 autocomplete widgets for CCK fields of type Text and Number.

• Autocomplete for allowed values list: This widget can be used for Text and Number fields and it takes candidate values from the defined list of Allowed values of the fields. You can even generate your allowed values list using PHP, so the limit to provide a widget with autocomplete features is your imagination!
• Autocomplete for existing field data: This widget can be used for Text only and it takes candidate values from existing values in the database for that field.
• (7.x only) Autocomplete for predefined suggestions: This widget can be used for Text only and allows an admin to provide a list of suggestions but still allows users to enter anything they want in a text field. Use this widget to help avoid (but not prevent) variations of the same value. Ex: burger, hamburger, Burger ...
• (7.x only) Autocomplete for existing field data and some node titles: This widget works just like the "existing field data" widget above except it will also suggest node titles for nodes of a specific content type(s).

All widgets allow you to choose the size of the text element and the method used to match values between 'Starts with' and 'Contains'. You can also enable case sensitive or insensitive matches option. Note however that MySQL may ignore case sensitivity depending on the collation used in your database definition.

When the Internationalization module is enabled, the 'Autocomplete for existing field data' widget also provides an option to filter values by the language assigned to their corresponding nodes. This option allows you to provide a different set of allowed values per language.

This is a helper module to address some problems in Drupals language behaviour.

Language Checker module provides a tiny little overview page which lists each installed module's translation percentage for each enabled language, and overalls.

Redirect by URL alias.