We have, presently, objects for which documentation cannot be properly parsed (i.e., rendered in proper HTML via docutils), some as a result of #253 (closed). The solution in these cases, is to render a
<pre></pre> formatted version of this documentation. This strategy is current adopted in websites like PyPI. So,
- If documentation can be parsed, render it properly via HTML
- If documentation cannot be parsed, render it in HTML with
This may make the fork work again, if the documentation of forked objects is bogus as reported in the mailing list.