Club Drupal

          if (isset($item['display'])) {

            $file->display = $item['display'];

          }

          if (isset($item['description'])) {

            $file->description = $item['description'];

          }

  if (module_exists('image') && file_entity_file_get_mimetype_type($file) == 'image' && $file->filesize && isset($file->original)) {

    if (!isset($file->metadata)) {

      $file->metadata = array();

    }

    if (!isset($file->original->metadata)) {

      if (!is_object($file->original)) {

        $file->original = new stdClass();

      }

      $file->original->metadata = array();

    }

; Information added by Drupal.org packaging script on 2017-06-19

version = "7.x-2.2"

datestamp = "1497884645"

      'application/zip',

      'application/x-7z-compressed',

      'application/x-tar',

      'application/gzip',

; Information added by Drupal.org packaging script on 2017-06-19

version = "7.x-2.2"

datestamp = "1497884645"

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"

The Block languages module, part of the Internationalization

(https://www.drupal.org/project/i18n) package, allows the user to configure

for which languages each block is visible.

* For a full description of the module,

  visit https://www.drupal.org/node/1279698.

* To submit bug reports and feature suggestions, or to track changes visit

  https://www.drupal.org/project/issues/i18n.

This module requires the following module:

* Internationalization - https://www.drupal.org/project/i18n

* Internationalization Views - https://www.drupal.org/project/i18nviews

* Language Icons - https://www.drupal.org/project/languageicons

* Translation Overview - https://www.drupal.org/project/translation_overview

* Localization Client - https://www.drupal.org/project/l10n_client

* Internationalization contributions -

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

This is a submodule of the Internationalization module. Install the

Internationalization module as you would normally install a contributed Drupal

module. Visit https://www.drupal.org/node/895232 for further information.

The settings for visibility per language are provided under Visibility

Settings via the Languages tab when configuring a block.

The Languages tab also provides a setting for whether the block is translatable.

For custom blocks, the block title and the block content will be translatable.

For blocks defined by modules, only the block title will be translatable. If

"Make this block translatable" is selected, a Translate tab will appear for that

block. This tab provides a UI for adding translations of the block in each

available language.

The Block languages module conflicts with the Context module, which alters how

blocks are rendered. This issue can be tracked in the Internationalization

issue queue: http://drupal.org/node/1343044

The user must allow your used string format to be translated on

admin/config/regional/i18n/strings or you are going to have an error message

like "The string blocks:block:1:body for textgroup blocks is not allowed for

translation because of its text format."

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"

The Contact translation module, part of the Internationalization

(https://www.drupal.org/project/i18n) package, helps with the multilingual

configuration of the site contact forms. This module makes contact categories

and replies available for translation.

* For a full description of the module, visit

  https://www.drupal.org/node/1396984.

* To submit bug reports and feature suggestions, or to track changes,

  visit https://www.drupal.org/project/issues/i18n.

This module requires the following module:

* Internationalization - https://www.drupal.org/project/i18n

* Internationalization Views - https://www.drupal.org/project/i18nviews

* Language Icons - https://www.drupal.org/project/languageicons

* Translation Overview - https://www.drupal.org/project/translation_overview

* Localization Client - https://www.drupal.org/project/l10n_client

* Internationalization contributions -

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

This is a submodule of the Internationalization module. Install the

Internationalization module as you would normally install a contributed Drupal

module. Visit https://www.drupal.org/node/895232 for further information.

1. Enable the Contact translation module included with the Internationalization

   module.

3. Select edit for the form to configure.

4. Select the Translate tab.

5. Select the translate link for a language.

7. Select Save translation.

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"

The Field translation module, part of the Internationalization

(https://www.drupal.org/project/i18n) package, allows for translation of text

associated with a field's settings including the label, help text, default

value, and list options.

* For a full description of the module, visit this page

  https://www.drupal.org/node/1279346.

* To submit bug reports and feature suggestions, or to track changes visit

  https://www.drupal.org/project/issues/i18n.

This module requires the following module:

* Internationalization - https://www.drupal.org/project/i18n

* Internationalization Views - https://www.drupal.org/project/i18nviews

* Language Icons - https://www.drupal.org/project/languageicons

* Translation Overview - https://www.drupal.org/project/translation_overview

* Localization Client - https://www.drupal.org/project/l10n_client

* Internationalization contributions -

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

This is a submodule of the Internationalization module. Install the

Internationalization module as you would normally install a contributed Drupal

module. Visit https://www.drupal.org/node/895232 for further information.

2. Go to Administration > Configuration > Regional and language > Translate

   interface.

3. Select the Filter Translatable Strings field set and limit search to fields.

For the translation to be displayed, the user needs to use some of the Field

Formatters provided by this module whose name usually ends up in 'translated'.

For most core fields it is Default translated.

Note: The Field Translation module does not provide content translation for

fields. This functionality is provided by the Entity Translation (ET) module.

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"

  elseif ($field['type'] == 'node_reference' && isset($element['nid'])) {

    // The node_reference fields using the entityreference_autocomplete widget.

    $alter_element = &$element['nid'];

  }

}

The Multilingual forum module, part of the Internationalization

(https://www.drupal.org/project/i18n) package, helps with the multilingual

configuration of the site’s forums.

* For a full description of the module visit

  https://www.drupal.org/node/1396988.

* To submit bug reports and feature suggestions, or to track changes visit

  https://www.drupal.org/project/issues/i18n.

This module requires the following module:

* Internationalization - https://www.drupal.org/project/i18n

* Internationalization Views - https://www.drupal.org/project/i18nviews

* Language Icons - https://www.drupal.org/project/languageicons

* Translation Overview - https://www.drupal.org/project/translation_overview

* Localization Client - https://www.drupal.org/project/l10n_client

* Internationalization contributions -

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

This is a submodule of the Internationalization module. Install the

Internationalization module as you would normally install a contributed Drupal

module. Visit https://www.drupal.org/node/895232 for further information.

3. Select the "edit vocabulary" for the Forums vocabulary.

5. Select the "Save and translate" button.

6. Select the "translate" link for a language.

8. Select the "Save translation" button.

2. Select the "edit" link for a forum or container.

3. Select the "Translate" tab.

4. Select the "translate" link for a language.

6. Select the "Save translation" button.

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"

The Menu translation module, part of the Internationalization

(https://www.drupal.org/project/i18n) package, allows users to select a

translation mode for each menu.

  https://www.drupal.org/node/1113982.

  https://www.drupal.org/project/issues/i18n.

This module requires the following module:

* Internationalization - https://www.drupal.org/project/i18n

* Internationalization Views - https://www.drupal.org/project/i18nviews

* Language Icons - https://www.drupal.org/project/languageicons

* Translation Overview - https://www.drupal.org/project/translation_overview

* Localization Client - https://www.drupal.org/project/l10n_client

* Internationalization contributions -

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

* Entity translation i18n menu module, a submodule of Entity translation -

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

* Menu translation node module - https://www.drupal.org/project/i18n_menu_node

This is a submodule of the Internationalization module. Install the

Internationalization module as you would normally install a contributed Drupal

module. Visit https://www.drupal.org/node/895232 for further information.

1. To create or edit a menu, navigate to Structure > Menus > (menu to edit) >

   Edit.

2. In the Translation mode section, choose Fixed Language and a Language field

   will appear.

There are three modes available: Translate and Localize, Fixed Language, and No

Multilingual Options.

The user can create one menu for all languages, and translate or localize each

menu item. There are two ways that menu items will be translated.

1. The user can set a language when creating a custom menu item so that the menu

   item will only show up for that language. Menu items that link to nodes in a

   particular language will be treated this way.

2. The user can localize other custom menu items without a language

   (for example, menu items linking to Views pages). Use the Translate tab to

   translate the menu item title and description. Translators can also use the

   "Translate interface" pages to translate these menu items.

If the user chooses Fixed Language, they'll have to set up a separate menu in

each language. This could become tedious if have a lot of languages enabled on

the site, but is useful if the content or menu structure is different for each

language.

A menu item linked to a node will be displayed only when the node language

matches the page language. This is due to how the menu system works and the

"Language selection" feature in i18n. Therefore, to get translated menus items

that link to nodes, you first need translated content. For more information

visit https://www.drupal.org/docs/7/multilingual/translating-content.

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"

The Multilingual content module, part of the Internationalization

(https://www.drupal.org/project/i18n) package, provides extended multilingual

options for nodes. These options help accommodate a variety of translation

workflows by controlling how the language for nodes is set.

Note that the Multilingual content module lives in the i18n_node directory

in the Internationalization package. Don't confuse this module with the core

Content translation module.

* For a full description of the module visit:

  https://www.drupal.org/node/1279644.

* To submit bug reports and feature suggestions, or to track changes visit

  https://www.drupal.org/project/issues/i18n.

This module requires the following module:

* Internationalization - https://www.drupal.org/project/i18n

* Internationalization Views - https://www.drupal.org/project/i18nviews

* Language Icons - https://www.drupal.org/project/languageicons

* Translation Overview - https://www.drupal.org/project/translation_overview

* Localization Client - https://www.drupal.org/project/l10n_client

* Internationalization contributions -

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

This is a submodule of the Internationalization module. Install the

Internationalization module as you would normally install a contributed Drupal

module. Visit https://www.drupal.org/node/895232 for further information.

For each content type, the following Extended language options are available

under the Multilingual Settings tab.

1. "Set current language as default for new content" can be useful for content

   that is community-generated.

3. "Lock language" prevents users from changing the language of a node after

   it's created.

1. There are also site-wide settings provided to help streamline how

   multilingual content is created. Navigate to Config > Regional and language >

   Multilingual settings > Node Options.

2. "Switch interface for translating" switches the language of the user

   interface to the chosen language when a user translates a node. This is

   useful if users speak the language in which the translation is written. It

   means that after the node translation is saved, the language of the UI will

   match the language of the node.

3. "Hide content translation links" will prevent the language switcher links

   from appearing in nodes and teasers. This is useful if a language switcher

   block is enabled on the site.

4. The user can also select the default language for new nodes if the

   corresponding content type doesn't have language support. By default, it is

   set to be in the default language of the site, but this can be changed to be

   language neutral. This is a useful option when thinking about forward

   compatibility for adding multilingual support to these content types in the

   future.

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"

---------------------

The Redirect translation module, part of the Internationalization

(https://www.drupal.org/project/i18n) package, improves search engine

optimization (SEO) for multilingual websites.

It redirects anonymous users (including web crawlers) to the translation of the

page in the requested language, if it exists, using a 301 redirect code.

  https://www.drupal.org/node/1280468.

   https://www.drupal.org/project/issues/i18n.

This module requires the following module:

* Internationalization - https://www.drupal.org/project/i18n

The Translation redirect module requires the implementation of

hook_i18n_translate_path by another module for the redirect page to be

determined. Currently, the Multilingual content, Path translation, and Taxonomy

translation modules implement this hook.

* Internationalization Views - https://www.drupal.org/project/i18nviews

* Language Icons - https://www.drupal.org/project/languageicons

* Translation Overview - https://www.drupal.org/project/translation_overview

* Localization Client - https://www.drupal.org/project/l10n_client

* Internationalization contributions -

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

This is a submodule of the Internationalization module. Install the

Internationalization module as you would normally install a contributed Drupal

module. Visit https://www.drupal.org/node/895232 for further information.

No configuration is necessary.

For node translation, enable the Multilingual content and the Translation

redirect modules. For non-node pages, the redirection hook must be implemented

by the relevant module.

For example, for taxonomy pages, you should enable the Taxonomy translation

module because the module provides the necessary hook code. If you are using the

Path translation module to create translation sets for non-node pages, then it

implements the hook code for determining the redirection page.

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"

The Multilingual select module, part of the Internationalization

(https://www.drupal.org/project/i18n) package, allows the user to define whether

content is filtered by language on pages provided by Drupal core.

* For a full description of the module visit:

  https://www.drupal.org/node/1279512.

* To submit bug reports and feature suggestions, or to track changes visit

  https://www.drupal.org/project/issues/i18n.

This module requires the following module:

* Internationalization - https://www.drupal.org/project/i18n

* Variable - https://www.drupal.org/project/variable

* Internationalization Views - https://www.drupal.org/project/i18nviews

* Language Icons - https://www.drupal.org/project/languageicons

* Translation Overview - https://www.drupal.org/project/translation_overview

* Localization Client - https://www.drupal.org/project/l10n_client

* Internationalization contributions -

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

This is a submodule of the Internationalization module. Install the

Internationalization module as you would normally install a contributed Drupal

module. Visit https://www.drupal.org/node/895232 for further information.

The module allows the user to configure whether or not to filter pages by the

current language. If the Taxonomy translation submodule is also enabled, an

option will be available for how taxonomy term pages are filtered. It also

allows the exclusion of the module’s language selection handling for some

elements and certain paths.

2. Navigate to Configuration > Regional and language > Multilingual settings >

   Selection.

3. Select nodes and taxonomy can be filtered by language in the Content to

   Filter by Language field set.

4. The "Content Selection Mode" allows content with specific tags to be skipped

   by entering a list of tags.

5. The "Enable for Specific Pages" field set allows specific pages to be

   included by path.

6. After making choices, Save configuration.

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"

The String translation module, part of the Internationalization

(https://www.drupal.org/project/i18n) package, provides support for other

modules to translate user-defined strings. This is an API module that must be

enabled only when required by other modules in the i18n package.

  https://www.drupal.org/node/1279668

  https://www.drupal.org/project/issues/i18n

This module requires the following module:

* Internationalization - https://www.drupal.org/project/i18n

* Internationalization Views - https://www.drupal.org/project/i18nviews

* Language Icons - https://www.drupal.org/project/languageicons

* Translation Overview - https://www.drupal.org/project/translation_overview

* Localization Client - https://www.drupal.org/project/l10n_client

* Internationalization contributions -

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

This is a submodule of the Internationalization module. Install the

Internationalization module as you would normally install a contributed Drupal

module. Visit https://www.drupal.org/node/895232 for further information.

Strings will be translated from the source languages. By default the source

language is the site's default language, so changing the default language could

break these translations.

1. The user can set which language is used as the source language via

   Administration > Configuration > Regional and language > Multilingual

   settings > Strings. By default, only plain strings are enabled, so regular

   blocks are not fully translatable.

2. To allow Filtered HTML, Full HTML or Plain text select the appropriate radio

   box(es) and Save configuration.

3. To select the strings to be translated navigate to Administration >

   Configuration > Regional and language > Translate interface and select on

   Stings vertical tab. From here the user can select which text groups to

   translate and select the Refresh strings tab.

The String translation module allows you to configure which text formats are

translatable. Formats like PHP Filter and Full HTML are translated before they

are processed, so allowing a translator to edit these can be a security risk.

This is particularly problematic when importing translations in bulk from a CSV

file, since the translator's access to the import formats isn't verified by

Drupal. After updating this setting, be sure to refresh the strings via

Administration > Configuration > Regional and language > Translate interface >

Strings so that strings in forbidden formats are deleted.

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"

The Taxonomy translation module, part of the Internationalization

(https://www.drupal.org/project/i18n) package, provides multiple options to

translate taxonomy vocabularies and terms. For each vocabulary, there are four

types of behaviors to choose from: Language-independent terms, Language-specific

terms, Localized terms, and Mixed-language vocabulary.

* For a full description of the module visit:

  https://www.drupal.org/node/1114016

* To submit bug reports and feature suggestions, or to track changes visit:

  https://www.drupal.org/project/issues/i18n

This module requires the following module:

* Internationalization contributions -

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

This is a submodule of the Internationalization module. Install the

Internationalization module as you would normally install a contributed Drupal

module. Visit https://www.drupal.org/node/895232 for further information.

Language-specific terms - vocabulary is only used for content in that language.

The terms will only be available if the term language matches the UI language.

Localized terms - Terms are common for all languages, but their name and

description may be localized.

4. Select Translate, translate the Name and Description, select

   "Save translation", and repeat for all languages.

7. By default, the term reference is set to Link. Change this to "Link

   (localized)" and Save.

Mixed-language vocabulary - Use for vocabularies with terms in multiple

languages.

3. Edit a vocabulary term and there will be a new Language field. Choose a

   language and then select Save and translate.

4. There are two options, the user can either select "Add translation link" or

   the user can select an existing term in the Select translations form.

Now if the user edits a node associated with this vocabulary, only the relevant

terms will appear.

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"

  if($view->base_table !== 'rules_scheduler') {

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"

The User mail translation module, part of the Internationalization

(https://www.drupal.org/project/i18n) package, translates emails sent from the

User module.

  https://www.drupal.org/node/133977.

  https://www.drupal.org/project/issues/i18n.

This module requires the following module:

* Internationalization - https://www.drupal.org/project/i18n

* Internationalization Views - https://www.drupal.org/project/i18nviews

* Language Icons - https://www.drupal.org/project/languageicons

* Translation Overview - https://www.drupal.org/project/translation_overview

* Localization Client - https://www.drupal.org/project/l10n_client

* Internationalization contributions -

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

This is a submodule of the Internationalization module. Install the

Internationalization module as you would normally install a contributed Drupal

module. Visit https://www.drupal.org/node/895232 for further information.

1. Navigate to Administration > Configuration > Regional and language >

   Multilingual settings and select the variables tab.

2. Select the "User emails" tab. Select the variables to be translated. Save

   configuration.

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"

The Variable translation module, part of the Internationalization

(https://www.drupal.org/project/i18n) package, allows the user to translate text

and settings that are stored in Drupal as variables. These variables include

text such as 'site name' and 'site slogan', as well as settings like 'Default

front page' and 'Default 404 page'.

* For a full description of the module, visit:

  https://www.drupal.org/node/1113374.

* To submit bug reports and feature suggestions, or to track changes visit:

  https://www.drupal.org/project/issues/i18n.

* Internationalization  - https://www.drupal.org/project/i18n

* Variable - https://www.drupal.org/project/variable

* Internationalization Views - https://www.drupal.org/project/i18nviews

* Language Icons - https://www.drupal.org/project/languageicons

* Translation Overview - https://www.drupal.org/project/translation_overview

* Localization Client - https://www.drupal.org/project/l10n_client

* Internationalization contributions -

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

This is a submodule of the Internationalization module. Install the

Internationalization module as you would normally install a contributed Drupal

module. Visit https://www.drupal.org/node/895232 for further information.

1. Enable the Variable translation module included with the Internationalization

   package.

2. Go to Administration > Configuration > Regional and language > Multilingual

   settings.

3. Select on the Variables tab.

5. Save configuration.

Once the user has the correct settings, they'll be marked with "This is a

multilingual variable" when the user navigates to the corresponding

administration pages. The user must switch the site language while in the

administration pages to set the variables for each language. A language switcher

link will appear at the top of each administrative page that has multilingual

variables.

; Information added by Drupal.org packaging script on 2017-06-17

version = "7.x-1.18"

datestamp = "1497704047"