>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #208539. --> Reported by: [alex ua](https://www.drupal.org/user/110386) >>> <p>***I'm pretty sure that this should be seperated into at least two (if not more) tasks, but I'm putting it up here as one for the moment as it is to hopefully get some feedback on if/where it should be split. We could also make it so they can just choose a few of the items (or groups of items, since some belong together)***</p> <p>The Auto Translate Module ( <a href="http://drupal.org/project/i18n_auto">http://drupal.org/project/i18n_auto</a> ) aims to assist with translations on Drupal sites by allowing content creators to press a button which scrapes the text area of a node, queries a third party translation service, and pastes the resulting translation which can then be edited and posted as a translation. When this module is complete it will greatly reduce the amount of time needed to translate a site, making it much easier to maintain multi-lingual content-heavy Drupal sites. However, the module is still in a development release, and needs a few significant improvements to bring it to the level of a full release. </p> <p>Tasks<br> The following need to be completed before the module can be released. The student is expected to complete at least X of these tasks for this project.<br> 1) it needs a checkbox on node type admin screens. then the node-&gt;body will work w/ that<br> 2) it needs to be activated for cck text fields (and #2 should only happen when #1 is true)<br> 3) a link to add autotranslate to any textarea (currently it only works on text areas on the node submissions page)<br> 4) an administrators option to decide where the translation links should appear and an "on/off" link under text areas<br> 5) make the other 2 translation providers functional (currently only google translation works) and research their Terms of Service (TOS) to ensure that the module doesn't put the users into violation of their rules.<br> 6) research new providers, and their TOS<br> 7) Write a warning message to be displayed on activation of module or configuration of its settings about providers TOS<br> 8) Add logos/links to provider's TOS on the admin page, and possibly on the auto translate form element<br> 9) integrate the with the i18n and locale modules, to allow the module to autofill i18n fields and determine the translation via the locale settings.<br> 10) make sure that accented characters are formatted correctly.</p> <p>Fixes for these items should be submitted to the issue queue as patches. To complete these tasks the student will have to demonstrate that the fixes work in at least 3 browsers.</p> <p>Resources<br> Google Translate - <a href="http://www.google.com/translate_t">http://www.google.com/translate_t</a><br> Yahoo Translate - <a href="http://babelfish.yahoo.com/">http://babelfish.yahoo.com/</a><br> Internationalization Module - <a href="http://drupal.org/project/i18n">http://drupal.org/project/i18n</a><br> CAPTCHA Module - <a href="http://drupal.org/project/captcha">http://drupal.org/project/captcha</a></p> <p>Primary Contact(s)<br> Aaorn Winborn (aaron) with help from Alex Urevick-Ackelsberg (Alex UA)</p>