now each gadget should do translation by itself
for the iframe reason

1. remove catch error in gadget_erp5.js and gadget_translate.js.
2. add acquisition method getTranslationMethod in main gadget.
3. add translaton_look key in configuration to define translation scipt.
4. fix can't save when edit.

1. Use form submit instead of ajax in erp5_gadgetfield.js file
2. Data decode is realized in GadgetFieldValidator
3. Move jio files in erp5_core for activity watcher gadget
4. Update gadgetfield test
   Add test with RelationStringField
   Remove DataURL test which is not necessary

Add IE supported

- make sure only strings are passed to and returned from translation gadget
- make sure to wrap in correct temporary elements (table rows in table, options in select, rest in div)
- make sure forms are present when declareService is called

- add notifyUpdate method to re-render header once translations are available
- add translations to all text elements

- update handlebars template, web sites with translations will have a collapsible language menu.
- add collapsible menu inside listview
- fix missing form element on panel searchfield
- add handler to retrieve available languages when creating template
- add translations for all text elements used
- update declareService to handle multiple forms (close panel, searchfield, languages)

- add uritemplate
- add getTranslationDict method to retrieve a language dictionary from ERP5
- add fetchLanguage to handle browser working with "en-EN" vs gadget/ERP5 only using "en"
- add ready handler to retrieve languages from web_site_module and translation method from custom
initialization gadget (temp fix) to remove hardcoded configuration parameters
- add error handler to catch missing translation method and not translate/expose language options to
ensure compat with existing rJS web sites
- add ready handler to initialize plugin and re-render header once translations are available
- add method to expose available languages, so they can be fetched from the panel gadget
- fix translation methods to only work with strings being passed in and out

- switch gadget declarations in html (translate needs jio_ajax, must be available before header/panel)
- add translation method bridge
- add notifyUpdate to re-render header once translations are available
- add getSiteRoot to return root url, so translation gadget can fetch languages declared on website
- add error handlers to make sure existing rjs websites don't break

Do not merge in Master

- Tested on an instance which DOM seems to be different than
  default one.

This reverts commit b8f34d3c.

tl;dr currently function/forum/{administrator,user} are mapped to Author
      only role on forum module without also mapping to Auditor role.

      Auditor role is needed because by definition Author cannot view
      content and without such role Admin & User cannot see
      DiscussionThreadModule at all.

      Similarly besides having Author role, Users also need to have
      Auditor role on DiscussionThread in order to view threads.

Currently for DiscussionThreadModule we map categories

    function/forum/administrator    and
    function/forum/user

to one Author role in A5 speak.

Then, for forum, it is assumed that each user will be assigned only one
functional category to each user (e.g. only one of
function/forum/{administrator,user,visitor}).

So it turns out e.g. function/forum/administrator category is mapped to
only Author role on DiscussionThreadModule.

Now by definition Authors can create documents, but they cannot
access/view them (as per http://www.erp5.org/ERP5SecurityModel).
This is also indirectly justified by default-assigned security settings
for Author role - see section "Adjust Permissions on the Module" -
Author is not allowed to "View".

    So if forum administrator is only mapped to Author role, he can
    _not_ view/access the forum module.

And I discovered this exactly this way - usual visitors (who map to
Auditor role) were being able to see the module, but admin and users
could not.

To solve this logically, lets also map

    function/forum/administrator    and
    function/forum/user

to Auditor role on DiscussionThreadModule (i.e. they now both map to
Author & Auditor). And now both admin & user can access/view the module
& create threads.

Similarly without Auditor role on DiscussionThread, User cannot view it.
( And Administrator has Assignor on DiscussionThread which allows viewing
  by itself )

NOTE for DiscussionPost we don't need to change anything in order for
users to view it because DiscussionPost acquires local roles.
Helped-by: Klaus Wölfel <klaus@nexedi.com>