Re: documentation format and html output --

[Hans-Bernhard B. <HBB...@t-...>]

Am 19.08.2015 um 01:34 schrieb Karl-Friedrich Ratzsch:
> Am 18.08.2015 um 02:12 schrieb Ethan A Merritt:

> Trying to link to them using
>
> ^ <a href="#positive">positivelink</a>
>
> was not possible, pdflatex complains about runaway arguments and
> unfound references. Hm. I'll look into this.

Well, maybe there's a reason all the existing links are spelled like 
this instead:

^ <a href="#positive">
  positivelink
^ </a>

;-)

> Doesn't, it does not even get boldfaced in a Table. TeX converts the
> backquotes into typographic quotation marks instead. I'll add a note
> to the README.

Note that the note is already there --- only it's just about *roff 
output, so far.  The limitation, and the reason for it, is the same for 
the other "clever" output formats, though: the doc2* tools can't 
generate correct table syntax for the various output formats as-is, much 
less if they're to mark-up parts of the tables' content, too, while 
trying to do that.

> I wanted to add an empty lines before section heading, two for
> levels 2,3, to make navigation in the source a bit easier. Any
> objection to changing that style rule?

Why make such a major change, when every self-respecting programmers' 
text editor can regex-search for, e.g., /^3/ ?

> There is one comment in docs/README, saying
>
> 	Tables must have a space in column 2.
>
> Any idea what this means? It is never done.

Ah, but it is! For _plain_text_ tables, that is.