Multilingual

Domain Locale allows to customize language sets per domain for Drupal installs using Domain Access and core Locale module.

On install Domain Locale enables all enabled languages for all domains setting either site default language as default for each domain or uses language_default variable set by Domain Conf (if it is enabled). A link is added to domain management section to administer domain specific languages. You can choose one or more from the enabled languages, change the weight they appear in for that domain and set default language for the domain. Updating this form will also keep language_default variable in Domain Conf in sync.

Things to keep in mind:
1. If you want a language enabled on a subdomain, it must be enabled for the default domain (e.g. sitewide settings). The reason lies in language_list() in bootstrap.inc
2. Set language negotiation to "Path prefix only". We are overriding $language in bootstrap hence overwriting any changes that might of been user's preferred language specific. Also user's preferred language might not exist all domains. You can leave the setting to "Path prefix with language fallback" but the language fallback will be overwritten.

Optional:
1. make sure all languages have a prefix (by default English does not). This gives unique urls for all languages on all domains.

Requires Domain Access rc9 or newer!

Automatically update your site translations!

The FeedAPI Language Filter is a simple add-on for the FeedAPI Item Filter module that allows incoming feed items to be filtered by language, using the Google AJAX Language API. This module differs from FeedAPI Language Detector module in that this module filters out feed items before they are added to Drupal.

Currently only the title field can be filtered on, though I would gladly accept patches that expand the module to support other fields.

This module provides a set of country icons and an API for retrieving and displaying them. It was originally designed for use with the ip2cc module, which stores it's own set of country icons. I wanted to extract these icons from the ip2cc module as it really is additional functionality to that module, that is probably not needed by the majority of ip2cc users. However, it seems apparent that several other modules also include their own set of country flag icons, and would possibly benefit from sharing the resource...

Currently there are 5 API functions:

Here is a scenario:

You run a Drupal 6 multilingual site (lets say English & Spanish). You set up the Story content type as a translatable content type and enable the language switcher block on the header.
Now lets say you write your first story in English about your life in the country and You immediately translate it to Spanish - so that all your friends in Barcelona will be able to read it.
After that you get exited and you write another story in English - this time a story about your life as a spy in the cold war days. you want to translate this story as well, but your mother calls you to eat dinner and you totally forget about the translation.

After a day or so a guy named Sergio for Argentina bumps into your site and starts reading the articles you wrote - after a while of reading the story about your life in the country in English he discovers the language switcher Spanish link so he clicks on it and sees the story in his native language.

But what would happen if he was reading your second and untranslated story and wanted to switch it to Spanish?!

Well the answer is that he'll get the English version again :(

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.