/ - Diff - Club Drupal - Forge Centrale Marseille

     files[] = i18n.test
     configure = admin/config/regional/i18n
     ; Information added by Drupal.org packaging script on 2016-10-22
     version = "7.x-1.14"
     ; Information added by Drupal.org packaging script on 2017-01-31
     version = "7.x-1.15"
     core = "7.x"
     project = "i18n"
     datestamp = "1477154943"
     datestamp = "1485834792"

     CONTENTS OF THIS FILE
     ---------------------
     * Introduction
     * Requirements
     * Recommended modules
     * Installation
     * Configuration
     * Troubleshooting
     * Maintainers
     INTRODUCTION
     ------------
     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
     REQUIREMENTS
     ------------
     This module requires the following modules:
     Internationalization - https://www.drupal.org/project/i18n
     RECOMMENDED MODULES
     -------------------
     *  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
     INSTALLATION
     ------------
     * 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/docs/7/extending-drupal-7/installing-contributed-modules-find-import-enable-configure-drupal-7 for further information.
     CONFIGURATION
     -------------
     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.
     TROUBLESHOOTING
     ---------------
     Conflicts with Context
     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
     String Errors
     The user must allow your used string format to be translated on admin/config/regional/i18n/strings or you are going to have a error message like "The string blocks:block:1:body for textgroup blocks is not allowed for translation because of its text format."
     MAINTAINERS
     -----------
     * Jose Reyero - https://www.drupal.org/u/jose-reyero
     * Florian Weber (webflo) - https://www.drupal.org/u/webflo
     * Peter Philipp - https://www.drupal.org/u/das-peter
     * Joseph Olstad - https://www.drupal.org/u/joseph.olstad
     * Nathaniel Catchpole - https://www.drupal.org/u/catch

     files[] = i18n_block.test
     ; Information added by Drupal.org packaging script on 2016-10-22
     version = "7.x-1.14"
     ; Information added by Drupal.org packaging script on 2017-01-31
     version = "7.x-1.15"
     core = "7.x"
     project = "i18n"
     datestamp = "1477154943"
     datestamp = "1485834792"

     CONTENTS OF THIS FILE
     ---------------------
     * Introduction
     * Requirements
     * Recommended modules
     * Installation
     * Configuration
     * Maintainers
     INTRODUCTION
     ------------
     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
     REQUIREMENTS
     ------------
     This module requires the following modules:
     Internationalization (https://www.drupal.org/project/i18n)
     RECOMMENDED MODULES
     -------------------
     * 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)
     INSTALLATION
     ------------
     * This is a submodule of the Internationalization module. Install the Internationalization module as you would normally install a contributed Drupal module. See https://drupal.org/documentation/install/modules-themes/modules-7 for further information.
     CONFIGURATION
     -------------
 . Enable the Contact translation module included with the Internationalization module.
 . Go to Administration > Structure > Contact form.
 . Click edit for the form to configure.
 . Click the Translate tab.
 . Click the translate link for a language.
 . Translate the Category and Auto-reply text.
 . Click Save translation.
 . Repeat steps 5 to 7 for each language.
 . Repeat steps 2 to 8 for all forms.
     MAINTAINERS
     -----------
     * Jose Reyero - https://www.drupal.org/u/jose-reyero
     * Florian Weber (webflo) - https://www.drupal.org/u/webflo
     * Peter Philipp - https://www.drupal.org/u/das-peter
     * Joseph Olstad - https://www.drupal.org/u/joseph.olstad
     * Nathaniel Catchpole - https://www.drupal.org/u/catch

     package = Multilingual - Internationalization
     core = 7.x
     ; Information added by Drupal.org packaging script on 2016-10-22
     version = "7.x-1.14"
     ; Information added by Drupal.org packaging script on 2017-01-31
     version = "7.x-1.15"
     core = "7.x"
     project = "i18n"
     datestamp = "1477154943"
     datestamp = "1485834792"

     CONTENTS OF THIS FILE
     ---------------------
     * Introduction
     * Requirements
     * Recommended modules
     * Installation
     * Configuration
     * Maintainers
     INTRODUCTION
     ------------
     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
     REQUIREMENTS
     ------------
     This module requires the following modules:
     Internationalization (https://www.drupal.org/project/i18n)
     RECOMMENDED MODULES
     -------------------
     * 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)
     INSTALLATION
     ------------
     * This is a submodule of the Internationalization module. Install the Internationalization module as you would normally install a contributed Drupal module. Visit https://drupal.org/documentation/install/modules-themes/modules-7 for further information.
     CONFIGURATION
     -------------
 . Enable the Field translation module included with Internationalization.
 . Go to Administration > Configuration > Regional and language > Translate interface.
 . Click on Filter Translatable Strings field set and limit search to fields.
 . Edit the desired field and Save.
     For the translation to be displayed, you need 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.
     MAINTAINERS
     -----------
     * Jose Reyero - https://www.drupal.org/u/jose-reyero
     * Florian Weber (webflo) - https://www.drupal.org/u/webflo
     * Peter Philipp - https://www.drupal.org/u/das-peter
     * Joseph Olstad - https://www.drupal.org/u/joseph.olstad
     * Nathaniel Catchpole - https://www.drupal.org/u/catch

     core = 7.x
     files[] = i18n_field.inc
     files[] = i18n_field.test
     ; Information added by Drupal.org packaging script on 2016-10-22
     version = "7.x-1.14"
     ; Information added by Drupal.org packaging script on 2017-01-31
     version = "7.x-1.15"
     core = "7.x"
     project = "i18n"
     datestamp = "1477154943"
     datestamp = "1485834792"

         return $info;
