Qt Gui Supported HTML Subset

JonB

I note from http://doc.qt.io/qt-5/richtext-html-subset.html, which is used by QTextDocument itself plus widgets:

specified using a subset of HTML 4 markup

When is this going to hit the 21st century and input/output HTML 5, please? :)

Christian Ehrlicher

Use QWebEngineView when you need a full-blown html browser. Don't know why it should be implemented twice...

JonB

@Christian-Ehrlicher
If you see my thread https://forum.qt.io/topic/91015/export-qtableview-to-pdf, you'll see I'm trying to construct HTML for a QTableView (in this particular instance).

I'm being recommended to do that via QTextDocument structured document, which makes sense. QTextDocument::toHtml() produces HTML 4. I'd like to put that into a QWebEngineView, which (I think you're implying?) uses HTML 5. So maybe the two HTML standards will be sufficiently compatible, maybe they won't...

I'd still like to be able to import/export QTextDocument from/to HTML 5 rather than 4, for other purposes.

I didn't mean it as a slight against Qt (hence the :) in my question)....

Christian Ehrlicher

Since QWebEngineView also understands HTML4 (since it's a complete browser engine) I don't see a problem here.

JonB

@Christian-Ehrlicher
Ah, I see, I didn't know that.

I would have liked to be able to get QTextDocument to output HTML 5 so I could take it elsewhere outside the Qt environment. I would have liked it to be able to parse HTML 5 input, as if I write HTML I do it for HTML 5 without knowing whether it will or will not work for HTML 4. That's all. I'm not going to die over it at present! If the answer is that Qt richtext subset stuff is going to stick at HTML 4, not 5, then at least I know.

No offence intended, I think Qt is just great!

mrjj

@JonB
Hi. Its only meant to be RichText ( like good old ms RTF) not full html.
To allow for Font styles and light formatting.

JKSH

@JonB said in Qt Gui Supported HTML Subset:

If the answer is that Qt richtext subset stuff is going to stick at HTML 4, not 5, then at least I know.

Yeah, I don't foresee the Qt Project developing an in-house HTML 5 renderer anytime soon.

Qt WebKit was dropped because it takes way too much resources to maintain a compliant HTML renderer. Qt WebEngine was chosen as a replacement because it's only a (relatively) thin wrapper around Chromium -- this takes a lot of burden off the Qt Project.