On Wednesday 2017-09-06 13:58, Phil Sutter wrote: > >Regarding reStructuredText, did you look at how tables are written >there? If not, see here[2]. I really think that speaks for itself. Markup is the least problem. Tables, when rendered, have a tendency to quickly grow too large for the display container because there is just so much data to show. Knowing that, people just avoid them most of the time for groff - and if I may say so, it has not reduced the document quality. >> There are many markup languages, it reminds me to xkcd #927 [0]. > >Well, the difference here is that I'm not inventing anything new but >search for better options amongst the existing solutions. :P That would be to stay with docbook then, because RST/MD/A2 do not seem to have left themselves a lot of room for later extension. >> I would prefer if we stick to groff, which seems to be the standard in Linux. > >Yes, this is the very basic alternative but as said I think providing >users with an easier to use markup makes sense. Users read the rendered text, not the markup. All of the glorious old markups are "unreadable" enough to be fed through a program to give a visually-cooked, markup-free rendering (browser, /usr/bin/man, evince, etc.) MediaWiki, RST, MD and asciidoc on the other hand however seem to propagate the use of just cat/less with very short markup, which, to a user, is not too bad to look at, but also not too visually pleasing either, giving the worst of both worlds :-p -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
