function webform_localization_help in Webform Localization 7.4

Same name and namespace in other branches

1. 7 webform_localization.module \webform_localization_help()

Implements hook_help().

File

./webform_localization.module, line 21

Webform localization module.

Code

function webform_localization_help($section = 'admin/help#webform_localization', $arg = NULL) {
  $output = '';
  switch ($section) {
    case 'admin/help#webform_localization':
      $output = '<p>' . t('The Webform Localization module provides multilingual features to the Webform Module. Special options in the webform and component configuration let you enable different ways to manage translation of forms and questionnaires.') . '</p>';
      $output .= '<p>' . t('You can choose two different ways to manage localization that cover this scenarios:') . '</p>';
      $output .= '<p>' . t('A) <strong>If you want to keep a single webform across all nodes in a translation set:</strong><br />Use i18n_string integration to translate webform strings. This module expose webform properties, components and emails strings through the i18n module. All submissions results are related to the original node only.<br />(You have a "<em>localization by string translation</em>" fieldset in the form settings to enable this)') . '</p>';
      $output .= '<p>' . t('B)<strong> If you want to keep a webform per node per language but synchronized:</strong><br />The entire webform structure is replicated when a translated node is created then you can customize it at will. You can add specific options or components per language and choose to keep sync: webform properties, components properties, roles and emails recipients. In this scenario make no sense of having results attached to one node since each webform could have a different structure with only a few components in sync.<br />(You have a "<em>localization by sync</em>" fieldset in the form settings to enable this)') . '</p>';
      break;
  }
  return $output;
}