Qt Designer: Simple HTML formatting option effects immediately lost

A recent change (in the last year I think) has now made populating rich-text static content into read-only QTextEdit/QTextBrowsers virtually useless where that text needs to be translatable for I18n purposes. As has been the case for the last ten years that QTBUG-1136 has been open Qt Linguist cannot handle the display of HTML and will display the raw text content to translators.

In the past Qt Designer has been largely content to leave what I might describe as "simple HTML" mark-up alone - especial if the "Simplify Rich Text" option is selected on the text entry form in Qt Designer (see indicated option on "Screenshot_editor.png"). Indeed as long as that control was left active then text enter/edited to be like "Screenshot_simple.png" was left untouched. Whilst that would end up turning into the "Screenshot_unpleasant.png" form if it was edited whilst in the "Rich Text" tab view it would be possible to hand-edit it back again. However the current Qt Creator now always converts the HTML into the unsimple form which I show as "Screenshot_repulsive.png".

There is no way anyone could hope to comprehend that even before the '<'/'>' and '&' at least are converted to HTML entities so they can be stored in the XML that is the `.ui` form/dialogue storage file format. And that is what users of Qt Linguist are suppose to read to convert into a different language.

Please, as a minimum, can Designer be revised to not un-simplify rich-text that has been explicitly set to be simple.

Of course there is something that would render this Issue moot - and that would be incorporating whatever the code is that renders all three of the samples of HTML in those pictures into the same rendered content (like Snapshot_rendered_HTML.png) into the guts of Qt Linguist so it too can show and allow edits to the translat-ish-able text. It is almost as if it needs a widget that can show either the rendered or raw HTML of the source text and allow entry of a translated version - and it is fortunate that the Qt Designer has one of those already operating - even if it cannot save what was actually entered without mangling to an much less user readable source form before it stores it at present...