On 09/12/2017 10:02 PM, Nicos Angelopoulos wrote:
> i don't care how it is provided. i just would like to have the
> facility. i have the following opening, predicate documentation
> paragraph,
>
> Replace a column in a Mtx. When there is no NewClmName (or when it is
> an unbound variable), then the existing column name is used.
> NewClmName can be atomic or a compound, when the latter it is called
> with =|NewClmName(ClmName,New)|= where_New_ is used as the new
> column name. NewVal could be a list of values, (equal length as
> Cid's?); a _|@(Goal)|_ term where_Goal_ will be maplist applied to
> Cid's elements to produce the new values;_Goal_ which ...
>
> if i view this in a browser which usually has quite wide view, it all
> becomes long lines that don't look very good. i would like to break
> the paragraph with newlines without creating a new paragraph.
>
> say i would like a <br> after "is used.". Seems like a reasonable
> thing to want ?
It is a matter of taste ...
I had a look. We have `official' markdown which does two spaces. That
seems a bad idea. Not only would it require significant changes to
PlDoc's markdown parser as tokenizing and normalization happens very
early in the process. Of course everything is possible, but re-format
and space normalization in program editors tend to remove trailing
spaces. Then we have GFM (Github Flavoured Markdown), which uses a
normal line break. We cannot use that as source code typically already
uses line breaks in comments.
One option would be <br/> (Wikipedia), but that does suggest HTML support
which is not in Markdown and I do not want it there either. Doxygen does
support HTML. Possibly the best is to allow for <br>, but only at the end
of the physical line? I'll give that a try.
--- Jan