Quote Originally Posted by wysota View Post
Start with stopping treating QTextDocument as HTML.
Cann you explain more exact? "treating" http://dictionary.reference.com/ dont have it..

Doc say...

http://doc.trolltech.com/4.0/qabstra...entlayout.html

The QAbstractTextDocumentLayout class is an abstract base class used to implement custom layouts for QTextDocuments. More...

#include <QAbstractTextDocumentLayout>
My question is here on QAbstractTextDocumentLayout if i can manipulate tag and reimplement as xml other tag:

example xml from scribus....

http://tuxmas.lug-bk.de/tuxmas.sla


An here comming xml return...


QString QTextDocument::toHtml ( const QByteArray & encoding = QByteArray() ) const
Returns a string containing an HTML representation of the document.
The encoding parameter specifies the value for the charset attribute in the html header. For example if 'utf-8' is specified then the beginning of the generated html will look like this:
<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>...
If no encoding is specified then no such meta information is generated.
If you later on convert the returned html string into a byte array for transmission over a network or when saving to disk you should specify the encoding you're going to use for the conversion to a byte array here.
See also Supported HTML Subset.


Or better write a :

QString QTextDocument::toNewXML ( const QByteArray & encoding = QByteArray() ) const

a total new one ..? an append the 100% relax ng schema <grammar define ....

If QTextDocument can transform to xml format from scribus all my problem is solved!
and on xslt can make docbook latex word pdf openoffice the scribus format can handle forms coordinate color rgb or cyan... so much choise.

The html paragraph tag dont return point X,Y or height x width