Capella 1.2.1 - Export Rich Text Description with M2Doc

I’m using Capella 1.2.1 and the corresponding M2Doc add-on.
In Capella, the Editor that appears when I select a Description field of an object allows to enter Rich Text.
(eg. One
Two Three
Four Five)
When I export the model using M2Doc, I see in MS-Word text with markup signs, and the formatting is lost

One Two Three Four Five …

My question is: is it possible to configure something somewhere to get the formatting in MS-Word after the export ? If not, as a workaround, is it possible to desactivate the Rich-Text editor ? (that would of course be a pity)

Dear Bernard,
For the moment the xhtml insertion is only an experimental development in M2Doc. There is a bug for this topic and for more general support of xhtml. The current result if not what ones would expect, but you can give it a try using this commit 4f00032d8ed99512d1606 and this example rg.obeonetwork.m2doc.html.tests/resources/m2DocHtmlServices/ fromHTMLStringWithBaseURI

Dear Bernard,
You can test the pxDoc document generation tool: the
language keyword allows to include HTML content in your generated document. It is simply implemented in that way:
Note: The HTML language renderer is an open source project which we are improving as we found some issues
You can find more information about pxDoc here: and to start with the Capella enabler (open source pxDoc connector) and some dedicated examples:
http:// =article&id=1&Itemid=142#pxDoc. Do not hesitate to contact me if you need some support to start with pxDoc!

Thank you Yvan; the bug & topic you refer too correspond indeed exactly to my concern.
Do you have already an estimation (even a very rough indication would help) of when this new feature could be released ?
According to your link, the topic #265 targets M2Doc 2.1.0 which is currently scheduled for the 5th of October …
(and if it is possible in the meantime to desactivate the rich text editor and/or to export only the raw text without the surrounding

Kind regards,

any update ?
issue is still there with Capella 1.3 and M2Doc 2.02

We don’t have a release date for this feature. The
PoC we have so far need the input to be xhtml not broken html. This make it hard to use when you don’t control the input html.
For the next release our goal will be to improve user experience. From the very first steps with M2Doc by improving the documentation to better interation with the interpreter view…
If you have any ideas on how to make M2Doc more user friendly you can submit them on the github by opening a
new issue.