i18n_string localized term translation doesn't use CKEditor for description

[laryn]

I noticed when translating localized terms that the description displays HTML code instead of using the CK Editor as expected. PR coming.

[indigoxela]

@laryn many thanks for your PR, I'll look into this ASAP, but maybe not before weekend.

[laryn]

Hmm... it's actually not working completely. I hadn't actually tried saving the translation, which produces an SQL syntax error with this PR.

[indigoxela]

@laryn should be fixed in 16c2a2e. Please test thoroughly, the automated tests are passing, but "human eyes" still might find something. 😃

[laryn]

Manually patched my dev site and did some testing -- basic functionality is looking good! A few visual/UI suggestions that come to mind as I am testing:

• can the submit button be wrapped in a '#type' => 'actions' array? I think this gives the button more consistent styling with the rest of the UI
• Adding the CKEditor interface also adds "Formatting options" so the manually added description is duplication:
  
• The CKEditor editing window opens very narrow, it should maybe be made taller by default:
  

[indigoxela]

...A few visual/UI suggestions that come to mind...

@laryn many thanks for testing. The visual glitches should be fixed in 11ff8c9.

[laryn]

Looks great!