+      }
+    }
     /**
      * Implements hook_field_info_alter().
      */
     function i18n_field_field_info_alter(&$field_info) {
       foreach(array_keys($field_info) as $type) {
         $field_info[$type]['property_callbacks'][] = 'i18n_field_entity_property_callback';
+      }
+    }
     /**
      * Callback to translate entity property info for a fields.
+     *
      * @see entity_metadata_field_entity_property_info()
      * @see entity_metadata_field_default_property_callback()
      * @see i18n_field_i18n_object_info_alter()
      * @see hook_module_implements_alter()
      */
     function i18n_field_entity_property_callback(&$info, $entity_type, $field, $instance, $field_type) {
       global $language;
       // This could create a endless recursion if it's called during rebuilding the
       // cache for i18n_object_info(). So if the cache of i18n_object_info isn't
       // available yet we assume the worst case, leave the info alone but trigger a
       // rebuild of the property when hook_i18n_object_info_alter is invoked. At
       // that point the info is available and we can rely on it.
       if (!$info = &drupal_static('i18n_object_info')) {
         $i18n_field_entity_property_callback_fallback = &drupal_static(__FUNCTION__);
         $i18n_field_entity_property_callback_fallback = TRUE;
         return;
+      }
       $name = $field['field_name'];
       $property = &$info[$entity_type]['bundles'][$instance['bundle']]['properties'][$name];
       $property['label'] = i18n_field_translate_property($instance, 'label', $language->language);
+    }
     /**
      * Implements hook_i18n_object_info_alter().
      */
     function i18n_field_i18n_object_info_alter(&$info) {
       if (drupal_static('i18n_field_entity_property_callback')) {
         if ($info = drupal_static('i18n_object_info')) {
           // Clean static and permanent cache of the data and then re-run the property
           // building.
           drupal_static_reset('entity_get_property_info');
           cache_clear_all('entity_property_info:' . $GLOBALS['language']->language, 'cache');
           entity_get_property_info();
+        }
         else {
           watchdog('i18n_field', 'Unable to run fall-back handling for entity property translation due missing "i18n_object_info" cache', array(), WATCHDOG_WARNING);
+        }
+      }
+    }
     /**
      * Implements hook_module_implements_alter().
      */
     function i18n_field_module_implements_alter(&$implementations, $hook) {
       if ($hook == 'i18n_object_info_alter') {
         // Move our hook implementation to the bottom.
         $group = $implementations['i18n_field'];
         unset($implementations['i18n_field']);
         $implementations['i18n_field'] = $group;
+      }
+    }

     CONTENTS OF THIS FILE
     ---------------------
     * Introduction
     * Requirements
     * Recommended modules
     * Installation
     * Configuration
     * Maintainers
     INTRODUCTION
     ------------
     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
     REQUIREMENTS
     ------------
     This module requires the following modules:
     * Internationalization (https://www.drupal.org/project/i18n)
     RECOMMENDED MODULES
     -------------------
     * 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)
     INSTALLATION
     ------------
     * This is a submodule of the Internationalization module. Install the Internationalization module as you would normally install a contributed Drupal module. See https://www.drupal.org/docs/7/extending-drupal-7/installing-contributed-modules-find-import-enable-configure-drupal-7 for further information.
     CONFIGURATION
     -------------
     To configure forum vocabulary
 . Enable the Multilingual forum module included with Internationalization.
 . Go to Administration > Structure > Taxonomy.
 . Click "edit vocabulary" for the Forums vocabulary.
 . Choose the translation mode (Localize or Translate).
 . Click "Save and translate" button.
 . Click "translate" link for a language.
 . Translate the "Name" and "Description" for the forum.
 . Click "Save translation" button.
 . Repeat steps 6 to 8 for each language.
     To configure forum terms
 . Go to Administration > Structure > Forums.
 . Click "edit" link for a forum or container.
 . Click "Translate" tab.
 . Click "translate" link for a language.
 . Translate the "Name" and "Description" for the term.
 . Click "Save translation" button.
 . Repeat steps 4 to 6 for each language.
 . Repeat all steps for all terms.
     MAINTAINERS
     -----------
     * Jose Reyero - https://www.drupal.org/u/jose-reyero
     * Florian Weber (webflo) - https://www.drupal.org/u/webflo
     * Peter Philipp - https://www.drupal.org/u/das-peter
     * Joseph Olstad - https://www.drupal.org/u/joseph.olstad
     * Nathaniel Catchpole - https://www.drupal.org/u/catch

     core = 7.x
     files[] = i18n_forum.test
     ; Information added by Drupal.org packaging script on 2016-10-22
     version = "7.x-1.14"
     ; Information added by Drupal.org packaging script on 2017-01-31
     version = "7.x-1.15"
     core = "7.x"
     project = "i18n"
     datestamp = "1477154943"
     datestamp = "1485834792"

     CONTENTS OF THIS FILE
     ---------------------
     * Introduction
     * Requirements
     * Recommended modules
     * Installation
     * Configuration
     * Troubleshooting
     * Maintainers
     INTRODUCTION
     ------------
     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.
     * For a full description of the module, visit this page:
     https://www.drupal.org/node/1113982
     * To submit bug reports and feature suggestions, or to track changes:
     https://www.drupal.org/project/issues/i18n
     REQUIREMENTS
     ------------
     This module requires the following modules:
     * Internationalization (https://www.drupal.org/project/i18n)
     RECOMMENDED MODULES
     -------------------
     * 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)
     To link menu item menus to nodes, it is useful to have the following modules:
     * Entity translation i18n menu module, a sub module of Entity translation (https://www.drupal.org/project/entity_translation)
     * Menu translation node module (https://www.drupal.org/project/i18n_menu_node)
     INSTALLATION
     ------------
     * 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/docs/7/extending-drupal-7/installing-contributed-modules-find-import-enable-configure-drupal-7 for further information
     CONFIGURATION
     -------------
     Language-specific menus
 . To create or edit a menu, navigate to Structure > Menus > (menu to edit) > Edit.
 . In the Translation mode section, choose Fixed Language and a Language field will appear.
 . Select a language, select Save, and add or update the menu items as needed.
     The menu block will only appear when viewing content in the same language.
     There are three modes available:
     Translate and Localize:
     You can create one menu for all languages, and translate or localize each menu item. There are two ways that menu items will be translated.
 . You 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.
 . You 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.
     Fixed Language:
     If you choose Fixed Language, you'll have to set up a separate menu in each language. This could become tedious if have a lot of languages enabled on your site, but is useful if the content or menu structure is different for each language.
     No Multilingual Options:
     Only the menu will be translatable.
     TROUBLESHOOTING
     ---------------
     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.
     MAINTAINERS
     -----------
     * Jose Reyero - https://www.drupal.org/u/jose-reyero
     * Florian Weber (webflo) - https://www.drupal.org/u/webflo
     * Peter Philipp - https://www.drupal.org/u/das-peter
     * Joseph Olstad - https://www.drupal.org/u/joseph.olstad
     * Nathaniel Catchpole - https://www.drupal.org/u/catch

     files[] = i18n_menu.inc
     files[] = i18n_menu.test
     ; Information added by Drupal.org packaging script on 2016-10-22
     version = "7.x-1.14"
     ; Information added by Drupal.org packaging script on 2017-01-31
     version = "7.x-1.15"
     core = "7.x"
     project = "i18n"
     datestamp = "1477154943"
     datestamp = "1485834792"

       $items['admin/structure/menu/item/%menu_link'] = $items['admin/structure/menu/item/%menu_link/edit'];
       $items['admin/structure/menu/item/%menu_link']['type'] = MENU_CALLBACK;
       $items['admin/structure/menu/item/%menu_link/edit']['type'] = MENU_DEFAULT_LOCAL_TASK;
       $items['admin/structure/menu/manage/%menu']['title callback'] = 'i18n_menu_menu_overview_title';
+    }
     /**
      * Preprocess theme_menu_admin_overview to translate menu name and description
+     *
      * @param $variables
      */
     function i18n_menu_preprocess_menu_admin_overview(&$variables) {
       $variables['title'] = i18n_string(array('menu', 'menu', $variables['name'], 'title'), $variables['title']);
       $variables['description'] = i18n_string(array('menu', 'menu', $variables['name'], 'description'), $variables['description']);
+    }
     /**
      * Title callback for the menu overview page and links.
      */
     function i18n_menu_menu_overview_title($menu) {
       return i18n_string(array('menu', 'menu', $menu['menu_name'], 'title'), $menu['title']);
+    }
     /**
-...
      * Add a "translate" link in operations column for each menu item.
      */
     function i18n_menu_form_menu_overview_form_alter(&$form, &$form_state) {
       foreach (element_children($form) as $element) {
         if (substr($element, 0, 5) == 'mlid:') {
           $mlid = $form[$element]['#item']['mlid'];
           if (i18n_get_object('menu', $mlid)->get_translate_access()) {
             $form[$element]['operations']['translate'] = array(
               '#type' => 'link',
               '#title' => t('translate'),
               '#href' => "admin/structure/menu/item/{$mlid}/translate",
             );
       if (i18n_menu_mode($form['#menu']['menu_name'], I18N_MODE_MULTIPLE)) {
         foreach (element_children($form) as $element) {
           if (substr($element, 0, 5) == 'mlid:') {
             $item = $form[$element]["#item"];
             $mlid = $form[$element]['#item']['mlid'];
             if (i18n_get_object('menu', $mlid)->get_translate_access()) {
               $form[$element]['operations']['translate'] = array(
                 '#type' => 'link',
                 '#title' => t('translate'),
                 '#href' => "admin/structure/menu/item/{$mlid}/translate",
               );
               $form[$element]['title']['#markup'] = l(_i18n_menu_link_title($item), $item['href'], $item['localized_options']);
+            }
+          }
+        }
+      }
-...
+    }
     /**
      * Implements hook_init().
      */
     function i18n_menu_init() {
       // The only way to override the default preferred menu link for a path is to
       // inject it into the static cache of the function menu_link_get_preferred().
       // The problem with the default implementation is that it does not take the
       // language of a menu link into account. Whe having different menu trees for
       // different menus, this means that the active trail will not work for all but
       // one language.
       // The code below is identical to the mentioned function except the added
       // language condition on the query.
       // TODO: Adding an alter tag to the query would allow to do this with a simple
       // hook_query_alter() implementation.
       $preferred_links = &drupal_static('menu_link_get_preferred');
       $path = $_GET['q'];
       // Look for the correct menu link by building a list of candidate paths,
       // which are ordered by priority (translated hrefs are preferred over
       // untranslated paths). Afterwards, the most relevant path is picked from
       // the menus, ordered by menu preference.
       $item = menu_get_item($path);
       $path_candidates = array();
       // 1. The current item href.
       $path_candidates[$item['href']] = $item['href'];
       // 2. The tab root href of the current item (if any).
       if ($item['tab_parent'] && ($tab_root = menu_get_item($item['tab_root_href']))) {
         $path_candidates[$tab_root['href']] = $tab_root['href'];
+      }
       // 3. The current item path (with wildcards).
       $path_candidates[$item['path']] = $item['path'];
       // 4. The tab root path of the current item (if any).
       if (!empty($tab_root)) {
         $path_candidates[$tab_root['path']] = $tab_root['path'];
+      }
       // Retrieve a list of menu names, ordered by preference.
       $menu_names = menu_get_active_menu_names();
       // Use an illegal menu name as the key for the preferred menu link.
       $selected_menu = MENU_PREFERRED_LINK;
       // Put the selected menu at the front of the list.
       array_unshift($menu_names, $selected_menu);
       $query = db_select('menu_links', 'ml', array('fetch' => PDO::FETCH_ASSOC));
       $query->leftJoin('menu_router', 'm', 'm.path = ml.router_path');
       $query->fields('ml');
       // Weight must be taken from {menu_links}, not {menu_router}.
       $query->addField('ml', 'weight', 'link_weight');
       $query->fields('m');
       $query->condition('ml.link_path', $path_candidates, 'IN');
       // Only look menu links with none or the current language.
       $query->condition('ml.language', array(LANGUAGE_NONE, i18n_language_interface()->language), 'IN');
       // Sort candidates by link path and menu name.
       $candidates = array();
       foreach ($query->execute() as $candidate) {
         $candidate['weight'] = $candidate['link_weight'];
         $candidates[$candidate['link_path']][$candidate['menu_name']] = $candidate;
         // Add any menus not already in the menu name search list.
         if (!in_array($candidate['menu_name'], $menu_names)) {
           $menu_names[] = $candidate['menu_name'];
+        }
+      }
       // Store the most specific link for each menu. Also save the most specific
       // link of the most preferred menu in $preferred_link.
       foreach ($path_candidates as $link_path) {
         if (isset($candidates[$link_path])) {
           foreach ($menu_names as $menu_name) {
             if (empty($preferred_links[$path][$menu_name]) && isset($candidates[$link_path][$menu_name])) {
               $candidate_item = $candidates[$link_path][$menu_name];
               $map = explode('/', $path);
               _menu_translate($candidate_item, $map);
               if ($candidate_item['access']) {
                 $preferred_links[$path][$menu_name] = $candidate_item;
                 if (empty($preferred_links[$path][MENU_PREFERRED_LINK])) {
                   // Store the most specific link.
                   $preferred_links[$path][MENU_PREFERRED_LINK] = $candidate_item;
+                }
+              }
+            }
      * Implements hook_query_TAG_alter()
+     *
      * Using tag 'preferred_menu_links' added in menu_link_get_preferred().
      * See http://drupal.org/node/1854134
      */
     function i18n_menu_query_preferred_menu_links_alter(QueryAlterableInterface $query) {
       global $language;
       // Get queried tables.
       $tables = $query->getTables();
       foreach ($tables as $alias => $table) {
         if ($table['table'] == 'menu_links') {
           // Add language filter, ensuring that we don't have any collision when
           // determining the active menu trail when there are multiple menu items
           // with same link path but different languages.
           if ($language) {
             $query->condition('language', array($language->language, LANGUAGE_NONE), 'IN');
+          }
           break;
+        }
+      }
+    }

     CONTENTS OF THIS FILE
     ---------------------
     * Introduction
     * Requirements
     * Recommended modules
     * Installation
     * Configuration
     * Maintainers
     INTRODUCTION
     ------------
     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
     REQUIREMENTS
     ------------
     This module requires the following modules:
     * Internationalization (https://www.drupal.org/project/i18n)
     RECOMMENDED MODULES
     -------------------
     * 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)
     INSTALLATION
     ------------
     * This is a submodule of the Internationalization module. Install the Internationalization module as you would normally install a contributed Drupal module. See https://www.drupal.org/docs/7/extending-drupal-7/installing-contributed-modules-find-import-enable-configure-drupal-7 for further information.
     CONFIGURATION
     -------------
     For each content type, the following Extended language options are available under the Multilingual Settings tab
 . "Set current language as default for new content" can be useful for content that is community-generated.
 . "Require language" prevents users from creating 'Language neutral' nodes.
 . "Lock language" prevents users from changing the language of a node after it's created.
     Site-wide Settings for Node Translation
 . 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.
 . "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.
 . "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.
 .You 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.
     MAINTAINERS
     -----------
     * Jose Reyero - https://www.drupal.org/u/jose-reyero
     * Florian Weber (webflo) - https://www.drupal.org/u/webflo
     * Peter Philipp - https://www.drupal.org/u/das-peter
     * Joseph Olstad - https://www.drupal.org/u/joseph.olstad
     * Nathaniel Catchpole - https://www.drupal.org/u/catch

     files[]=i18n_node.test
     files[]=i18n_node.variable.inc
     ; Information added by Drupal.org packaging script on 2016-10-22
     version = "7.x-1.14"
     ; Information added by Drupal.org packaging script on 2017-01-31
     version = "7.x-1.15"
     core = "7.x"
     project = "i18n"
     datestamp = "1477154943"
     datestamp = "1485834792"

drupal7/sites/all/modules/i18n/i18n_node/i18n_node.module
506	506	}
507	507	}
508	508	elseif (variable_get('i18n_node_default_language_none', 0) && !isset($form['#node']->nid)) {
509		// Override locale module setting default language to nodes. It is already in form_state.
510		$form['language']['#value'] = $form_state['values']['language'] = LANGUAGE_NONE;
	509	// Only do this if the language is really disabled
	510	if (variable_get('language_content_type_' . $node->type, 0) == 0) {
	511	// Override locale module setting default language to nodes. It is already in form_state.
	512	$form['language']['#value'] = $form_state['values']['language'] = LANGUAGE_NONE;
	513	}
511	514	}
512	515	// Translate field names for title and body for the node edit form.
513	516	if (!empty($form['title']['#title'])) {

     files[] = i18n_path.inc
     files[] = i18n_path.test
     ; Information added by Drupal.org packaging script on 2016-10-22
     version = "7.x-1.14"
     ; Information added by Drupal.org packaging script on 2017-01-31
     version = "7.x-1.15"
     core = "7.x"
     project = "i18n"
     datestamp = "1477154943"
     datestamp = "1485834792"

     CONTENTS OF THIS FILE
     ---------------------------
     * Introduction
     * Requirements
     * Recommended modules
     * Installation
     * Configuration
     * Maintainers
     INTRODUCTION
     ------------
     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.
     * For a full description of the module, visit this page:
     https://www.drupal.org/node/1280468
     * To submit bug reports and feature suggestions, or to track changes:
     https://www.drupal.org/project/issues/i18n
     REQUIREMENTS
     ------------
     This module requires the following modules:
     * 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.
     RECOMMENDED MODULES
     -------------------
     * 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)
     INSTALLATION
     ------------
     * 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/docs/7/extending-drupal-7/installing-contributed-modules-find-import-enable-configure-drupal-7 for further information.
     CONFIGURATION
     -------------
     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.
     MAINTAINERS
     -----------
     * Jose Reyero - https://www.drupal.org/u/jose-reyero
     * Florian Weber (webflo) - https://www.drupal.org/u/webflo
     * Peter Philipp - https://www.drupal.org/u/das-peter
     * Joseph Olstad - https://www.drupal.org/u/joseph.olstad
     * Nathaniel Catchpole - https://www.drupal.org/u/catch

     package = Multilingual - Internationalization
     core = 7.x
     ; Information added by Drupal.org packaging script on 2016-10-22
     version = "7.x-1.14"
     ; Information added by Drupal.org packaging script on 2017-01-31
     version = "7.x-1.15"
     core = "7.x"
     project = "i18n"
     datestamp = "1477154943"
     datestamp = "1485834792"

     CONTENTS OF THIS FILE
     ---------------------
     * Introduction
     * Requirements
     * Recommended modules
     * Installation
     * Configuration
     * Maintainers
     INTRODUCTION
     ------------
     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
     REQUIREMENTS
     ------------
     This module requires the following modules:
     * Internationalization (https://www.drupal.org/project/i18n)
     * Variable (https://www.drupal.org/project/variable)
     RECOMMENDED MODULES
     -------------------
     * 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)
     INSTALLATION
     ------------
     * This is a submodule of the Internationalization module. Install the Internationalization module as you would normally install a contributed Drupal module. See https://www.drupal.org/docs/7/extending-drupal-7/installing-contributed-modules-find-import-enable-configure-drupal-7 for further information.
     CONFIGURATION
     -------------
     The module allows you 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.
 . Enable the Multilingual select module included with Internationalization.
 . Go to Configuration > Regional and language > Multilingual settings > Selection.
 . Select nodes and taxonomy can be filtered by language in the Content to Filter by Language field set.
 . The "Content Selection Mode" allows content with specific tags to be skipped by entering a list of tags.
 . The "Enable for Specific Pages" field set allows specific pages to be included by path.
 . After making choices click Save configuration.
     MAINTAINERS
     -----------
     * Jose Reyero - https://www.drupal.org/u/jose-reyero
     * Florian Weber (webflo) - https://www.drupal.org/u/webflo
     * Peter Philipp - https://www.drupal.org/u/das-peter
     * Joseph Olstad - https://www.drupal.org/u/joseph.olstad
     * Nathaniel Catchpole - https://www.drupal.org/u/catch

     configure = admin/config/regional/i18n/select
     files[] = i18n_select.test
     ; Information added by Drupal.org packaging script on 2016-10-22
     version = "7.x-1.14"
     ; Information added by Drupal.org packaging script on 2017-01-31
     version = "7.x-1.15"
     core = "7.x"
     project = "i18n"
     datestamp = "1477154943"
     datestamp = "1485834792"

     CONTENTS OF THIS FILE
     ---------------------
     * Introduction
     * Requirements
     * Recommended modules
     * Installation
     * Configuration
     * Maintainers
     INTRODUCTION
     ------------
     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.
     * For a full description of the module, visit this page:
     https://www.drupal.org/node/1279668
     * To submit bug reports and feature suggestions, or to track changes:
     https://www.drupal.org/project/issues/i18n
     REQUIREMENTS
     ------------
     This module requires the following modules:
     Internationalization (https://www.drupal.org/project/i18n)
     RECOMMENDED MODULES
     -------------------
     * 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)
     INSTALLATION
     ------------
     * 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/docs/7/extending-drupal-7/installing-contributed-modules-find-import-enable-configure-drupal-7 for further information.
     CONFIGURATION
     -------------
     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.
 . You 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.
 . To allow Filtered HTML, Full HTML or Plain text select the appropriate radio box(es) and Save configuration.
 . To select the strings to be translated navigate to Administration > Configuration > Regional and language > Translate interface and select on Stings vertical tab. From here you can select which text groups to translate and select the Refresh strings tab.
     FAQ
     ---
     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.
     MAINTAINERS
     -----------
     * Jose Reyero - https://www.drupal.org/u/jose-reyero
     * Florian Weber (webflo) - https://www.drupal.org/u/webflo
     * Peter Philipp - https://www.drupal.org/u/das-peter
     * Joseph Olstad - https://www.drupal.org/u/joseph.olstad
     * Nathaniel Catchpole - https://www.drupal.org/u/catch

     files[] = i18n_string.test
     configure = admin/config/regional/i18n/strings
     ; Information added by Drupal.org packaging script on 2016-10-22
     version = "7.x-1.14"
     ; Information added by Drupal.org packaging script on 2017-01-31
     version = "7.x-1.15"
     core = "7.x"
     project = "i18n"
     datestamp = "1477154943"
     datestamp = "1485834792"

     files[] = i18n_sync.module.inc
     files[] = i18n_sync.node.inc
     files[] = i18n_sync.test
     ; Information added by Drupal.org packaging script on 2016-10-22
     version = "7.x-1.14"
     ; Information added by Drupal.org packaging script on 2017-01-31
     version = "7.x-1.15"
     core = "7.x"
     project = "i18n"
     datestamp = "1477154943"
     datestamp = "1485834792"

     CONTENTS OF THIS FILE
     ---------------------
     * Introduction
     * Requirements
     * Recommended modules
     * Installation
     * Configuration
     * Maintainers
     INTRODUCTION
     ------------
     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
     REQUIREMENTS
     ------------
     This module requires the following modules:
     * Internationalization - https://www.drupal.org/project/i18n
     RECOMMENDED MODULES
     -------------------
     * 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
     INSTALLATION
     ------------
     * 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/docs/7/extending-drupal-7/installing-contributed-modules-find-import-enable-configure-drupal-7 for further information.
     CONFIGURATION
     -------------
     Language-independent terms - only vocabulary will be translatable.
 . Navigate to Structure > Taxonomy.
 . Select the "edit vocabulary" link.
 . Select the "No multilingual options for terms".
     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.
 . Navigate to Structure > Taxonomy and select the "edit vocabulary link".
 . Choose "Fixed Language" and a Language drop-down field will be displayed.
 . Select the language.
 . Select "Fixed Language" and Save.
     Localized terms - Terms are common for all languages, but their name and description may be localized.
 . Navigate to Structure > Taxonomy > vocabulary-to-edit > Edit.
 . Select "Localize" and select Save.
 . Edit a term and there will be a Translate tab. Select this tab.
 . Select Translate, translate the Name and Description, select "Save translation", and repeat for all languages.
 . Repeat the process for all terms.
 . Navigate to Structure > Content types > term-to-edit > Manage display.
 . By default, the term reference is set to Link. Change this to "Link (localized)" and Save.
     The vocabulary will be appropriate for the language.
     Mixed-language vocabulary - Use for vocabularies with terms in multiple languages.
 . Navigate to Structure > Taxonomy > vocabulary-to-edit > Edit.
 . Select the Translate radio button and Save.
 . Edit a vocabulary term and there will be a new Language field. Choose a language and then select Save and translate.
 . 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.
 . Create translations for the terms and add terms for specific languages only.
     Now if the user edits a node associated with this vocabulary, only the relevant terms will appear.
     MAINTAINERS
     -----------
     * Jose Reyero - https://www.drupal.org/u/jose-reyero
     * Florian Weber (webflo) - https://www.drupal.org/u/webflo
     * Peter Philipp - https://www.drupal.org/u/das-peter
     * Joseph Olstad - https://www.drupal.org/u/joseph.olstad
     * Nathaniel Catchpole - https://www.drupal.org/u/catch

     files[] = i18n_taxonomy.admin.inc
     files[] = i18n_taxonomy.test
     ; Information added by Drupal.org packaging script on 2016-10-22
     version = "7.x-1.14"
     ; Information added by Drupal.org packaging script on 2017-01-31
     version = "7.x-1.15"
     core = "7.x"
     project = "i18n"
     datestamp = "1477154943"
     datestamp = "1485834792"

         $query->join('taxonomy_term_hierarchy', 'h', 'h.tid = t.tid');
         $result = $query
           ->addTag('translatable')
           ->addTag('term_access')
           ->addTag('taxonomy_term_access')
           ->fields('t')
           ->fields('h', array('parent'))
           ->condition('t.vid', $vid)
-...
+        }
+      }
+    }
     /**
      * Implements hook_views_pre_render().
      */
     function i18n_taxonomy_views_pre_render(&$view) {
       if(!module_exists('rules_scheduler')) {
         global $language;
         foreach ($view->result as $delta => $term){
           if (isset($term->tid)) {
             i18n_string_translate_langcode($language->language);
             $localized_term = i18n_taxonomy_localize_terms(taxonomy_term_load($term->tid));
             $term->tid = $localized_term->tid;
             $term->taxonomy_term_data_name = $localized_term->name;
             $term->taxonomy_term_data_description = $localized_term->description;
+          }
+        }
+      }
+    }

         $query = db_select('taxonomy_term_data', 't')
           ->fields('t', array('tid', 'name'));
         $query->addTag('translatable');
         $query->addTag('term_access');
         $query->addTag('taxonomy_term_access');
         // Disable i18n_select for this query
         $query->addTag('i18n_select');
         // Add language condition

     files[] = i18n_translation.inc
     ; Information added by Drupal.org packaging script on 2016-10-22
     version = "7.x-1.14"
     ; Information added by Drupal.org packaging script on 2017-01-31
     version = "7.x-1.15"
     core = "7.x"
     project = "i18n"
     datestamp = "1477154943"
     datestamp = "1485834792"

     CONTENTS OF THIS FILE
     ---------------------
     * Introduction
     * Requirements
     * Recommended modules
     * Installation
     * Configuration
     * Maintainers
     INTRODUCTION
     ------------
     The User mail translation module, part of the Internationalization (https://www.drupal.org/project/i18n) package, translates emails sent from the User module.
     * For a full description of the module, visit this page:
     https://www.drupal.org/node/133977
     * To submit bug reports and feature suggestions, or to track changes:
     https://www.drupal.org/project/issues/i18n
     REQUIREMENTS
     ------------
     This module requires the following modules:
     Internationalization (https://www.drupal.org/project/i18n)
     RECOMMENDED MODULES
     -------------------
     * 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)
     INSTALLATION
     ------------
     * 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/docs/7/extending-drupal-7/installing-contributed-modules-find-import-enable-configure-drupal-7 for further information.
     CONFIGURATION
     -------------
     To configure email translations
 . Navigate to Administration > Configuration > Regional and language > Multilingual settings and select the variables tab.
 . Select the "User emails" tab. Select the variables you would like translated and Save configuration.
     MAINTAINERS
     -----------
     * Jose Reyero - https://www.drupal.org/u/jose-reyero
     * Florian Weber (webflo) - https://www.drupal.org/u/webflo
     * Peter Philipp - https://www.drupal.org/u/das-peter
     * Joseph Olstad - https://www.drupal.org/u/joseph.olstad
     * Nathaniel Catchpole - https://www.drupal.org/u/catch

     package = Multilingual - Internationalization
     dependencies[] = i18n_variable
     ; Information added by Drupal.org packaging script on 2016-10-22
     version = "7.x-1.14"
     ; Information added by Drupal.org packaging script on 2017-01-31
     version = "7.x-1.15"
     core = "7.x"
     project = "i18n"
     datestamp = "1477154943"
     datestamp = "1485834792"

      */
     function i18n_user_mail_alter(&$message) {
       if ($message['module'] == 'user') {
         $language = $message['language'];
         $language = (isset($message['language']) ? $message['language'] : language_default());
         $variables = array('user' => $message['params']['account']);
         $key = $message['key'];

     CONTENTS OF THIS FILE
     ---------------------
     * Introduction
     * Requirements
     * Recommended modules
     * Installation
     * Configuration
     * Maintainers
     INTRODUCTION
     ------------
     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
     REQUIREMENTS
     ------------
     This module requires the following modules:
     * Internationalization (https://www.drupal.org/project/i18n)
     * Variable (https://www.drupal.org/project/variable)
     RECOMMENDED MODULES
     -------------------
     * 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)
     INSTALLATION
     ------------

Projet

Général

Profil

Club Drupal

Révision b3ab3446

Ajouté par Assos Assos il y a plus de 7 ans