(SUGGESTION) Rich text editing

[adrienne]

@joedixon --

So, first of all, I love this package. Most of the other packages to handle translation-related stuff are storing long blocks of crap as JSON in database columns and i hate that.

However, I'm running into a limitation: Some of my translation strings are rich text, and some of them are long. Editing with the little inline editor is pretty tricky, and definitely not useful for my client. Basically, what I'd like is to be able to toggle a rich text editor for some strings. (Nova already provides Trix.)

Here are some possible ways I've thought of to do this:

• It happens that in my application, all my rich text translation keys are in the same group. So if there were a configuration setting that let me say, for instance, "everything in the specified groups should show Trix instead of a textarea", that would solve it
• You could just allow a manual selection of plain/rich text by having two action buttons (one for "edit" and one for "rich edit")

Also, especially with the rich text editor, in-column string editing is a little squished. Perhaps consider popping up a modal for the editor instead?

[joedixon]

Thanks for you kind words.

I like this idea, but I'm a little strapped for time at the moment. Would you be interested in submitting a PR for this?