WYSIWYG editors don't work on Translation Editor page

Issue Summary

All translation fields are text areas, regardless of the type of the original fields. So for example Title is a text area instead of a simple text field, therefore if I enable CKEditor for all text areas, the Title field will be WYSIWYG as well, and will become <p>My title</p>, which is undesirable. If I don't enable WYSIWYG on all text areas, CCK fields with Full HTML filter won't be WYSIWYG, which means the translator would need to edit html-formatted text in plain text, and that's undesirable as well.

CKEditor also lets me disable WYSIWYG on specific fields, but I can't use that to solve this problem, because on the Translation Editor page the field IDs are not unique for each content type. So for example, in my case the ID of a field is translate/3.edit-field-data-translated-3. I can't exclude this from CKEditor, because next time I translate a page, this field will be translate/4.edit-field-data-translated-3, and i can't exclude translate/*.edit-field-data-translated-3 either, because in an other content type edit-field-data-translated-3 might be a Full HTML field.

Possible solutions:
- Only those fields that are originally text areas should be text areas during translation.
- The ID of the fields should contain the content type.