Extend and customize Drupal functionality with contributed modules.
If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
Provides one-way string transliteration (romanization) and cleans file names during upload by replacing unwanted characters.
Generally spoken, it takes Unicode text and tries to represent it in US-ASCII characters (universally displayable, unaccented characters) by attempting to transliterate the pronunciation expressed by the text in some other writing system to Roman letters.
After enabling the module as usual, visit the Manage fields page of the content type, taxonomy vocabulary or "comment type" which you wish to replace fields of and click the replace link. That's all.
Bug fixing policy
This project is maintained mainly through voluntary and sponsored work, this means our resources are limited. Bug reports will be taken into consideration only if they allow to reproduce the reported issue:
Translate views using Internationalization. This is a work in progress and not all Views properties can be translated yet. Requires Internationalization 6.x-1.5 or newer.
This module has been moved from Internationalization package so we can have different branches compatible with each of the Views versions. Use the same branch of the Views version you are using (2.x. 3.x)
Drupal 6 i18nviews 2.x
The 2.x version has grown up over some time. It was already a long way to go and we've collected handler by handler to improve support for all possible cases. However we've also learned that views 2.x translation is sometimes very ugly and hackish. Performance is limited.
Drupal 6 i18nviews 3.x
Views 3 introduces a complete new translation layer. We have pushed views 3 improvements to have a clean next-generation translation system that allows cleaner solution with scaleable performance.
We're working on a stable 3.x solution: We're almost there.
There's a basic D7 port available now. Quality review and finalizing still pending. Your feedback appreciated. Note that we rely on the latest Views 7.x-3.x-dev version, not the alpha or rc.
The work was primary done by Miro Dietiker of MD Systems and dereine of Erdfisch.
Beta 4 introduces some database schema changes, read carefully the release notes before upgrading.
Allows (fieldable) entities to be translated into different languages, by introducing entity/field translation for the new translatable fields capability in Drupal 7. Maintained by the Drupal core i18n team.
This project does not replace the Internationalization project, which focuses on enabling a full multilingual workflow for site admins/builders. Some features, e.g. content language negotiation or taxonomy translation, might overlap but most of them are unrelated.
Title module allows to replace entity labels with fields to make them translatable.
Entity Translation requires core version at least 7.15.
This module helps you fix translations on your site as you see the issues. Just by navigating around your pages, you'll be able to fix translations and fill in missing ones using the on-page translation editor. At the same time, if configured properly, the module also submits your translations back to the community, to localize.drupal.org or any other localization server.
Localized Drupal, an install profile that will download translations automatically (and comes with Localization client and Localization update).
The Format Number API module provides a method to configure number formats (site default and user defined) with configurable decimal point and thousand separators.
This module also provides the 'numericfield' Forms API element, which is a right aligned text input element that allows the user enter numbers using the configured thousands separator and decimal point (site default or user defined). This Forms API element provides a validation callback that is used automatically and that ensures input is valid numeric as per the options defined for the element.
The Translation Overview page provides a table listing the site's nodes and showing what's been translated into each language. It also lets you assign priorities for translating nodes into the various languages.
For translations of taxonomy terms and menu items check out the Translation table module.
The Translation template extractor provides a web based and a command line Gettext translation template extractor interface for Drupal as well as a reusable API to look for translatable strings and translatability errors. This tool is used under the hood at http://localize.drupal.org/ as well to serve as a parsing machine for Drupal.org project releases.
Web based extraction: If you are a translator, install the module on a Drupal site as you would with any other module. Once potx module is turned on, you can go to the "Extract strings" tab on the Locale administration interface, select the module or theme you want to have a translation template for, and submit the form. You will get one single template file generated.
Web based code review: If you are a module or theme developer, install this module and the coder review module. Pick the Interface text translatability review offered by potx and check your module for translatability problems.
Translation helpers enables other modules to respond to changes in the "source translation" of a set of translated content. This functionality is useful for modules that track data by the "source translation" (node.tnid value).
This module doesn't do anything on its own. You should install it only if it's suggested or required by another module you're using.
The module also provides other methods for modules to use with translated content.
A Drupal 8 version won't be needed. Translation Helpers addresses use cases related to the model of translation used in the Drupal 7 core Content Translation module, in which each language has its own node. Drupal 8 has switched to fields-based translation, in which the awkward workarounds of D7 will be a thing of the past.
The Mail Editor module lets you edit the bodies and subjects of all emails that go out from your site to your users through Drupal's drupal_mail() function. You are able to edit any email body text based on which email it is and which language it is being sent for. You may use token variables in your templates to better customize dynamic email text.
Mail Editor has special support built-in for the User core module and the LoginToboggan module. Enable the Locale core module to activate non-English and even multi-lingual email template translation.
Mail Editor was originally written for D5 by chx, and rewritten and expanded for D6 by litwol. Thanks to both! The D7 version was ported and adapted to use the new core tokens by salvis.
Mail Editor for Drupal 7
We recommend installing the Token module for assistance with editing the templates and to get access to the tokens that it provides.
Client modules can enhance Mail Editor by exposing additional standard token types and even adding types of their own. The Subscriptions module does this extensively, and it also adds a preview feature to Mail Editor.
UI for quick translation of taxonomies and menus. The i18n module allows for translation of taxonomy terms and menu items, but the process is tedious - you need to look up strings you want to translate, there is no overview of what's already translated etc.
This module presents your taxonomy terms or menu items in a table, and each language has a corresponding column. Just fill out the translations and click Save.
Requires the i18n module, and either taxonomy or menu string translation.
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.
Divide your website page to a number of sections where each sections contains nodes in one language (see the screenshot).
Currently with core locale module, there is two language switcher blocks, one for interface, and the other for the content. This module should only alter the content one, not the interface one. Currently, it alters the interface block!
Enable Locale and Content Translation modules.
Add other languages, e.g. Arabic, French (admin/config/regional/language).
Go to Language Switcher config page (admin/config/regional/language/language_switcher), select what mode you want to use.
Go the content type you want the translation to be enabled on, select `Enable, with node translation` (e.g. admin/structure/types/manage/article).
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.
The Node Relationships module provides methods to complete two way relationships between content types enhancing the features of node reference fields.
It provides the following features:
Enhancements for node reference fields: "View reference in new window", "Edit reference" (in modal frame, updates widget if node title changes), "Search and reference view" (single and multiple selection based on dynamically configured views), "Create and reference" and "Translate and reference" (when the Drupal core translation module is enabled, with additional support for Internationalization module). These features use the Modal Frame API to provide popup dialogs from buttons attached to node reference fields configured to use the autocomplete widget.
Automatic back references using dynamically configured views that are able to extract the relations from existing database information. This views can be rendered using a myriad of methods in the node view.
The Node Relationships module provides default views for each feature that can be modified and/or cloned (recommended) should you need to add more fields, filters or change any other option to suit your needs.
Basic entity relations diagram (ERD) that can be used to view the relations of each individual content type. The provided diagram can be used to walk the relationships of all types in the system.