From: Stephen Gregoratto <dev@sgregoratto.me> To: tech@mandoc.bsd.lv Subject: Re: [PATCH docbook2mdoc] Add NODE_EMAIL Date: Sat, 23 Mar 2019 21:18:35 +1100 [thread overview] Message-ID: <20190323101835.bqaltgzmfbnvxcfl@BlackBox> (raw) In-Reply-To: <20190323084616.GA62193@athene.usta.de> On 2019-03-23 09:46, Ingo Schwarze wrote: > I can't say i have ever *used* the DocBook format, but the man(7) > output from DocBook files has struck me over and over again as the > by far lowest quality man(7) code i have ever seen from any manual > page generator. DocBook is without any doubt the number one manual > page generation scheme causing the most trouble in real life, in > multiple respects. By far. So i am definitely not able to approach > DocBook in good faith; i strongly hate DocBook and i am heavily > biased against it based on previous experience. But our different > perspective on it can likely be productive. :) I believe you've mentioned this before on the markdown output article on undeadly.org. Actually that section at the end was the reason why I'm making these comparisons. I forgot to mention that I'll be publishing my findings on my blog. I aim to write up an example user command/library call man-page, porting them by hand to the different formats. I'll describe the methods/programs used to validate/format/convert each format, and analyse the quality of the conversions. I'll also see how it fares going through mandoc's HTML output, groff's PDF output and the UTF-8 output of both. Finally, I'll ask each respective "camp" if they'd like to comment on my findings, and include them at the end (that means you, Ingo). That's why I say good faith, I certainly don't want to anger anyone from a different camp by hating their work right out of the gate. That I can leave that up to you ;). > I'm not sure i understand that sentence. What do you mean with > "I'll put"? Aren't DocBook elements part of input documents, and > aren't input documents things that are given a priori? How can you > influence what is found in input documents? Whoops, forgot to put in the rest of the nodes. What I meant to say was that I'll do this: <refsect1> <title>Authors</title> <para>The <command>foo</command> utility is maintained by <author> ... </author>.<para> </refsect1> -- Stephen Gregoratto PGP: 3FC6 3D0E 2801 C348 1C44 2D34 A80C 0F8E 8BAB EC8B -- To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2019-03-23 10:18 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-22 10:33 Stephen Gregoratto 2019-03-22 12:32 ` Ingo Schwarze 2019-03-22 20:07 ` Ingo Schwarze 2019-03-23 5:30 ` Stephen Gregoratto 2019-03-23 8:46 ` Ingo Schwarze 2019-03-23 10:18 ` Stephen Gregoratto [this message] 2019-04-25 18:33 ` Ingo Schwarze
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190323101835.bqaltgzmfbnvxcfl@BlackBox \ --to=dev@sgregoratto.me \ --cc=tech@mandoc.bsd.lv \ --subject='Re: [PATCH docbook2mdoc] Add NODE_EMAIL' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).