Closed (won't fix)
Project:
Google Language Tools
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
11 Mar 2009 at 19:26 UTC
Updated:
30 Mar 2011 at 01:37 UTC
I've tried your development version -- I would certainly find it useful.
On the form I tried it with, I have a wysiwyg editor installed and full HTML fields, for nice looking input.
The "Translate this text" option appears with these fields, but doesn't produce a translation.
It would be a great improvement if text in an HTML field were translated by this module (maintaining the formatting), just as multiline plain text fields are.
Comments
Comment #1
zroger commentedThis module only translates textarea fields. WYSIWYG editors usually swap the textarea for an iframe, and each WYSIWYG editor is implemented differently. The best advice I can give you is to switch to a non-wysiwyg mode before translating, then back to wysiwyg after.
I'm marking this as wont fix, but it is at very least post-poned.
Comment #2
ailgm commentedThat'd be fine as a workaround, if it was just me doing the translations, but every user of the site will be doing this. The first item on your feature wishlist (provide translation suggestions for all of the text inputs on the form) would mitigate the need for it, if it handled HTML fields, but I suspect that it would be subject to the same limitation.
Perhaps an idea on how to do this fairly easily will occur to you someday. If anyone reading this posting has a suggestion, please feel free to offer it.
Comment #3
mgungora commentedI would like to post a patch for this. Is it possible? My version handles tinyMCE and CKEDITOR. It also has some extras like converting a few language codes between drupal and google, ignoring text areas based on ids, etc.