Antoine Durr
If you figure this out, let me know! I've been trying to figure out exactly the same thing for a while, and basically gave up.
The fundamental problem is that the houdini-wiki expects text, wiki text to be specific. If you have your own wiki, e.g. TWiki, Tiki Wiki, MediaWiki, etc. the output of that is html, not plain text.
I suppose if you could make a theme for your helpcard wiki pages (I'm defining a theme to be css + text->html processing) that deliberately skips all processing, you might be able to get output that's pretty close to the original input.
Then all that's left is to actually get your wiki to call SESI's wiki translator, and create HTML out of that.
The thing I really want to avoid is the double work of doing macros/scripts from one wiki format to another, is not really a problem to embeed the output of SESIWiki into an other wiki or doc system, cos at the end everything is html.
The key thing is how to use the wiki engine used by Houdini for your own pourposes. So you can do two things:
Having a text file in SESIWiki format convert it to html
Having a site, for instance, the studio intranet, how to use the SESIWiki into it so people can directly write Houdini inhouse tools docs in the SESIWiki format and keep a consistency with the Houdini docs
Another useful thing will be in the case you can get a html file, as you have said with the output from othe wikis, how to make an operator help to use this file instead of the help embeebed into the HDA.
Basically I would be happy if the SESIWiki could be used outside of Houdini, as an stand alone wiki, this will help a lot for studios and 3rd party developers to write docs for Houdini custom tools.